roadmap: #237 filed

ROADMAP.md

@@ -16435,3 +16435,11 @@ Required fix shape: (a) extend `OutputContentBlock` enum at `rust/crates/api/src
 **Status:** Open. No source code changed. Filed as ROADMAP-only dogfood pinpoint from the 2026-04-26 07:00 KST clawhip nudge after rebasing on top of #235 (gaebal-gajae's `tool_choice: image_generation` filing at 06:48 KST). Filed 2026-04-26 07:00 KST. HEAD: 476a1a4 (post-#235). Branch: feat/jobdori-168c-emission-routing. Sibling-shape cluster: 35 pinpoints. Multimodal-IO cluster: 12 members. Provider-asymmetric-delegation cluster: 12 members. **Sandbox-locality-axis META-cluster: 2 members stable (#230 + #232).** **Tool-locality-axis META-cluster: 3 members stable (#232 + #233 + #234) — #236 does NOT extend this META-cluster because no client-side music-tool-stub exists; instead #236 founds the inverse-pattern complement.** **Server-managed-tool-as-tool-choice-discriminator cluster: 4 members stable (#232 + #233 + #234 + #235) — #236 does NOT extend this cluster because no major-provider canonical music-generation tool_choice surface exists upstream.** **Async-task-polling cluster grows to 4 members (#221 + #227 + #228 + #236) — first member where polled-resource is exclusively-third-party-routed.** **Multi-domain-multipart cluster grows to 3 members (#225 + #227 + #236).** **Zero-overlap-with-major-providers-exclusively-third-party-partner-set-shape cluster: 1 member (founder, FIRST exclusively-third-party-partner-set variant).** **Lyrics-plus-style-prompt-bifurcation-on-USER-INPUT-side cluster: 1 member (founder).** **Multi-modal-bundled-output-with-temporal-binary-AND-linguistic-text-AND-structural-musical-data-on-output-side cluster: 1 member (founder).** **Multi-track-stems-decomposition-on-output-side cluster: 1 member (founder).** **Symbolic-music-notation-output-discriminator cluster: 1 member (founder, FIRST cluster member where same endpoint family emits BOTH binary-media AND symbolic-structured-notation).** **Vocals-vs-instrumental-toggle-with-vocal-gender-and-voice-cloning-id cluster: 1 member (founder).** **Section-aware-music-extension-on-USER-INPUT-side cluster: 1 member (founder).** **Copyright-and-attribution-metadata-on-output-side cluster: 1 member (founder).** **Structural-musical-metadata-on-output-side cluster: 1 member (founder).** **Music-specific-seven-state-task-state-machine-with-modality-specific-blocking-states cluster: 1 member (founder).** **Multi-domain-multipart-form-data-with-binary-audio-and-text-lyrics-on-USER-INPUT-side cluster: 1 member (founder).** **Eleven-plus-axis-music-generation-request-side-opt-in cluster: 1 member (founder, LARGEST request-side opt-in axis-set).** **Per-clip-AND-per-segment-AND-per-minute-AND-per-character-of-lyrics-compound-pricing-axis cluster: 1 member (founder, SEVEN-dimensional pricing model — LARGEST yet).** **Upstream-blocked-tool-choice-extension cluster: 1 member (founder, FIRST cluster member where natural follow-on tool_choice lane is contingent on upstream emergence).** **Unilateral-server-side-only-gap-with-no-client-side-complement cluster: 1 member (founder, INVERSE-PATTERN of Tool-locality-axis META-cluster doctrine).** Fifteen new clusters founded in a single pinpoint plus participation in FIVE inherited clusters — exceeds #234's thirteen-cluster-founding count by two, the LARGEST single-cycle cluster-founding count yet, AND the FIRST single cycle to found a cluster that REPRESENTS THE INVERSE-PATTERN of an existing META-cluster (Unilateral-server-side-only-gap inverts Tool-locality-axis META-cluster's bilateral inverse-locality-pair shape). Twelve-layer-fusion-shape with exclusively-third-party-partner-set is novel within the cluster. Distinct from prior cluster members; the twelve-layer-fusion-shape-with-zero-overlap-with-major-providers-and-lyrics-plus-style-prompt-bifurcation-and-multi-modal-bundled-output-and-music-specific-seven-state-task-state-machine is novel. #236 closes the upstream prerequisite of every music-generation / song-extension / song-inpaint / multi-track-stems-export / symbolic-music-MIDI-export / lyrics-driven-vocal-synthesis / instrumental-only-generation / mood-and-genre-driven-music-composition / collaborative-music-remix / soundtrack-generation-for-coding-projects / podcast-intro-music-generation / video-game-music-composition / film-score-prototyping / audio-branding-for-products / accessibility-narration-with-music-bed coding-agent affordance — the canonical FIRST `Zero-overlap-with-major-providers-exclusively-third-party-partner-set-shape` cluster member that establishes the inverse-pattern of the Tool-locality-axis META-cluster doctrine where the gap is unilateral-server-side without client-side complement.
 
 🪨
+
+## Pinpoint #237 — Cron dogfood timeout failure collapses partial execution state into one opaque chat error
+
+Dogfooded 2026-04-26 07:30 KST on `feat/jobdori-168c-emission-routing` from the live nudge stream. Immediately before the 07:30 KST clawhip nudge, the channel emitted `Cron job "clawcode-dogfood-cycle-reminder" failed: cron: job execution timed out` with no structured run-attempt id, no started-at/deadline/timed-out-at timestamps, no last-output tail, no partial-progress marker, no active worktree/session pointer, no commit/head observed by the timed-out run, no indication whether the timeout happened before prompt delivery, during ROADMAP mutation, during git push, or during report-posting, and no machine-readable retry/duplicate/continuation contract binding the later successful #236/#237-style report back to the timed-out attempt.
+
+Verified gap shape in repo context: existing roadmap sections 4.10 through 4.24 describe nudge dedupe, report atomicity, no-op acks, staleness, negative evidence, field-level deltas, and schema versioning as desired contracts, but the concrete cron-timeout failure mode still has no first-class run-attempt artifact in the dogfood reporting surface. Current runtime/CLI code has heartbeat/progress lines and post-tool stall handling, but there is no `CronRunAttempt` / `DogfoodRunAttempt` / `TimedOutRunReport` schema that downstream claws can parse after a watchdog timeout. The chat surface therefore compresses a high-value operational failure into a single lossy sentence, forcing humans/claws to infer whether to retry, ignore as duplicate, resume an in-progress branch, or audit for a half-written ROADMAP entry.
+
+Required fix shape: (a) every scheduled dogfood run gets a stable `run_attempt_id` plus `nudge_id`/cycle id; (b) the runner writes an append-only attempt ledger before first side effect and updates it at phase boundaries (`received_nudge`, `checked_repo_head`, `selected_pinpoint`, `mutated_roadmap`, `committed`, `pushed`, `reported`); (c) timeout reports include phase, deadline, elapsed time, last stdout/stderr tail, repo/worktree/head, pending side effects, and whether a retry is safe/idempotent; (d) a later retry/report links to the timed-out attempt as `continues`, `supersedes`, or `duplicate_of`; (e) channel output renders a compact human summary but exposes the structured payload for clawhip/Jobdori/other claws. Acceptance: a future `cron: job execution timed out` message is enough to answer `what was the last completed phase`, `did it mutate ROADMAP or push`, `should another claw file a new pinpoint or just resume`, and `which report eventually closed the timed-out attempt` without scraping terminal scrollback or guessing from adjacent chat messages. **Status:** Open. No source code changed. Filed as ROADMAP-only dogfood pinpoint from the 2026-04-25 22:30 UTC claw-code nudge, grounded in the immediately preceding timeout event. Cluster delta: operational-clawability +1, event/log-opacity +1, cron-run-attempt-ledger cluster founded, timeout-resume-idempotency cluster founded, report-provenance/atomicity cluster linked to existing 4.10–4.24 reporting-contract roadmap items.