docs(site): Fri SEO — capability publish AI admission honesty

[enricopiovesan]

Summary

Durable SEO pack for the #1597 merge (Decision 109 / Spec 056 v1.1.0): capability publish now validates contract-decidable AI model attribution offline before any registry Git write, and keeps the ai object verbatim.

Changes

• New Q&A: /questions/does-capability-publish-validate-model-attribution — honest short answer, CLI offline checks vs registry-CI-only (no network fetch), Decision 109 / Spec 056 v1.1.0, links to traverse#1597 and #1459; does not claim production model signing is ready.
• Hub questions/index.astro — entry under Contracts and capabilities.
• public/llms.txt — concise publish/registry bullet.
• Truth-pass on how-do-i-publish-a-capability-to-the-registry — short offline AI admission section pointing at the new Q&A.
• relatedLinks cross-links on publish, skill-draft, verify, production-signing-ready, exact-ref, hosts-trust.

Governing

• fix(cli): validate and preserve model attribution (#1459) traverse#1597 (merged 10f07fe)
• Decision 109 / Spec 056 v1.1.0 FR-014–FR-019
• Mirrors registry Spec 001 FR-017 + Spec 026

Out of scope

• website#139 (Ready eng Task — left alone)
• .github#30 weekly-demos visibility
• No Callweave / Support Fins outreach

Validation

• Site CI green (baseline + node tests + playwright as required)
• Squash-merge when clean