Repository navigation
Verify published 0.8.0 and close out release documentation - #16
Merged
Merged
Conversation
Exact source local commit: 00cf48fefe4db6447bcd5a9d5b1fdb93674e0d4b Verified tracked tree: 7f6865b Original local history retained; remote SHA intentionally differs.
Exact source local commit: 03660076325ce7eedc6d85ac5bfff6cc38d7dfd7 Verified tracked tree: e39754e Original local history retained; remote SHA intentionally differs.
focaxisdev
marked this pull request as ready for review
October 18, 2026 05:53
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.
The published 0.8.0 package still contains preparation-era wording. Update current repository README, changelog and release guides to record the independently verified publication, preserve measured limitations, and distinguish later documentation commits from npm gitHead and the unchanged release tag.
Add a read-only Ubuntu/Windows workflow that downloads the actual registry archive, compares the complete 138-file manifest and SHA-1/SHA-512 with the original release CI fingerprint, installs the exact version with a separate empty cache/directory, and exercises CLI init/doctor/explain plus the existing installed API assertions. Registry version/latest/gitHead and public tag/Release correspondence are checked without publishing credentials or elevated permissions.
Independent registry verification passed on both platforms: https://github.com/focaxisdev/deja-vu/actions/runs/39101806633 . Version/latest are 0.8.0; npm gitHead, tag and Release target all remain 4222180. The original complete source/compiled/package/type/quality/cache CI also passed for the first verification commit; both workflows rerun for this final documentation commit before merge.
Local documentation check: 73 public Markdown files passed. No product source, package version, lockfile, AGENTS rules or product assertions changed. No publish, tag move, Release mutation, proxy/security change or private-memory access. The workflow intentionally verifies 0.8.0 as latest at closeout; a future version can legitimately supersede that assertion.
Exact tracked-tree mapping: local 03660076325ce7eedc6d85ac5bfff6cc38d7dfd7 → remote fb2f810; tree e39754ec9088fc3f5e5af4a239a143fbd99145cb. Original local history is retained.