diff --git a/.hive/memory/decisions.jsonl b/.hive/memory/decisions.jsonl
index 41ab779b..e4b37577 100644
--- a/.hive/memory/decisions.jsonl
+++ b/.hive/memory/decisions.jsonl
@@ -54,3 +54,5 @@ DECISIONS_CONTENT_PLACEHOLDER
 {"ts":"2026-06-04T10:30:00Z","agent":"orchestrator","action":"pm-dispatch","decision":"v41: PRs #531+#532 merged; npm E404 root-cause diagnosed (scope @aimasteracc not registered on npmjs.com); fix 66f91cb pushed to release/v0.2.0 (publish_one graceful E404); PR #533 opened for develop; PR #528 closed as superseded. v0.2.0 ceremony unblocked pending CI re-run.","ref":"PR#523,PR#531,PR#532,PR#533,Issue#525,Issue#526","artifacts":{"merged":["#531 b69695313c","#532 dff97c49bd"],"pushed":"release/v0.2.0 66f91cb","opened":["#533 fix/release-npm-graceful-comprehensive"],"closed":["#528"]}}
 {"ts":"2026-06-04T11:10:00Z","agent":"orchestrator","action":"pm-dispatch","decision":"PM dispatch v42 (2026-06-04): (1) Pre-flight complete; develop HEAD fdd35258 (PM v41+#533 squash). (2) Assessed: 1 open PR #533 (20/20 CI ✅, Codex P1 open); 2 open issues #526 (already fixed by #531) and #525 (P2 signal exit code); release/v0.2.0 CI in_progress run 26947365908. (3) Addressed Codex P1 on #533: created Issue #534 (spin-off tracking for E404 tightening post-npm-scope-registration), replied to Codex with 1-para justification + issue link. Merged PR #533 (squash fdd35258). (4) Closed Issue #526 (mutation kill-rate fix already on develop via PR #531). (5) Fixed Issue #525 (TDD): extracted signalToExitCode(signal)=128+(SIGNAL_NUMS[signal]??0), wired into main(), exported, 9/9 node:test GREEN; CHANGELOG updated; committed 9a92900 to fix/npm-signal-exit-code-issue-525; pushed; opened PR #535. (6) Updated PM state v42 + decisions.jsonl (this entry).","rationale":"Highest-value items: Codex P1 on #533 had to be addressed before merging (Hard Rule); spin-off was correct because the concern is valid long-term but wrong to block v0.2.0 on. Issue #526 close was a bookkeeping gap. Issue #525 was the only P2 tractable in the remaining time window — 3-line code change, clean TDD, no RFC needed (npm-only, non-core).","ref":"PR#533,PR#535,Issue#525,Issue#526,Issue#534,RFC-0110,Charter§5.12","artifacts":{"merged":["#533 fdd35258"],"closed_issues":["#526"],"created_issues":["#534"],"opened_prs":["#535 (fix/npm-signal-exit-code-issue-525 — closes #525)"],"codex_addressed":"PR#533 P1 spin-off→Issue#534 + rejection justification","next_actions":["founder: monitor Release CI run 26947365908; once SUCCESS/SKIPPED → merge PR #523 → push tag v0.2.0 → GitHub Release","founder: admin-merge PR #535 once CI green","founder: register @aimasteracc npm scope on npmjs.com"]}}
 {"ts":"2026-06-04T05:26:18Z","agent":"orchestrator","action":"release-prep","decision":"Prepared release v0.2.0 (founder-authorized 'リリースしましょう' → version 0.2.0, prepare+push): bumped workspace 0.1.19→0.2.0 (Cargo.toml + 4 inter-crate pins + Cargo.lock), sealed+consolidated CHANGELOG [Unreleased]→[0.2.0], README badge/status/roadmap + npm now-available, added check-npm-token preflight to release.yml (gates publish-crates so missing NPM_TOKEN aborts before any irreversible publish — no partial release). Branch release/v0.2.0 (with v per convention; extract yields 0.2.0). Pushing triggers registry publish (crates.io + npm); finalize (main merge/tag/GH release/back-merge) is workflow_dispatch-only per Charter §5.12 = separate founder step.","rationale":"First release with the new RFC-0110 release automation (build-cli-binaries + publish-npm). 0.2.0 chosen (breaking CLI JSON shape + npm channel; matches roadmap 'npm 🔜 v0.2'). check-npm-token added because NPM_TOKEN is env-scoped and was only checked after crates published — partial-release risk.","ref":"RFC-0110,RFC-0102,RFC-0109,Charter§5.12"}
+{"ts":"2026-06-04T14:10:00Z","agent":"orchestrator","action":"pm-dispatch","decision":"PM dispatch v45 (2026-06-04): (1) Pre-flight complete: CHARTER §2/§5.1/§5.10/§5.12/§5.13, _orchestrator, decisions tail-20, anti-patterns, PM state v42 (from develop at 4e60400f), v0.2 PRD. (2) GitHub: 3 open PRs — #537 (back-merge CI 20/20 ✅, Codex P2 fixed 7a5987a), #539 (PM v44, CI 22/22 ✅), #540 (back-merge duplicate, CI 20/20, Codex P2 LIVE). 1 open issue: #534 (P2 npm scope). (3) TWO duplicate back-merge PRs (#537 and #540). #537 had Codex addressed; #540 had live Codex P2 (same README npm issue). (4) Replied to Codex P2 on #540 (valid; closing superseded by #537). Closed PR #540. (5) Squash-merged PR #537 (commit 4e60400f) — Charter §5.12 Step 4 COMPLETE. (6) PR #539 (PM v44) conflicted after #537 landed; closed superseded by v45. (7) PM state v45 written + decisions.jsonl appended.","rationale":"PR #537 was fully clean (CI 20/20 ✅, Codex P2 addressed in 7a5987a). PR #540 had a live Codex P2 and duplicate content — cleanest path: address Codex+close #540, merge #537. PR #539 conflict was expected after back-merge; closing is correct; v45 carries forward the v44 information.","ref":"PR#537,PR#539,PR#540,Charter§5.12","artifacts":{"pr_merged":"537 (squash 4e60400f — Charter §5.12 Step 4)","prs_closed":["539 (PM v44 conflict)","540 (superseded by #537)"],"codex_addressed":"#540 P2 replied+closed","ceremony_status":"Step 1 ✅ Step 4 ✅ Steps 2+3 founder-gated","next_actions":["founder: push tag v0.2.0 + create GitHub Release (Steps 2+3)","founder: register @aimasteracc npm scope (Issue #534)"]}}
+{"ts":"2026-06-04T15:00:00Z","agent":"orchestrator","action":"pm-dispatch","decision":"PM dispatch v46 (2026-06-04): (1) Pre-flight complete: CHARTER, _orchestrator, decisions tail-20, anti-patterns, PM state v45 (PR #541 open), v0.2 PRD. (2) GitHub: 1 open PR — #541 (chore pm-dispatch-v45, CI 22/22 ✅, 2 Codex findings). 0 open issues. (3) Addressed Codex P2 (Hard Rule): fixed decisions.jsonl line 1 rewrite — reverted MCP resource-prefix artifact; memory is append-only (Charter). (4) Addressed Codex P1: corrected v0.2.0 ceremony tracking — Charter §5.12 Step 3 = crates.io publish (already done ✅), not GitHub Release; Step 2 (tag push) is the sole remaining founder action. Updated header, ceremony table, and P0 list across pm-state.md. (5) Committed fixes + pushed to chore/pm-dispatch-v45; CI re-run. (6) Replied to both Codex threads on PR #541.","rationale":"Both Codex findings were substantive: P2 was a Hard Rule violation (append-only memory); P1 was a ceremony-tracking error that would route founder attention to the wrong blocker (GitHub Release instead of crates.io, which was already done). The correction clarifies that v0.2.0 ceremony is 3/4 complete — only the tag push remains.","ref":"PR#541,Charter§5.12,Charter§5.3","artifacts":{"fixed_p2":"decisions.jsonl line 1 reverted (MCP resource-prefix artifact removed)","fixed_p1":"pm-state ceremony Step 3 = crates.io (done), Step 2 = tag (pending), GitHub Release noted separately","escalations":["founder: push tag v0.2.0 + publish GitHub Release (Step 2 of ceremony)","founder: register @aimasteracc npm scope (Issue #534)"]}}
diff --git a/docs/sprints/2026-Q2-pm-state.md b/docs/sprints/2026-Q2-pm-state.md
index ffbc09cc..98db4772 100644
--- a/docs/sprints/2026-Q2-pm-state.md
+++ b/docs/sprints/2026-Q2-pm-state.md
@@ -5,12 +5,12 @@ This file is the **live state** of the PM brain. Update on every cadence checkpo
 | Field | Value |
 |---|---|
 | PM | orchestrator (Hive AI agent) |
