Name the fold in the transcript, and share the window frames with the daemon

The window opens after the session's context fold, so the daemon now says which record that fold drained through and the console mentions it at the window's edge — while the window is above it. A reader who has paged back past the fold is reading the prefix itself, and there is nothing summarized about what they are looking at, so the note goes. The window request is `after_seq: 0` with a `limit` rather than `after_seq: null`: a daemon that does not know about windows ignores the limit and replays the session, which is what it did before, so the request cannot leave a client against an older daemon with an empty transcript. The fixture reports the fold and carries it on pages, and its folds are `lcm_frontier` records with the payload the runtime actually writes. `src/lib/protocol-v2.test.ts` replays the exact frames `klbr-ipc/src/v2.rs`'s `window_frames` suite pins, through this console's parser and client. Two implementations of one contract drift in silence otherwise: a renamed field is an empty session on one side with nothing red on the other.

1a5d2172 parent ac5f1f52 +189 −35
browse files