task: distill Hopper knowledge from KDA KernelWiki with provenance and architecture boundaries #126

Goal and acceptance

• Problem / desired outcome: Systematically distill Hopper-relevant knowledge from KDA's pinned KernelWiki into InferRSI's canonical knowledge/skill library, preserving immutable source provenance and architecture applicability.
• Completion criteria:
  • Record KDA → KernelWiki gitlink provenance, inspected readset, licensing, source cutoff, and explicit exclusions.
  • Deliver English, source-grounded candidate guidance for Hopper kernel reasoning: TMA/barriers, WGMMA and warp specialization, resource/pipeline trade-offs, FP8 GEMM, and applicable scheduling/layout patterns.
  • Separate Hopper-supported mechanisms, cross-generation principles, and Blackwell-only instructions/features; retain upstream contradictions and unverified conditions.
  • Integrate library navigation, affected catalog projections, Reference Matrix and SearchSpace Matrix without changing runtime/CI contracts or promoting candidates.
  • Verify metadata, resource links, catalog/CLI discovery, CPU smoke and noneditable installed-package reads; obtain independent revision-scoped review.
  • Deliver a reviewable PR with truthful knowledge-model-policy declaration and remaining limitations.

Scope and constraints

• In scope: A bounded knowledge-only repository change, owner-local references/cases, provenance/readset and source qualification. Existing skills may be extended where ownership fits; preserve existing stable IDs.
• Out of scope: Kernel implementation, GPU experiments, performance/quality claims, new CI lanes, thresholds, unrelated campaigns, automatic merge or Issue closure.
• Dependencies / limits: KernelWiki is Blackwell-first; an sm90 tag alone is insufficient. Upstream snippets and benchmark reports are source material, not local validation. Do not import artifact trees wholesale. Keep empirical validation not-run and candidates unpromoted.

Ownership and authorization

• Actual requester: Human requester in the current Codex chat.
• Status: Accepted for the scoped implementation by the requester.
• Accountable parent: Codex coordinating this Issue.
• Acting contributor: Delegated implementation and independent review under AGENTS.md and docs/agent-collaboration.md; exact material AI authors/settings recorded in the PR.
• Goal-acceptance / closure owner: Requester or explicitly authorized repository maintainer.
• Accepted decision / scoped delegation: Requester explicitly instructed: “把 KDA 的 KernelWiki 里 Hopper 相关知识系统蒸馏到这个仓库，按仓库规范先开 Issue，保留来源和架构适用边界。” This authorizes research, implementation, checks and a reviewable delivery, not merge or closure.

Inputs and deliverables

• KDA source snapshot: https://github.com/NVlabs/kda/tree/acdd79343c5e9d0c7cb96289f26fd3f1051ce785
• KernelWiki gitlink: https://github.com/mit-han-lab/KernelWiki/tree/76d27b56f804e7e7295d4c570e1e5d7eef4b0a75
• Repository contracts: AGENTS.md, docs/contributing.md, docs/agent-collaboration.md, docs/knowledge-base.md, docs/knowledge-model-policy.md, docs/privacy-security.md.
• Expected artifacts: canonical CUDA-owned knowledge/procedure and references, source manifest/readset, updated navigation/matrices/catalog where affected, check results and independent review linked from PR.
• These SHAs identify research sources, not baseline/candidate campaign pins.

Completion and closure

• Who accepts completion and may close: Requester or explicitly authorized maintainer; use non-closing Refs in PR.
• Remaining uncertainty: Exact Hopper coverage and source contradictions will be established by the pinned readset. No GPU correctness, performance or service gain is claimed.

Delivery for acceptance — 2026-10-23

Implemented in PR #127, ready for review at head 04ca833eff7cf83aede933cfa041807305316dab against base 28ddd06a48128c187f093763c7f52ffdfd04a5f0.

• Entry: reason-hopper-kernels.
• Complete source readset, architecture dispositions, retained contradictions and licensing qualifications are packaged with the skill. Candidate/not_run and locally-unverified boundaries remain explicit.
• Local validation: 707 tests passed, 7 skipped, 70 subtests passed; lint, generator check, builds, noneditable installed-resource and actual CLI reads passed. Initial macOS temporary-directory alias failures and canonical-path rerun are disclosed in the PR.
• Independent read-only review at this head/base reported no actionable findings. Its scope and limits are recorded in the PR.
• Current-main AFD knowledge was preserved while resolving shared registry/generated-card conflicts.

These checkboxes record delivery of the scoped artifacts and local review, not maintainer acceptance, GPU validation or campaign PASS. Repository CI has passed; maintainer review and requester/authorized-maintainer goal acceptance remain pending. This Issue stays open; no merge or closure was authorized.

Final CI evidence for the same head: ready lane succeeded (full checks and installed-package checks on Python 3.10 and 3.11); knowledge-model-policy succeeded. The earlier draft-triggered ready run was cancelled when superseded by the ready-for-review run; it is not counted as a passed run.