Everything since 93f66d4 has been carried in the working tree. This lands it: - The cut campaign: 208 files retired (benchmarks and the router experiments, klbr-bench, the old LCM store surface, the starter's own root docs), -180,096 lines against +22,583. By its own census: 110,545 -> 62,750 physical lines, -43.2%. - The runtime work whose files were never added: peers, orientations, prompt headers, skills, attempt budget, migrations 010..016, and the Python workspace/peer/orientation surface with the skills that document it. - The daemon half of the windowed transcript: a bounded `subscribe` that opens after the session's context fold (`lcm_frontier`, `drained_through_seq`), `earliest_seq`/`fold_seq` on the replay frames, and a `history` request that pages backwards. The console half, and the frames the two sides share, are in their own commits. One commit rather than three because the halves are not separable: the modified files reference modules that exist only in the new files (klbr-runtime/src/{peer,frontier, prompt_header,skills}.rs, the 010..016 migrations), so any split leaves a commit that does not build. The tree as one unit is verified: `cargo test -p klbr-ipc -p klbr-daemon` green, the store suite green including its new bounds/page test, the console's own suite green. Also ignored now: /target-parent (123,424 build-artifact paths that `git status` was showing) and /.releases (behavior releases published by Release::publish at runtime).