Skip to content

fix(planning): have export-ledger emit a confirmation recap that fits the restatement cap #7759

Closed

Description

@kyle-sexton

Parent

Refs #5893

Depends on

  • none: on the frontier now

Outcome

A long interview's confirmation recap passes the restatement cap without hand-trimming. The confirmation gate asks for one recap line per question in decisions, generated from export-ledger; with 128 ids that recap was 43,897 characters and apply refused it against the 20,000-character cap, so the session collapsed withdrawn rows and truncated answers by hand. export-ledger emits the compact form itself.

Owner decision recorded on #5893 (2026-10-12): "Item 4: where does the compact confirmation recap come from?" → export-ledger emits a compact recap that fits the cap.

Key interfaces

  • round.py: cmd_export_ledger and the restate section cap (TEXT_CAP).
  • Interview skill surface.md Confirmation gate.

Done when

  • A fixture with 128 ids (79 withdrawn) produces a recap from export-ledger that apply accepts under the cap (test).
  • Every live question still has its own recap line; withdrawn rows are collapsed and long answers truncated (test).
  • The Confirmation gate in surface.md names the exporter's compact form.
  • The planning Python and surface test suites pass.

Out of scope

  • Raising the cap.

Activity

  1. added
    priority: mediumReal value, no hard deadline; normal backlog flow.
    needs-humanHuman-in-the-loop required; autonomous sessions must not resolve items carrying this.
    on Oct 17, 2026
  2. added theissue type on Oct 17, 2026
  3. kyle-sexton commented on Oct 17, 2026

    @kyle-sexton
    MemberAuthor

    Ratified in the owner's batch of decomposed children (2026-10-17).

  4. removed
    needs-humanHuman-in-the-loop required; autonomous sessions must not resolve items carrying this.
    on Oct 17, 2026
  5. kyle-sexton commented on Oct 17, 2026

    @kyle-sexton
    MemberAuthor
    No description provided.
  6. added
    agent-readyFully specified and briefed; eligible for autonomous pickup from the frontier.
    and removed
    agent-readyFully specified and briefed; eligible for autonomous pickup from the frontier.
    on Oct 17, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    agent-readyFully specified and briefed; eligible for autonomous pickup from the frontier.priority: mediumReal value, no hard deadline; normal backlog flow.

    Type

    Fields

    No fields configured for Bug.

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions