Summary
Replace large peer mutation responses with a bounded receipt while preserving intentional retrieval through workflow-read and result paths.
Evidence
Mutation responses repeated full workflow, brief, and memo payloads at roughly 170–382 KiB; aggregate status reached roughly 953 KiB. Large stdout re-enters parent context and contributed to transport fragility.
Desired outcome
Peer mutations return a shared receipt below 2 KiB and never echo brief, memo, checkpoint, or final payloads.
Acceptance criteria
- Use a shared receipt containing workflowId, mode, revision, epoch, status, phase, target, and optional payloadSha256.
- Keep receipts below 2 KiB.
- Peer-final results are read through $cc:result or workflow-read.
- Create and resume retain plans and diagnostics with only a workflow header in stdout.
- Existing stored v1.7.x shapes remain readable.
Severity/release disposition
High transport and context-amplification risk; mandatory v1.7.4 scope.
Provenance
Confirmed by the v1.7.4 reliability audit of peer mutation and status output sizes.
Summary
Replace large peer mutation responses with a bounded receipt while preserving intentional retrieval through workflow-read and result paths.
Evidence
Mutation responses repeated full workflow, brief, and memo payloads at roughly 170–382 KiB; aggregate status reached roughly 953 KiB. Large stdout re-enters parent context and contributed to transport fragility.
Desired outcome
Peer mutations return a shared receipt below 2 KiB and never echo brief, memo, checkpoint, or final payloads.
Acceptance criteria
Severity/release disposition
High transport and context-amplification risk; mandatory v1.7.4 scope.
Provenance
Confirmed by the v1.7.4 reliability audit of peer mutation and status output sizes.