docs(release): record archctx 0.4.2 registry readback - #104
Conversation
![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: e5376b6bae
ℹ️ 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".
| - [x] Focused architecture-domain tests prove runtime traces are ignored and `.claude/settings.json` remains digest-significant. | ||
| - [x] A real repo-harness projection apply completes while `.claude/.session-id` and `.claude/.trace.jsonl` are active. | ||
| - [x] Pull request is merged to `main`; Claude review is waived by the user's explicit instruction. | ||
| - [x] Publish `archctx-contracts@0.4.2` and read back version, integrity, and shasum. |
There was a problem hiding this comment.
A repo-wide search for archctx-contracts@0.4.2 finds only this checklist, while the dedicated docs/verification/archcontext-contracts-npm-scope-readback.md still records 0.3.0; consequently, the claimed 0.4.2 registry version, integrity, and shasum are not preserved anywhere in the repository. This leaves the downstream adoption gate without auditable evidence that it is consuming the published artifact that was checked, so record the publish helper's registry readback (or refresh the dedicated evidence document) before marking this item complete.
AGENTS.md reference: AGENTS.md:L15-L15
Useful? React with 👍 / 👎.
1 participant
Summary
Verification
Boundary
This is npm-only release evidence. It does not promote ledger authority or complete the separate repo-harness dependency adoption gate.