[p4gs]

Summary

The Projects catalogue omits the GRC Engineering Cheat Sheet even though the site already cites it. Add one compact reference entry and a direct canonical link so readers can find its definition, comparison, glossary, tools, and teachings.

The change is exactly six added lines in docs/projects.md. It preserves the homepage citation and layout, the Teachings navigation, and PR #44's removal of the redundant homepage button. It adds no runtime code, dependencies, tracking, or data collection. The entry does not advertise the withdrawn Practice section or synthetic example.

Validation

• Source review and git diff --check passed. All 13 actual PR checks completed successfully on signed head c709186efc72522e3c2d63a68921e1a774c001d9.
• The unchanged main baseline built successfully with the repository's CI-pinned MkDocs toolchain (exit 0). Existing optional and network asset warnings remain; this was not a clean strict build.
• The prior edited head was intentionally stopped at the existing git-committers plugin's unbounded GitHub contributor request. Its supported cache requires a fetch date strictly later than the local commit date, so today's honest cache cannot serve today's Projects commit. No future cache date, altered SCM date, plugin/config change, or substitute SCM context was used.
• The prior edited build did not generate projects/index.html, and this documentation correction has not received a completed build or browser pass. Keep this PR in draft until exact-head build and browser verification pass; human review and merge remain pending.

AI Provenance Declaration

• AI generated or assisted with code in this PR
• AI generated or assisted with tests in this PR
• AI introduced or suggested new dependencies in this PR
• AI generated or assisted with documentation in this PR

AI tool(s)/model(s) used (if any): Codex (GPT-6).

Human review performed on AI-generated parts (what/how): Pending. Agent source review is complete; human review is required before merging.

Dependency Changes

• No new dependencies
• New dependencies validated (sscsb deps check) and approved

Merge Policy Reminder

Merge through the repository's required checks and approved human review/signing process after the pending exact-head build and browser checks are complete.