Finish the organization-wide migration to hayatepy.dev and create-hayate 0.13.2

[yhay81]

Problem

The canonical generator and hayatepy.dev now use Hayate 0.15.2 and
create-hayate 0.13.2, but several public default branches still route users
through the superseded .github/blob/main/docs/ tree. golden-app and one
family quickstart also retain actionable create-hayate==0.13.1 pins.

This is a public-discovery and PyPI long-description consistency gap, not a
runtime compatibility failure.

Audited default-branch scope

• organization profile and llms.txt
• create-hayate frontend compatibility documentation
• golden-app
• hayate-admin
• hayate-auth
• hayate-fetch
• hayate-htmx
• hayate-mcp
• hayate-openapi
• hayate-sql
• design-partner links in .github and docs

Acceptance criteria

• route public Start here links to https://hayatepy.dev/
• route compatibility links to https://hayatepy.dev/evidence/compatibility/
• route production/first-app links to their canonical hayatepy.dev pages
• update actionable generator pins to create-hayate==0.13.2
• synchronize golden-app with the released generator and rerun its complete gate
• preserve immutable historical evidence links when they intentionally identify a source snapshot
• add a default-branch regression audit so the superseded prefix and stale actionable pins cannot return
• publish patch releases where README changes must reach PyPI long descriptions
• verify every changed main branch, release artifact, and public page

Already completed

• create-hayate 0.13.2 prevents stale links in every newly generated project:
  https://github.com/hayatepy/create-hayate/releases/tag/v0.13.2
• hayatepy.dev is live on Hayate 0.15.2 / create-hayate 0.13.2:
  docs: publish Hayate 0.15.2 and create-hayate 0.13.2 docs#15

Owner-external design-partner and independent-security-review gates remain
separate; this owned-channel cleanup does not count toward either.

[yhay81]

Progress update (2026-07-30):

• Released hayate-mcp 0.12.1 from signed tag v0.12.1; PyPI Trusted Publishing, immutable GitHub Release, SHA-256 parity, SLSA provenance, and SPDX SBOM attestations were verified. Release run: https://github.com/hayatepy/hayate-mcp/actions/runs/30504320516
• Locked hayate-mcp 0.12.1 in the production golden app and passed direct/ASGI/browser/real Workerd class+global/dependency gates on main: https://github.com/hayatepy/golden-app/actions/runs/30504943669
• Updated the organization profile, llms.txt, canonical start command (create-hayate 0.13.2), design-partner intake, and generated compatibility evidence in docs: publish current release evidence and canonical links #37. Main: 039e629e1b4dfa3ec767cfd209e32f6028dd8f56; CI: https://github.com/hayatepy/.github/actions/runs/30505184220
• Updated and deployed hayatepy.dev from docs main 7bf08cfe4a8d08f080da5777642a0c40241e321f. The live compatibility and ecosystem pages now expose Hayate 0.15.2, create-hayate 0.13.2, and hayate-mcp 0.12.1 with immutable source/run links.

Remaining in this issue: migrate the individual package README/template links (including generated create-hayate README text), add an organization-wide drift gate, and patch-release published packages whose distribution metadata changes.