Files
pipdock/docs
poli0981andClaude Opus 5 465b54f7e8 docs: close M1, and correct the M2 estimate against what the bridge actually is
ROADMAP said L2 "has never run". It had, three times, failing each time; record
what failed and why, since both causes were in the harness rather than the product
and neither is obvious from the job name.

M2 was estimated at 3-4 weeks. Surveying the code for it shows the bridge is
scaffolding: ui/src/ipc/index.ts fixes 26 command *names* with zero wrappers,
src-tauri registers exactly one command (app_info, a smoke test), and 2 of 16 Pd*
components, 1 of 5 Zustand stores and 2 of 14 locale catalogs exist. Scope is
unchanged; the estimate moves to 7-8 weeks to match it, and three pieces with no
home in the core yet are named so they get sequenced before the screens rather
than discovered during them:

  - the flow layer, since plan_and_run is ~200 lines of DATA-FLOW section 3 living
    only in the CLI, and duplicating it would mean two implementations of the hard
    invariants
  - cancellation, which does not exist at all -- plan_cancel is a declared TS name
    with no Rust counterpart, and exec.rs's watchdog drops the future rather than
    killing the child
  - progress, where ProgressEvent.step is hardcoded 0 at all four producers and
    scan-progress has no producer

Also: ARCHITECTURE section 10 still said uv "0.9.x line, minimum pinned after
SP-1" when SP-1 pinned 0.10.0 and shipped it as UV_MIN_VERSION; CLAUDE.md said
"Status: Phase 0" three lines above a paragraph saying M1 was substantially
complete; and the fixture redaction now needs recording under "things that look
like bugs but are not", because "these are not literal engine bytes" is exactly
the kind of thing someone will otherwise try to helpfully undo.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
2026-07-29 20:26:01 +07:00
..
2026-07-27 17:08:14 +07:00