chore(main): release 0.4.7

[github-actions]

Release scope and approval boundary

v0.4.7 records repository research and test maintenance. Published runtime source, dependency pins, JSON v1 schema, unlock policy and platform support remain unchanged from v0.4.6. Reported version and version-derived update checks reflect 0.4.7 as expected. The npm artifact changes release/version/changelog metadata; excluded research files are not new shipped runtime functionality.

Repository-only integration includes macOS launcher/description/visibility experiments (#153, #156), Windows recovery contracts and identity/observer research (#154, #155, #158), Linux guard-liveness and attribution-gate experiments (#139, #157), and the shared CLI-output collection test repair (#159). Historical measurements retain their original source revisions; static checks and synthetic fixtures do not prove native Codex interoperability or complete holder visibility.

Linux attribution prototype #137 remains Draft/NO-GO. Research issues #126, #127 and Windows W1–W7 (#146–#152) remain open; their unresolved product/policy gates are not waived by this release. Windows observer modes remain refused and Windows remains unsupported. macOS/Linux x64 and arm64, Node.js ^22.13.0 || ^24.0.0, remain the supported platform/runtime contract.

CI follow-up #161 also remains open. The original candidate's Linux ARM64/Node24 first-inspection classification failure is unexplained; the test-only evidence/count clarification in #162 is not claimed as a root-cause fix. It preserves the assertions, samples, timing and skip conditions and adds no retry or safety relaxation. Historical failed CI is retained separately from any later current-head green runs.

Release Please owns the four expected metadata files: package.json, package-lock.json, CHANGELOG.md, .release-please-manifest.json. No manual version editing, dependency update or operational change is part of preparation.

This PR must remain OPEN for human approval. Opening it publishes nothing; merging it would start the existing gated tag/GitHub release/npm publication pipeline. The current user authorization covers preparation, not that final release-PR merge or publication.

Final preparation verification

• Candidate head: 2e489f9; base main: e734c81. Exactly four Release Please-generated metadata files with matching 0.4.7 version fields; no runtime/dependency changes.
• All 41 current-head candidate checks passed, including required repository CI and research validation. Both current-head Code and Security reviews completed without findings; no unresolved review threads.
• Final main CI 39123405170 passed. Candidate CI 39123435768 passed.
• Local current-candidate npm ci/check/lint/test/smoke:package and diff checks passed: 273 total, 269 passed, four expected skips (three Linux-only plus case-sensitive filesystem). CLI reports 0.4.7. Per-command logs retained privately.
• Normal GitHub run approvals were bound to this generated head. No admin bypass, protection change, empty commit or manual version-file edit.
• Original dead1bd CI failure remains preserved in #161, not called fixed by later green runs. test: retain first owner inspection failure evidence #162 improves first-observation evidence and clarifies filesystem-dependent counts only.
• PR is OPEN/ready with auto-merge disabled. Latest published release remains v0.4.6. The Release preparation run skipped build-release/publish. No tag, release or package publication performed; human approval is required before this release PR is merged.

---

🤖 I have created a release beep boop

0.4.7 (2026-10-18)

Tests

• separate Linux attribution causes and guard-gap models (#157) (acb1edb)

---

This PR was generated with Release Please. See documentation.

[chatgpt-codex-connector]

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review	Status	Commit	Review trigger
📝 Code Review	✅ Completed 2026-10-18T11:37:55.802502Z	2e489f9	Draft marked ready
🔒 Security Review	✅ Completed 2026-10-18T11:38:55.015411Z	2e489f9	Draft marked ready

ℹ️ 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" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

[github-actions]

🤖 Created releases:

• v0.4.7

🌻