chore(release): close out open-scaffold@0.33.0 — record publication proof - #229
Merged
Merged
Conversation
…roof Finalize the 0.33.0 release-sync from candidate to published state: evidence note records npm/GitHub Release/trusted-publishing proof, CHANGELOG v0.33.0 Status moves to published with v0.32.1 marked superseded, and MISSION.md appends the 174 closeout entry. Release-truth closeout only; no code/version changes.
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
1 participant
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
Release closeout for
open-scaffold@0.33.0— records the post-merge publication proof in repo truth now that 0.33.0 is published to npm (latest, with provenance) and GitHub Releasev0.33.0is Latest. PR #228 carried the candidate release-sync state; this PR finalizes it.Changes
.osc/releases/2026-06-20-174-evidence-battery-package-sync.md— finalize from candidate to published state: Summary now records0.33.0published; Traceability filled with the release-sync PR (chore(release): sync open-scaffold@0.33.0 — evidence battery package sync #228, merged250e3a), trusted publishing run (27875553205), GitHub Release, and npm URLs; all post-merge/publication gates checked with proof; Outcome recordsv0.33.0Latest supersedingv0.32.1.docs/CHANGELOG.md—v0.33.0Status moved from candidate to published; publish-proof evidence lines (release-sync PR, trusted publishing run, GitHub Release, npm) added;v0.32.1marked superseded.MISSION.md— append the2026-06-20: closed 174-evidence-battery-package-synccloseout entry.Plan
174-evidence-battery-package-syncis left untouched in.osc/plans/done/(plan immutability); its acceptance criteria (release-sync preparation) are met, and publication was the owner-approved follow-through recorded in the evidence note.Verification
npm view open-scaffold version→0.33.0;latest: 0.33.0.npx open-scaffold@latestinstalls0.33.0and--helprenders.27875553205completed/success.v0.33.0is Latest../verify.sh --strict10 pass / 0 fail / 0 warn;npm test -- --run48 files / 563 tests pass;git diff --checkclean; secret-scan PASS; public-safety scan of added diff lines clean.No code, version, or package-surface changes in this PR — it is release-truth closeout only.