Skip to content

Proof output retention Phase 5: documentation and skill refresh #204

@tonyketcham

Description

@tonyketcham

Summary

Finish the operator-facing README/SKILL refresh once the remaining output-retention phases land.

Source Context

Why This Exists

  • PR docs: plan proof output retention #199 pulled forward some documentation updates for Phase 1, but the proposal's full Phase 5 is broader and depends on Phase 2 CLI flags and Phase 4 oracle evidence behavior.
  • The docs need to explain where each output surface lives after the whole project completes: execution transcripts, prompt policy, canvas display tails, persisted state, findings sidecars, and oracle evidence logs.
  • This issue should stay open until the CLI option table and caveats describe the shipped behavior, not just the Phase 1 carve-out.

Acceptance Criteria

  • Add/refresh a Where output lives section in packages/proof/README.md with the operator version of the consumer/source table.
  • Refresh .cursor/skills/proof/SKILL.md caveats and CLI tables for Phase 2 flags and --max-in-memory-output-bytes.
  • Document oracle stdout/stderr artifact behavior after Phase 4 lands.
  • Add a short migration/release-note paragraph explaining the behavior change from silent truncation to explicit display/prompt policies.
  • Verify stale execution-plane mentions of STREAM_CAP, 4000, and 2000 are gone except where documenting display caps.

Verification

  • pnpm lint
  • 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.

Metadata

Metadata

Assignees

No one assigned

    Labels

    documentationImprovements or additions to documentation

    Type

    No type
    No fields configured for issues without a type.

    Projects

    Status

    Todo

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions