{"date":"2026-08-25","from":{"k":"unit","s":"tasks","n":"main: the patterns list = the default-app STEP entry (its charge NARROWED 2026-08-24) + the lunch-poll-vote FILE entry, both under OW45 arm B. The b04 client-start death — the flag-ON client's navigate-deferred piece start dying terminally on a stale-confirmed-read ConflictError — is CLOSED by the RULED catch-up-and-start recovery (the refusal is 'the server won the race'; the client awaits the conflict's readiness and starts from the served documents through the ordinary load walk, committing nothing; OW45's CATCH-UP-AND-START block, serving-loop.md §3d RULED 2026-08-24), and the fix-head gate watched the recovery resurrect the notebook space's refused root start in the GREEN runs. What keeps the STEP entry is the gate's 7/10: the arm-B residue is READ-SIDE — a silent sticky readCell of the argument's redirect-linked notes with the piece context fully live (r01), and a stranded whole-piece mid-session read death behind a keyless pattern-load-error, with zero start deaths (r06/r09) — both store-verified zero-loss, neither reachable from the deferred-start error arm. The lunch-poll-vote FILE entry is #5744's 2026-08-24 deliberate re-skip: its profile-first join creates the viewer's profile piece mid-test and the deferred start died on exactly the b04 class this recovery closes (its reds predate the recovery landing); it lifts on its own gate evidence at the merged head, a FILE entry because every later step depends on that join. An EMPTY list is the flip PR's bar; any change here is a deliberate edit that reddens this pin"},"to":{"k":"unit","s":"tasks","n":"main: the patterns list = the default-app STEP entry (its charge NARROWED 2026-08-24) + the lunch-poll-vote FILE entry, both under OW45 arm B. The b04 client-start death — the flag-ON client's navigate-deferred piece start dying terminally on a stale-confirmed-read ConflictError — is CLOSED by the RULED catch-up-and-start recovery (the refusal is 'the server won the race'; the client awaits the conflict's readiness and starts from the served documents through the ordinary load walk, committing nothing; OW45's CATCH-UP-AND-START block, serving-loop.md §3d RULED 2026-08-24), and the fix-head gate watched the recovery resurrect the notebook space's refused root start in the GREEN runs. What keeps the STEP entry is the gate's 7/10: the arm-B residue is READ-SIDE — a silent sticky readCell of the argument's redirect-linked notes with the piece context fully live (r01), and a stranded whole-piece mid-session read death behind a keyless pattern-load-error, with zero start deaths (r06/r09) — both store-verified zero-loss, neither reachable from the deferred-start error arm. The lunch-poll-vote FILE entry is #5744's 2026-08-24 deliberate re-skip, and its OWN 10-run gate has now RUN at the merged head — 7/10, no lift: the b04 class it was minted for is closed there too (catch-up activations 10/10 runs, zero terminal deferred-start deaths), and the entry now stands on a THIRD, WRITE-SIDE residue member — the guest browser's mid-session profile piece never landing its program-materialization commit, its space stuck at 4 commits with no patternIdentity and zero server-log mentions against the greens' 14-21; refused vs dropped vs never issued is NOT determined. It still lifts only on its own gate evidence at the merged head, a FILE entry because every later step depends on that join. An EMPTY list is the flip PR's bar; any change here is a deliberate edit that reddens this pin"}}
{"date": "2026-08-25", "from": {"k": "unit", "s": "tasks", "n": "main: the patterns list = the default-app STEP entry (its charge NARROWED 2026-08-24) + the lunch-poll-vote FILE entry, both under OW45 arm B. The b04 client-start death — the flag-ON client's navigate-deferred piece start dying terminally on a stale-confirmed-read ConflictError — is CLOSED by the RULED catch-up-and-start recovery (the refusal is 'the server won the race'; the client awaits the conflict's readiness and starts from the served documents through the ordinary load walk, committing nothing; OW45's CATCH-UP-AND-START block, serving-loop.md §3d RULED 2026-08-24), and the fix-head gate watched the recovery resurrect the notebook space's refused root start in the GREEN runs. What keeps the STEP entry is the gate's 7/10: the arm-B residue is READ-SIDE — a silent sticky readCell of the argument's redirect-linked notes with the piece context fully live (r01), and a stranded whole-piece mid-session read death behind a keyless pattern-load-error, with zero start deaths (r06/r09) — both store-verified zero-loss, neither reachable from the deferred-start error arm. The lunch-poll-vote FILE entry is #5744's 2026-08-24 deliberate re-skip, and its OWN 10-run gate has now RUN at the merged head — 7/10, no lift: the b04 class it was minted for is closed there too (catch-up activations 10/10 runs, zero terminal deferred-start deaths), and the entry now stands on a THIRD, WRITE-SIDE residue member — the guest browser's mid-session profile piece never landing its program-materialization commit, its space stuck at 4 commits with no patternIdentity and zero server-log mentions against the greens' 14-21; refused vs dropped vs never issued is NOT determined. It still lifts only on its own gate evidence at the merged head, a FILE entry because every later step depends on that join. An EMPTY list is the flip PR's bar; any change here is a deliberate edit that reddens this pin"}, "to": {"k": "unit", "s": "tasks", "n": "main: the patterns list = the default-app STEP entry (its charge NARROWED 2026-08-24) + the lunch-poll-vote FILE entry (both under OW45 arm B) + the topic-board pivot-baseline STEP entry under issue #6304 (2026-08-25). The b04 client-start death — the flag-ON client's navigate-deferred piece start dying terminally on a stale-confirmed-read ConflictError — is CLOSED by the RULED catch-up-and-start recovery (the refusal is 'the server won the race'; the client awaits the conflict's readiness and starts from the served documents through the ordinary load walk, committing nothing; OW45's CATCH-UP-AND-START block, serving-loop.md §3d RULED 2026-08-24), and the fix-head gate watched the recovery resurrect the notebook space's refused root start in the GREEN runs. What keeps the STEP entry is the gate's 7/10: the arm-B residue is READ-SIDE — a silent sticky readCell of the argument's redirect-linked notes with the piece context fully live (r01), and a stranded whole-piece mid-session read death behind a keyless pattern-load-error, with zero start deaths (r06/r09) — both store-verified zero-loss, neither reachable from the deferred-start error arm. The lunch-poll-vote FILE entry is #5744's 2026-08-24 deliberate re-skip, and its OWN 10-run gate has now RUN at the merged head — 7/10, no lift: the b04 class it was minted for is closed there too (catch-up activations 10/10 runs, zero terminal deferred-start deaths), and the entry now stands on a THIRD, WRITE-SIDE residue member — the guest browser's mid-session profile piece never landing its program-materialization commit, its space stuck at 4 commits with no patternIdentity and zero server-log mentions against the greens' 14-21; refused vs dropped vs never issued is NOT determined. It still lifts only on its own gate evidence at the merged head, a FILE entry because every later step depends on that join. The topic-board entry skips ONE step — the pivot baseline case — because the ON arm's served crossrefs pivot diverges from the durable store (four rows for three topics; the store holds exactly three adds and the topics side is clean), a real serving/delivery defect the case exists to observe; it lifts when #6304 closes and the case greens ON. An EMPTY list is the flip PR's bar; any change here is a deliberate edit that reddens this pin"}}
{"date":"2026-08-26","from":{"k":"unit","s":"tasks","n":"main: the patterns list = the default-app STEP entry (its charge NARROWED 2026-08-24) + the lunch-poll-vote FILE entry (both under OW45 arm B) + the topic-board pivot-baseline STEP entry under issue #6304 (2026-08-25). The b04 client-start death — the flag-ON client's navigate-deferred piece start dying terminally on a stale-confirmed-read ConflictError — is CLOSED by the RULED catch-up-and-start recovery (the refusal is 'the server won the race'; the client awaits the conflict's readiness and starts from the served documents through the ordinary load walk, committing nothing; OW45's CATCH-UP-AND-START block, serving-loop.md §3d RULED 2026-08-24), and the fix-head gate watched the recovery resurrect the notebook space's refused root start in the GREEN runs. What keeps the STEP entry is the gate's 7/10: the arm-B residue is READ-SIDE — a silent sticky readCell of the argument's redirect-linked notes with the piece context fully live (r01), and a stranded whole-piece mid-session read death behind a keyless pattern-load-error, with zero start deaths (r06/r09) — both store-verified zero-loss, neither reachable from the deferred-start error arm. The lunch-poll-vote FILE entry is #5744's 2026-08-24 deliberate re-skip, and its OWN 10-run gate has now RUN at the merged head — 7/10, no lift: the b04 class it was minted for is closed there too (catch-up activations 10/10 runs, zero terminal deferred-start deaths), and the entry now stands on a THIRD, WRITE-SIDE residue member — the guest browser's mid-session profile piece never landing its program-materialization commit, its space stuck at 4 commits with no patternIdentity and zero server-log mentions against the greens' 14-21; refused vs dropped vs never issued is NOT determined. It still lifts only on its own gate evidence at the merged head, a FILE entry because every later step depends on that join. The topic-board entry skips ONE step — the pivot baseline case — because the ON arm's served crossrefs pivot diverges from the durable store (four rows for three topics; the store holds exactly three adds and the topics side is clean), a real serving/delivery defect the case exists to observe; it lifts when #6304 closes and the case greens ON. An EMPTY list is the flip PR's bar; any change here is a deliberate edit that reddens this pin"},"to":{"k":"unit","s":"tasks","n":"main: the patterns list carries the three current phase-7 entries and keeps the flip bar explicit"}}
{"date": "2026-08-26", "from": {"k": "unit", "s": "tasks", "n": "main: the patterns list carries the three current phase-7 entries and keeps the flip bar explicit"}, "to": {"k": "unit", "s": "tasks", "n": "main: the patterns list carries the two current phase-7 entries and keeps the flip bar explicit"}}
{"date": "2026-08-28", "from": {"k": "unit", "s": "tasks", "n": "main: the patterns list carries the two current phase-7 entries and keeps the flip bar explicit"}, "to": {"k": "unit", "s": "tasks", "n": "main: the patterns list carries the one remaining phase-7 entry and keeps the flip bar explicit"}}
{"date": "2026-08-28", "from": {"k": "unit", "s": "tasks", "n": "main: the patterns list carries the one remaining phase-7 entry and keeps the flip bar explicit"}, "to": {"k": "unit", "s": "tasks", "n": "main: the patterns list is EMPTY and the flip bar's list-EMPTY precondition is met"}}
{"date": "2026-08-28", "from": {"k": "unit", "s": "tasks", "n": "main: the runner list is EMPTY — pattern-and-data-persistence LIFTED by the arrival-witness predicate (RULED 2026-08-22, candidate (B): a cover at the floor witnesses only when derived-class) on 10/10 green at the true ON topology — so the full suite runs, and the ONLY file-level skip in ANY suite is patterns' lunch-poll-vote entry (the 2026-08-24 deliberate OW45 arm-B re-skip)"}, "to": {"k": "unit", "s": "tasks", "n": "main: the runner list is EMPTY and NO suite carries any entry — the ON-skip registry is EMPTY"}}
{"date": "2026-08-28", "from": {"k": "unit", "s": "tasks", "n": "main: the patterns list is EMPTY and the flip bar's list-EMPTY precondition is met"}, "to": {"k": "unit", "s": "tasks", "n": "main: the patterns list carries the restored lunch-poll-vote FILE entry — the probe-mapped forever-park"}}
{"date": "2026-08-28", "from": {"k": "unit", "s": "tasks", "n": "main: the runner list is EMPTY and NO suite carries any entry — the ON-skip registry is EMPTY"}, "to": {"k": "unit", "s": "tasks", "n": "main: the runner list is EMPTY and the only entry in ANY suite is the restored lunch-poll-vote FILE entry"}}
{"date": "2026-08-28", "from": {"k": "unit", "s": "tasks", "n": "main: the patterns list carries the restored lunch-poll-vote FILE entry — the probe-mapped forever-park"}, "to": {"k": "unit", "s": "tasks", "n": "main: the patterns list is EMPTY after the geometry-3 lift and the flip bar's list-EMPTY precondition is met"}}
{"date": "2026-08-28", "from": {"k": "unit", "s": "tasks", "n": "main: the runner list is EMPTY and the only entry in ANY suite is the restored lunch-poll-vote FILE entry"}, "to": {"k": "unit", "s": "tasks", "n": "main: the runner list is EMPTY and NO suite carries any entry — the ON-skip registry is EMPTY after the geometry-3 lift"}}
{"date": "2026-08-28", "from": {"k": "unit", "s": "tasks", "n": "main: the patterns list is EMPTY after the geometry-3 lift and the flip bar's list-EMPTY precondition is met"}, "to": {"k": "unit", "s": "tasks", "n": "main: the patterns list carries the lunch-poll-vote FILE entry restored on probe 5 — geometry 3b confirmed"}}
{"date": "2026-08-28", "from": {"k": "unit", "s": "tasks", "n": "main: the runner list is EMPTY and NO suite carries any entry — the ON-skip registry is EMPTY after the geometry-3 lift"}, "to": {"k": "unit", "s": "tasks", "n": "main: the runner list is EMPTY and the only entry anywhere is the probe-5-restored lunch-poll-vote FILE entry"}}
{"date": "2026-08-28", "from": {"k": "unit", "s": "tasks", "n": "main: the patterns list carries the lunch-poll-vote FILE entry restored on probe 5 — geometry 3b confirmed"}, "to": {"k": "unit", "s": "tasks", "n": "main: the patterns list is EMPTY after the ruled 3b close and the flip bar's list-EMPTY precondition is met"}}
{"date": "2026-08-28", "from": {"k": "unit", "s": "tasks", "n": "main: the runner list is EMPTY and the only entry anywhere is the probe-5-restored lunch-poll-vote FILE entry"}, "to": {"k": "unit", "s": "tasks", "n": "main: the runner list is EMPTY and NO suite carries any entry — the ON-skip registry is EMPTY after the ruled 3b close"}}
{"date":"2026-09-25","from":{"k":"unit","s":"tasks","n":"main: the patterns list is EMPTY after the ruled 3b close and the flip bar's list-EMPTY precondition is met"},"to":{"k":"unit","s":"tasks","n":"the patterns list is EMPTY after the ruled 3b close and the flip bar's list-EMPTY precondition is met"}}
{"date":"2026-09-25","from":{"k":"unit","s":"tasks","n":"main: the runtime-client list is EMPTY — the OW33 triage (2026-08-22) lifted both STEP entries (CT-1606 PerUser header render; single-navigateTo dispatch) on 12/12 green at the true ON topology — so the full suite runs, and the in-file guard resolves to no entry"},"to":{"k":"unit","s":"tasks","n":"the runtime-client list is EMPTY — the OW33 triage (2026-08-22) lifted both STEP entries (CT-1606 PerUser header render; single-navigateTo dispatch) on 12/12 green at the true ON topology — so the full suite runs, and the in-file guard resolves to no entry"}}
{"date":"2026-09-25","from":{"k":"unit","s":"tasks","n":"main: the runner list is EMPTY and NO suite carries any entry — the ON-skip registry is EMPTY after the ruled 3b close"},"to":{"k":"unit","s":"tasks","n":"the runner list is EMPTY and NO suite carries any entry — the ON-skip registry is EMPTY after the ruled 3b close"}}