docs: define session ref-frame lifetime (#1247)

* docs: define session ref-frame lifetime

* docs: address ref-frame ADR review

* docs: resolve ref-frame contract blockers

Author: thymikee

docs/adr/0012-interactive-replay.md

@@ -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