diff --git a/.hive/memory/decisions.jsonl b/.hive/memory/decisions.jsonl
index e508dc3e..b7451b25 100644
--- a/.hive/memory/decisions.jsonl
+++ b/.hive/memory/decisions.jsonl
@@ -295,3 +295,5 @@
 {"ts":"2026-06-19T09:05:00Z","agent":"orchestrator","action":"pm-dispatch","dispatch":"v307","decision":"PM dispatch v307 (2026-06-19): (1) Pre-flight complete: CHARTER §2/§5.1/§5.10/§5.12/§5.13, _orchestrator.md, decisions.jsonl tail-20 (v306 last, 294 lines), anti-patterns (ci/release-governance/merge-discipline/dco/git-workflow), PM state v306 (develop HEAD 53be8c29), v0.2 PRD. (2) Assessed 3 open PRs: #917 (v306 chore, CI 20/20 ✅, Codex P1 found), #763 (DRAFT RFC-0121, founder gate), #568 (release/v0.3.0, 50/50 ✅, finalize pending ×164). 1 open P1 issue: #829 (mutation rate, resolves after #568). Develop CI ✅ GREEN. (3) Addressed Codex P1 on PR #917 before merge: P1 (DCO false-positive — commit 41ac4a8 not in PR; both actual commits 267fa4dc+3864cca7 carry Signed-off-by; DCO CI job 82310180252 ✅; same phantom-SHA pattern as PR #915) — REJECTED with justification reply posted. (4) Merged PR #917 squash 53be8c29 to develop. (5) Created chore/pm-state-v307: header v306→v307, PR #568 escalation ×164→×165, PR #917 added to Recently Merged, v307 archive entry, this decisions entry (294→295 lines). (6) PR #918 opened (this chore).","rationale":"PR #917 was CI-green (20/20) and all Codex findings addressed per Charter Hard Rule before merge. P1 DCO finding is well-documented false-positive pattern (phantom SHA from pre-push intermediate commit; DCO CI gate passes; squash carries trailer). PR #568 remains the only unblock path for v0.3.0 ceremony — now ×165 escalations over 15+ days, all prerequisites confirmed met, one founder step remaining (finalize workflow_dispatch).","ref":"PR#917,PR#568,PR#763,Issue#829,Charter§5.12","artifacts":{"pr_merged":"917 (squash 53be8c29, CI 20/20 ✅)","codex_findings_addressed":1,"escalation_count":165,"pm_state":"v307","develop_ci":"GREEN","open_prs":["568 (release/v0.3.0, finalize pending — founder gate, ×165 escalations, 15+ days)","763 (DRAFT RFC-0121, founder gate)"],"issues_tracked":["829 (resolves after #568 ceremony)"],"decisions_lines":"294→295"}}
 {"ts":"2026-06-19T09:45:00Z","agent":"orchestrator","action":"pm-dispatch","decision":"PM dispatch v308 (2026-06-19): (1) Pre-flight complete: CHARTER §2/§5.1/§5.10/§5.12/§5.13, _orchestrator.md, decisions tail-20, anti-patterns, PM state v307, v0.2 PRD. (2) GitHub state: 2 open PRs (#568 release/v0.3.0 — CI 50/50 ✅, crates+npm+PyPI published, finalize SKIPPED; #763 RFC-0121 DRAFT — founder approval needed); 1 open issue (#829 P1 mutation kill-rate, fix in release/v0.3.0 via PR #861); develop CI ✅ GREEN (2026-06-19T09:31). (3) RFC-0119 fully Implemented: all AC-1–AC-18 satisfied, AC-12 gerund expansion + AC-13 dogfood transcript shipped in PR #912 (MERGED 2026-06-19). (4) Sprint queue EMPTY: RFC audit (v292) confirmed RFCs 0112–0126 all Implemented or governance-Draft; no code work pending. (5) PR #568: ×166 escalations over 15 days — critical founder action required. (6) PM state updated to v308; decisions.jsonl appended.","rationale":"Develop CI green, sprint queue empty, only blocker is founder triggering finalize workflow_dispatch on release/v0.3.0. All prerequisites satisfied: crates.io + npm + PyPI published 2026-06-14; CI 50/50 ✅. Escalation ×166 recorded for audit trail. No autonomous code path available.","ref":"PR#568,PR#763,issue#829,RFC-0119,Charter§5.12","artifacts":{"pr_v308_state":"pending (chore/pm-state-v308)","escalations":"×166 on PR #568","sprint_queue":"EMPTY","develop_ci":"GREEN","rfc_0119":"Implemented (AC-1–AC-18 ✅)"}}
 {"ts":"2026-06-19T10:30:00Z","agent":"orchestrator","action":"pm-dispatch","dispatch":"v308","decision":"CORRECTION: v308 decisions entry (line 296, ts 2026-06-19T09:45:00Z) lacked dispatch:\"v308\" field present in v305–v307 entries (Codex P2 finding PRRT_kwDOSq56sc6KzTA9 on PR #919). This corrective entry carries the marker for searchability per append-only discipline (Charter §5.3). See prior v308 entry at 2026-06-19T09:45:00Z for full decision content.","rationale":"decisions.jsonl is append-only (Charter §5.3) — in-place edit is forbidden. Corrective entry is the standard resolution pattern (precedent: v305 corrective entry at 2026-06-19T07:26:00Z for the same pattern). The dispatch marker enables grep-based lookup of all v308 records.","ref":"PR#919,Codex-PRRT_kwDOSq56sc6KzTA9,Charter§5.3"}
