[Jammy2211]

Summary

The capability matrix (docs/searches/index.rst) gets a Catalogue column. Each manifest search now links to its card in the autofit_inference benchmark catalogue. A search without a card reads "no catalogue card yet".

• docs/_generate_searches.py fetches catalogue/search_catalogue.json by raw URL at the pinned CATALOGUE_COMMIT = bea1d8746cf009ff414ea0786c92f3e3e0909f70 (autofit_inference main, 2026-10-15). Nothing is vendored except the generated .rst.
• Cards are keyed by search name (tasks.<task>.searches.<Name>). Each cell links the task label to the GitHub blob of the catalogue at the pinned sha, with a #L<line> anchor on that card and its status (measured / deferred / unsupported). All 15 anchors were checked against the file at the pin.
• The pin is recorded twice: in an RST comment at the top of the generated page, and in the column note.
• Offline (no connection), the matrix is skipped with a stderr message that names it, and the other two pages are still written (exit 1) or checked (exit 0). An HTTP error (a bad or unpushed pin) or an unreadable catalogue is always an error. The Docs workflow's generated-search-docs job runs --check --require-catalogue, so CI never skips.
• Pages board: autofit_inference has no GitHub Pages site (gh api .../pages returns 404, and its README names none). The PyAutoInsight board (https://pyautolabs.github.io/PyAutoInsight/) has no per-search anchors. So the cards link to the catalogue JSON at the pinned commit, and the page points readers to the Insight board.
• New test test_autofit/test_generate_searches_catalogue.py uses a fixture catalogue and no network. It covers a present card, an absent card, line anchors (with a decoy searches block), the pin recorded in the page, unreadable JSON, HTTP 404 as an error, the offline --check skip and --require-catalogue.

Test Plan

• python docs/_generate_searches.py --check --require-catalogue reports "3 generated search pages are up to date". docs/api/searches.rst and docs/searches/citations.rst were regenerated with no change.
• pytest test_autofit/test_generate_searches_catalogue.py test_autofit/test_generated_search_docs.py: 8 passed.
• Full pytest test_autofit (first commit): 3817 passed, 1 skipped.
• Sphinx: python -m sphinx -b html docs ... -w warnings.log, the same command as Heart's docs-build workflow. Branch: 30 warnings. Main (7f36e16): 30 warnings. Baseline: 30. The warning sets are identical apart from the build path, and none are in searches/index. After review, only one sentence of prose in the column note changed (no new markup); the Docs CI leg re-checks this.

Validation checklist (--auto run — plan was not pre-approved)

• Effective level: safe (header: safe, cap: docs → safe); Consequence: glance
• Plan: on the issue (docs: link each capability-matrix search row to its autofit_inference catalogue card #1694), written at start, unmodified since
• Gate: tests 8/8 targeted + 3817 passed / 1 skipped full suite · smoke n-a (docs generator + generated .rst only; no library code path changes) · review: one independent Opus round returned FINDINGS (1 medium, 2 low, 1 nit). The medium (HTTP 404 silently skipped under --check), the board-wording low and the nit are fixed in f815746. The low on the unbounded forward key scan is not fixed: the anchors are correct at the pin, the decoy case is tested and a missed anchor degrades to a plain file link · Heart RED under the development-only override below
• Witness: every manifest search gets a card link or "no catalogue card yet" in docs/searches/index.rst at a pinned commit ✔ · Sphinx shows no new warnings (30 = 30 = baseline) ✔ · generated files regenerated in the PR ✔
• Human: plan sound in hindsight?
• Human: diff matches plan (no scope creep)?
• Human: merge, amend, or reject — then log the outcome

Heart RED — development-only override (quoted from #1694)

Heart at the door: Heart: RED — Release RED; monitoring RED · 10/100 · 415 unresolved; [red] release validation FAILED (stage integrate); … Live human in session 6ffb59e9 answered AskUserQuestion "Yes, override for development (Recommended)" on 2026-10-15 for this launch. Permitted: commit, push, PR-open. Merge is a separate human act; this never reaches a release.

Tier: glance — ends at PR-open under the Heart RED override

pending-release: the generated docs ship with the next PyAutoFit release.

Closes #1694

🤖 Generated with Claude Code