V47 Gate 2: Feature Excess And Alignment Audit#234
Conversation
Classify V47 website launch, supporting, compatibility, and deferred surfaces with a package-backed feature-excess audit artifact. Rewrite launch-facing Terminal and Exchange entrypoints into Read and Packs, keep Terminal direct entry feature-flaggable, and tighten BTD wording to scalar volume plus settled rights. Wire Gate 2 generation, package exports, tests, workflow checks, and future-tolerant V46 rehearsal roadmap posture.
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 46ee86103c
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| { mode: 'read-assetpack', target: '/read?intent=submit-read-for-btd', gate: 'V47' }, | ||
| { mode: 'packs-existing-btd', target: '/packs?intent=buy-existing-btd', gate: 'V47' }, |
There was a problem hiding this comment.
Remove gate-version tags from runtime intent
In runtime UI state, these gate: 'V47' fields explicitly version source behavior; the repo instruction in AGENTS.md says source code must stay implicitly versioned to the active canon and must not introduce version/gate source constructs unless explicitly needed for a bounded compatibility artifact. When this sessionStorage payload is consumed later, it can preserve stale V47 semantics after the canon advances instead of using the current Read/Packs acquisition contract.
Useful? React with 👍 / 👎.
Summary
Validation