Skip to content

docs: define session ref-frame lifetime #1247

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
thymikee merged 3 commits into from
Jul 13, 2026
Merged

docs: define session ref-frame lifetime #1247

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
a225fa8
docs: define session ref-frame lifetime
thymikee Jul 13, 2026
fee1415
docs: address ref-frame ADR review
thymikee Jul 13, 2026
5134f53
docs: resolve ref-frame contract blockers
thymikee Jul 13, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 6 additions & 0 deletions docs/adr/0012-interactive-replay.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -463,6 +463,12 @@ every `screen` ref with `refsGeneration` before returning it, including on the e
client callers receive the unpinned refs and generation already present in the daemon error. No caller
gets a text-only divergence that loses its repair data.

> **Proposed ADR 0014 amendment:** if ADR 0014 is accepted and implemented, replay divergence
> `screen.refs` becomes a partial ref publication. MCP keeps auto-pinning those refs; CLI text renders
> `@eN~s<refsGeneration>`; JSON and Node.js callers pair each plain ref with the response-level
> generation before mutation. Until that migration lands, the current unpinned contract above remains
> accepted. The implementation must update this note and its contract tests in the same change.

`--from N` is a `replay`-only flag. `test` must reject it as `INVALID_ARGS`; test shares replay execution
but must remain a full, deterministic suite run. `N` is a 1-based index into the fully expanded
executable plan and must be in range. It is never a YAML line number, fractional source-step number, or a
Expand Down
Loading
Loading