[Docs] Update docs for the single nested config layout

[Boss2002n]

No description provided.

[github-actions]

🏷️ CI Guide

Runs automatically on every PR:

• ✅ Pre-checks (submodule verification, code formatting)
• ✅ Aiter op tests (gfx942 + gfx950)
• ✅ Triton tests on MI35X (only when aiter/ops/triton/** or related paths are changed)

Extended tests (opt-in via labels):

Label	Tests
ci:gfx1250-ffm-triton	Run the five-shard gfx1250 FFM Triton test suite
ci:triton-300x	Run an additional Triton test job on MI300X in PRs; main branch always runs both MI35X and MI300X
multigpu	Aiter multi-GPU tests on the 8-GPU runner
ci:sglang	SGLang integration tests: DeepSeek-R1-MXFP4 accuracy, Qwen 3.5 accuracy
ci:atom	ATOM benchmark: DeepSeek-R1-0528, GPT-OSS-120B
ci:atom_full	ATOM accuracy suite for PR and main models from ATOM models_accuracy.json
ci:vllm	vLLM benchmark: GPT-OSS-120B, DeepSeek-R1-0528, Kimi-K2.5
ci:all	All standard extended tests (excludes ci:atom_full)

Only add ci:atom_full for FlyDSL or Triton upgrades.
Add labels via the sidebar or gh pr edit 5085 --add-label <label>

PR title tags:
Component tags ([Triton/Gluon], [HIP], [CK], [ASM], ...) are added to the PR title automatically from the changed files and re-synced on every push — change-type tags like [fix]/[Perf] and op tags like [MLA] are left untouched. Add the no-auto-title label to opt this PR out of title tagging.

[Copilot]

Pull request overview

This PR updates AITER Triton documentation to describe a single nested tuned-config layout (configs/<arch>/<backend>/<op>/<d_type>/) and removes remaining references to the legacy flat config tree.

Changes:

• Updates tuning workflow docs to instruct copying tuned JSON into the nested config tree.
• Revises top-level Triton docs and config rulebook (configs/CLAUDE.md) to describe the nested layout and loader expectations.
• Refreshes conv docs to reference nested config locations.

Reviewed changes

Copilot reviewed 6 out of 6 changed files in this pull request and generated 6 comments.

Show a summary per file

File	Description
aiter/ops/triton/utils/_triton/tunning/README.md	Updates manual tuning “verify performance” copy-path guidance for the nested layout.
aiter/ops/triton/README.md	Rewrites tuned-config documentation to describe the single nested layout and loader behavior.
aiter/ops/triton/conv/README.md	Updates conv tuning documentation to the nested config tree paths.
aiter/ops/triton/conv/DESIGN.md	Updates conv design docs to reference nested config resolution and probing.
aiter/ops/triton/configs/CLAUDE.md	Updates the config “rulebook” to reflect the single nested layout and loader conventions.
.github/instructions/aiter-ops-triton.instructions.md	Updates repository review rules to match the new config layout guidance.

Suppressed comments (5)

aiter/ops/triton/README.md:100

• This description says resolve_config_dir "builds" the path with no probing/candidate list, but the current implementation probes the filesystem for DEFAULT.json and (when backend is None) tries triton then gluon. Either the docs need to match that behavior, or the resolver needs to be updated to match these claims.

It **builds** the path — no probing, no candidate list, no cross-backend or
cross-arch search — and validates every argument against a whitelist, so a bad
value fails closed with an `AssertionError` rather than resolving to an
escaped or wrong directory. `backend` is declared by the caller (gluon kernels
and gluon dispatch paths pass `"gluon"`; everything else takes the `"triton"`

aiter/ops/triton/configs/CLAUDE.md:37

• This table points at config_utils._dtype_dir(), but there is no utils/config_utils.py in the current tree; the helper is utils/gemm_config_utils.py::_dtype_dir().

| `<d_type>`  | `config_name.lower().replace("-", "_")` — `GEMM-AFP4WFP4` → `gemm_afp4wfp4`. The transform is `config_utils._dtype_dir()` |

aiter/ops/triton/configs/CLAUDE.md:73

• This describes resolve_config_dir as a deterministic path builder with no probing/fallback chain, but the current implementation explicitly probes the filesystem and has a triton→gluon fallback when backend is omitted (backend=None).

directory; it never probes, never searches, and has no fallback chain:

{AITER_TRITON_CONFIGS_PATH}/{arch}/{backend}/{op}/{_dtype_dir(config_name)}

aiter/ops/triton/README.md:94

• utils/config_utils.py and the shown resolve_config_dir(...)->str signature do not exist in the current codebase. Today resolve_config_dir lives in utils/gemm_config_utils.py and returns (cfg_dir, name_prefix).

All of it is built by one function in `utils/config_utils.py`:

```python
resolve_config_dir(op, config_name, backend="triton", arch=None) -> str

**aiter/ops/triton/configs/CLAUDE.md:68**
* The `resolve_config_dir` signature/module here doesn't match the current implementation: it lives in `utils/gemm_config_utils.py`, returns `(cfg_dir, name_prefix)`, and probes for `DEFAULT.json` (with `backend=None` trying triton then gluon).

resolve_config_dir(op, config_name, backend="triton", arch=None) -> str

in utils/config_utils.py is the single path builder. It builds the

</details>



---

💡 <a href="/ROCm/aiter/new/main?filename=.github/skills/code-review/SKILL.md" class="Link--inTextBlock" target="_blank" rel="noopener noreferrer">Add a `code-review` agent skill</a> or configure MCP servers for context-aware, tailored reviews. <a href="https://docs.github.com/en/copilot/how-tos/use-copilot-agents/request-a-code-review/use-code-review#mcp-servers-and-agent-skills" class="Link--inTextBlock" target="_blank" rel="noopener noreferrer">Learn more in the docs.</a>

[Copilot]

Pull request overview

Copilot reviewed 6 out of 6 changed files in this pull request and generated 1 comment.

Suppressed comments (1)

aiter/ops/triton/utils/_triton/tunning/README.md:63

• "tunned" is a misspelling, and the sentence is ungrammatical ("files ... is"). Update to "tuned" and adjust agreement so the README reads cleanly.

To verify that your tunned JSON config files actually is performant and can be correctly picked up by AITER, first you have to copy the generated JSON config files into the config tree. Every family lives in one nested layout, `configs/<arch>/<backend>/<op>/<d_type>/` (`<path_to_aiter_root>/aiter/ops/triton/configs/CLAUDE.md` is the authoritative rulebook). Files there carry **no arch prefix** — the arch is the directory — and the default file is named exactly `DEFAULT.json`, so drop the arch prefix when copying:

[brunomazzottiamd]

LGTM!