Summary

Publishes the previously-deferred recipe-health matrix into docs/user/recipe-health.md — all 32 leaf recipes now grade pass.

Motivation / Context

Issue #1229 shipped the tools/health generator, the make recipe-health-docs / recipe-health-check targets, and the doc scaffolding, but withheld the committed matrix body behind an AICR-HEALTH-DEFERRED sentinel. The deferral reason was a chart_pinned false-positive: manifest-only Helm components (declared type: Helm but shipping local manifestFiles with no external chart, e.g. nodewright-customizations) were graded fail, making 17/32 recipes falsely fail. That signal was corrected in #1303 ("exempt manifest-only Helm components from chart_pinned"), so the matrix is now accurate and safe to publish.

Fixes: #1229
Related: #1303

Type of Change

• Documentation update
• Build/CI/tooling

Component(s) Affected

• Docs/examples (docs/, examples/)
• Other: Makefile (recipe-health-check target)

Implementation Notes

• Ran make recipe-health-docs to splice the generated matrix between the BEGIN/END AICR-HEALTH markers, replacing the sentinel and deferred-note prose. Result: 32 recipes, all pass (0 warn/fail/unknown).
• Removed the now-dead sentinel-skip guard from the recipe-health-check target. With the matrix published, the staleness check runs unconditionally — its intended end state.
• No Go source changed; the generator/targets/doc registration (docs/index.yml, component-catalog cross-link, CODEOWNERS) all landed in the original tools/health generator + make targets + public recipe-health matrix #1229 PR.

Testing

make recipe-health-docs   # idempotent: second regen byte-identical
make recipe-health-check  # passes against the committed doc
go test ./tools/health/...  # ok (golden + budget-timing gate)

Risk Assessment

• Low — Doc regen + dead-code removal in an advisory make target; easy to revert.

Rollout notes: N/A — recipe-health-check is advisory and not wired into make qualify or the merge gate.

Checklist

• Tests pass locally (make test with -race)
• Linter passes (make lint)
• I did not skip/disable tests to make CI green
• I added/updated tests for new functionality
• I updated docs if user-facing behavior changed
• Changes follow existing patterns in the codebase
• Commits are cryptographically signed (git commit -S)