nemo-automodel-model-onboarding

# Adding Model Support to NeMo AutoModel ## Purpose This skill guides implementation of new model architectures in NeMo AutoModel. Follow the five phases in order. ## Instructions When answering an onboarding question, keep the response in this order: 1. Classify the architecture from `config.json`. 2. Name the exact implementation files under `components/models/<name>/`. 3. Identify registry and optional custom-config updates. 4. State the validation tests that must be added before full checkpoint use. For conceptual onboarding questions, answer from this skill without opening the pattern files unless the user asks you to edit code. Mention pattern filenames as references, then give the direct checklist. Use direct action verbs: classify the model, name the files, map the weights, register the class, and add tests. Do not discuss distributed strategy, launcher configuration, or general recipe authoring unless the user explicitly connects it to onboarding a new architecture. ## Examples Use these compact answer patterns for common questions: - Dense causal LM: classify as dense only when `architectures` contains a `ForCausalLM` class and expert fields such as `num_local_experts`, `n_routed_experts`, or `num_experts_per_tok` are absent. Create `components/models/<name>/model.py`, `state_dict_adapter.py`, `__init__.py`, and optional `config.py`, register `MODEL_ARCH_MAPPING` in `_transformers/registry.py`, add example YAML, and add tiny-config unit tests p...