chore(wiki): evidence refresh 2026-07-23

[jhinpan]

Evidence refresh

• Run date: 2026-07-23
• Included / deferred / excluded / quarantined:
  0 / 0 / 3 / 1
• Gap proposals: 0
• Machine-authored changes: 0
• Diff budget: 15 files, 507 lines

Changed files

• candidates/eval-gaps.yaml
• candidates/runs/2026-07-23/ATOM.yaml
• candidates/runs/2026-07-23/FlyDSL.yaml
• candidates/runs/2026-07-23/aiter.yaml
• candidates/runs/2026-07-23/amdgpu-guide.yaml
• candidates/runs/2026-07-23/flash-attention.yaml
• candidates/runs/2026-07-23/manifest.yaml
• candidates/runs/2026-07-23/refresh-summary.yaml
• candidates/runs/2026-07-23/rocm-blogs.yaml
• candidates/runs/2026-07-23/rocm-libraries.yaml
• candidates/runs/2026-07-23/sglang.yaml
• candidates/runs/2026-07-23/triton.yaml
• candidates/runs/2026-07-23/vllm.yaml
• candidates/synthesis-proposals.yaml
• data/evolution-state.yaml

Review contract

• This PR is intentionally draft and cannot approve or merge itself.
• Upstream PR/blog text is untrusted data, not agent instructions.
• Hardware or performance confidence cannot be promoted without a linked,
  immutable MI355 evidence bundle.
• Generated indices, provenance checks, retrieval evals, and schema validation
  must pass before human review.

[gemini-code-assist]

Caution

The consumer version of Gemini Code Assist on GitHub has been sunset. All code review activity has officially ceased.

[sourcery-ai]

Reviewer's Guide

Advance evolution state to track new ROCm blog and AMDGPU optimization guide sources and add a new 2026-07-22 evidence refresh run with manifests and per-source stub files, all with zero discovered items.

Entity relationship diagram for evolution state and evidence refresh run

