Reject stale release prose in compatibility evidence

[yhay81]

Outcome

Keep the human-readable compatibility explanation on the same current release
and immutable evidence snapshot as the generated family map.

The family map now records create-hayate 0.13.1 and canonical compatibility
commit 1496dc8..., while docs/evidence/compatibility.md still names
create-hayate 0.13.0, an older matrix run/hash, an older golden-app run, and
an older canonical snapshot.

Acceptance criteria

• Advance the explanation to create-hayate 0.13.1.
• Link canonical compatibility commit
  1496dc87b780ff81470518df468a18bd6783ebce.
• Pin the current 112/112 matrix run and aggregate SHA-256.
• Pin the current golden-app run.
• Extend the release-freshness gate to reject stale prose references such
  as create-hayate 0.13.0, not only command pins using ==.
• Extend tests for stale and current prose references.
• Deploy and verify the exact reviewed main commit.

[yhay81]

Completed through PR #13 at main commit
bf69d8fc102a6b551678a214fd9ab35f338ef260.

• source evidence was checked against canonical commit
  1496dc87b780ff81470518df468a18bd6783ebce; the current matrix and golden-app
  runs are both successful
• the release-freshness suite now has 17 tests and rejects stale exact
  create-hayate X.Y.Z prose in addition to stale == commands
• main build, live PyPI freshness, external links, dependency audit, and
  workflow audit:
  https://github.com/hayatepy/docs/actions/runs/30499727672
• static site Worker version: df69358d-be61-4fde-b659-78c8d58f7b76
• redirect Worker version: 057867b9-650e-4bbc-9099-d804fa3b22d8
• production now contains create-hayate 0.13.1, the current 112/112 run,
  aggregate SHA-256, golden-app run, and immutable canonical snapshot; explicit
  checks found none of the superseded references
• HSTS and HTTP-to-HTTPS redirect remain intact