[witbrock]

Merge decision: ready for code publication — the existing worker launch path exposes private task-linked activity before exit and a verified downloadable archive after exit in a bounded canonical-service fixture. Live activation and the two selected historical backfills remain an operator handoff; this PR does not establish that recording is already active on the DGX.

User outcome

JVNAUTOSCI-2751: delegated coding tasks gain a private run history and readable/downloadable execution record instead of only host paths and a final prose result.

Material changes

• Register attempts independently of tasks; publish ordered, retry-safe batches through the existing controller wait loop and canonical blob storage.
• Reconcile terminal JSONL/companion files into a versioned ZIP manifest with original/exported hashes and byte counts, event counts, thread and execution provenance, missing-source accounting, redactions and exposed-summary availability.
• Keep coding outcomes when capture is pending; retry finalisation on the existing controller schedule without repeating coding. Preserve current work products and existing evidence.
• Add private actor/org/source-scoped read routes and an inert task-panel activity viewer. Ordinary task visibility does not grant transcript access; reassigned/cancelled tasks receive no new attachment.
• Provide bounded, explicit task/run backfill without session discovery, new agents or additional model calls.

The new read boundary prevents a concrete disclosure: normal attachment upload grants organisation visibility, while coding records may contain private conversation context. Run reads/downloads instead retain the original authorised audience and recheck source access.

Evidence

• 81 targeted backend/controller/release/route tests passed. An actual launch() fixture subprocess exposes records through the Flask task route before exit, then the requester downloads the reconciled ZIP. Coverage includes large outputs, partial lines, finalisation retry, source corruption, redaction, source-access revocation, reassignment, legacy-header denial and real Flask-session/trusted-controller context resolution.
• 13 affected frontend tests passed (4 suites).
• Playwright desktop/mobile fixture passed: inert source text, no horizontal overflow, running/final refresh, window-scoped download and clearing on scope change. This is an isolated UI fixture, not public authentication acceptance.
• Ruff and diff checks passed. Frontend static lint has no errors; three existing taskPanel unused-catch warnings remain.
• 1,000 events use three run-record writes: registration, one batch, final reference.

Ship boundary

The bounded worker-path fixture and targeted scope/recovery checks support this code merge. Silent loss/corruption, audience expansion, duplicate/reassigned attachment or false archive completion would block it.

Live controller/backend/UI activation, shared blob-store read-back and the requested selected backfills remain outstanding. The retained DGX browser bridge points at another checkout and requires operator retargeting for authenticated candidate acceptance. Jira connector access failed with reauthentication required, so delivery status must be reconciled by the coordinator.

No hidden reasoning is extracted or decrypted. Summaries are preserved only when emitted in the exec stream. No supported bounded rollout export is configured; raw session rollouts are not collected. Oversized capture remains explicitly pending with local originals retained. Broad historical import, a new polling schedule and unrelated deployment are outside this change.