docs: publish Hayate 0.15.2 and create-hayate 0.13.2

[yhay81]

Summary

• publish Hayate 0.15.2 and create-hayate 0.13.2 in the generated family map
• move every actionable create-hayate command and current-release statement to 0.13.2
• link the exact 0.13.2 release workflow and frontend smoke evidence
• retain Hayate 0.15.1 only on the immutable benchmark baseline that actually measured it

Evidence

• Hayate source: 8cb27385cbc2655e531c37bdcdb45b1309c3a392
• create-hayate source: 8bcca24bbd43854c05a6467d26b675c20a89b63e
• create-hayate release: https://github.com/hayatepy/create-hayate/releases/tag/v0.13.2
• release workflow: https://github.com/hayatepy/create-hayate/actions/runs/30502570222
• current frontend smoke: https://github.com/hayatepy/create-hayate/actions/runs/30502309672
• aggregate frontend evidence SHA-256:
  f207dcd979c695508c4bf672432848e5469ebf4ab1b58b0f2c4fecb8e004af05

Validation

• 17 tests passed
• Ruff check and format check
• ecosystem export drift check
• live PyPI release-freshness check
• strict Zensical build
• generated headers and site/internal-link validation
• pip-audit: no known vulnerabilities
• zizmor: no findings (4 suppressed)
• npm audit: 0 vulnerabilities

Closes #14