Synchronize hayatepy.dev with Hayate 0.15.2 and create-hayate 0.13.2

[yhay81]

Problem

hayatepy.dev still presents Hayate 0.15.1 and pins
create-hayate==0.13.1 after the verified 0.15.2 and 0.13.2 releases.
This leaves the canonical first-app path one patch behind and prevents users
from receiving the new canonical discovery links in generated projects.

Acceptance criteria

• update the ecosystem manifest to Hayate 0.15.2 at 8cb27385...
• update the ecosystem manifest to create-hayate 0.13.2 at 8bcca24...
• regenerate the family map
• update every actionable create-hayate command and current-release prose
• retain the immutable Hayate 0.15.1 benchmark baseline as historical evidence
• pass release-freshness, site build, headers, link, dependency, and workflow checks
• merge through a reviewed PR and verify the Cloudflare production deployment

Release inputs:

• https://github.com/hayatepy/hayate/releases/tag/v0.15.2
• https://github.com/hayatepy/create-hayate/releases/tag/v0.13.2

[yhay81]

Completed and verified.

• PR: docs: publish Hayate 0.15.2 and create-hayate 0.13.2 #15
• main commit: f77018a924b4c21039e41175a4ec32b048ce0e1d
• main Documentation workflow:
  https://github.com/hayatepy/docs/actions/runs/30503227545
• production: https://hayatepy.dev/

The main workflow passed tests, release freshness, strict site build, generated
headers, internal and external links, dependency audit, and workflow audit.
The repository Cloudflare token is not configured, so the workflow accurately
reported its deploy steps as skipped. Wrangler OAuth was already authenticated
for the owning account, and the exact main commit was therefore deployed
directly:

• site Worker version: bb23c3ae-b943-4b47-8d4a-9f1d5e00ccf5
• HTTP redirect Worker version: 188f8f0c-b017-4015-b2f6-56f5e4e40049

External verification confirmed 0.15.2 / 0.13.2, immutable source links,
current release/workflow evidence, and no 0.13.1 actionable pin on the home,
first-app, or Workers.dev fallback pages. HTTPS returns the one-year HSTS, CSP,
referrer, and content-type headers; HTTP returns a 301 to the same HTTPS path.