@@ -17,11 +17,10 @@ used the published v0.49.0 archive.
 
 | Order | ID | Scope/status | Dependency |
 | --- | --- | --- | --- |
-| 1 | #122 | Existing: managed-policy-aware setup | #155; one pinned host/native policy fixture set |
-| 2 | #156 | New: local skill/plugin change-review receipt; experiment | #141; one consumer; fixed file/host scope |
-| 3 | #157 | New: pinned external-report ingestion; conditional | #156 or a concrete multi-tool support case |
-| 4 | #140 | Existing: remaining Skills manifest/byte verification | Actual consumer; pinned beta revision |
-| 5 | #158 | New: native artifact activation/drift measurement; conditional | #156 demand; disposable profile/host access |
+| 1 | #156 | New: local skill/plugin change-review receipt; experiment | #141; one consumer; fixed file/host scope |
+| 2 | #157 | New: pinned external-report ingestion; conditional | #156 or a concrete multi-tool support case |
+| 3 | #140 | Existing: remaining Skills manifest/byte verification | Actual consumer; pinned beta revision |
+| 4 | #158 | New: native artifact activation/drift measurement; conditional | #156 demand; disposable profile/host access |
 | Later | #159 | New: offline ACP v1 evidence spike; demand-gated | One real trace consumer; stable interpretation |
 | Later | #95 | Existing: hook confinement GO/NO-GO experiment | Measured cohort and restrictive policy |
 
@@ -65,7 +64,7 @@ writes, recursive whole-home discovery or native policy reimplementation.
 
 ## #122 — Managed-policy-aware setup and wrap plan
 
-**Status:** built by Sol and reviewed/fixed by Astra; merged in PR #324 but not released. The pre-follow-up candidate passed 19 native cases and 87 protocol comparisons. The home-ancestor and empty-current-config follow-up candidate is verified and Astra reviewed: 22 native cases, three packed initialization cases and 87 protocol checks passed. PR/CI, merge and release are pending. See [projection and limits](MANAGED-POLICY-VALIDATION.md). **User/problem:** changing the command to a
+**Status:** bounded Claude Code MVP shipped in [v0.50.1](RELEASE-2026-11-06-v0.50.1.md), after #324/#325 and Astra review/fixes. Actual published archive passed 22 native policy cases, three initialization cases and 87 protocol checks. Whole-host coverage and legacy-wrapper migration limits remain explicit in the [projection record](MANAGED-POLICY-VALIDATION.md). **User/problem:** changing the command to a
 wrapper can change a client's allow/deny decision. **MVP:** read one supported,
 versioned policy source set and compare current/proposed launches before writes.
 Report exact reason and uncertainty; preserve native restrictions.
 
@@ -2,17 +2,16 @@
 
 ## Current checkpoint — 2026-11-06
 
-Current published CLI: **v0.50.0**. The bounded Claude Code scope inventory from
-project backlog #141 shipped; broader host/project coverage remains open.
-**#122 managed-policy-aware setup** merged in PR #324 but remains unreleased.
-The compatibility follow-up candidate is verified and Astra reviewed; PR/CI,
-merge and release are pending. Its [candidate validation](MANAGED-POLICY-VALIDATION.md)
-separates the earlier archive checkpoint from the verified follow-up and records
-the bounded profile and limits.
-See the [active backlog](BACKLOG.md) and
-[v0.50.0 release evidence](RELEASE-2026-11-06-v0.50.0.md) for the actual source,
-companion matrix, archive verification and proof limits. Historical native
-measurements belong to their named versions; this checkpoint is not a new run.
+Current published CLI: **v0.50.1**. The bounded Claude Code managed-policy slice
+from #122 shipped after #324/#325 and Astra review/fixes. Exact published archive,
+protocol/native evidence and companion synchronization state are in the
+[v0.50.1 release record](RELEASE-2026-11-06-v0.50.1.md). The
+[policy profile](MANAGED-POLICY-VALIDATION.md) retains whole-host uncertainty and
+legacy-wrapper migration limits. #156 remains next in the queue; it was not
+started during this release-first closeout. Conditional #157/#159 retain their
+consumer/demand stop rules. Broader #141 host coverage remains open.
+See the [active backlog](BACKLOG.md). Historical native measurements belong to
+their named versions; this checkpoint does not extend them to another archive.
 
 ## Instruction and skill loading
 
 
@@ -1,6 +1,10 @@
-# Claude Code managed-policy preflight — candidate #122
+# Claude Code managed-policy preflight — bounded #122
 
-This candidate adds the `claude-code-2.1.296-stdio-files` projection before
+Available in [v0.50.1](RELEASE-2026-11-06-v0.50.1.md), after #324/#325 and
+Astra review/fixes. Published archive verification is in that release record;
+earlier candidate checkpoints below retain their own identities.
+
+This release adds the `claude-code-2.1.296-stdio-files` projection before
 Claude Code user-global stdio configuration writes. It addresses a measured
 failure in the published 0.50.0 baseline: replacing a denied server command with
 a relay command can bypass native exact-command denial, while replacing an