-| Last updated | 2026-06-04 (PM dispatch v42 — PR #533 merged; Issue #526 closed; Issue #534 created; PR #535 opened (Issue #525 signal exit code fix)) |
-| Current sprint | **v0.2.0 — "The Three-Surface Release" CEREMONY RE-UNBLOCKED** — Release workflow in_progress on release/v0.2.0 (run 26947365908). PR #523 awaiting CI + founder merge. |
-| Active release branch | `release/v0.2.0` — PR #523 open → main, CI in_progress (run 26947365908 with npm E404 graceful fix) |
-| Next release target | **v0.2.0** — RFC-0109 7/7 + RFC-0102 budget + RFC-0110 npm/bun. Version 0.1.19→0.2.0. |
-| Final release target | **v0.2.0 — THIS RELEASE** (ETA: 2026-06-04, accelerated from 2026-07-15) |
-| Last shipped | **v0.1.19 (ceremony COMPLETE)** — all 4 ceremony steps complete 2026-06-03T15:49Z. v0.1.20 crates.io ✅ orphan (git ceremony superseded by v0.2.0). |
+| Last updated | 2026-06-04 (PM dispatch v46 — Codex P1+P2 fixes on #541; v0.2.0 ceremony Steps 1+3+4 done; Step 2 (tag) awaits founder) |
+| Current sprint | **v0.2.0 ceremony STEPS 1+3+4 COMPLETE** — Step 1 ✅ (PR #523→main); Step 3 ✅ (crates.io published); Step 4 ✅ (PR #537 back-merge `4e60400f`); Step 2 (tag push) awaits founder. |
+| Active release branch | none — `release/v0.2.0` back-merged to develop ✅; Step 2 (tag) pending |
+| Next release target | **v0.2.1** — npm scope registration + E404 tightening (Issue #534), post-v0.2.0 backlog |
+| Final release target | v0.2.0 ceremony closing; v0.3.0 ETA TBD |
+| Last shipped | **v0.1.19 (ceremony COMPLETE)** — v0.2.0 Steps 1+3+4 done; Step 2 (tag push) pending founder. |
 
 ---
 
@@ -80,18 +80,6 @@ This file is the **live state** of the PM brain. Update on every cadence checkpo
 
 ## ⚠️ v0.1.17 — CRATES PUBLISHED; GIT CEREMONY SUPERSEDED BY v0.1.18
 
-**Content already on develop (post-v0.1.16):**
-- [x] RFC-0101 Phase 2: `mycelium context` CLI twin — Three-Surface Rule fully satisfied (PR #414)
-- [x] RFC-0102 Implemented: OutputBudget moved to `mycelium-core`; CLI+MCP byte-identical (PR #438)
-- [x] RFC-0100 Phase 3: **redb is now the default storage backend** (PR #448)
-- [x] RFC-0104: Charter §2 warm/cold SLA split — founder-approved 2026-06-02 (PR #444)
-- [x] Issue #428 god-file-split slice 1: redb value codecs → `store::redb_codec` (PR #441)
-- [x] Issue #428 god-file-split slice 2: `mod tests` → `src/tests.rs` (PR #442, `lib.rs` 12191→5627 lines, −54%)
-- [x] 100k-node redb SLA gate + env-guarded nightly benchmark (PR #440)
-- [x] Orphan `BoundedStore`/`MemoryBudget`/`FileAccessTracker` LRU removed (PR #440)
-- [x] Repo hygiene: orphan `.claude/worktrees/` gitlinks removed + `.gitignore` updated (PR #449)
-- [x] Vision scorecard updated to v0.1.16+ reality (PR #450)
-
 **v0.1.17 ceremony status — PARTIAL (crates only; git superseded by v0.1.18):**
 - [x] **Pre-release**: `publish to crates.io/npm/PyPI` ✅ — all 5 crates at v0.1.17.
 - [x] **Step 4**: Back-merge `release/v0.1.17` → `develop` — **PR #477 MERGED ✅** 2026-06-03T07:54Z
@@ -110,9 +98,9 @@ This file is the **live state** of the PM brain. Update on every cadence checkpo
 - Reactive-completion roadmap: **4/4 COMPLETE** (watch ✅ push ✅ subscribe ✅ salsa ✅).
 
 **v0.1.18 ceremony status — ALL FOUR STEPS COMPLETE ✅ (2026-06-03):**
-- [x] **Step 1**: PR #490 merged `release/v0.1.18` → main (`-X ours` to resolve stale gitlinks + ADR numbering) ✅
+- [x] **Step 1**: PR #490 merged `release/v0.1.18` → main ✅
 - [x] **Step 2**: Tag `v0.1.18` pushed ✅ (SHA e429a224, 2026-06-03T12:30Z)
-- [x] **Step 3**: GitHub Release v0.1.18 created ✅ (2026-06-03T12:30Z) — "reactive-completion roadmap complete"
+- [x] **Step 3**: GitHub Release v0.1.18 created ✅ (2026-06-03T12:30Z)
 - [x] **Step 4**: Back-merge PR #483 MERGED to develop ✅ (2026-06-03T09:10:56Z)
 - [x] RFC-0105 EXCEPTION ratified by founder — PR #491 (2026-06-03)
 
@@ -134,40 +122,21 @@ This file is the **live state** of the PM brain. Update on every cadence checkpo
 **v0.1.19 ceremony status — ALL FOUR STEPS COMPLETE ✅:**
 - [x] **Step 1**: `release/v0.1.19` → `main` — founder ceremony ✅
 - [x] **Step 2**: Tag `v0.1.19` pushed ✅ (SHA 55761a85, 2026-06-03)
-- [x] **Step 3**: GitHub Release v0.1.19 created ✅ (2026-06-03T15:49Z) — "precision pass + ADR docs"
+- [x] **Step 3**: GitHub Release v0.1.19 created ✅ (2026-06-03T15:49Z)
 - [x] **Step 4**: Back-merge PR #493 MERGED ✅ (develop HEAD = `55761a85`)
 
 ---
 
 ## ⚠️ v0.1.20 — CRATES PUBLISHED; GIT CEREMONY SUPERSEDED BY v0.2.0
 
-**What ships in v0.1.20 (all on `release/v0.1.20` SHA `1b0d7dc`):**
-- [x] docs: align doc claims with code — tool count 89→93, RFC-0100/0102 acceptance criteria synced (PR #495)
-- [x] RFC-0102 nested `budget{}` response object + BudgetMode tag (PR #497)
-- [x] RFC-0102 per-call budget override knob on `mycelium_context` + CLI twin (PR #498)
-- [x] fix(budget): cap `callee_paths`/`caller_paths`/`dead_symbols`/`isolated_symbols` in `apply_budget` (PR #499)
-- [x] docs(rfc): RFC-0109 graph-list output-shape parity, Option A ratified (PR #500)
-- [x] feat(queries): RFC-0109 **get_callees** shared builder + object shape + budget knob (PR #501)
-- [x] feat(queries): RFC-0109 **get_callers** shared builder + object shape + budget knob (PR #504)
-- [x] feat(queries): RFC-0109 **get_dead_symbols** shared builder + object shape + budget knob (PR #507)
-- [x] docs(adr): **ADR-0010** — no live LSP; prefer static SCIP/LSIF (PR #496)
-- [x] feat(queries): RFC-0109 **get_isolated_symbols** shared builder + budget knob (PR #509)
-- [x] fix(ci): macOS `sla_ancestors_100k` guard 30ms → 100ms (PR #508)
-- [x] feat(queries): RFC-0109 **get_reachable** shared builder + budget knob (PR #511)
-- [x] feat(queries): RFC-0109 **get_reachable_to** shared builder + budget knob (PR #512)
-- [x] feat(queries): RFC-0109 **get_all_symbols** object shape + budget knob — **RFC-0109 7/7 COMPLETE** (PR #513)
-- [x] CHANGELOG sealed + Cargo.toml 0.1.19 → 0.1.20
-
 **v0.1.20 ceremony status — SUPERSEDED BY v0.2.0 ⚠️:**
 - [x] Release branch `release/v0.1.20` cut from develop
-- [x] **crates.io v0.1.20 published** ✅ (orphan, 2026-06-04T01:17Z via release.yml run #26930459563)
+- [x] **crates.io v0.1.20 published** ✅ (orphan, 2026-06-04T01:17Z)
 - [x] **npm v0.1.20 published** ✅ (orphan)
 - [x] **PyPI v0.1.20 published** ✅ (orphan)
-- [x] **PR #515 closed** as superseded (PM dispatch v36, 2026-06-04T05:3xZ) — git ceremony will not proceed.
-- ✅ Git ceremony superseded: main jumps v0.1.19 → v0.2.0. Founder decision (cut v0.2.0 at 05:26Z incorporating all v0.1.20 content + RFC-0110).
-- ❌ **Step 2**: Tag `v0.1.20` NOT pushed (skipped per supersession strategy).
-- ❌ **Step 3**: GitHub Release NOT created (skipped).
-- ❌ **Step 4**: Back-merge NOT done (not needed; v0.2.0 back-merge will carry all content).
+- [x] **PR #515 closed** as superseded (PM dispatch v36)
+- ✅ Git ceremony superseded: main jumps v0.1.19 → v0.2.0. Founder decision.
+- ❌ **Steps 2, 3, 4**: skipped per supersession strategy.
 
 **Resolution**: v0.1.20 content (RFC-0109 7/7, RFC-0102 budget, RFC-0110 npm) absorbed into v0.2.0.
 
@@ -177,92 +146,71 @@ This file is the **live state** of the PM brain. Update on every cadence checkpo
 
 **Goal:** `npm i -g @aimasteracc/mycelium && mycelium --version` works on machines without Cargo.
 
-- [x] **Increment 1** (PR #517, founder-authored, merged 2026-06-04T02:15Z): npm package scaffolding — launcher `bin/mycelium.cjs`, `package.json` with 5-platform `optionalDependencies`, `build-npm.mjs` assembly script, 8 unit tests.
-- [x] **Increment 2** (PR #519, merged 2026-06-04T02:26Z): `release.yml` cross-compile matrix — builds CLI binaries for darwin-arm64/x64, linux-x64/arm64, win32-x64; attaches to GitHub Release.
-- [x] **Increment 3** (PR #520, merged 2026-06-04T02:56Z): `publish-npm` job rewired (assemble + publish platform + main packages); CI smoke test (`npm install --install-links` → launcher → `--version`).
+- [x] **Increment 1** (PR #517, merged 2026-06-04T02:15Z): npm package scaffolding
+- [x] **Increment 2** (PR #519, merged 2026-06-04T02:26Z): `release.yml` cross-compile matrix
+- [x] **Increment 3** (PR #520, merged 2026-06-04T02:56Z): `publish-npm` job rewired + CI smoke test
 
-**Status:** RFC-0110 **Implemented** on develop. Goes live at **v0.2.0** (this release — founder included in `release/v0.2.0`).
+**Status:** RFC-0110 **Implemented** on develop. Goes live at **v0.2.0**.
 
 ---
 
-## 🔥 v0.2.0 — "The Three-Surface Release" CEREMONY READY (PR #523, CI green)
+## 🔥 v0.2.0 — "The Three-Surface Release" CEREMONY STEPS 1+4 DONE
 
-**Founder-cut 2026-06-04T05:26:18Z** — `release/v0.2.0` branched from develop (Cargo.toml 0.1.19→0.2.0).
+**Founder-cut 2026-06-04T05:26:18Z** — `release/v0.2.0` branched from develop.
 
 **What ships in v0.2.0:**
-- [x] **RFC-0109** — graph-list CLI↔MCP output parity 7/7 tools COMPLETE (`get_callees`, `get_callers`, `get_dead_symbols`, `get_isolated_symbols`, `get_reachable`, `get_reachable_to`, `get_all_symbols`)
-- [x] **RFC-0102** — adaptive output budget roll-out COMPLETE (`budget_ms` knob on all 7 RFC-0109 tools; `budget{}` BudgetMode response tag)
-- [x] **RFC-0110** — npm/bun CLI distribution (Increments 1+2+3) — **marquee v0.2.0 feature** (no Rust toolchain required)
+- [x] **RFC-0109** — graph-list CLI↔MCP output parity 7/7 tools COMPLETE
+- [x] **RFC-0102** — adaptive output budget roll-out COMPLETE
+- [x] **RFC-0110** — npm/bun CLI distribution (Increments 1+2+3)
 - [x] CHANGELOG [Unreleased] sealed + consolidated into [0.2.0]; version bump 0.1.19→0.2.0
-- [x] `release.yml`: `check-npm-token` preflight graceful (warning+exit 0 when absent; commit `4eb0cef` on `release/v0.2.0`, PM dispatch v38)
-- [x] README: npm/bun install documented; version badge/roadmap updated
-- [x] **DCO sign-off fixed (v39)**: `git rebase --signoff HEAD~21` on `release/v0.2.0` — all 21 non-merge commits now carry `Signed-off-by`. Force-pushed as `29b01dc`. DCO check: **SUCCESS** ✅.
-
-**v0.2.0 ceremony status — UNBLOCKED PENDING CI RE-RUN (npm E404 fix `66f91cb` pushed):**
-- [x] `release/v0.2.0` branch created by founder at 05:26Z ✅
-- [x] **CI blocker 1 fixed (v38)**: `check-npm-token` preflight graceful (warning+exit 0). ✅
-- [x] **CI blocker 2 fixed (v39)**: DCO sign-off fixed (`29b01dc`, rebase --signoff). ✅
-- [x] **CI blocker 3 fixed (v41)**: `publish to npm` E404 "Scope not found" — `publish_one()` now catches E404/Scope-not-found, warns and exits 0. Commit `66f91cb` on `release/v0.2.0`. Root cause: `@aimasteracc` scope not registered on npmjs.com. ✅
-- [x] **`publish to crates.io`**: ✅ v0.2.0 crates published (run `26944137925`). Idempotent (will skip on re-run).
-- [x] **`publish to PyPI`**: ✅ SUCCESS.
-- [ ] **Step 1**: PR #523 → `main` — **AWAITING CI RE-RUN + FOUNDER** (CI running on `66f91cb`)
-- [ ] **Step 2**: Tag `v0.2.0` — NOT pushed
-- [ ] **Step 3**: GitHub Release NOT created
-- [ ] **Step 4**: Back-merge `release/v0.2.0` → `develop` — PM opens after Step 1
-
-**v0.2 PRD success metrics (verified):**
-
-| Metric | Target | Status |
-|---|---|---|
-| Three-Surface Rule | 88/88 capabilities | ✅ CI skill-parity gate enforced |
-| Dogfood pass rate | 8/8 CLI commands | ✅ E2E CI green on develop |
-| npm/bun distribution | shipped | ✅ RFC-0110 (this release) |
-| RFC-0090 | Implemented | ✅ after this merge |
+- [x] README: npm/bun install documented (coming soon wording; live once Issue #534 resolved)
+- [x] DCO sign-off fixed: all 21 non-merge commits carry `Signed-off-by`
+
+**v0.2.0 ceremony status — STEP 2 PENDING (founder action required):**
+- [x] **Step 1**: PR #523 MERGED → `main` ✅ (2026-06-04T10:41:45Z)
+- [ ] **Step 2**: Tag `v0.2.0` pushed — **founder action required**
+- [x] **Step 3**: All 5 crates to crates.io ✅ (release.yml, 2026-06-04)
+- [x] **Step 4**: PR #537 MERGED → `develop` ✅ (squash `4e60400f`, 2026-06-04T14:07Z)
+
+**Note on npm/PyPI:** PyPI ✅ published. npm `@aimasteracc` scope not yet registered; `publish to npm` exits 0 gracefully (Issue #534). Draft GitHub Release at `untagged-eb9b123` will be published by founder when tag is pushed.
 
 ---
 
 ## Live priorities (ordered)
 
-**P0 (v0.2.0 ceremony — CI re-running, founder action imminent):**
-1. **⚡ CEREMONY UNBLOCKED**: Commit `66f91cb` pushed to `release/v0.2.0` — `publish_one()` now handles E404 scope-not-found gracefully. CI re-running. **Founder action**: once all checks SUCCESS/SKIPPED → merge PR #523 → push tag `v0.2.0` → create GitHub Release. PM opens Step 4 back-merge after Step 1.
-2. **Register `@aimasteracc` npm scope** on npmjs.com — this is what caused `publish to npm` E404. No code fix will substitute; founder must create the scope. Once done, npm publish on next release will succeed. (See Issue #525 for v0.2.1 scope notes.)
-
-**P0 done this run ✅ (v42):**
-- PR #533 MERGED ✅ (ci(release): npm graceful degradation, squash `fdd35258`) — Codex P1 addressed via Issue #534 spin-off
-- Issue #526 CLOSED ✅ (mutation kill-rate fix already on develop via PR #531)
-- Issue #534 CREATED — tracks re-tightening E404 once @aimasteracc npm scope registered
-- PR #535 OPENED — fix(npm): 128+signal exit code for Issue #525 (9/9 node:test GREEN)
+**P0 (v0.2.0 ceremony — founder action required):**
+1. **Push tag `v0.2.0`** + publish GitHub Release (Step 2; Steps 1+3+4 already done ✅).
+2. **Register `@aimasteracc` npm scope** on npmjs.com (Issue #534) — enables real npm publish for v0.2.1+.
 
 **P1 (quality — post v0.2.0 ceremony):**
-3. **Admin-merge PR #535** (`fix/npm-signal-exit-code-issue-525` → develop) once CI green. Closes Issue #525.
-4. **Security scan post-v0.2.0** — PENDING (run after ceremony).
+4. **Security scan post-v0.2.0** — pending (run after ceremony complete).
 5. **Dogfood re-run** — RFC-0109 object shapes + RFC-0110 npm launcher + redb-as-default + watch --subscribe (8/8 CLI).
 6. **RFC-0104 cold SLA numbers** — nightly `sla_ancestors_100k` for Charter §2 cold-open budget.
-7. **Add NPM_TOKEN secret** to `npm` environment — enables npm publish on next release run.
+7. **Add NPM_TOKEN secret** to `npm` environment — enables npm publish on next release.
 
 **P2 (post-v0.2.0):**
-10. Issue #534 — npm scope E404 tightening once @aimasteracc scope registered on npmjs.com.
-11. `release.yml` systemic auto-close fix (ceremony script is current workaround).
-12. **Systemic DCO fix** (for v0.3.0+): update `dco-check` script in `ci.yml` to grep full commit message body, OR switch `release.yml` merge to `git push origin release/vX.Y.Z:main` (fast-forward preserves trailers).
-13. Issue #428 god-file-split remaining slices.
-14. Skill marketplace submission to Claude Code marketplace.
-15. "First 5 minutes" walkthrough validation.
+8. Issue #534 — npm scope E404 tightening once @aimasteracc scope registered.
+9. `release.yml` systemic auto-close fix (ceremony script is current workaround).
+10. **Systemic DCO fix** (for v0.3.0+): update `dco-check` script in `ci.yml` to grep full commit message body.
+11. Issue #428 god-file-split remaining slices.
+12. Skill marketplace submission to Claude Code marketplace.
+13. "First 5 minutes" walkthrough validation.
 
 ---
 
-## Dispatch state (2026-06-04 v42 — PR #533 merged; Issue #526 closed; Issue #534 created; PR #535 opened)
+## Dispatch state (2026-06-04 v45 — PR #537 merged (Step 4 ✅); #539/#540 closed)
 
 | Agent | Status | Current item |
 |---|---|---|
-| founder | **action requested (P0+P1)** | **(P0)** Release CI in_progress (run 26947365908) — once SUCCESS/SKIPPED → merge PR #523 → push tag `v0.2.0` → GitHub Release. **(P1)** Register `@aimasteracc` scope on npmjs.com. **(P1)** Admin-merge PR #535 once CI green (Issue #525 signal exit code). |
-| PM | **DONE ✅** | v42: PR #533 merged; Issue #526 closed; Issue #534 created; PR #535 opened; PM state v42 + decisions.jsonl. |
-| release | **WAITING CI** | v0.2.0 ceremony: Release workflow in_progress (run 26947365908). Founder merge imminent. |
+| founder | **action requested (P0)** | **(P0)** Push tag `v0.2.0` + create GitHub Release (ceremony Steps 2+3). **(P0)** Register `@aimasteracc` npm scope on npmjs.com (Issue #534). |
+| PM | **DONE ✅** | v45: PR #537 merged (Step 4); #539/#540 closed; PM state + decisions.jsonl updated. |
+| release | **WAITING** | v0.2.0 ceremony: Steps 1+4 ✅. Step 2 (tag) + Step 3 (GH Release) founder-gated. |
 | security-reviewer | **P1** | Post-v0.2.0 scan pending (after ceremony). |
 | architect | **DONE ✅** | ADR-0009 ✅, ADR-0010 ✅. |
 | e2e-runner | **P1** | Dogfood re-run: RFC-0109 object shapes + RFC-0110 npm + redb-as-default + watch --subscribe. |
 | bench | **P1** | `sla_ancestors_100k` nightly for RFC-0104 cold SLA. |
 | tech-writer | **P1** | Marketplace submission (v0.2.0 ships npm — right time to submit). |
-| rust-implementer | **P1** | PR #535 awaiting CI (fix/npm-signal-exit-code-issue-525 — closes Issue #525). |
+| rust-implementer | idle | Next sprint backlog (P2 items). |
 
 ---
 
@@ -276,11 +224,10 @@ This file is the **live state** of the PM brain. Update on every cadence checkpo
 - **RFC-0104 cold SLA measurement**: Charter §2 table amendment requires measured nightly data.
 - ~~**RFC-0105 Three-Surface EXCEPTION**~~: ✅ RATIFIED 2026-06-03T12:30Z.
 - ~~**v0.1.17 git ceremony skip**~~: ✅ RESOLVED.
-- ~~**v0.1.20 ceremony**~~: SUPERSEDED by v0.2.0 (PM dispatch v36). PR #515 closed. crates.io/npm/PyPI v0.1.20 published (orphan). Founder confirmed via cutting release/v0.2.0.
-- **v0.2.0 ceremony**: PR #523 open. Fix `66f91cb` on release/v0.2.0 — npm E404 scope graceful. CI re-running. Founder: once SUCCESS/SKIPPED → merge PR #523 → push tag `v0.2.0` → GitHub Release. Also: register `@aimasteracc` npm scope on npmjs.com.
-- **Systemic DCO config**: The `.github/dco.yml` approach does NOT fix the CI gate — the gate is a custom shell script (`ci.yml` `dco-check`), not the GitHub DCO App. Fix: update the `dco-check` script to grep full message body, OR switch release merge to `git push origin release/vX.Y.Z:main`.
-- **RFC-0104 cold SLA measurement**: Charter §2 table amendment requires measured nightly data.
-- **RFC-0110 merge auth**: PRs #517, #519, #520 all merged by founder ✅. RFC-0110 Implemented. Goes live in v0.2.0.
+- ~~**v0.1.20 ceremony**~~: SUPERSEDED by v0.2.0. Founder confirmed.
+- **v0.2.0 ceremony**: Step 1 ✅ (PR #523). Step 4 ✅ (PR #537 `4e60400f`). **Founder: push tag `v0.2.0` + create GitHub Release.**
+- **Register `@aimasteracc` npm scope**: npmjs.com account creation + org scope registration. One-time founder action.
+- **Systemic DCO config**: update `dco-check` script in `ci.yml` (same issue will recur on every future release with squash-merged commits).
 
 ---
 
@@ -289,288 +236,45 @@ This file is the **live state** of the PM brain. Update on every cadence checkpo
 - **Hourly (autonomous)**: each agent picks the top item from its queue.
 - **Daily PM check** (orchestrator): scan issue queue for new P0/P1; rebalance.
 - **Weekly Sprint review** (orchestrator + founder if available): mark sprint exit criteria; cut next sprint.
-- **Bi-weekly release** (orchestrator): if sprint exit criteria met, cut release/v0.1.x branch, publish.
+- **Bi-weekly release** (orchestrator): if sprint exit criteria met, cut release/vX.Y branch, publish.
 
 ---
 
 ## Archive
 
-### 2026-06-04 PM dispatch v42 (this run — PR #533 merged; Issue #526 closed; PR #535 opened; Issue #534 created)
-
-**Pre-flight:** Read CHARTER.md §2/§5.1/§5.10/§5.12/§5.13, _orchestrator.md, decisions.jsonl tail-20 (latest: 2026-06-04T10:30Z v41), anti-patterns (domains: release-governance, ci — no new hits), PM state v41, v0.2 PRD.
-
-**Assessment:**
-- 1 open PR: #533 (fix/release-npm-graceful-comprehensive, 20/20 CI ✅, Codex P1 open).
-- 2 open issues: #526 (P1 mutation kill-rate — PR #531 already merged, awaiting formal close), #525 (P2 npm signal exit code).
-- Release workflow in_progress (run 26947365908) on release/v0.2.0. Previous run (26946150331) FAILED. Fix `66f91cb` pushed to release/v0.2.0 in v41.
-
-**Actions taken:**
-1. **Created Issue #534** (P2): `release.yml: re-enable hard E404 failure once @aimasteracc npm scope registered` — spin-off tracking for Codex P1 concern on PR #533. ✅
-2. **Replied to Codex P1** on PR #533 (discussion_r3355193388): rejected with 1-paragraph justification + Issue #534 link. ✅
-3. **Merged PR #533** (squash `fdd35258`) — all Codex findings addressed; 20/20 CI ✅. ✅
-4. **Closed Issue #526** — mutation kill-rate fix already merged (PR #531, `b696953`). ✅
-5. **Fixed Issue #525** (npm 128+signal exit code): TDD RED→GREEN. Created `signalToExitCode(signal)` function, wired into `main()`, exported. 9/9 `node --test` GREEN. CHANGELOG updated. ✅
-6. **Pushed branch** `fix/npm-signal-exit-code-issue-525` and **opened PR #535**. CI running. ✅
-7. **Updated PM state v42** + decisions.jsonl. ✅
-
-**Escalations to founder:**
-- **(P0)** Release CI (run 26947365908) — once all checks SUCCESS/SKIPPED → merge PR #523 → push tag `v0.2.0` → create GitHub Release.
-- **(P1)** Register `@aimasteracc` npm scope on npmjs.com.
-- **(P1)** Admin-merge PR #535 once CI green.
-
-### 2026-06-04 PM dispatch v41 (this run — PRs #531+#532 merged; npm E404 diagnosed + fixed; PR #533 opened; PR #528 closed)
-
-**Pre-flight:** Read CHARTER.md §2/§5.1/§5.10/§5.12/§5.13, _orchestrator.md, decisions.jsonl tail-20 (latest: 2026-06-04T10:00Z v40), anti-patterns (domains: release-governance, ci, pm-dispatch — no new hits), PM state v40, v0.2 PRD.
-
-**Assessment:**
-- 4 open PRs: #532 (PM v40 chore, 22/22 CI ✅), #531 (mutation fix, 24/24 CI ✅), #528 (npm graceful, stale), #523 (release/v0.2.0, FAILING — `publish to npm` E404 FAILURE).
-- 2 open issues: #526 (P1 mutation kill-rate, addressed by PR #531), #525 (P2 npm exit code, v0.2.1).
-- PR #523 latest Release workflow run `26944137925`: `publish to npm` FAILURE (E404 "Scope not found"). Root cause: `@aimasteracc` npm scope not registered on npmjs.com. NPM_TOKEN IS present (preflight SUCCESS). Previous PM state claimed "CI green" based on stale run — stale state.
-- PR #533 not yet opened (this run's action). PR #528 addresses wrong failure mode.
-
-**Actions taken:**
-1. **Merged PR #531** (test(mcp): mutation kill-rate fix, 24/24 CI SUCCESS, squash `b69695313c`) ✅ — Issue #526 CLOSED.
-2. **Merged PR #532** (chore(pm): dispatch v40, 22/22 CI SUCCESS, squash `dff97c49bd`) ✅.
-3. **Diagnosed npm E404**: job log for run `26944137925` job `79494753448` — `npm error 404 Not Found - PUT @aimasteracc%2fmycelium-darwin-arm64 - Scope not found`. Root cause: npm scope `@aimasteracc` unregistered. Not a token issue.
-4. **Fixed release/v0.2.0**: Edited `.github/workflows/release.yml` `publish_one()` — catch E404/Scope-not-found with warning + `return 0`. Committed as `66f91cb`, pushed directly to `release/v0.2.0`. CI re-triggered.
-5. **Opened PR #533** (`fix/release-npm-graceful-comprehensive` → develop): comprehensive fix — token absent (warning+exit 0) + E404 scope-not-found (warning+return 0). Supersedes PR #528.
-6. **Closed PR #528** as superseded by PR #533.
-7. **Updated PM state v41** + decisions.jsonl.
-
-**Escalations to founder:**
-- **(P0)** Wait for CI on `release/v0.2.0` commit `66f91cb` → once all checks SUCCESS/SKIPPED → merge PR #523 → push tag `v0.2.0` → create GitHub Release.
-- **(P1)** Register `@aimasteracc` npm scope on npmjs.com (one-time, needed for npm distribution in v0.2.1+).
-- **(P1)** Admin-merge PR #533 once CI green.
-
-### 2026-06-04 PM dispatch v40 (this run — PR #530 merged; #527+#529 closed; Issue #526 mutation kill-rate → PR #531)
-
-**Pre-flight:** Read CHARTER.md §2/§5.1/§5.10/§5.12/§5.13, _orchestrator.md, decisions.jsonl (last: v39 DCO rebase), anti-patterns (hits: release-governance + mutation-test), PM state (v39 on develop, post-#530-merge), v0.2 PRD.
-
-**Assessment:**
-- 3 open PRs: #530 (PM v39 chore, 22/22 CI SUCCESS ✅), #528 (npm token fix, 2 triage checks only), #523 (release/v0.2.0 → main, all Quality Gate + test matrix + release workflow checks GREEN).
-- Release workflow on `release/v0.2.0` still running (darwin-x64 binary queued; not a Quality Gate blocker).
-- 2 open issues: #526 (P1 mutation kill-rate <70%), #525 (P2 npm signal exit code).
-- PR #530 22/22 green → admin-mergeable now. PRs #527 and #529 marked superseded in PR #530 body.
-
-**Actions taken:**
-1. **Merged PR #530** (PM dispatch v39, 22/22 CI SUCCESS, squash `ddd6362a`) ✅
-2. **Closed PRs #527 + #529** (superseded by v39 per PR #530 body) ✅
-3. **Fixed Issue #526** — explored mutation-weak test pattern: 6 MCP tests using `.contains()`-only assertions without exact-count checks. Added `assert_eq!(len, N)` and `assert_eq!(raw.is_error, Some(true))` assertions. 437/437 mycelium-rcig-mcp lib tests GREEN. fmt + clippy clean. Committed `68262d1`. **PR #531 opened** (`fix/mutation-kill-rate-issue-526` → develop). ✅
-4. **Updated PM state v40** + decisions.jsonl. ✅
-
-**Escalations to founder:**
-- **(1) P0 CEREMONY**: PR #523 all CI green. Merge PR #523 → push tag `v0.2.0` → GitHub Release.
-- **(2) P1 quality**: Admin-merge PR #531 (mutation fix, Issue #526) and PR #528 (npm token graceful) once their CI passes.
-- **(3) NPM_TOKEN**: Add to repo Settings → Environments → npm to re-enable npm distribution.
-
-### 2026-06-04 PM dispatch v39 (this run — DCO sign-off fixed on release/v0.2.0; PR #523 CI fully green)
-
-**Pre-flight:** Read CHARTER.md §2/§5.1/§5.10/§5.12/§5.13, _orchestrator.md, decisions.jsonl tail (latest: v36 entry on develop; v37/v38 in open PRs #527/#529), anti-patterns (hits: release-governance squash-merge DCO strip), PM state v38 (on `chore/pm-dispatch-2026-06-04-v38`), v0.2 PRD.
-
-**Assessment:**
-- 4 open PRs: #523 (release/v0.2.0 → main, npm-token fix `4eb0cef` applied but NEW DCO FAILURE exposed by PR synchronize event), #529 (PM v38 → develop, pending), #528 (fix/release-npm-token-graceful → develop, pending), #527 (PM v37 → develop, pending). 2 open issues: #526 (P1 mutation kill-rate), #525 (P2 npm exit code).
-- Root cause of NEW DCO failure: pushing `4eb0cef` to `release/v0.2.0` triggered a `pull_request synchronize` event, which fired the standalone `ci.yml` `dco-check` job. This job checks `git rev-list --no-merges base.sha..head.sha` — range includes 21 non-merge squash-merge commits, none carrying `Signed-off-by` (GitHub web UI squash-merge drops DCO trailers). Same systemic issue as v0.1.20 (required HEAD~16).
-- Fix: `git rebase --signoff HEAD~21` on `fix-dco-release-v0.2.0` branch → force-push to `origin/release/v0.2.0` as `29b01dc`.
-
-**Actions taken:**
-1. **Counted non-merge commits**: `git rev-list --no-merges 55761a857..HEAD | wc -l` → 21. ✅
-2. **Rebased all 21 with sign-off**: `GIT_SEQUENCE_EDITOR=true git rebase --signoff HEAD~21` → success, new HEAD `29b01dc`. ✅
-3. **Force-pushed**: `git push --force-with-lease origin HEAD:release/v0.2.0` → `4eb0cef...29b01dc`. ✅
-4. **CI verified**: `DCO sign-off` → **SUCCESS** ✅; `preflight (npm token present)` → **SUCCESS** ✅; all other fast jobs green; test matrix completing (no failures). ✅
-5. **PM state v39 updated** + `decisions.jsonl` appended. ✅
-
-**Escalations to founder:**
-- **(P0) v0.2.0 ceremony**: PR #523 CI green. Once test matrix completes (all SUCCESS/SKIPPED) → merge PR #523 → push tag `v0.2.0` → create GitHub Release → PM opens Step 4 back-merge.
-- **(P1) Admin-merge PRs #528+#529** (or #530) once CI green.
-- **(P1) NPM_TOKEN**: Add to repo Settings → Environments → npm.
-- **(P2 systemic) DCO fix**: Update `dco-check` script in `ci.yml` to grep full commit body for `Signed-off-by:`, OR switch `release.yml` merge to `git push origin release/vX.Y.Z:main`. Same issue will recur on every future release with squash-merged commits.
-
-### 2026-06-04 PM dispatch v38 (npm-token preflight fix; PR #528 opened)
-
-**Pre-flight:** Read CHARTER.md §2/§5.1/§5.10/§5.12/§5.13, _orchestrator.md, decisions.jsonl tail (latest: v36 entry), anti-patterns (hits: release-governance, ci-portability), PM state v36 (develop HEAD `b2fe917`), v0.2 PRD.
-
-**Assessment:**
-- 2 open PRs: #527 (PM v37 chore, 2 triage checks only — Quality Gate not yet visible), #523 (release/v0.2.0 → main, CI BLOCKED by `preflight (npm token present)` FAILURE + darwin-x64 binary queued). 2 open issues: #526 (P1 mutation kill-rate < 70%), #525 (P2 npm 128+signal).
-- Root cause of PR #523 CI failure: `check-npm-token` job exits 1 when NPM_TOKEN absent — hard FAILURE violates Charter §5.12 (every check must be SUCCESS or SKIPPED before merging release/* to main). NPM_TOKEN secret not configured in `npm` environment. crates.io v0.2.0 already published orphan (previous run).
-- `build CLI binary (darwin-x64)` still queued (macOS runner availability) — will resolve on its own.
-- Codex review on PR #523: 1 P2 finding (npm 128+signal exit code) — already addressed in v37 (Issue #525 spun off, reply posted). No open P1/P0 Codex findings.
-
-**Actions taken:**
-1. **Pushed `4eb0cef`** to `release/v0.2.0`: `check-npm-token` now exits 0 + `::warning::` when NPM_TOKEN absent; `publish-crates` decoupled from npm-token dependency; `publish-npm` Publish step now exits 0 + warning (graceful skip). PR #523 CI retriggered. ✅
-2. **Pushed `5126787`** to `fix/release-npm-token-graceful` (new branch from develop): same `publish-npm` graceful fix for future releases. ✅
-3. **Opened PR #528** (`fix/release-npm-token-graceful` → develop): CI-only change, no RFC required, same category as PR #468/455/471. ✅
-4. **Updated PM state v38**: header, v0.2.0 ceremony section, live priorities (added Issue #526 P0, PR #528 P1, NPM_TOKEN setup), dispatch table (rust-implementer P0 for #526). ✅
-5. **Appended decisions.jsonl**. ✅
-
-**Escalations to founder:**
-- **(P0)** PR #523 CI re-running. Wait for darwin-x64 binary + all checks SUCCESS/SKIPPED → merge PR #523 → push tag `v0.2.0` → create GitHub Release.
-- **(P0 quality)** Issue #526 — mutation kill-rate < 70% — dispatch rust-implementer.
-- **(P1)** Add `NPM_TOKEN` to repo Settings → Environments → npm to enable npm distribution.
-
-### 2026-06-04 PM dispatch v37 (PR #524 merged; Codex P2 on #523 addressed; Issues #525+#526 filed)
-
-**Pre-flight:** Read CHARTER.md, _orchestrator.md, decisions.jsonl tail, anti-patterns, PM state v36, v0.2 PRD.
-
-**Assessment:**
-- PR #524 (PM v36 chore, 22/22 CI green) and PR #523 (release/v0.2.0 → main, CI running) both open.
-- PR #523 Codex review: 1 P2 finding on `npm/mycelium/bin/mycelium.cjs` line 71 — exits with code 1 for signal-terminated processes instead of conventional 128+signal. Not blocking v0.2.0 but should be tracked.
-- Nightly CI run `#26934880069` on main: `mutation testing (kill-rate gate >= 70%)` FAILED — Charter §2 SLA breach.
-
-**Actions taken:**
-1. **Merged PR #524** (PM dispatch v36, 22/22 CI green, squash `b2fe917`) ✅
-2. **Addressed Codex P2 on PR #523**: replied to `discussion_r3353893253` with acceptance rationale + tracked as Issue #525 for v0.2.1. ✅
-3. **Filed Issue #525** (`fix(npm): use 128+signal exit code in mycelium.cjs launcher`) — P2, good-first-issue, v0.2.1 target. ✅
-4. **Filed Issue #526** (`P1: nightly mutation testing kill-rate below 70% gate`) — P1, quality, Charter §2 SLA. ✅
-5. **PM state v37 + decisions.jsonl** updated. PR #527 opened.
+### 2026-06-04 PM dispatch v45 (this run — PR #537 merged (Step 4); #539/#540 closed)
 
-**Escalations to founder:**
-- **(P0)** PR #523 CI completing — binary builds in progress. Merge once ALL checks SUCCESS/SKIPPED.
-- **(P1)** NPM_TOKEN missing → npm publish will be skipped (pr preflight failure).
-- **(P1)** Issue #526 — mutation kill-rate — rust-implementer dispatch needed.
-
-### 2026-06-04 PM dispatch v36 (this run — founder cut v0.2.0; PR #522 merged; PR #523 opened)
-
-**Pre-flight:** CHARTER §2/§5.1/§5.10/§5.12/§5.13, _orchestrator.md, decisions.jsonl tail (latest: 2026-06-04T05:10Z v35 — Codex P1 fix), anti-patterns (no new domain hits), PM state v35, v0.2 PRD.
+**Pre-flight:** Read CHARTER.md §2/§5.1/§5.10/§5.12/§5.13, _orchestrator.md, decisions.jsonl tail-20, anti-patterns (no new domain hits), PM state v42 (from develop HEAD `4e60400f` post-#537 merge), v0.2 PRD.
 
 **Assessment:**
-- 2 open PRs: #515 (release/v0.1.20 → main, 44/44 CI ✅), #522 (chore/pm-dispatch-v33, 20/20 CI ✅, Codex P1 REPLIED by founder ✅).
-- 0 open issues.
-- **CRITICAL NEW FINDING**: `release/v0.2.0` branch created by founder (aisheng.yu) at 2026-06-04T05:26:18Z. Commit `1105cc6d`: "chore(release): bump version 0.1.19 → 0.2.0; seal CHANGELOG". Content: RFC-0109 + RFC-0102 + RFC-0110 npm/bun. Release workflow #26932722905 queued at 05:27Z. No PR existed for release/v0.2.0 → main.
-- v0.1.20 CI status: ALL green (crates/npm/PyPI published as orphan). Superseded by v0.2.0 founder decision.
+- 3 open PRs: #537 (back-merge CI 20/20 ✅, Codex P2 fixed in `7a5987a`), #539 (PM v44, CI 22/22 ✅), #540 (back-merge duplicate, CI 20/20, Codex P2 LIVE — same README npm issue).
+- 1 open issue: #534 (P2 npm scope E404 tightening, not blocking).
+- Key finding: duplicate back-merge PRs (#537 and #540 both target Charter §5.12 Step 4). #537 is clean; #540 has live Codex P2 (same README npm install issue that #537 already fixed in commit `7a5987a`).
 
 **Actions taken:**
-1. **Merged PR #522** (PM dispatch v33, 20/20 CI ✅, Codex P1 REPLIED by founder, squash `02b71878`) ✅
-2. **Closed PR #515** as superseded by v0.2.0 (same pattern as v0.1.17→v0.1.18 supersession) ✅
-3. **Opened PR #523** (release/v0.2.0 → main): founder-cut branch, RFC-0109+RFC-0102+RFC-0110, CI running ✅
-4. **Updated PM state v36**: header, v0.1.20 section marked SUPERSEDED, v0.2.0 section added, RFC-0110 status updated, Live priorities v0.2.0, dispatch table, decision gates, archive ✅
-5. **Appended decisions.jsonl** ✅
+1. **Replied to Codex P2 on PR #540**: finding is valid; closing as superseded by #537 which carries identical fix. ✅
+2. **Closed PR #540** as superseded by #537. ✅
+3. **Squash-merged PR #537** (commit `4e60400f`) — Charter §5.12 Step 4 COMPLETE ✅
+4. **PR #539** (PM v44) conflicted after #537 back-merge advanced develop; closed as superseded by v45. ✅
+5. **PM state v45 written** + decisions.jsonl appended. ✅
 
 **Escalations to founder:**
-- **(1) P0 — v0.2.0 ceremony**: PR #523 CI running. Wait for green → merge PR #523 → push tag `v0.2.0` → create GitHub Release. Release workflow may also publish crates/npm/PyPI automatically.
-- **(2) Systemic DCO fix**: Must fix before v0.3.0 (same bug as every previous release).
-
-### 2026-06-04 PM dispatch v35 (this run — Codex P1 fixed on PR #522; PR #515 44/44 ✅)
+- **(P0)** Push tag `v0.2.0` + create GitHub Release (ceremony Steps 2+3).
+- **(P0)** Register `@aimasteracc` npm scope on npmjs.com (Issue #534).
 
-**Pre-flight:** CHARTER §2/§5.1/§5.10/§5.12/§5.13, _orchestrator.md, decisions.jsonl tail (latest: 2026-06-04T04:35Z v34 — deep DCO fix HEAD~16), anti-patterns (no new domain hits), PM state v34 (on branch v33), v0.2 PRD.
-
-**Assessment:**
-- 2 open PRs: #515 (release/v0.1.20 → main, 44/44 CI ✅ ALL GREEN, 0 Codex findings ✅ — ready for founder ceremony), #522 (chore/pm-dispatch v33, 20/20 CI ✅, **1 Codex P1 blocking merge**).
-- 0 P0/P1 issues. Latest tag: `v0.1.19`. Tags v0.1.18 + v0.1.19 exist — founder completed those ceremonies.
-- Codex P1 on PR #522 (line 190): `.github/dco.yml` recommendation is wrong — the CI gate is the custom shell script in `ci.yml` lines 205-229 (not the GitHub DCO App). Adding `.github/dco.yml` has zero effect on the actual check. This is a genuine documentation bug that would misdirect the founder.
-
-**Actions taken:**
-1. **Fixed Codex P1**: corrected the incorrect `.github/dco.yml` recommendation in 3 locations (lines 190, 209, 232) → now correctly identifies the real fix (update `dco-check` script to check full message body, OR switch `release.yml` merge to direct `git push`). ✅
-2. **Updated PM state v35**: header (44/44 CI green), v0.1.20 ceremony section (all CI confirmed green), dispatch state, decision gates, archive. ✅
-3. **Appended decisions.jsonl** with v35 summary. ✅
-
-**Escalations to founder:**
-- **(P0)** Merge PR #515 → push tag `v0.1.20` → create GitHub Release. 44/44 CI ✅, 0 Codex findings. PM will open Step 4 back-merge PR after Step 1.
-- **(P0 systemic)** DCO systemic fix: update `ci.yml` `dco-check` to grep full message body for `Signed-off-by:`, OR switch `release.yml` merge to `git push origin release/vX.Y.Z:main`.
-
-### 2026-06-04 PM dispatch v34 (this run)
-
-**Pre-flight:** PM state v33 (branch `chore/pm-dispatch-2026-06-04-v33-real`, PR #522). decisions.jsonl tail (latest: 2026-06-04T04:10Z v33 session summary). PR #515 DCO check still failing after v33's `HEAD~4` rebase — discovered 2 more unsigned commits deeper in history.
-
-**Assessment:**
-- PR #515 CI: DCO check FAILED after `HEAD~4` rebase. Root cause: `4bdc4de` (ADR-0010, HEAD~7) and `bb685def` (get_callees, HEAD~10) also lack `Signed-off-by`. `HEAD~4` only covered the top 4 commits, missing 12 earlier ones. Full range: 16 non-merge commits above `8ffcad9` (Merge PR #494, v0.1.19 → main).
-- Fix: `git rebase --signoff HEAD~16` on `fix-dco-release-v0.1.20` branch (HEAD~16 = `8ffcad9` confirmed via `git rev-parse`).
-
-**Actions taken:**
-1. **Deep DCO fix**: ran `git rebase --signoff HEAD~16` on `fix-dco-release-v0.1.20` — replayed all 16 non-merge commits. All now carry `Signed-off-by`. Force-pushed to `origin/release/v0.1.20`. ✅
-2. **DCO verified**: `git show --no-patch --format="%B" d0f6b74 | grep "Signed-off-by"` and `0bc266e` both return `Signed-off-by: Claude <noreply@anthropic.com>`. ✅
-3. **PR #515 CI re-ran**: DCO sign-off check shows `conclusion: success`. Clippy/rustfmt/unit tests/e2e in progress. ✅
-4. **PM state v34**: updated header, v0.1.20 ceremony status, Live priorities, Dispatch table, Decision gates, archive. ✅
-5. **decisions.jsonl**: appended v34 session summary. ✅
-
-**Escalations to founder:**
-- **(P0) v0.1.20 ceremony**: PR #515 DCO ✅ green. Wait for all CI green → merge PR #515 → push tag `v0.1.20` → create GitHub Release. PM opens Step 4 back-merge PR after Step 1.
-- **(P0 systemic) DCO config**: Add `.github/dco.yml` with `allowRemediationCommits: true`.
-
-### 2026-06-04 PM dispatch v33 (superseded by v34)
-
-**Pre-flight:** Read CHARTER.md §2/§5.1/§5.10/§5.12/§5.13, _orchestrator.md, decisions.jsonl tail (latest: 2026-06-04T03:12Z v32 session), anti-patterns (hits: release-governance `HEAD~2` repair depth wrong; async blocking_read; squash-merge DCO strip), PM state (v32 stale — develop at `746826d`; v32 on PR #521 open), v0.2 PRD.
-
-**Assessment:**
-- 2 open PRs: #521 (PM v32 chore, 22/22 CI ✅ on original commit — Codex P1×2 UNRESOLVED), #515 (release/v0.1.20 → main, DCO FAILURE, Quality Gate red). 0 open P0/P1 issues.
-- develop HEAD `746826d` (RFC-0110 increment 3). CI SUCCESS ✅.
-- Key findings: (a) PR #515 DCO failure — `9b51c35` and `39808637` are squash-merge commits with no valid Signed-off-by trailer (only Codex rejection text in body). (b) PR #521 has 2 Codex P1 findings: rebase depth `HEAD~2` wrong (must be `HEAD~4`); ceremony-script fallback with `git push origin main` is a DCO bypass prohibited by Charter §5.12. (c) No P0/P1 issues. (d) No Codex findings on PR #515 (0 review threads).
-
-**Actions taken:**
-1. **DCO fix on release/v0.1.20**: checked out `origin/release/v0.1.20`, ran `git rebase --signoff HEAD~4` (replays `39808637`, `9b51c35`, `bf0399a`, `1b0d7dc` — all 4 now carry `Signed-off-by: Claude <noreply@anthropic.com>`). Force-pushed with `--force-with-lease`. PR #515 CI re-triggered. ✅
-2. **Codex P1 #1 fixed on PR #521**: pushed fix commit `374bf8e` to `chore/pm-dispatch-2026-06-04-v32` correcting `HEAD~2` → `HEAD~4` in all 5 locations in PM state. Replied to Codex comment with explanation. ✅
-3. **Codex P1 #2 fixed on PR #521**: same commit `374bf8e` removes the dangerous `git push origin main` fallback section; replaced with explicit no-bypass warning. Replied to Codex comment. ✅
-4. **PM state v33**: updated header, v0.1.20 ceremony status, Live priorities, Dispatch table, Decision gates. Added this archive entry. ✅
-5. **decisions.jsonl**: appended v33 session summary. ✅
-
-**Escalations to founder:**
-- **(P0) v0.1.20 ceremony**: PR #515 CI re-running (DCO repaired). Wait for green → merge PR #515 → push tag `v0.1.20` → create GitHub Release. PM opens Step 4 back-merge PR after Step 1.
-- **(P0 systemic) DCO config**: Add `.github/dco.yml` with `allowRemediationCommits: true` to prevent squash-merge DCO stripping recurrence.
-
-### 2026-06-04 PM dispatch v32 (this run — superseded by v33)
-
-**Pre-flight:** Read CHARTER.md §2/§5.1/§5.10/§5.12/§5.13, _orchestrator.md, decisions.jsonl tail (latest: 2026-06-04T02:47Z RFC-0110 increment 3), anti-patterns (no new domain hits), PM state v28 on develop (stale — v29 in decisions but PM state file not updated), v0.2 PRD.
-
-**Assessment:**
-- 2 open PRs: #518 (PM v31 chore, 22/22 CI ✅, merge-conflict after RFC-0110 PRs #517/#519/#520 landed), #515 (release/v0.1.20 → main, DCO FAILURE + Quality Gate red). 0 open issues.
-- develop HEAD `746826d` (RFC-0110 increment 3 squash, 2026-06-04T02:56Z). CI SUCCESS ✅.
-- Key findings: (a) PR #518 had 2 Codex P1 findings — both about wrong v0.1.20 repair path (`-s ours` strategy discards release content; direct-push main bypasses release gate). (b) RFC-0110 all 3 increments COMPLETE on develop (PRs #517, #519, #520). (c) v0.1.20 DCO root cause: GitHub web UI squash-merges for PRs #508 + #513 lack `Signed-off-by`.
-
-**Actions taken:**
-1. **Replied to Codex P1 #1 on PR #518** (ours strategy): Accepted — `-s ours` discards release content; correct is `--no-ff`. ✅
-2. **Replied to Codex P1 #2 on PR #518** (direct-push bypass): Accepted — fix DCO on release branch instead. ✅
-3. **Closed PR #518** as superseded (merge conflict with decisions.jsonl from RFC-0110 PRs). ✅
-4. **Created branch `chore/pm-dispatch-2026-06-04-v32`** from develop HEAD `746826d`. ✅
-5. **Updated PM state v32**: corrected v0.1.20 repair path, added RFC-0110 complete section, updated live priorities + dispatch + decision gates. ✅
-6. **Appended decisions.jsonl** (v32 entry). ✅
-
-**Escalations to founder:**
-- **(P0) v0.1.20 ceremony**: Fix DCO on `release/v0.1.20` with `git rebase --signoff HEAD~4` (covers unsigned commits at HEAD~3 + HEAD~2). No direct-push-main fallback — fix commits, then merge through PR #515.
-- **(P0 systemic) DCO config**: Add `.github/dco.yml` to prevent recurrence.
-
-### 2026-06-04 PM dispatch v31 (PR #518 — CLOSED superseded; Codex P1×2 addressed)
-
-*(Findings: `-s ours` repair path wrong + direct-push-main bypass wrong. Both P1s accepted and fixed in v32. PR #518 closed due to merge conflict with RFC-0110 decisions.)*
-
-### 2026-06-04 PM dispatch v29–v30 (RFC-0109 tools 4–7 + v0.1.20 cut)
-
-*(v29: PRs #508+#513 merged; RFC-0109 7/7 COMPLETE on develop. v30: release/v0.1.20 cut from `bf0399a`; PR #515 opened. See decisions.jsonl entries 2026-06-04T00:08Z and 2026-06-04T01:11Z.)*
-
-### 2026-06-03 PM dispatch v28 (this run)
-
-**Pre-flight:** Read CHARTER.md §2/§5.1/§5.10/§5.12/§5.13, _orchestrator.md, decisions.jsonl tail-20, anti-patterns (domain hits: ci/testing/release-governance), PM state (v25 on disk — stale; v27 on branch), v0.2 PRD.
-
-**Assessment:**
-- 4 open PRs: #496 (ADR-0010, CI ✅), #502 (PM v26, CI ✅, Codex 2 findings), #505 (get_callers, CI ✅, Codex 1 finding), #506 (PM v27, CI ✅, Codex 1 finding).
-- 0 open issues.
-- Develop CI RED: `sla_ancestors_100k` macOS failure (32.978ms vs 30ms limit) on SHA `2c130452` (get_dead_symbols squash merge). Feature branch and PR CI had passed; failure is develop-only (loaded macOS runner, ~6× slower than Linux).
-- RFC-0109 tools 1–3 (get_callees, get_callers, get_dead_symbols) already on develop.
-- Codex findings: #496 (2 outdated), #502 (1 outdated, 1 live), #505 (1 live — stale PR), #506 (1 live — v0.1.19 content boundary error).
-
-**Actions taken:**
-1. **Diagnosed** develop CI red: macOS `sla_ancestors_100k` timing SLA flake. Bumped macOS limit 30ms → 100ms. Committed + pushed `fix/sla-ancestors-macos-flake`. **PR #508** opened (CI running). ✅
-2. **Replied to all Codex findings** (6 replies): #502 threads (1 outdated acknowledged, 1 v28 will fix), #496 threads (both outdated, fixed by `836ada4`), #505 thread (PR stale, text-mode concern addressed in merged #504), #506 thread (v0.1.19 boundary bug, v28 will fix). ✅
-3. **Merged PR #496** (docs/adr-0010-no-live-lsp, Codex all outdated, CI ✅) → squash `4bdc4de`. ✅
-4. **Closed PR #502** as superseded by v28 (merge conflict after #496 landed; Codex replies posted). ✅
-5. **Closed PR #505** as stale (develop has get_callers from #504; text-mode Codex concern resolved in merged version). ✅
-6. **Closed PR #506** as superseded by v28 (v0.1.19 content boundary error corrected in this PM state). ✅
-7. **Corrected PM state**: v0.1.19 section now has boundary note; PRs #497–#501 moved to post-v0.1.19 unreleased section. Dispatch/priorities updated. ✅
-8. **Appended decisions.jsonl**. ✅
-
-**Escalations to founder:**
-- **(1) PR #508**: Admin-merge once CI green — restores develop Quality Gate to green. Minimal 2-file change (sla_trunk.rs + CHANGELOG).
+### 2026-06-04 PM dispatch v44 (PR #535 merged; Codex P2 on #537+#538 addressed)
 
-### 2026-06-03 PM dispatch v27 (PRs #485+#486 merged; ADR numbering fix: 0008-redb-storage-engine → 0009; v0.1.18 ceremony still BROKEN pending founder)
+**Summary:** PR #535 MERGED (fix(npm): 128+signal exit code `3f812410`) → Issue #525 CLOSED. Codex P2 on PR #537 (README npm install) fixed in commit `7a5987a` (reverted to "coming soon"). Codex P2 on PR #538 (pm-state "Last shipped") corrected. PR #538 superseded by v45. v0.2.0 Step 1 ✅ confirmed (PR #523 → main 2026-06-04T10:41:45Z).
 
-*(see closed PR #506 for full archive)*
+### 2026-06-04 PM dispatch v43 (PRs #537+#538 opened)
 
-### 2026-06-03 PM dispatch v26 (PR #501 merged; PR #496 Codex fix; v0.1.17–v0.1.19 ceremonies confirmed)
+**Summary:** Back-merge PR #537 opened (Charter §5.12 Step 4). PM state correction PR #538 opened (Last shipped: v0.1.19 until Steps 2+3 complete). Ceremony Step 1 confirmed merged.
 
-*(see closed PR #502 for full archive)*
+### 2026-06-04 PM dispatch v42 (PR #533 merged; Issue #526 closed; Issue #534 created; PR #535 opened)
 
-### 2026-06-03 PM dispatch v25 (PRs #485+#486 merged; ADR numbering fix)
+*(See full archive in closed PR #539 and decisions.jsonl entries for v42.)*
 
-*(see earlier archive entries for full detail)*
+### Earlier dispatches (v1–v41)
 
-### Earlier dispatches (v1–v24)
+*(archived in older versions of this file and decisions.jsonl)*
 
-*(archived in older versions of this file)*