Phase 8A.1: close release truth drift - #55
Merged
Conversation
There was a problem hiding this comment.
🟢 Approval recommended
The changes consistently remove stale hard-coded alpha identifiers and add matching smoke coverage without introducing behavioral risk beyond deterministic documentation checks.
Pull request overview
Closes “release truth drift” by removing hard-coded “current alpha” identifiers from user-facing guidance and adding smoke assertions to keep release/install docs aligned with the repo’s current-release authority model (GitHub Releases feed + published state).
Changes:
- Update
docs/RELEASE.mdto define current public release identity via the GitHub Releases feed (without pinning a specific alpha tag), and add explicit guidance for manual qualification closure plus a classification-only prerelease repair procedure. - Update
docs/INSTALL.mdto direct users to select a qualifying alpha from the official Releases feed instead of a specific versioned alpha. - Extend
scripts/smoke-public-release.jswith deterministic checks that enforce the above documentation contracts and prevent reintroducing hard-coded alpha tags.
File summaries
| File | Description |
|---|---|
| scripts/smoke-public-release.js | Adds smoke assertions to enforce release identity/repair/closure guidance and prevent hard-coded alpha tags in INSTALL/RELEASE docs. |
| docs/RELEASE.md | Removes “current alpha tag” pinning; documents Releases feed authority, manual qualification closure, and a prerelease-classification repair flow. |
| docs/INSTALL.md | Replaces concrete alpha download links with Releases-feed-based install instructions and clarifies current-alpha authority. |
Review details
- Files reviewed: 3/3 changed files
- Comments generated: 0
- Review effort level: Lite
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary\n\n- Remove stale concrete alpha tags from durable release/install guidance.\n- Add deterministic public-release smoke coverage for feed-based current-release authority, classification-only repair guidance, and manual qualification closure.\n- Preserve the existing six-file bundle, build-once publication path, tag/commit checks, digest checks, release-notes checks, and qualification declaration behavior.\n\n## Validation\n\n- npm run smoke:release-notes\n- npm run smoke:published-release\n- npm run smoke:release-identity\n- npm run smoke:release-metadata\n- npm run smoke:public-release\n- npm run smoke:release-workflow\n- npm run lint\n- git diff --check\n\nNo live GitHub Release, tag, asset, issue, version, or product behavior was mutated. Do not merge as part of this task.