Legal: add the Hegemony Social Contract to Alpha entry

[ael-dev3]

Stack and release coordinates

• Draft, stacked PR: base agent/alpha-0.3.7-lush-forest-biomes / Alpha 0.3.9: Canonical Genesis forest layout #52 at ac8ec75329e567480dfb5634caa5525cbf0f0cbf.
• Alpha 0.3.9: Canonical Genesis forest layout #52 remains dependent on Alpha 0.3.9: Gold Mine wagon expeditions #51 at 47344f4b3332e4b5ab09ca24a2a5e182475e3869. This PR must not merge before that stack is reconciled with protected main.
• Refreshed protected main: 3ca99d2d263453fbb112a7a21fa1bfde294e186b (public Alpha 0.3.8).
• This PR head: 26e39af1ccb09d7127ed43602ee25347676b8a70.

What this adds

• A script-free canonical Hegemony Social Contract with strict CSP, local legal CSS, canonical metadata, and three-way legal navigation.
• One quiet entry gate: Alpha Terms → Hegemony Social Contract → Privacy Notice, with the single unchecked acceptance statement:

  I have read and agree to the Alpha Terms and Hegemony Social Contract.

• A versioned entry-agreement authority that preserves the existing accept_alpha_terms_v1 wire and private immutable acceptance row. The exact current bundle gates entry and gameplay; explicit retained historical evidence can preserve an already-public Marks projection only.
• Current release truth and QA/operations documentation for the 0.3.10 draft candidate.

Exact policy binding

Item	Value
Alpha Terms visible document version	0.3.3
Alpha Terms visible-main SHA-256	0c2fab74ee3eaf0f453503decb9eaafb65bb7ae226f99742b65797e89e3ab864
Social Contract version	2026-07-18-hegemony-social-contract-v1
Social Contract visible-main SHA-256	c6cd22628622aceaba25dd4f9cc5f609873f86a0e7d458c0e4bdf54c9b012571
Current entry-agreement / retained Terms identifier	2026-07-18-hegemony-entry-agreement-v1

The browser derives the bundle identifier from the Social Contract identifier; browser/server equality is tested so a Contract version change requires a matching authority change and fresh acknowledgement.

Privacy and scope

• Acceptance evidence remains private and limited to verified FID, exact bundle version, and acceptance time. No checkbox telemetry, proof, token, cookie, wallet, IP, faction, chat, or moderation data is added.
• No schema migration, protocol bump (still 3), generated binding change, reducer-wire change, faction table/selector, chat, moderation system, AI actor, combat, premium power, payment, token spending, or Marks policy change.
• Alpha remains Hegemony-only and allowlist/admission gated. Ousters and Core are provisional future-setting names only; neither is playable or in active development.

Validation

• Root: 154 files / 1,541 tests passed; TypeScript passed.
• SpacetimeDB: typecheck, 146 pure tests, CLI 2.6.1 build, and generated-binding verification passed.
• Disposable loopback additive-migration proof passed (including old-ID rejection, exact-current gate, retained Marks-projection boundary, and no destructive publish path).
• Ordinary, GitHub Pages subpath, and canonical-root production builds passed; production-output exclusions, runtime assets, and file-size policy passed.
• Auth bridge: 173 standard + 4 workerd tests passed; dry-run packaging passed; high-severity audit found no known vulnerabilities.
• Root audit found 0 vulnerabilities; 302 registry signatures and 108 attestations verified.
• Rendered gate and Social Contract checks covered 320×568, 360×800, 390×844, 667×375, tablet, and desktop with no console errors or horizontal overflow.

Remaining review / residual risks

• Formal legal, privacy, and naming/originality review remain required. No clearance is claimed; Ousters/Core remain provisional.
• Future faction rules, conversion, and neutralisation may change and are not activated here.
• Current Hegemony-admission revocation removes current game access because no alternate faction is playable.
• The Covenant does not activate premium power, chat, combat, AI actors, or moderation tooling; literary atmosphere must never obscure enforceable rules.
• Hosted required checks, including CodeQL, are pending this draft PR. No production verifier requiring credentials was run.

Explicitly not done

No module publish, Pages deployment, tag/release, production-data mutation, or action on PRs #51/#52 was performed.

[ael-dev3]

Superseded by the audited Alpha 0.3.11 integration in #64, now merged to protected main. Accepted work was reconciled, corrected where needed, and validated there; this original branch is intentionally not merged again.