roadmap: #239 filed

ROADMAP.md

@@ -16488,3 +16488,11 @@ Required fix shape: (a) every scheduled dogfood run gets a stable `run_attempt_i
 **Status:** Open. No source code changed. Filed 2026-04-26 07:30 KST. HEAD: 3f41341 (post-#237 fast-forward-rebase after gaebal-gajae's parallel cron-timeout-failure-state-collapse pinpoint at 07:31 KST). Branch: feat/jobdori-168c-emission-routing. Sibling-shape cluster: 36 pinpoints. Multimodal-IO cluster: 13 members. Provider-asymmetric-delegation cluster: 13 members. Persistent-WebSocket-transport cluster: 2 members (#229 + #238 — FIRST expansion). ToolResultContentBlock-extension mini-cluster: 6 members. **Cross-pinpoint-synthesis-fusion-shape META-cluster: 1 member (founder, THIRD distinct META-cluster founding pattern).** Ten new clusters founded plus one NEW META-cluster founded — the THIRD largest single-cycle cluster-founding count, but the FIRST single cycle where the META-cluster is founded by cross-axis-synthesis rather than new-axis-pair-introduction. Twelve-layer-fusion-shape-with-cross-pinpoint-synthesis is novel within the cluster. **#238 closes the upstream prerequisite of every multi-participant voice-driven coding-agent affordance** (call-center voice-of-customer transcription, podcast/meeting transcription with speaker-tagged transcripts, voice-driven multi-user collaborative-coding sessions, accessibility-real-time-captioning with speaker-attribution, legal/courtroom transcription, sermon/lecture transcription, voice-message-transcription with multi-speaker-thread-reconstruction) — the canonical 2024-2026-era multi-speaker voice workflow that is currently impossible to build on top of claw-code DESPITE Deepgram nova-3 / AssemblyAI Universal-1 / Speechmatics realtime / Soniox / six-plus other providers all shipping streaming-STT-with-diarization as flagship 2024-Q3-or-later GA capabilities AND DESPITE every voice-driven-coding-agent peer in the surveyed ecosystem (anomalyco/opencode + Cursor + claudecode-voice + Aider + simonw/llm + continue.dev) shipping streaming-STT-with-diarization as first-class typed surface. The cross-pinpoint-synthesis META-pattern means future cluster expansion can SYNTHESIZE existing axes rather than always introducing new axes, opening a combinatorial follow-on space (#225 × #229 = #238 streaming-STT-with-diarization, #229 × #232/#233/#234/#235 = #239 candidate realtime tool-use, #220 × #225 = #240 candidate visual-grounded-voice-input where image+audio-frame are streamed together, #225 × #227 = #241 candidate audio-grounded-video-generation where audio narration drives video generation, etc) — establishing combinatorial-cross-axis-synthesis as the THIRD pinpoint-discovery-mode after new-axis-founding and existing-cluster-extension.
 
 🪨
+
+## Pinpoint #239 — Concurrent dogfood writers have no branch lease / append reservation contract, forcing repeated manual fast-forward rebases
+
+Dogfooded 2026-04-26 08:00 KST on `feat/jobdori-168c-emission-routing` after two consecutive cross-claw interleavings: gaebal-gajae filed #237 on top of Jobdori #236, then Jobdori explicitly reported rebasing onto `3f41341` before filing #238, and this cycle had to fast-forward local from `3f41341d` to `716d17e2` before doing any safe write. This worked only because everyone manually fetched/pulled before appending. The workflow has no machine-readable branch lease, append reservation, expected-parent precondition, or stale-worktree refusal contract for ROADMAP-only dogfood writers sharing one long-lived branch.
+
+Verified concrete surface: `CronRegistry` tracks only `last_run_at` and `run_count` (runtime `team_cron_registry.rs`) and has no per-run/branch/write lease. ROADMAP sections already describe nudge/report dedupe and report atomicity, but there is no `roadmap_append_intent { base_head, expected_next_id, writer_id, lease_expires_at }` artifact, no compare-and-swap check before appending `## Pinpoint #NNN`, no canonical `behind_origin` refusal payload, no auto-rebase-and-renumber protocol when two claws choose the same next id, and no post-push verification event that binds the pushed commit to the lease. Current safety is social: each claw happens to run `git pull --ff-only`; a timeout, stale pane, or prompt-misdelivery could still append a duplicate id, push a non-FF failure, or report a commit that was never accepted upstream.
+
+Required fix shape: (a) before mutating ROADMAP, emit/acquire a `DogfoodWriteLease` containing branch, base_head, expected_parent, expected_next_pinpoint_id, writer, nudge_id, and expiry; (b) append code refuses to write if local HEAD != remote HEAD or if expected next id changed; (c) if remote advanced, the runner performs an explicit rebase/renumber step and records `rebased_from`/`rebased_to`; (d) push requires `--force-with-lease`-style expected remote OID even for append-only branches, with failure reported as structured `stale_branch` rather than generic git noise; (e) final report includes lease id, base head, pushed head, and whether the write was first-attempt or rebased continuation. Acceptance: concurrent Jobdori/gaebal-gajae dogfood cycles can safely append to the same ROADMAP branch without relying on terminal folklore, and clawhip can distinguish `new pinpoint filed`, `stale branch refused`, `rebased continuation`, and `duplicate id prevented` from structured state. **Status:** Open. No source code changed. Filed as ROADMAP-only dogfood pinpoint from the 2026-04-25 23:00 UTC nudge. Cluster delta: stale-branch-confusion +1, concurrent-dogfood-coordination +1, branch-lease/append-reservation cluster founded, expected-parent push-provenance cluster founded; linked to #237 timeout-run-attempt ledger because both require durable attempt ids and phase/state provenance.