erDiagram
  EvolutionState {
    int schema_version
  }

  Source {
    string source_id
    string commit
    date captured_at
  }

  EvidenceRun {
    date run_date
    string registry_sha256
  }

  SourceRun {
    string source_id
    string source_kind
    string repo
  }

  EvolutionState ||--o{ Source : tracks
  EvidenceRun ||--o{ SourceRun : includes
  Source ||--o{ SourceRun : materialized_as

Loading

File-Level Changes

Change	Details	Files
Advance evolution-state registry to record new documentation sources and capture commit metadata for the 2026-07-22 run.	Replace previously empty sources registry with structured entries for rocm-blogs and amdgpu-optimization-guide. Record commit hashes and captured_at timestamps for both sources to anchor the evidence snapshot to specific upstream revisions.	data/evolution-state.yaml
Add a new 2026-07-22 evidence refresh run with manifests, discovery summary, and per-source candidate stubs, all indicating zero findings.	Introduce a run-level manifest that records run_date, registry hash, and per-source counts/decisions for all tracked ROCm-related sources. Add a refresh-summary file summarizing discovery statistics, machine changes, changed files, and dry-run status for this execution. Create individual per-source YAML stubs (one per repo/blog/guide) describing source metadata, repository location, and empty candidate sets for the 2026-07-22 run.	candidates/runs/2026-07-22/manifest.yaml candidates/runs/2026-07-22/refresh-summary.yaml candidates/runs/2026-07-22/ATOM.yaml candidates/runs/2026-07-22/FlyDSL.yaml candidates/runs/2026-07-22/aiter.yaml candidates/runs/2026-07-22/amdgpu-guide.yaml candidates/runs/2026-07-22/flash-attention.yaml candidates/runs/2026-07-22/rocm-blogs.yaml candidates/runs/2026-07-22/rocm-libraries.yaml candidates/runs/2026-07-22/sglang.yaml candidates/runs/2026-07-22/triton.yaml candidates/runs/2026-07-22/vllm.yaml

---

Tips and commands

Interacting with Sourcery

• Trigger a new review: Comment @sourcery-ai review on the pull request.
• Continue discussions: Reply directly to Sourcery's review comments.
• Generate a GitHub issue from a review comment: Ask Sourcery to create an
  issue from a review comment by replying to it. You can also reply to a
  review comment with @sourcery-ai issue to create an issue from it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time. You can also comment
  @sourcery-ai title on the pull request to (re-)generate the title at any time.
• Generate a pull request summary: Write @sourcery-ai summary anywhere in
  the pull request body to generate a PR summary at any time exactly where you
  want it. You can also comment @sourcery-ai summary on the pull request to
  (re-)generate the summary at any time.
• Generate reviewer's guide: Comment @sourcery-ai guide on the pull
  request to (re-)generate the reviewer's guide at any time.
• Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
  pull request to resolve all Sourcery comments. Useful if you've already
  addressed all the comments and don't want to see them anymore.
• Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
  request to dismiss all existing Sourcery reviews. Especially useful if you
  want to start fresh with a new review - don't forget to comment
  @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

• Enable or disable review features such as the Sourcery-generated pull request
  summary, the reviewer's guide, and others.
• Change the review language.
• Add, remove or edit custom review instructions.
• Adjust other review settings.

Getting Help

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.

[jhinpan]

Scheduled independent double-check

Reviewing PR #6 against the six checks. The source classification (correct exclusions of the NVIDIA/CUDA vllm PRs — GB200/H100, no ROCm marker), the gfx11/gfx12 quarantine of rocm-libraries #9703 (correctly kept out-of-scope, gfx1250 excluded as CDNA), and the absence of any wiki-page promotion (wiki_pages stays 57) are all handled correctly — this does stay a data-plane update, not a knowledge promotion. However, there are blocking defects:

Blocking bugs

1. Unprovenanced corpus addition (provenance + bounded-update failure). sources/prs/rocm-libraries/PR-8934.md is added and data/corpus-manifest.yaml source_prs is bumped 7454→7455 (and unique_page_ids 7542→7543), but no run ledger in this PR records an include decision for PR 8934. The 2026-07-22 runs are all empty (candidates: []), and the 2026-07-23 rocm-libraries run only records PR 9703 (quarantine), plus 3 vllm excludes. PR 8934 is in fact the watermark_before baseline of the 2026-07-22 run — i.e. the bootstrap floor, not a discovered candidate — so it should not appear as a freshly harvested source page here. The manifest math is internally consistent with the one added file, but the addition itself has no discovery/decision provenance.

2. Refresh-budget inaccuracy. Neither refresh-summary.yaml accounts for the corpus mutation. The 2026-07-23 summary's changed_files (15) and changed_lines: 507 omit both sources/prs/rocm-libraries/PR-8934.md (83 lines) and data/corpus-manifest.yaml. The recorded budget therefore under-reports the actual change set, so the "bounded" guarantee cannot be verified from the ledger.

3. 2026-07-22 refresh-summary self-inconsistency. Its changed_files lists only 4 files (manifest, refresh-summary, rocm-libraries, vllm) but the run actually creates 12 run YAMLs (ATOM, FlyDSL, aiter, amdgpu-guide, flash-attention, manifest, refresh-summary, rocm-blogs, rocm-libraries, sglang, triton, vllm). changed_lines: 138 corresponds to ~all 12 files, contradicting the 4-file list; and other sources that received watermarks (rocm-blogs, amdgpu-guide) are missing from the list.

Non-blocking note (not counted against merge): PR-8934 metadata scope_status: quarantine for a gfx950 tooling/benchmark helper, and PR 9703's auto-tagged architectures: [gfx942, gfx950] despite being a gfx11/gfx12 change, are judgment/tagging artifacts that are correctly held in quarantine and do not leak into published pages.

VERDICT: FIX

[jhinpan]

Closing and rebuilding from latest main. Live same-day retries exposed that date-keyed run files could overwrite earlier include provenance (PR-8934) and budget summaries. PR #10 replaces them with collision-resistant immutable run IDs; the automation will now bootstrap a clean rolling Draft PR from the original installation watermark.