docs(audit): add founder control audit

[HitsuyoAkuWeb3]

Business change

Make the existing Exit-Ready worksheet usable as a privacy-first, GitHub-native Founder Control Audit.

Why now

The personal profile now routes visitors to a diagnostic path. The public framework needs a bounded first experience that helps a founder identify one control gap without sending business data into a public issue.

What changed

• Added a Founder Control Audit entry point and private-copy template.
• Reused the existing eight-dimension Exit-Ready Score rather than creating a second score.
• Added a machine-readable audit contract and deterministic validation in the existing evidence gate.
• Updated public audit guidance so completing the worksheet does not require a public issue.
• Added 32 punctuation-only copy-rail repairs required for the existing evidence gate to pass.

Proof

• The audit-contract validator passes.
• The existing copy rail passes with no em dashes in its scan scope.
• Navigation targets exist.
• No Issue Form, GitHub Pages route, analytics event, GitHub App, OAuth connection, or data collection was added.

Risk

This is public review content, not approval to collect founder data or make legal, financial, security, investment, acquisition, or customer-outcome claims.

Decision needed

Red Pillar and Hitsuyo Aku: approve the exact public audit language before merge.

After merge

Run one private dry audit with a willing founder. Retain, revise, or retire the guide based on whether the founder can identify their lowest control gap and one safe next step.

[HitsuyoAkuWeb3]

Owner approval from Hitsuyo Aku: I approve the Founder Control Audit scope and exact public language within this PR. This does not approve merge, data collection, Pages, deployment, or any change outside this PR. Red Pillar code-owner review remains required before merge.