46 KiB
Row 191 stopRun inspection round
Design: ../DESIGN-r2.md, approved by Dewey in 29473; scope sage-2244; per-run contract ../STOP-RUN-CONTRACT.md, honker-0079/0081. Not review-ready: full package/shell/Docker gate and acceptance/guard mutants remain pending.
Current commit 7aa18b0f6e, new branch
rocko/row191-stoprun-dcd8-20261022, parent dcd8d4dda. Worktree
/mnt/storage/scratch/rocko-r191-r3. Earlier inspection f7bf7dfec is preserved.
All 79 manifest paths have identical blobs at f7bf7dfec and 7aa18b0f6;
rebase-product-diff.stat is empty, rebase-product-check.txt names the check.
The manifest SHA-256 stays
9971ac5fe56d0d36eb914ecaf2c282e14ab3cd29860fd27b268ec0baadaf0e52.
Rocko author and committer identity were selected explicitly. No attribution
lines, force-push or branch deletion. Sage publishes through jarvis.
Changes Dewey must review: two focused-run fixes
-
packages/bus/src/broker.mjs, requestHost: the new processingWork guard was initially inserted into the inner refusal logger's try block. That let the original request reach validation, then prevented its refusal being logged while halted, returning storage-unavailable. Move it to the main admission try, before keys/credentials/authority/effects. The refusal logger retains its existing unconditional audit behavior. The new host-admission test now expects processing-halted and proves neither executor method was called. Initial evidence: ../logs/stoprun-focused-packages_bus_tests_processing.test.mjs.log.
-
packages/bus/tests/processing.test.mjs, real socket await test: row 196's asynchronous kernel-peer subprocess now precedes dispatch. The old 5 ms server deadline could fire during that subprocess, before the processing await branch extends it. This test already stubs authenticateHuman; give it a deterministic peerReader too, with read and close, and assert exactly two proof reads for halt/resume. Keep the 5 ms ordinary timeout and 30 ms halt delay. Production peer discovery, proof/transport and timeout behavior are unchanged. The test still fails if the async branch timeout is removed. The first fixture retry omitted close(); its teardown failed and left its own server running. Only that verified test group 2831504 was killed. Both unsuccessful logs remain. Corrected evidence: ../logs/stoprun-focused-bus-processing-fixed-2.log (14/14).
These are diagnosed code/fixture mistakes, not declared flakes. No failed log was removed and no existing security assertion was weakened.
Focused evidence, sage-2250
Ran singly on 41b0cf755 because none of row 254's seven paths overlaps ours.
Sage-2265 carries this evidence to dcd8d4dda after the empty 79-path diff.
Scripted busy check exited 0 before the first file. Every test runner used its
own process group, 180 s timeout, scratch TMPDIR
/mnt/storage/scratch/rocko-r191-tmp and DOCKER_HOST=unix:///nonexistent.sock.
There was no Docker, browser, package suite, shell suite or mutant run.
| File | Final passed | Failed | Skipped |
|---|---|---|---|
| processing-control/tests/stop-run.test.mjs | 12 | 0 | 0 |
| processing-control/tests/runtimes.test.mjs | 10 | 0 | 0 |
| processing-control/tests/coordinator.test.mjs | 3 | 0 | 0 |
| processing-control/tests/containers.test.mjs | 6 | 0 | 0 |
| processing-control/tests/effects.test.mjs | 5 | 0 | 0 |
| processing-control/tests/task.test.mjs | 7 | 0 | 0 |
| bus/tests/processing.test.mjs | 14 | 0 | 0 |
| bus/tests/processing-runtime.test.mjs | 2 | 0 | 0 |
| bus/tests/project-runtime.test.mjs | 3 | 0 | 0 |
| Script sum | 62 | 0 | 0 |
All final runners exited 0. The batch stopped at the initial bus failure, then that file was diagnosed/rerun before the final two files. Counts are from focused-run-table-final.json and include only each final successful file log. Earlier bus failures are reported above, not silently included as green. Approximate run span 23:59Z–00:00:41Z; start second was not recorded. Cwd-scoped node/chromium sweep was empty at 00:00:41Z; slot returned to Sage.
stopRun implementation
The export resolves host-owned run identity even without a bound bus claim. It checks boot/start/group identity immediately before each signal, preserves verified member anchors, waits 5 s before KILL and observes for 2 s. Signals are acknowledgements only, never invented. Root/business/run cache joins the same Promise. Atomic hard-link publication plus durable exclusive claim coordinates other host processes. First owner/reason/deadline/result persists; completed retries never re-escalate or overwrite that result. Halt links its generation to the first fire receipt without relabelling the runtime's stop cause. A later verified exit is separate immutable observation evidence. The seam writes no bus events. Honker maps killed/alive to lifecycle events.
No global unit, live config, binding, token, slot file or live store touched. No schema migration. First activation still requires stopping old processing before trusted initialization and aligning the copy/image/read-only mount in Mos's window. Existing result.json evidence remains write-once.
Integration and outstanding work
The 12 latest-base conflict resolutions are listed in STATUS.md. New landed host execution, publish and library sync paths are now wrapped in processing scopes; host credential cancellation composes with its existing revocation signal. This changes only files already owned by 191. Those wider integrations still need the full owning-file/package gate and mutant evidence.
Fifteen proposed per-run mutants preflight exact once in stoprun-mutants.json; none has been applied or run. The broader kill-switch acceptance/guard table and executable mutant runner are still being completed. No kill count or review-ready claim is made. Ask Sage for the later CLEAR when the packet is complete, as sage-2259/2262 requires.
Gate preparation after the focused slot
The published product implementation is unchanged. Three uncommitted test-file strengthenings are saved in post-inspection-tests.patch: effects.test.mjs adds a 4-second bounded abort expectation for the watcher mutant; Discord's early start fence is also checked before a malformed journal can be read; WebUI's body limit now uses oversized valid JSON, and a direct-handler test isolates its own origin/site guards from serve's outer fence. These edits are unrun and are not included in the published 9971ac5f manifest. They must pass before a new candidate is cut. Thus 62/62 is prior focused evidence, not a claim for these changed test bytes.
The complete proposed table has 70 exact-once sites in all-mutants.json, including expected killing test names. Static preflight is clean; no mutant has been applied. run-mutants.py validates preflight, uses new process groups, tracks only its own verified descendant identities, kills those groups on timeout, checks named TAP failures, and restores all source bytes in finally. A timeout or wrong-test failure is not counted as a valid kill. The table and runner are prepared evidence, not a kill result. The requested nine-package, ten-shell, seventy-mutant gate is in gate-plan.json; Sage CLEAR is pending.
Published test-strengthening commit and full gate (sage-2269/2271)
81889b58d5 is one fast-forward commit on
7aa18b0f6, same branch rocko/row191-stoprun-dcd8-20261022. It commits the
three test changes saved in post-inspection-tests.patch; that patch remains
historical evidence, not an uncommitted candidate. Product implementation is
unchanged. Earlier manifest 9971ac5f belongs to 7aa18b0f6; candidate.txt now
names the manifest for 81889b58d. Sage published this tip before granting CLEAR.
The full gate checks HEAD equality and clean product bytes before its first file. Changed test files run singly, then nine packages, all ten shell suites, then seventy mutants. Each step gates on its exit status and retains its full log. run-gate.sh uses pipefail and an EXIT trap for the label-verified Compose network rocko-r191-gate_default, project rocko-r191-gate. TMPDIR is /mnt/storage/scratch/tmp/rocko-r191-gate. Docker is available only for test-task and test-release; other steps use unix:///nonexistent.sock. Live provider calls are disabled. No daemon, socket, volume or live configuration changes.
Gate start: 2026-10-22T00:18:00Z. Results remain pending until gate-results.json and mutant-results.json provide actual exit statuses and counts.
First full-gate stop and fixture correction (sage-2274)
The 81889b58d run stopped at its first failure, 00:18:00Z–00:19:21Z.
27 files completed: 268 passed, 1 failed, 0 skipped. Packages, shells and
mutants did not start. Full logs/results are in gate-attempt-81889/.
The tester refusal test's fixture requested tester:true over TCP, which row
196 now refuses before route handling. This is a stale fixture, not a flake.
The correction uses the existing startTesterSocket helper, a private fixture
root, socketPath requests, TESTER_ORIGIN and no human identity header. Every
assertion remains; the request now reaches the intended processing refusal
rather than failing listener setup or the outer identity fence. A grep of all
changed test files found no other tester:true TCP setup. The cwd node/chromium
sweep returned []; no Docker test workload ran. Commit c78f48946 is a single
fast-forward test-only fix on 81889b58d, authorized by sage-2274. The complete
gate restarts from its first single file only after Sage publishes this tip.
Sage-2275 published c78f48946 and granted full restart. Second attempt begins
2026-10-22T00:21:03Z; any further failure stops before additional edits.
Candidate manifest b49fd493dc75ef2484ffc255213dc8eeaaaa348dee416c8d26d1c2bab8e20067.
Second attempt stopped; no further changes (sage-2275)
Run 00:21:03Z–00:23:50Z on published c78f48946: all 27 changed singles
269/269, processing-control 61/61, bus 646/646. The CLI package emitted 26
failed subtests before its verified own runner group 3119310 was stopped.
Its result is interrupted, not a complete package count. Six gate-lane image
checks refuse because scripts/testing/lane-image.mjs pins the old four COPY
lines and 191 adds processing-control to Containerfile. Twenty launch-account,
launch-limit-checks, launch-limits and launch-routes cases hit
processing-uninitialized on fixture roots with no explicit control init.
No edits, retries, later packages, shells, Docker test workloads or mutants
followed this second failure. Parent runner exited; cwd node/chromium sweep
returned [] at 00:23:50Z. Slot returned to Sage at 00:24:05Z with the exact
failures and a request for scope on image-manifest and fixture initialization.
This is an integration failure, not a declared flake or a passing gate.
Image-input manifest and launcher fixture scope (sage-2278, sage-2282)
Commit eb3abba12 is one fast-forward commit on c78f48946. This is an image-input
manifest change: scripts/testing/lane-image.mjs now pins the exact Containerfile
COPY of packages/processing-control/src/state.mjs and entrypoint.mjs and hashes
both named source paths, without a wildcard. Its only two changed lines add
those inputs. Without them, a lane could reuse a stale image after a reader or
entrypoint change. The image test fixtures copy both files and each has its
own receipt-invalidating test. Mutant KS56 drops state.mjs from the hash list;
its named killer is the state.mjs receipt-invalidating test. Static preflight
is 71 sites / 0 errors. No new run result is claimed before CLEAR.
The launch-account, launch-limit-checks, launch-limits and launch-routes fixtures now explicitly call initializeControl(f.dataRoot) before constructing their launchers. Existing assertion lines are byte-identical. A new launch-limit-checks test leaves initialization off and asserts processing-uninitialized, no mayLaunch/authorizeLaunch, and no registered session. A live root gets control initialized by the bus broker. The re-pin order is bus start before any seat launch; a launcher started before that refuses. This supplements the existing window precondition to stop old processing before the first trusted init.
Sage-2282 supersedes the test-only image ruling: lane-image.mjs is a product blob, so mos-1200 carries no earlier results. The complete plan restarts from the first single file, all nine packages, all ten shells and all 71 mutants only after publication and Sage CLEAR. Earlier attempts remain in their separate gate-attempt directories; neither is a passing full gate.
Sage-2283 published eb3abba12. Current 85-path candidate manifest is
01a2b33651414c9b0cb094d2108f9e39c48a41b79974dcc16bdec374f8371091.
The gate prints HEAD and this digest, verifies every manifest blob before its
first test, and carries no old results. Awaiting CLEAR after Gander 253.
Full restart on eb3abba12 stopped at Discord (sage-2286)
Verified HEAD and all 85 manifest blobs before tests. Run span: 2026-10-22T00:34:50Z–00:47:33Z. No old result carried.
| Step | Passed | Failed | Skipped | Exit |
|---|---|---|---|---|
| 32 changed test files singly | 304 | 0 | 0 | 0 |
| processing-control | 61 | 0 | 0 | 0 |
| bus | 646 | 0 | 0 | 0 |
| cli | 761 | 0 | 0 | 0 |
| discord | 190 | 2 | 0 | 1 |
Singles sum independently confirmed by awk over all 32 TAP logs. Discord's binding.test.mjs:201 STOP check and recover.test.mjs:145 ready recovery check both get processing-uninitialized before the expected behavior. Those older fixture roots do not explicitly initialize control. The gate stopped at this step; no subsequent package, shell suite, Docker test workload or mutant ran. Docker availability was checked read-only (29.7.2); no daemon/volume changes. The EXIT trap completed. Cwd node/chromium sweep returned [] at 00:47:49Z, source tree remains clean, and the slot was handed back at 00:47:58Z. No test or product edits or retries followed this failure; Sage has the table and the fixture-initialization recommendation. This is not a green full gate.
Discord fixture init and all-package static sweep (sage-2294)
Commit e6800380dc is test-only and fast-forwards eb3abba12.
Only binding.test.mjs and recover.test.mjs change: one initializeControl import
and one initializeControl(dep.dataRoot) call in each affected CLI fixture.
Every original assertion line is retained. Product blobs are unchanged.
FIXTURE-SWEEP.md and fixture-sweep.json enumerate 338 source call-site hits,
with the two fixes and the already-initialized chains, plus the screens for
rootless optional contexts and read-only/usage CLI calls. The generator reads
repository source only and invokes no fixture. Deliberate missing/deleted/
corrupt-state refusal tests remain negative; no shared helper masks them.
Current manifest be36af8f0855f57336e6a33283aa0a8e94297f338b1f8180936cbccf1119c60a, 87 paths. Sage-2294 carries only unchanged processing-control 61/61, bus 646/646, CLI 761/761 and unchanged singles from gate-attempt-eb3/. The resume must run both touched files wholly, whole Discord, then the never-run WebUI/tasks/seat/project/library packages, every shell suite and all 71 mutants. No result is claimed for the new test bytes before CLEAR. The live initialization order remains bus start before any seat or Discord start; no fixture change initializes or repairs a live root.
Resume on e6800380d stopped at WebUI (sage-2311)
Start 2026-10-22T01:27:40Z; failed-step exit 01:28:45Z. Startup verified HEAD, manifest be36af8f and all 87 blobs, and read-only Docker availability (29.7.2).
| New step | Passed | Failed | Skipped | Exit |
|---|---|---|---|---|
| binding.test.mjs whole | 15 | 0 | 0 | 0 |
| recover.test.mjs whole | 5 | 0 | 0 | 0 |
| Discord whole | 192 | 0 | 0 | 0 |
| WebUI whole | 314 | 4 | 1 | 1 |
Carried unchanged under sage-2294: 32 singles 304/304, processing-control 61/61,
bus 646/646 and CLI 761/761, from gate-attempt-eb3/. These are explicitly carried
results, not fresh runs on e6800380d.
Four WebUI failures are retained in gate-logs/package-webui.log:
- board-held.test.mjs:91: processing's config/state GETs omit redirect:manual.
- board-held.test.mjs:194 and send-browser.test.mjs:58: processing's independent hash/focus/interval refresh continues to read after the shell signs out.
- shell.test.mjs:104: the added control bar makes the short desktop page 1095px high at a 1000px viewport. Its new height is not accounted for by the existing frame/sidebar/footer layout.
Static diagnosis: processing.js ignores the existing body.signed-out state and mosaic-signed-out event that app.js and bus.js already share. Its GETs also lack manual redirect handling. processing.css adds an external bar while shell.css's frame minimum and sidebar heights still subtract only bar-h and foot-h. These are product integration defects; no assertions were weakened and no fix was made after the failed step. Sage received the table and recommendations.
One TAP skip: the editor rebuild requires exactly esbuild 0.28.2; installed shared node_modules has 0.28.1. Full skip line is in tap-skips.json. No shell suite ran, so there are no ^skip shell lines (skip-lines.txt remains empty). No tasks/seat/project/library suite, shell Docker workload or mutant ran after WebUI failed. Parent runner exited, EXIT cleanup completed, cwd node/chromium sweep returned [] at 01:29:00Z, source tree is clean, and slot returned to Sage. No retries or source edits were made. This is not a passing gate.
Console shared sign-out and bounded desktop layout (sage-2317)
Commit 8e1f55c1db, fast-forward on e6800380d, changes only the
processing assets and their owning two tests. Current 87-path manifest:
d3b014e6a0e9e547a29ae780eb27b1c0e57cc7b0e73dc49954abbff623929f41.
All three processing fetch sites use redirect:manual. responseBody dispatches the existing mosaic-signed-out event for an opaque redirect, or its signIn variant for exactly 401/sign-in required. No independent sign-out state is added: refresh/action guards read body.signed-out. The existing event cancels the interval, invalidates pending reads, clears stale state and disables writes. In-flight answers cannot restore state after sign-out. Initial work waits for DOMContentLoaded because this deferred asset precedes app.js in the HTML and needs its shared sign-out listener registered first. app.js/bus.js and their proof baselines remain untouched.
The CSS keeps the control bar in normal document flow. On desktop, the frame flexes into the remaining viewport rather than imposing another full-height minimum below the bar. Fixed navigation retains the shell's command/footer bounds and existing responsive column widths. Mobile retains natural flow. No short-page, sidebar or footer assertion is changed; rendering remains to be verified on the next authorized gate, not claimed from static checks.
The VM fixture models the existing body class, document events and DOM ready; its original assertion lines are unchanged. Six new browser cases cover config, state and POST opaque redirects and sign-in-required replies, manual redirect requests, interval cancellation and no subsequent fetch from forced refreshes or clicks. KS57 removes manual redirect from the config GET; KS58 removes the refresh signed-out guard. Both name the config-redirect browser case as their killer. Static preflight: 73 exact-once sites / 0 errors. Syntax checks pass; no owning test or mutant has run on this commit.
A product blob changes, so sage-2317/mos-1200 carries nothing. The next CLEAR runs all changed files singly, all nine package suites, all ten shell suites with Docker available and all 73 mutants. The editor rebuild's esbuild0.28.1 vs pinned0.28.2 skip remains host drift and is reported separately. Earlier failed attempts remain immutable in gate-attempt-* directories.
Rebase onto row 202 (sage-2329)
New branch rocko/row191-stoprun-ddfb-20261022, tip eafcbd3e7d,
base ddfb29af7. The prior published branch is preserved; no force-push, delete
or old-name reuse. Six Rocko commits rebased, with one manual conflict in
scripts/mosaic's human CLI case: prepend halt|resume|processing and retain
row 202's appended access. packages/cli/src/cli.mjs auto-merges retain the
access import/branch and all three processing commands. CLI README retains
both the Access and Instance processing switch sections.
The full old/new tip diff has 15 paths (base plans/queue/logs, row 202's new access files and its three shared CLI paths), 2327 insertions/32 deletions. Within row 191's owned paths only CLI README, cli.mjs and scripts/mosaic differ, with the row 202 additions. rebase-ddfb-log.txt, rebase-ddfb-tip-diff.stat, rebase-ddfb-owned-diff.stat and rebase-ddfb-range-diff.txt retain exact evidence.
Manifest fd0f2740b1cccadaaad8c613640fdddb0497cdab33ec2c0fd11debf3cae6c4ee, 87 candidate paths. The package command lists were regenerated from this base; CLI includes access.test.mjs. All 73 mutant sites must preflight again. No tests ran, no result carries, and the complete gate waits for publication and Sage CLEAR after Megavolt's debug run.
Sage-2333 published eafcbd3e7. Their per-file patch-id comparison matches
the prior six-commit range except the exactly ruled scripts/mosaic dispatch
line; binary/secrets/attribution checks pass. Gate remains unrun pending CLEAR.
eafcbd3e7 full gate stopped on timer fixture attribution (sage-2339)
Run 2026-10-22T02:18:04Z–02:19:25Z. HEAD, 87 blobs and fd0f2740 manifest verified. Short mktemp TMPDIR /mnt/storage/scratch/tmp/gxbC; named Compose project rocko-r191-gate. Nothing carried. 32 changed files completed: 313 passed, 6 failed, 0 skipped. All six new processing-browser sign-out cases stop at their common precondition, processingTimers length2 vs1. The original two browser cases pass. Their recorder attributes every 5000ms interval to processing, but app.js:307 already arms its own freshness timer. The intended processing interval is at processing.js:87. These new cases have not yet exercised sign-out or killed KS57/KS58, so no behavior proof is claimed.
The gate stopped at this first red step. No package, shell, Docker workload or mutant ran; the esbuild rebuild was not reached. Runner exited, EXIT cleanup completed and cwd node/chromium sweep returned [] at 02:19:34Z. No source edit or retry followed the failure. Sage received the exact failure and a proposed test-only caller-attribution filter with the assertions unchanged. This is a fixture error, not a passing gate or a declared flake.
Timer recorder attribution correction (sage-2345)
Commit 4db8b57785, fast-forward on eafcbd3e7, is a one-line
test-only correction in processing-browser.test.mjs. Cause: app.js:307's
freshness interval is also 5000ms, and the recorder incorrectly counted it as
a processing interval. The recorder now requires the processing.js caller
stack. Every assertion remains byte-identical, including exactly one timer
before sign-out and zero after it. A second 5000ms interval from processing.js
would still be counted and fail the exactly-one assertion. No product byte
changes, and no test or mutant ran for this correction.
Manifest ffb46fbdb875f97ff2eb7a7bed8bf6d5c4df53b8a63c738ffcde5fc5f6b7f6ad, 87 paths. Full restart after publication and CLEAR, with nothing carried. Sage-2345 counts the timer-fixture red as the first in this 191 window; any second red stops and is escalated to Mos. Previous logs are retained in gate-attempt-eaf/.
Full gate on 0f8235277: second red (sage-2351)
Candidate: 0f8235277e on ddfb29af7.
Manifest: ffb46fbdb875f97ff2eb7a7bed8bf6d5c4df53b8a63c738ffcde5fc5f6b7f6ad.
No prior result carried. Start 2026-10-22T02:33:41Z; failed-step exit
2026-10-22T02:46:17Z. Fresh TMPDIR /mnt/storage/scratch/tmp/giNF.
Compose project rocko-r191-gate, trapped ownership-checked network cleanup.
| Step | Passed | Failed | Skipped | Exit |
|---|---|---|---|---|
| 34 changed test files singly | 330 | 0 | 0 | 0 |
| processing-control | 61 | 0 | 0 | 0 |
| bus | 646 | 0 | 0 | 0 |
| cli (including access) | 783 | 0 | 0 | 0 |
| discord | 192 | 0 | 0 | 0 |
| webui | 323 | 1 | 1 | 1 |
| tasks, seat, project, library | not run | — | — | — |
| all ten scripts/test-*.sh | not run | — | — | — |
| all 73 mutants | not run | — | — | — |
Singles sum independently confirmed with awk over all 34 TAP logs. The sole failure is shell.test.mjs:380 in the full shell-browser test: scrollHeight 1062 vs innerHeight 1000. Full evidence is gate-logs/package-webui.log (not ok 271, line 1626). All prior manual-redirect/sign-out failures and eight processing-browser cases pass, but the desktop short-page geometry is still wrong. No passing layout or full-gate claim is made.
Known host-drift TAP skip: editor rebuild requires exactly esbuild 0.28.2, while shared node_modules has 0.28.1. Full line is in tap-skips.json. This skip is not counted as a red. No shell suite ran, so skip-lines.txt has no ^skip shell line. No Docker test workload or mutant started.
Stopped at the first failed step without retry or product edits, per sage-2351. This is the second red in the 191 window and is with Sage for Mos escalation under mos-0823. Parent runner exited; EXIT cleanup completed. Cwd-scoped node and chromium sweep returned [] at 02:47:14Z, product worktree is clean, and the slot was returned. No in-review move was made.
mos-1248 / sage-2363: desktop viewport allocation (unrun static candidate)
The second red on 0f8235277 was shell.test.mjs:380 (1062 versus 1000).
The shell gives .frame a viewport-based minimum at packages/webui/src/public/shell.css:135;
processing.css:12-14 replaced that minimum but used a column flex body with only
min-height:100vh, so the new bar was not allocated a bounded share of the viewport.
The desktop body now uses explicit grid rows for the command bar, controls, optional
banner, frame and footer. The frame row is minmax(min-content,1fr): it takes the
remaining short-page space while long content may grow the document. No clipping,
overflow suppression, fixed body height, test viewport change or assertion removal.
The existing shell.test.mjs:380 equality stays byte-identical. Added assertions
check actual processing-bar visibility, positive height, viewport placement and
no document scroll at 1440x1000; the existing 1440x420 long-page checks remain.
KS59 reverts processing.css to 0f8235277's bytes and must fail that same shell
browser test. Total: 74 planned mutants. No test or mutant has run on this fix.
Webby must statically review this delta before Sage opens the full no-carry gate.
Correction after Webby B1 (webby-0104, 2026-10-22 03:00Z)
The cause stated in the mos-1248/sage-2363 note above is withdrawn.
processing.css loads after shell.css and already overrides the frame minimum.
With the tree fixed and inspector hidden, the remaining floor is the Board's
main content. The grid min-content row preserves that floor, so 5cd32f4c1
is not an accepted layout fix. Its static review is CHANGES at Webby's
REVIEW-layout.md, commit e2e7c60e5. No run established a new layout measurement.
Next step requires a granted fixture probe for main/control heights and an
owner layout ruling; no further product change or gate is authorized yet.
Existing shell assertions remain unchanged.
Static nav placement: mos-1249/mos-1250, sage-2383/2385/2386, webby-0106/0108
Fast-forward on 5cd32f4c1; the rejected grid is removed. The unchanged labeled region is now the first child of nav.tree, before its Console h2. The banner stays at its original body location with every id, role, label and shipped string unchanged. No processing.js change and no runtime reparenting. At >=760 the tree is the same fixed box, with the same width breakpoints and ordinary overflow:auto. The controls are non-shrinking and non-sticky; they scroll with overflowing nav links (sage-2386 withdraws persistent visibility). Below760 the region takes a full flex line before Console/Projects. Its mobile location changes from before .frame to first in the static nav; the banner therefore precedes it in a halted mobile view. Banner behavior itself is unchanged. Specificity (0,3,0) resets .btn margin/order and .small margin/basis, leaving the shell rules unchanged. No content is shortened and no overflow is hidden.
Correct height arithmetic (Webby B1): page=max(innerHeight,86+C), where C is main content height. Controls consume space within the existing nav box, not another body row. The old failing layout was max(innerHeight,86+barHeight+C). The halted banner remains a body row; Sage tracks that separately.
Candidate-test design change at processing-ui.test.mjs:67 under mos-1250. Old assertion:
assert.ok(html.indexOf('id="processing-controls"') < html.indexOf('<div class="frame">'));
New assertion text:
const controlsAt = html.indexOf('id="processing-controls"');
const mainAt = html.indexOf('<main id="main"'), inspectorAt = html.indexOf('<aside class="inspector"');
assert.ok(controlsAt >= 0 && controlsAt < mainAt, 'controls are outside and before #main');
assert.ok(!(inspectorAt < controlsAt && controlsAt < html.indexOf('</aside>', inspectorAt)),
'controls are outside aside.inspector');
Reason: the bar moves into the frame's first column under mos-1249 while remaining outside route-specific #main and aside.inspector. This is a change to our unlanded candidate assertion, not a landed assertion.
All existing shell assertions stay unchanged. Added bar-inside-tree assertion and diagnostic height output. New processing browser coverage checks 400px Stop order=0, visibility, focus and position above Projects; also on-load visibility/focus at1440x1000,1440x420,800x420. Debug logs report controls/tree heights at those desktop sizes and main height; Sage judges controls over half the 334px nav at1440x420 before the window. No run yet.
Mutant delta: KS59 now reverts the complete layout (HTML and CSS together); KS60 hides the controls; KS61 moves them into #main; KS62 drops the (0,3,0) button reset. Total77. Every new site has its named killing test.
sage-2394 debug on published da4334806 (2026-10-22)
03:14:37Z–03:14:53Z: shell.test.mjs whole 5/5, processing-browser.test.mjs whole 9/9, 0 failures/skips. awk sum14/0/0. Original shell short-page and long-page assertions pass unchanged. Logs/results and empty cwd sweep are in debug-da4334806/. Slot clear sent Sage/Webby03:15:11Z after sweep. Controls/tree/main heights: read-only shell1440x1000 212.5/914/914; writable processing fixture1440x1000 127/914/914;1440x420 127/334/907.734375;800x420 127/334/1131.65625. Stop visible/order0/focusable/aboveProjects at400x1000. Writable127 is below half the334 nav. The read-only212.5 height at1000 was flagged for Sage's usability call; that state was not measured at420, so no claim is made that all states use less than half the short nav. No mutants or full gate run under this debug grant. Await separate CLEAR.
R6 accepted: sage-2399 / webby-0111 (2026-10-22 03:16Z)
Sage accepts the short-nav usability tradeoff. Writable controls occupy38% of the334px nav at1440x420. The read-only recovery note makes that about64%, inferred from the measured212.5px height at the same width. The region is non-sticky and scrolls away; Projects was already below the fold at that size before191. Webby confirmed the debug TAP and has no window blocker. Sage tracks the read-only note length with the halt-banner follow-up; no change to this row.
Do not rebase or run now. Row273 lands first. On Sage's landing message, rebase the candidate including the two latest layout commits onto the new refactor under a new branch name (mos-1086), then provide range-diff, patch-ids and the refreshed88-product-path manifest. The full no-carry window requires a separate Sage CLEAR on that published tip.
Rebase after row273: sage-2402 (2026-10-22 03:42Z)
New branch rocko/row191-stoprun-86f9-20261022, tip
0fa7bf421f, on86f95bb27. All10 commits
rebase cleanly and range-diff pairs each with '='; no conflict resolution.
All88 per-file patch-ids match the old candidate. Whole product diff stable
patch-id before/after:0846823aefe165363601a6c68134ad46cc701c73.
87 product blobs are identical; only docs/TOOLS.md changes because the new
base carries row273's --send/--no-sso usage and three explanatory F39 lines.
191's TOOLS hunks stay unchanged. New88-path manifestSHA256:
0bcbf337433f6d46d809ee1dcaf8a5a8503160403d273cf73d6dac64adef3c02.
Range-diff, per-path patch-ids and TOOLS comparison are rebase-86f9-* files.
Static77-site exact-once preflight has0errors. No tests run, nothing carried
into the required full window; await Sage publication and separate CLEAR.
Full no-carry window on0fa7bf421: stopped at SR08 (sage-2407/2418)
03:44:56Z–04:01:29Z. All35touched files passed336/0/0; nine packages passed2403/0 with1known editor/esbuild skip. Every shell exited0:425selftests plus156queue node tests passed; the canonical-root queue check and two explicit live-provider exclusions are saved in skip-lines.txt. See GATE-RESULTS.md for per-suite counts and mutant table. SR01–SR07 killed. SR08 timed out at90seconds without named assertion failure (TAP header only); runner restored all88candidate blobs and stopped. The69 later mutants did not run. SR08 is not counted as killed. Cwd sweep[] and owned network cleanup completed; slot clear sent Sage04:02:12Z. Saved mutation, timeout policy lines64–89 and shell/skip table sent Sage in response to sage-2418. No source edit or retry; no in-review move. Await Mos ruling and explicit Sage CLEAR before any control/replay/resume.
SR08 timeout policy: mos-1259 / sage-2423 (2026-10-22 04:07Z)
Cause confirmed by Mos: runtimes.mjs:333 loops on now() <= deadline, while stop-run.test.mjs:106-108 gives the second host a fixed fake clock with real sleep. Removing the join branch enters the stop loop without advancing that clock. Original SR08 log contains TAP header only; original timeout record stays immutable. Mos permits separate classification as killed-by-timeout only after the unmutated same whole test file passes the same90second harness in this resumed run. Control result: not run; awaiting CLEAR. No assertion kill is claimed for SR08.
Runner review requested from Dewey, Sage copied. SHA256 of run-mutants.py: fe0d360f86d86ab2df967da5338479c593c27c88d06eb38a1389d99a08489369. Diff:runner-mos1259.diff; baseline: run-mutants.before-mos1259.py. Shared execution harness uses90seconds, own process groups, verified descendant cleanup and restored source bytes. A control must pass every test with exit0, no not-ok/skip/cancel/fail. Its record binds invocation id, candidate HEAD/manifest and test hash; all88candidate blobs verified before and after control, and before each mutation. The approved historical SR08 classification and69-site SR09+resume use separate files so the original seven kills and timeout evidence remain intact. Assertion kills and timeout kills have separate counters. No control for the same file in this invocation means a timeout stops; survivors and invalid failures stop too. Every timeout gets a cause/control record before review.
No product/test change, no control/mutant execution. Wait for independent runner approval and Sage CLEAR. Green suites carry only on unchanged0fa7bf421 and manifest0bcbf337. Test clock fix is deferred to Vikunja502 as Mos ruled.
Independent runner approval: dewey-0789 (2026-10-22 04:11:20Z)
Dewey APPROVES the frozen fe0d360f86d86ab2df967da5338479c593c27c88d06eb38a1389d99a08489369 runner, static only. Use only the proposed --control-file stop-run.test.mjs --adjudicate-timeout SR08 --resume-from SR09 invocation. A positional-id or full run would overwrite the original evidence and is not this resume.
Report the complete tally as7 prior assertion kills (old status killed), plus SR08 separately adjudicated by timeout after control passes, plus69 resumed sites. The summary file counts only this invocation. No control or resume result exists yet; Sage CLEAR remains required.
Classification change: the reviewed runner recognizes indented not-ok lines with ^\s* rather than only top-level lines. Controls therefore reject nested failures too, and mutant assertion kills still require the named pattern in a failing test name. SR01–SR07 evidence was classified by the original runner.
Historical SR08 has no HEAD field. Its binding to0fa7bf421 relies on the saved commit.txt/log timestamps and the new candidate HEAD+88blob check, not a retroactively invented HEAD field in the old result. Preserve this provenance in the adjudication report. Any newly detected timeout needs a concrete cause before review; the generic placeholder is not accepted review evidence.
Control and resume: sage-2427, stopped on KS43
Control/resume began04:13:44Z; last saved mutant result2026-10-22T04:14:08Z; process absence confirmed04:14:56Z and slot returned to Sage. Whole unmutated stop-run.test.mjs control passed12/12, exit0, no not-ok, no skips/cancels, in0.459seconds. The reviewed runner adjudicated original SR08 separately as killed-by-timeout under mos-1259. The immutable original SR08 row/log stay unchanged; adjudication binds the control, exact cause, current HEAD and manifest. Historical HEAD provenance remains as Dewey N4 described.
Resume stopped at KS43, not retried. It removes the inner processingHTTP origin check and its selected outer-route test passed1/1(exit0). Saved evidence:resume-mutant-logs/KS43.tap and resume-mutant-results.json. Tally:7prior assertion kills +49resumed assertion kills =56assertion kills; 1historical timeout kill;1survivor(KS43);19unrun. No new timeouts or placeholder causes. All88candidate blobs restored and resume cwd sweep[]; no product or test change. No in-review move. Sage and Mos notified directly.
Static diagnosis only: KS43 selects processing.test.mjs:52's outer-server fence test. The unchanged direct-handler test at:95 already isolates this origin guard from serve's outer refusal. Its pattern was not selected. Sent recommendation to Sage/Mos to correct only the mutant's named killer after their ruling, then run KS43+19remaining. No metadata edit or rerun authorized yet; no claim the direct-handler test kills it until the run proves it.
KS43 metadata retarget: mos-1261 (2026-10-22 04:16:41Z)
Original pattern processing write fences refuse selected processing.test:52.
KS43 survived with1passing test and no writer call, preserved in
resume-mutant-results.json and resume-mutant-logs/KS43.tap. The serve-level
test cannot isolate the handler guard: outer fences and later refusal can
mask its removal. No product defect or new kill is claimed from static read.
New pattern: processing handler independently refuses wrong origin and cross-site before its writer,
the existing direct processingHTTP test at:95-107 with valid user/site/content
headers, asserted403 and no writer call. Only KS43's pattern changed in the
77-site table; product/test/mutation bytes unchanged. Generator mirrors it.
TableSHA256:5dbc8308c995e1974d6da63b3daa967896d822154eab38a8bb96154be667edf5. Diff:mutant-table-mos1261.diff, baseline:all-mutants.before-mos1261.json. Dewey must independently review this metadata diff before the next run. Static audit of all19unrun sites: mutant-pattern-audit-mos1261.md; no other serve-level/direct-handler mismatch with an existing direct test warrants retargeting. KS44 body-bound case has no direct-handler counterpart; its oversized whitespace+{} case is valid JSON without the bound, so it retains the existing pattern.
Carry56assertion kills+1timeout kill and green suites only on unchanged
0fa7bf421. Next approved scope is KS43+19sites after review and Sage CLEAR.
No run authorized by this metadata change.
Retarget review APPROVE and C1 archive: dewey-0791 (2026-10-22 04:19:55Z)
Dewey approves table5dbc8308 and the19-site audit, conditional on preserving the first resume evidence before any next run. Archive:mos-1261-archive/, full per-file inventory:mos-1261-archive/sha256-manifest.txt.
-
resume-mutant-results.jsonSHA256f5725ef26cdb488441285081fadaa9ce4a3e7d390ab2a1c6d04acfd27f105fc6 -
resume-mutant-logs/KS43.tapSHA256c778ee33edb667f795ab560a328fd5c1c04ef6acf99d7b79c364f6302cf29864 -
unmutated-control.jsonSHA256ee9ddcd69d24276165abe1185f159a2737157fcae8fd37f731768e9324b765e5 -
SR08-timeout-adjudication.jsonSHA256214a04696d3329ef67bf10578daf4d251599816fd246bc31abecae1a6230e1e0
The50-row result, all first-resume logs and control/adjudication records were copied byte-for-byte. Original paths remain untouched too. A separate retarget-mos1261/ directory holds byte-identical approved runnerfe0d360f, reviewed table5dbc8308 and identical candidate/commit files. The proposed --resume-from KS43 invocation there selects20sites and writes its own logs and results without overwriting either original or archive. No control flag is needed for these tests; any timeout without a same-file control stops. Final tally will combine7old assertionkills +49first-resume assertionkills + SR08separate timeout adjudication +20retarget results. Still no run; awaiting Sage CLEAR. Product/test bytes remain unchanged.
KS43 retarget run: sage-2436, stopped on KS44 invalid mutation
Run began04:21:06Z; KS43 is killed by the named direct-handler assertion. KS44 then fails import with SyntaxError Unexpected token catch at processing-http.mjs:40. The failing TAP name is the test file, not the selected test, so runner records invalid-failure and stops without a kill. Evidence remains in retarget-mos1261/console.log,resume-mutant-results.json and resume-mutant-logs/KS43.tap,KS44.tap. No original evidence overwritten.
Cause: our KS44 mutation uses // no body bound to replace an inline
if (size > 1024) throw Error(); in a one-line for-await body. The comment
swallows the remaining chunks.push and closing brace. This is malformed
mutation metadata, not an observed product failure. No metadata correction
or retry yet. Proposed to Sage/Mos: replace only the new text with void 0;,
then independent review and a new CLEAR for KS44+18 on unchanged candidate.
Current tally57assertionkills (7+49+1),1SR08timeoutkill,1invalid(KS44),18unrun. Cwd sweep[] and all88candidate hashes restored04:21:30Z; slot returned and Sage/Mos notified. No in-review move. Wait for ruling before any edit or run.
KS44 syntax metadata correction: mos-1264 (2026-10-22 04:22:16Z)
Only KS44.new changes from // no body bound to void 0;. Old site,
test and pattern stay unchanged. The invalid import result remains in
retarget-mos1261/resume-mutant-results.json and resume-mutant-logs/KS44.tap.
TableSHA256:85d9a7b13ad510e840f258d892afbfce393cefbc4006e1f808605b83adc84570. Diff:mutant-table-mos1264.diff;
baseline:all-mutants.before-mos1264.json. Generator mirrors the one field.
Authorized syntax-class preflight applied KS44–KS62 individually in scratch,
ran node --check on each JavaScript file, and restored before advancing.
All15JS checks passed; no other replacement fix was needed. KS59–KS62
change only HTML/CSS and are explicitly asset-only/not-applicable for the
Node parser; Mos/Sage informed, no false JS syntax pass claimed. All19
mutations restored and88candidate hashes match. Per-site logs/results and
restoration record:syntax-mos1264/. No behavioral test or assertion-mutant
run occurred. Dewey must review table diff and syntax results before next
Sage CLEAR for KS44+18. Carry57assertionkills+1timeoutkill only on unchanged
0fa7bf421. No product or test change.
dewey-0795 approval: syntaxfixed-mos1264 staged (unrun)
Dewey APPROVES table85d9a7b1 and syntax preflight, static only. Conditions met:syntaxfixed-mos1264/ holds byte copies of runnerfe0d360f, table85d9a7b1, commit.txt,candidate.txt,candidate-manifest.sha256. Full SHA256 and byte-cmp list is syntaxfixed-mos1264/byte-copy-check.txt. Invocation after Sage CLEAR: python3 syntaxfixed-mos1264/run-mutants.py --resume-from KS44 (19sites). All previous invalid/survivor evidence stays untouched in its original dirs. No behavioral run occurred during preparation.
Final19 resume stopped at KS54: sage-2444 (2026-10-22)
Run began04:27:45Z; KS44–KS53 are10named assertion kills. KS54 then timed out at90.073seconds. Its log contains the expected dependency-list assertion: "the runtime refuses an invalid adapter and closes a valid one" at bus/tests/tasks.test.mjs:263. The mutation drops processing from runtime.mjs tasks factory deps. The test opens runtime then asserts before close at:265; a failing assertion skips the close and leaves Node alive. No same-file control ran in this invocation, so this is timeout-without-control, not a kill. No assertion or timeout kill is claimed for KS54.
Raw resume result's generic cause sentence says a control passed, which is incorrect: its control:null and timeout-without-control status establish the opposite. The raw evidence remains unchanged; the concrete cause and correction are in syntaxfixed-mos1264/KS54-timeout-report.json. This explicit report replaces the placeholder as explanation without altering the log.
Current tally67assertionkills(7+49+1+10),1adjudicatedSR08timeoutkill, 1unqualifiedKS54timeout,8unrun. All88candidate blobs restored; cwd sweep[] and slot returned04:30:06Z to Sage, Mos directly copied as instructed. No retry, product/test edit or in-review move. Sage's disclosed syntaxcheck caused no busy refusal or foreign-node report. Await owner ruling/CLEAR.
Final controls/mutants GREEN: mos-1267, sage-2448, dewey-0798
On unchanged0fa7bf421, whole-file tasks control9/9 passed in0.815s; KS54 rerun killed-by-timeout with the exact dependency not-ok at tasks.test:263. KS55–KS62 are8assertionkills. Final run04:35:32Z–04:37:17Z, cwd sweep[] and 88hashrestore04:37:48Z; slot returned to Sage and direct handoff to Dewey/Mos. Final77-site tally:75assertionkills(7+49+1+10+8),2separate timeoutkills (SR08adjudication,KS54control+rerun). final-mutant-results.json consolidates latest accepted evidence by id; no prior record or log overwritten. GATE-RESULTS.md is the final per-suite/mutant table; prior narrative saved as GATE-RESULTS-before-final.md.
KS54 raw placeholder result saved as resume-mutant-results.raw.json before filling concrete cause in its review result. Same-invocation control id 1792643732624962173; prior syntaxfixed eleven-row result file remains exact 0ede036954ff77c21f29e1a744b21d1d9b18eb75736f78ecd1cf4ae559358911. Dewey independently read logs/control/restoration and confirmed tally in dewey-0798, explicitly not yet a manifest verdict. N6test cleanup stays deferred under mos-1267/Vikunja502; no candidate byte changes permitted.
Claimant review handoff
Queue move rocko-191-review-r1 entered in-review at revision3114, round1 on#1689, manifest0bcbf337. Revision3115 records the expected missing-token request failure; command exit1. Receipt:in-review-receipt.txt. Sage posts the request as jarvis; Dewey owns the manifest verdict. Candidate source remains published0fa7bf421 with88product paths, base86f95bb27. No live action, push, source change or further gate authorized by this handoff.