@@ -171,9 +175,9 @@ These are candidate observations, separate from the vulnerable published 0.50.0
 baseline and any later actual-published artifact verification. No model/provider
 turn, full host-policy coverage or macOS native-client result is claimed.
 
-### Compatibility follow-up — release pending
+### Reviewed compatibility follow-up checkpoint — 2026-11-06
 
-PR #324 merged the reviewed implementation, but no release was published. A later
+At this candidate checkpoint, PR #324 had merged and publication was held. A later
 review found two compatibility regressions: projects below home misclassified
 user settings as an unsupported ancestor, and empty current-config initialization
 was rejected. Both have shared-adapter regressions and narrowly scoped fixes. Node 24.20.0
 
@@ -0,0 +1,130 @@
+# v0.50.1 publication and managed-policy compatibility — 2026-11-06
+
+Dates use Asia/Hong_Kong; raw receipts retain UTC timestamps.
+[Release](https://github.com/getmcpm/cli/releases/tag/v0.50.1) source:
+`b3cc859d083cf684a5bf82cffa6a79ceb3f0ff61`. Annotated tag
+`26144765049c08f901d63e779f427a2fe14667dd` was read back with the same peeled source.
+
+## Reviewed scope
+
+Sol built project backlog #122; Astra independently reproduced and fixed policy
+matching, preview, exact-wrapper and bounded-read issues. [PR #324](https://github.com/getmcpm/cli/pull/324)
+merged the main slice. Late automatic review found home/project-layout and blank
+current-config compatibility regressions; the release tag was held until Astra
+reproduced/fixed them and [PR #325](https://github.com/getmcpm/cli/pull/325) passed
+all ten checks. Its reviewed head `21a921b0987cfabd425afb22ce2503c82c2197f5`
+and merged release source have identical trees. Both PRs shipped in this PATCH.
+
+The bounded `claude-code-2.1.296-stdio-files` projection compares current/proposed
+launchers and recognized underlying commands before user-global stdio writes.
+Denied or unsupported local policy refuses with exit 1; overall host-policy
+coverage stays unknown. Shared gates cover install/update/up/setup/guard/toggles,
+with preview before backups/profiles/secret persistence. Existing wrappers are
+audited; exact authorized teardown can restore native denial. Explicit blank
+current-config initialization preserves original-byte backups; policy/settings
+and scope reads remain strict. See [profile and migration limits](MANAGED-POLICY-VALIDATION.md).
+Public mcpm skill 1.2.2 documents this consumer behavior; npm still ships `dist`
+only, and tracked package version stays the intentional `0.15.0` placeholder.
+
+Node 24.20.0 typecheck/tooling/build and 161 test files passed: **3,793 tests,
+three skipped**. Coverage passed at 91.56% lines, 86.72% branches, 90.28%
+statements and 86.75% functions; the negative-threshold gate passed. Hosted
+Node 22/24/26, security, protocol and macOS confinement checks passed before
+merge. Real local Seatbelt dogfood also passed positive-control access, denied
+synthetic-secret read, intact stdio, tampered-profile refusal and event logging.
+These source/candidate confinement results are separate from published native
+Linux observations below.
+
+## Authenticated publication
+
+All five [publish jobs](https://github.com/getmcpm/cli/actions/runs/42170778579)
+succeeded: three Node clean-install gates, npm/GitHub publication and official
+MCP registry listing. The exact npm version and official registry record were
+read back. Initial npm reads returned 404 while the listing job waited; visibility
+resolved without republishing.
+
+The actual downloaded archive is **737,031 bytes**:
+
+```text
+sha512-2ddRvViZNcJakVzcXNXMn/8qKXAGaN/ZBHedS3xYcNZi1JJCOb3WfUx++gBCpCfLlEV6O3DMs9KG+tkmXpOHfg==
+SHA-256 423866f3c8ce91e494ea66744f86053f868f59b9e2abaae96acc3d4d093e0e63
+```
+
+Existing Sigstore libraries and the vendored trusted root authenticated the SLSA
+archive subject, resolved source commit, workflow SAN
+`https://github.com/getmcpm/cli/.github/workflows/publish.yml@refs/tags/v0.50.1`
+and issuer `https://token.actions.githubusercontent.com`.
+The signed SBOM verified and altered bytes were rejected. This authenticates
+build/artifact identity, not code safety or complete SBOM coverage.
+
+## Actual published archive execution
+
+Clean-install smoke passed under Node 24.20.0 with a disposable HOME: version,
+help, completions, doctor, signature catalog, bundled trust material and the
+public blocking `guard inspect --json` seam.
+
+The same archive passed **87 modern/legacy direct/guarded protocol checks, zero
+failures, two expected unsupported combinations and four exclusions**. Independent
+read-back matched archive SRI, all 66 installed JavaScript files, raw dependency
+lock, tagged harness/public skill and actual container boundaries. The exact
+protocol install-lock SHA-256 is
+`cfe11040ef155097ecf8f3b2de9aea2f66233e3e5fd9bc8947e0465439a2fd93`.
+
+**22 native policy cases and three explicit-initialization CLI cases passed** on
+Linux arm64 / Node 26.11.1 / Claude Code 2.1.296. Native cases cover seven enable
+states, three legacy teardowns, two previews, five independently reproduced
+matching gaps, two existing-wrapper audits and three realistic home/repo layouts.
+The three initialization cases cover empty/whitespace current config with exact
+backup preservation and strict empty-policy refusal. They do not claim native
+activation. A separate pinned-native probe observed blank JSON corruption recovery,
+not clean native acceptance; mcpm's explicit initialization is a separate contract.
+
+Native connection claims include synthetic peer `initialize`/`tools/list` traffic.
+Product configuration operations neither executed that peer nor exposed its
+synthetic secret. Containers were offline, read-only, UID 1000, capability-free,
+no-new-privileges and without host binds/credentials. Independent image read-back
+matched the archive, every installed JS file and actual harness/peer/loader bytes;
+case inputs and container identity were retained. Published validation containers and their temporary volumes were
+removed after receipts were copied; the independent read-back is retained in
+`/private/tmp/mcpm-release-0501-20261106/cleanup-proof.json`.
+
+A first published protocol attempt omitted the pinned fixture copy and failed
+before starting a container; it is excluded. The corrected fresh evidence root
+passed. Earlier source-coverage timeout and native-harness precondition failures
+remain excluded under their original candidate identities.
+
+Temporary maintainer receipts: `/private/tmp/mcpm-release-0501-20261106`,
+`/private/tmp/mcpm-policy-122-published-0501-native-20261106/verified-final.json`,
+`/private/tmp/mcpm-policy-122-published-0501-protocol-v2-20261106/verified-binding.json`.
+Reproduce protocol checks using the [documented harness](PROTOCOL-VALIDATION.md)
+and integrity-verified exact npm archive. Historical candidate archives retain
+their own attribution in the [policy validation record](MANAGED-POLICY-VALIDATION.md).
+
+## Companion completion matrix
+
+| Repository | Target/source | Validation | Merge/publication/deployment |
+| --- | --- | --- | --- |
+| cli | v0.50.1 / `b3cc859d083cf684a5bf82cffa6a79ceb3f0ff61` | Authenticated archive/SBOM, smoke, 87 protocol, 22 native + 3 initialization cases passed | #324/#325 merged; npm/GitHub/official registry published |
+| guard-playground | Exact CLI 0.50.1, engine source `b3cc859`, corpus pin `329e4e14` | Sol build/sync/check, 63 tests and Chromium action/signature/UI parity passed; generated engine/corpus bytes unchanged | Astra review clear; [#32](https://github.com/getmcpm/guard-playground/pull/32) merged as `0ab8f55a6e79ba053f58f29925cffeab00b3584d`; [Pages 42172527092](https://github.com/getmcpm/guard-playground/actions/runs/42172527092) succeeded; all seven public assets read back byte-identical |
+| mcp-guardbench | Exact published 0.50.1, corpus `ba18d3deb4e4836920735a6fd97ca96ad836679e` | Fresh 57/57 score: recall 86.5%, FP 0%, precision 100%, exact 87.7%; zero errors/anomalies/unsupported; second clean install reproduced every verdict | Astra review clear; [#21](https://github.com/getmcpm/mcp-guardbench/pull/21) merged as `5315197b01379b1a2c5050cf1848f64c81c2b499` after scoring CI passed |
+
+Both companion PRs passed CI before merge. The
+[public playground](https://getmcpm.github.io/guard-playground/) serves version
+0.50.1 metadata/source `b3cc859` and engine SHA-256
+`376e77f182351c0826f12163ba334f31914de13ba923fc8c572e1efe1072ba3a`.
+Metadata, engine, corpus and all four UI assets match the tested commit exactly;
+public receipt `/private/tmp/mcpm-playground-0501-public-20261106/verified-public.json`.
+Benchmark [versioned results](https://github.com/getmcpm/mcp-guardbench/tree/main/results/mcpm-0.50.1-2026-11-06)
+retain the exact npm integrity/archive, installed-file manifest, input/adapter/
+runner/Node hashes and reproducible install lock. Corpus and historical scores
+were preserved. Companion synchronization is complete. Detector parity/benchmarking does not establish
+relay, native activation or OS enforcement. No fresh macOS/Windows native editor
+or real provider/model suite was run for this archive. Overall policy, session,
+remote/MDM/registry/other-project selection remain unknown, and snapshots are not
+a concurrent policy-tree transaction. Upgrading does not repair existing wrappers
+or stop already-running servers.
+
+The bounded Claude Code #122 MVP shipped; broader #141 host coverage remains
+open. #156 remains next in the queue; it was not started during this release-first
+closeout. Conditional #157/#159 retain the research backlog's consumer/demand
+stop rules.