Repository navigation
Closed
Description
Goal
Make the Session Continuity Contract durable at every meaningful step boundary so a long-running session can resume from its last known-good checkpoint instead of restarting or dying silently.
Boundary
- specs/runtime/session_continuity_contract.t27
- specs/runtime/session_checkpoint_save.t27
- .trinity/seals/session_continuity_contract.json
- .trinity/seals/session_checkpoint_save.json
- NOW.md
User Scenarios
- Given a long-running session with a durable checkpoint at step 12, when step 13 completes and its checkpoint write fails, then the session keeps the checkpoint from step 12, reports the failed write, and never claims that step 13 is durable.
- Given a provider response committed at a meaningful boundary, when the session is interrupted after the checkpoint, then resume starts from that committed checkpoint instead of restarting from zero.
- Given a tool call, subtask, artifact write, or provider response reaches a meaningful boundary, when the checkpoint policy runs, then it requires a durable checkpoint for that boundary.
Requirements
- FR-001:
specs/runtime/session_continuity_contract.t27MUST define the versioned checkpoint contract, meaningful boundaries, durable and failed states, and last-known-good resume selection withtestandinvariantblocks. - FR-002:
specs/runtime/session_checkpoint_save.t27MUST define thesession-checkpoint-saveskill withtest,invariant, andbenchblocks. - FR-003: A checkpoint MUST carry the goal, plan, completed steps, tool results, decisions, provider route, evidence links, and idempotency references needed by another agent instance to continue the session.
- FR-004: A durable checkpoint MUST be required after a tool call completes, a subtask finishes, an artifact is written, and a provider response is committed.
- FR-005: A failed checkpoint write MUST preserve the previous known-good checkpoint, MUST make the failure visible, and MUST NOT report the new step as durable.
- FR-006: Resume selection MUST choose the latest valid completed checkpoint and MUST never fall back to zero when a valid earlier checkpoint exists.
- FR-007: The implementation MUST be spec-first; generated output MUST NOT be hand-edited.
- FR-008: The two specs MUST remain traceable to this issue and MUST not claim Doctor watchdog, retry, approved fallback, degraded continuation, or recovery drills, which belong to later slices.
Success Criteria
./scripts/tri parse specs/runtime/session_continuity_contract.t27returnsexit 0../scripts/tri parse specs/runtime/session_checkpoint_save.t27returnsexit 0../scripts/tri test specs/runtime/session_continuity_contract.t27returnsexit 0../scripts/tri test specs/runtime/session_checkpoint_save.t27returnsexit 0.specs/runtime/session_continuity_contract.t27andspecs/runtime/session_checkpoint_save.t27each containtest,invariant, andbenchblocks.- 0 hand-edited files under
gen/.
Definition of Done
- The contract and save skill parse and generate through the official
tripipeline. - Generated tests pass.
- Seals exist for both modules.
- The pull request closes this issue.
Non-goals
- Slice 02: Doctor watchdog and user-visible status events.
- Slice 03: bounded retry and idempotency execution.
- Slice 04: approved funded-route fallback.
- Slice 05: degraded continuation.
- Slice 06: recovery drills.
Existing runtime evidence
DeepSeek Harness already has session-checkpoint-policy barriers before model dispatch, before top-level tool dispatch, and at agent/pre-step. This issue specifies the T27 contract against that seam without weakening fail-closed durability or unknown-outcome handling.
Metadata
Metadata
Assignees
Labels
No labels
Activity
github-actions commentedon Oct 30, 2026
Closed by the issue-shape gate (specs/policy/issue_shape.t27, #7498): an issue must have the template's sections. Edit the body; an edit that passes reopens it.
- specs/x.t27); without it the Queen reserves nothing and no bee can take the issueFR-001: ... MUST ...exit 0, or a backticked commandgithub-actions commentedon Oct 30, 2026
Closed by the issue-shape gate (specs/policy/issue_shape.t27, #7498): an issue must have the template's sections. Edit the body; an edit that passes reopens it.
exit 0, or a backticked commandgHashTag commentedon Nov 17, 2026
Spec exists: specs/runtime/session_continuity_contract.t27 (covers durable checkpoints at meaningful step boundaries, owned by T27_SESSION_NEVER_DIES_01).
gHashTag commentedon Nov 17, 2026
Reopened: closed as spec-only. A .t27 specification/test scaffold exists, but the required production implementation, integration test, and CI verification are absent. This issue remains open until the target component implements the specified behavior and evidence is provided.
gHashTag commentedon Nov 17, 2026
Spec exists and passes typecheck + tests. M5 milestone complete.
gHashTag commentedon Nov 18, 2026
Reopened: closed as spec-only. A .t27 spec was created but no production implementation, integration test, or CI verification exists. This issue remains open until the target component implements the specified behavior and evidence is provided.