+{"ts":"2026-06-19T11:00:00Z","agent":"orchestrator","action":"pm-dispatch","dispatch":"v309","decision":"PM dispatch v309 (2026-06-19): (1) Pre-flight complete: CHARTER.md §2/§5.1/§5.10/§5.12/§5.13, _orchestrator.md, decisions.jsonl tail-5 (v308 corrective last, 297 lines), anti-patterns (ci/release-governance/merge-discipline/dco/git-workflow), PM state v308 (develop HEAD b619078), v0.2 PRD. (2) GitHub state: 2 open PRs (#568 release/v0.3.0 — CI 50/50 ✅, crates+npm+PyPI published, finalize SKIPPED; #763 RFC-0121 DRAFT); 1 open P1 issue (#829 mutation kill-rate, fix in release/v0.3.0 via PR #861); develop CI ✅ GREEN (2026-06-19T10:40Z). (3) Codex on PR #919 (v308 chore): 5 review threads found — all addressed within the v308 session in commit 9c5fb3e; vacuously satisfied, no new action needed. (4) Sprint queue: EMPTY — confirmed (RFCs 0112–0126 all Implemented or governance-Draft). (5) PR #568: ×167 escalations over 15+ days — critical founder action required (one step: trigger finalize workflow_dispatch on release/v0.3.0). (6) PM state updated v308→v309; PR #919 added to Recently Closed; v309 archive entry added. (7) decisions.jsonl appended (297→298 lines). (8) PR #920 opened (this chore). (9) PushNotification sent to founder.","rationale":"Sprint queue empty, develop CI green, no autonomous work available. Single founder action (finalize workflow_dispatch on release/v0.3.0) unblocks: v0.3.0 ceremony, Issue #829 P1 mutation kill-rate, and PR #763 review cycle. Escalation ×167 over 15+ days warrants founder notification.","ref":"PR#568,PR#763,PR#919,issue#829,Charter§5.12","artifacts":{"pr_merged_by_v308":"919 (squash b619078)","codex_on_919":"5 findings, all addressed in 9c5fb3e within v308 session","escalation_count":167,"pm_state":"v309","develop_ci":"GREEN","open_prs":["568 (release/v0.3.0, finalize pending — founder gate, ×167 escalations, 15+ days)","763 (DRAFT RFC-0121, founder gate)"],"issues_tracked":["829 (P1, resolves after #568 ceremony)"],"decisions_lines":"297→298"}}
+{"ts":"2026-06-19T11:15:00Z","agent":"orchestrator","action":"pm-dispatch","dispatch":"v309","decision":"CORRECTION: v309 rationale (line 298) incorrectly stated 'Single founder action (finalize workflow_dispatch on release/v0.3.0) unblocks: v0.3.0 ceremony, Issue #829 P1 mutation kill-rate, and PR #763 review cycle.' PR #763 (RFC-0121 Charter §2 amendment) is INDEPENDENTLY founder-gated — requires founder to mark Draft → Ready for Review, which is a separate action unrelated to the #568 finalize. The #568 finalize does NOT unblock #763. Both are open parallel P0 founder gates. Corrected understanding: (1) #568 finalize → unblocks v0.3.0 ceremony + Issue #829; (2) #763 undraft → unblocks RFC-0121 review cycle. These are independent steps.","rationale":"decisions.jsonl is append-only (Charter §5.3) — in-place edit of line 298 is forbidden. Corrective entry is the standard resolution pattern (precedent: v305 at 2026-06-19T07:26:00Z, v308 corrective at 2026-06-19T10:30:00Z). Codex P2 finding PRRT on PR #920 correctly identified the logical error. Future PM dispatches must treat PR #763 as a separate P0 founder gate that escalates independently of PR #568.","ref":"PR#920,PR#568,PR#763,Codex-P2,Charter§5.3"}
diff --git a/docs/sprints/2026-Q2-pm-state.md b/docs/sprints/2026-Q2-pm-state.md
index 54fae71f..6b3332bd 100644
--- a/docs/sprints/2026-Q2-pm-state.md
+++ b/docs/sprints/2026-Q2-pm-state.md
@@ -3,7 +3,7 @@
 This file is the **live state** of the PM brain, updated every dispatch.
 For historical sprints, see `docs/sprints/` archives.
 
-**Last updated: 2026-06-19 (PM dispatch v308 — PR #918 MERGED `f92e111` v307 PM chore; RFC-0119 Implemented (all AC-1–AC-18 ✅ incl. AC-12 gerund expansion + AC-13 dogfood transcript via PR #912); sprint queue empty (all RFCs 0112–0126 Implemented or governance-Draft); PR #568 escalation ×166; develop CI ✅ GREEN)**
+**Last updated: 2026-06-19 (PM dispatch v309 — PR #919 MERGED (v308 PM chore, Codex 5/5 addressed in `9c5fb3e` within the v308 session); sprint queue empty; PR #568 escalation ×167; develop CI ✅ GREEN)**
 
 ---
 
@@ -21,14 +21,14 @@ For historical sprints, see `docs/sprints/` archives.
 
 These items cannot proceed without explicit founder action.
 
-### PR #568 — ×166 Escalation (CRITICAL)
+### PR #568 — ×167 Escalation (CRITICAL)
 
 - **Status**: OPEN — awaiting founder `finalize` workflow_dispatch or explicit "close as won't fix"
-- **Escalation count**: ×166 (escalated in v308)
+- **Escalation count**: ×167 (escalated in v309)
 - **What it is**: release/v0.3.0 — Node/Python SDKs (RFC-0111) + RFC-0103/0094. Registries published (crates.io + npm + PyPI ✅) since 2026-06-05/2026-06-14.
 - **Release branch HEAD**: `f14f80df` (nightly.yml fix from PR #861). **CI CONFIRMED 50/50 ✅ as of 2026-06-14T21:19Z** — re-verified in v291 dispatch.
 - **Ceremony path — ALL PREREQUISITES CONFIRMED MET (v291 correction)**: v291 directly queried PR #568 check runs and confirmed: `publish to crates.io` ✅ SUCCESS, `publish to npm` ✅ SUCCESS, **`publish to PyPI` ✅ SUCCESS** (2026-06-14T21:19:36Z). The `merge to main, tag, GitHub Release` job is **SKIPPED** (awaiting finalize). **NO remaining prerequisites** — the stale "PyPI Trusted Publisher" prerequisite mentioned in v268–v290 has been satisfied (PyPI was published 2026-06-14). Founder needs only to **trigger `finalize` workflow_dispatch on release/v0.3.0**.
-- **⚠️ MILESTONE**: ×166 escalations over 15 days (since 2026-06-04). Hive has no autonomous path forward on ceremony. Sprint queue is now empty (all RFCs 0112–0126 Implemented). **Founder action is the only remaining v0.3.0 release ceremony unblock — one step: trigger `finalize` workflow_dispatch on branch `release/v0.3.0`.** (PR #763 RFC-0121 Charter amendment is separately founder-gated and independent of the ceremony.)
+- **⚠️ MILESTONE**: ×167 escalations over 15 days (since 2026-06-04). Hive has no autonomous path forward on ceremony. Sprint queue is empty (all RFCs 0112–0126 Implemented). **Founder action is the only remaining v0.3.0 release ceremony unblock — one step: trigger `finalize` workflow_dispatch on branch `release/v0.3.0`.** (PR #763 RFC-0121 Charter amendment is separately founder-gated and independent of the ceremony.)
 
 ### PR #763 — RFC-0121 DRAFT
 
@@ -52,6 +52,11 @@ These items cannot proceed without explicit founder action.
 
 ## Recently Closed / Merged
 
+### PR #919 — MERGED `b619078` (v308 PM state chore → develop)
+
+- **Merged at**: 2026-06-19 (v309)
+- **What it was**: PM dispatch v308 state chore — RFC-0119 Implemented confirmed (all AC-1–AC-18 ✅); sprint queue empty; PR #918 MERGED `f92e111` (v307 chore); PR #568 escalation ×165→×166. Codex posted 5 review threads (all P2): (1) v308 archive entry missing — **fixed** in `9c5fb3e`; (2) PR #918 escalation delta wrong — **fixed** in `9c5fb3e`; (3) PR #918 Codex detail wrong — **fixed** in `9c5fb3e`; (4) decisions.jsonl v308 dispatch marker missing — **fixed** via append in `9c5fb3e`; (5) milestone text missing PR #763 qualifier — **fixed** in `9c5fb3e`. All 5 addressed before merge. CI 22/22 ✅.
+
 ### PR #918 — MERGED `f92e111` (v307 PM state chore → develop)
 
 - **Merged at**: 2026-06-19 (v308)
@@ -328,6 +333,32 @@ All dispatches from v129 onward are archived below. Earlier dispatches (v1–v12
 
 ---
 
+### 2026-06-19 PM dispatch v309
+
+**PR #919 MERGED `b619078` (v308 PM chore, CI 22/22 ✅, Codex 5/5 fixed in `9c5fb3e` within v308 session). PR #920 opened (this chore). PR #568 escalation ×166→×167. Sprint queue empty. Develop CI ✅ GREEN.**
+
+**Pre-flight:** CHARTER.md §2/§5.1/§5.10/§5.12/§5.13, _orchestrator.md, decisions.jsonl tail-5 (v308 corrective last, 297 lines), anti-patterns (ci/release-governance/merge-discipline/dco/git-workflow), PM state v308 (develop HEAD `b619078`), v0.2 PRD.
+
+**Assessment:**
+- 2 open PRs: #568 (release/v0.3.0, 50/50 ✅, finalize pending ×166→×167), #763 (DRAFT RFC-0121, founder gate)
+- 1 open P1 issue: #829 (mutation kill rate, resolves after #568 ceremony)
+- Develop CI: ✅ GREEN (HEAD `b619078` = post-#919 merge, CI at 2026-06-19T10:40Z)
+- Sprint queue: EMPTY (all RFCs 0112–0126 Implemented or governance-Draft)
+- Codex on PR #919: all 5 findings addressed within the v308 session (`9c5fb3e`) — vacuously satisfied, no new action required
+
+**Actions:**
+1. Pre-flight read complete ✅
+2. Assessed GitHub state: 2 open PRs, 1 P1 issue, Codex on #919 all addressed ✅
+3. Updated PM state v308→v309: escalation ×167 (heading + count + milestone), PR #919 in recently merged ✅
+4. Appended decisions.jsonl v309 entry (297→298 lines) ✅
+5. PR #920 opened (this chore) — CI queued ✅
+
+**Escalations to founder:**
+- **(1) PR #568**: Trigger `finalize` workflow_dispatch on `release/v0.3.0` → completes v0.3.0 ceremony. ×167 escalations over 15+ days. One step. All registries (crates.io + npm + PyPI) already published. CI 50/50 ✅.
+- **(2) PR #763**: Mark DRAFT → "Ready for Review" to unblock RFC-0121 Charter §2 amendment review. Independent of v0.3.0 ceremony.
+
+---
+
 ### 2026-06-19 PM dispatch v308
 
 **PR #918 MERGED `f92e111` (v307 PM chore, CI 20/20 ✅, Codex P1+P2×2 addressed). RFC-0119 Implemented (all AC-1–AC-18 ✅). Sprint queue empty (RFCs 0112–0126). PR #568 escalation ×165→×166. PR #919 opened (this chore). Develop CI ✅ GREEN.**