docs: remove stale first-run release gates#486
Conversation
Signed-off-by: Jeremi Joslin <[email protected]>
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 5fb5738cb4
ℹ️ 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".
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 51a0f6cfd9
ℹ️ 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".
Signed-off-by: Jeremi Joslin <[email protected]>
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 19662b860b
ℹ️ 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".
1 participant
What changed
Historical changelog entries and normative specification issue tracking remain unchanged.
Why
Temporary release-management prose was carried forward by release version bumps after the old hosted Registry Lab was retired and the linked issues changed scope or closed. That made current tutorials expose internal gating state and, in one case, route readers to the wrong quickstart.
Impact
Current pages now describe supported reader journeys and capability boundaries directly, without requiring readers to interpret mutable issue state or obsolete release workarounds.
Validation
npm ci(0 vulnerabilities)npm test(117 passed)npm run check:contentnpm run check:markdown(0 errors)npm run check:style(0 errors; 2 pre-existing generated-doc warnings)npm run check:tutorial:dry-runnpm run buildnpm run check(latest site, all 15 archived docsets, SEO, and 597,130 internal links/assets passed)git diff --check