Summary
Implement honest prompt-budget controls for full/summarized upstream transcript use.
Source Context
Why This Exists
- Phase 1 splits execution-authoritative transcripts from bounded canvas display, but it intentionally leaves prompt-budget controls narrow.
- The proposal says Phases 1 and 2 together carry the full 'remove the silent truncation' promise: Phase 2 makes expanded upstream context safe by validating prompt size before dispatch.
- The review notes the Phase 1 parser only accepts
'full' | 'summarize'; this issue should finish the planned { maxChars: N } object form and CLI/DAG precedence model instead of leaving authors with a vague rejection.
Acceptance Criteria
Verification
pnpm -F @flatbread/proof test
pnpm -F @flatbread/proof typecheck
pnpm verify
Related Phase Issues
Artifact Linkage
This issue is linked back from docs/proposals/proof-output-retention-plan.md and, where relevant, docs/proposals/proof-output-retention-review.md so the repo artifacts and GitHub issues remain navigable in both directions.
Summary
Implement honest prompt-budget controls for full/summarized upstream transcript use.
Source Context
Why This Exists
'full' | 'summarize'; this issue should finish the planned{ maxChars: N }object form and CLI/DAG precedence model instead of leaving authors with a vague rejection.Acceptance Criteria
DAG.outputPolicyvalidation to supportupstream: 'full' | 'summarize' | { maxChars: number }plusmaxPromptChars.agent.send(stitched); overflow marks the taskBUDGET-EXCEEDEDand names parent contribution sizes.--output-policy-upstream <full|summarize|maxChars:N>and--max-prompt-chars <N>with documented DAG-vs-CLI precedence.EXIT_BUDGET_EXCEEDED = 4path and preserve downstream skip behavior for budget-exceeded parents.Verification
pnpm -F @flatbread/proof testpnpm -F @flatbread/proof typecheckpnpm verifyRelated Phase Issues
Artifact Linkage
This issue is linked back from
docs/proposals/proof-output-retention-plan.mdand, where relevant,docs/proposals/proof-output-retention-review.mdso the repo artifacts and GitHub issues remain navigable in both directions.