Generate organization profile from current evidence

[yhay81]

What changed

• generate profile/README.md from an editable template plus immutable Hayate
  benchmark and capability evidence;
• publish the current Hayate 0.15.1 / FastAPI 0.140.0 / Django 6.0.7 /
  Hono 4.12.32 values and computed ratios;
• reuse the four source-backed capability profile summaries instead of
  maintaining a second hand-written verdict;
• fail closed on schema, framework-set, result-commit, evidence-date,
  universal-winner, or profile-position drift;
• add five unit regressions and require the generated profile in Documentation
  CI.

Why

The organization landing page was the only public compatibility surface
outside a drift gate. It still showed Hayate 0.12.1 and obsolete competitor
measurements while the canonical evidence had advanced to 0.15.1. This made a
green documentation build compatible with a stale first impression.

Impact

The organization profile now reports current evidence and preserves the
explicit scope: Hayate is advantaged for portable Python agent APIs, FastAPI
remains competitive for conventional typed Python APIs, Django remains
advantaged for traditional model-driven full stack, and Hono remains
advantaged for JavaScript/TypeScript edge applications. No package or runtime
API changes.

Validation

• 5 unit tests
• profile and compatibility exporters in --check mode
• immutable golden and competitive evidence checks
• Markdown link check
• Ruff check and format check
• zizmor: no findings (2 existing suppressions)
• canonical released create-hayate production quickstart: 16 tests, Ruff, and
  6 checked SQL queries
• git diff --check

Closes #24.