From 8af52dec02366f31af559c56c509db71600b43f4 Mon Sep 17 00:00:00 2001 From: bitkyc08-arch Date: Sun, 30 Aug 2026 11:53:17 +0900 Subject: [PATCH] docs(devlog): record the terminal outcome the unit close claimed The _fin move in #2970 landed as a pure rename: 10 files, 0 insertions. Its commit message described a Terminal outcome section appended to 070, but that edit was unstaged when the commit was taken, so git recorded only the staged rename and the section never reached dev. The message therefore claims a change the tree does not contain. This adds the section for real. It names the merge commit 62df78d8d, the post-merge remote gate at that commit (exit 0, 16359 pass / 0 fail / 16 skip, so the landed tree is verified and not only the pre-merge head), the round 11 PASS verdict with the two notes it left, and the finding that rounds 5 through 10 were each triggered by the previous round's own fix - every one of those fixes added a fact to the pruning code without asking which existing block had assumed that fact absent. It also names the three items scoped out on purpose, so a later reader does not reopen them as defects of this unit: the envelope_exhausted reason that a spread copy in live-transport.ts makes provably inert, the extreme-byte-axis case where the repetition note can outlive the result, and composer-2.5's hybrid root count. The last two are identical on dev before this unit and are pre-existing rather than introduced. Docs only. Nothing in the build, typecheck or test path reads devlog/. --- ...0_phase8_checkpoint_suffix_orphan_strip.md | 26 +++++++++++++++++++ 1 file changed, 26 insertions(+) diff --git a/devlog/_fin/260829_cursor_tool_continuation_pairing/070_phase8_checkpoint_suffix_orphan_strip.md b/devlog/_fin/260829_cursor_tool_continuation_pairing/070_phase8_checkpoint_suffix_orphan_strip.md index cd47672280..58abb93c18 100644 --- a/devlog/_fin/260829_cursor_tool_continuation_pairing/070_phase8_checkpoint_suffix_orphan_strip.md +++ b/devlog/_fin/260829_cursor_tool_continuation_pairing/070_phase8_checkpoint_suffix_orphan_strip.md @@ -686,3 +686,29 @@ Full replay has no abandon branch to rescue it, which makes it a genuine follow- non-problem, and it belongs to its own phase. Four-suite total is 213 pass / 0 fail; `cursor-blob` alone 127. + +## Terminal outcome + +PR #2940 landed on `dev` as squash commit `62df78d8dd2451accdc0ddd615b9fad080d64a60`, from head +`0340d17599b65dda8b739a30107f59297e0d145b`, with CI green at that exact head. The remote gate on +`ssh lidge` was re-run against the merge commit itself and reported exit 0 with 16359 pass / 0 fail / +16 skip, so the landed tree is verified rather than only the pre-merge head. + +Round 11 is the closing verdict: PASS, with two minor notes, both addressed in `0340d1759` before the +merge — a threshold case pinned from the tight side, and the correction of a wrong secondary claim in +the round 10 record. Rounds 1 through 10 each found a genuine blocker, and rounds 5 through 10 were +each triggered by the previous round's own fix. That is the finding worth carrying forward: every one +of those fixes added a fact to the pruning code without asking which existing block had assumed that +fact absent. + +Three items were scoped out on purpose and are not defects of this unit. The `envelope_exhausted` +reason still does not reach the checkpoint store, and the spread copy in `live-transport.ts` makes it +provably inert rather than merely unobserved; propagating it needs a signature change on a shared +prepare path. On the extreme byte axis near a 523 KB system prompt the repetition note can survive +while the result truncates to a marker, which is pre-existing and measurably better here than on the +parent. And `composer-2.5` assembles 194 roots because it is a hybrid — `echoToolResultInRoot` true +with `externalModel` false — which places it outside the envelope guard; that behaviour is identical +on `dev` and predates this work. + +This unit moves to `_fin` under the rule in `AGENTS.md`: the work it records is now visible in public +git history.