Skip to content

feat(release): prepare sealed Genesis 002 launch for 0.4.0 - #222

Closed
ael-dev3 wants to merge 27 commits into
mainfrom
codex/0.4.0-preparation
Closed

feat(release): prepare sealed Genesis 002 launch for 0.4.0#222
ael-dev3 wants to merge 27 commits into
mainfrom
codex/0.4.0-preparation

Conversation

@ael-dev3

Copy link
Copy Markdown
Owner

Release contract

  • preserve admitted Genesis 001 players on the frozen 0.3.43 realm
  • add the Genesis 001 / Genesis 002 realm chooser with admitted and not-admitted status marks and tooltips
  • keep Genesis 002 sealed with zero admissions and zero player access
  • suspend all admission and access-request paths before activation
  • prepare private applicant census export, frozen G1 publisher, private G2 publisher/import, and guarded activation receipts
  • keep the public Pages release blocked in this preparation phase; the 0.4.0 version bump and Pages activation happen only in the receipt-bound successor

Local verification

  • complete root suite: 5,273 tests passed across bounded serial shards
  • Spacetime pure suite: 598/598 passed
  • clean-tree release shard: 55 files / 512 tests passed
  • private Genesis 002 loopback: 3 consecutive passes
  • closure/policy: 952 exact signed members
  • root and Spacetime typechecks/builds passed
  • production Vite build and public-boundary checks passed
  • two independent final reviews: approved, no blockers

Production remains unchanged until required GitHub checks pass and the guarded operational sequence completes.

ael-dev3 added a commit that referenced this pull request Aug 27, 2026
## Release contract

- preserve admitted Genesis 001 players on the frozen 0.3.43 realm
- add the Genesis 001 / Genesis 002 realm chooser with admitted and
not-admitted status marks and tooltips
- keep Genesis 002 sealed with zero admissions and zero player access
- suspend all admission and access-request paths before activation
- prepare private applicant census export, frozen G1 publisher, private
G2 publisher/import, and guarded activation receipts
- keep the public Pages release blocked in this preparation phase; the
0.4.0 version bump and Pages activation happen only in the receipt-bound
successor

## Local verification

- complete root suite: 5,273 tests passed across bounded serial shards
- Spacetime pure suite: 598/598 passed
- clean-tree release shard: 55 files / 512 tests passed
- private Genesis 002 loopback: 3 consecutive passes
- closure/policy: 952 exact signed members
- root and Spacetime typechecks/builds passed
- production Vite build and public-boundary checks passed
- two independent final reviews: approved, no blockers

Production remains unchanged until required GitHub checks pass and the
guarded operational sequence completes.

Supersedes #222 with an exact-tree-identical, GitHub-verified signed
commit required by protected-main policy.

Co-authored-by: ael-dev3 <ael-dev3@users.noreply.github.com>
@ael-dev3

Copy link
Copy Markdown
Owner Author

Superseded by #223, which preserves the exact tested tree in a GitHub-verified signed commit and merged through protected branch policy.

@ael-dev3 ael-dev3 closed this Aug 27, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant