row 206 (#1704): BUILD.md Runs, gate GREEN on 9538e0fc8 (bus 850, cli 869, shell suites, M2-M9 and Q2 killed)

2026-10-22 14:40:53 -05:00
1 parent 9538e0fc86
commit 0cbe2e9b35
@@ -183,4 +183,69 @@ phase goes to Mos unplaced (mos-1275).

 ## Runs

-None yet. Node and https git wait for Sage's CLEAR (Gander holds the slot for row 253 run 5).
+Slot from sage-2959 (CLEAR 19:13Z 10-22). Claimed rev 3317. Everything ran on launchpad/row206-17f4
+on refactor 17f415792, after `npm ci --ignore-scripts` from the lockfile (oauth4webapi 3.8.8, no
+symlinked node_modules). Each run had TMPDIR from `mktemp -d /mnt/storage/scratch/tmp/gXXXXXX` and
+`timeout -k 10` at the limits above. Logs are in /mnt/storage/scratch/launchpad-r206/runs/.
+
+- First-run red, placed under mos-1272 (Sage accepted it, sage-2960). On 1a228f395,
+  thread-shares.test.mjs "the owner's trail and replies..." failed with ERR_SQLITE_ERROR "a threaded
+  message's session is in its thread". The test inserted the reply's message_threads row with
+  session = the thread id, but a fresh thread's default session has its own id (264a; only a
+  migrated thread's reuses the thread's). The fix (9538e0fc8) reads the session from
+  session_defaults. It changes one fixture line in a new test, with no product change and no
+  assertion changed.
+- Each touched file, whole and alone. The first 13 ran on 1a228f395 (the code under test is the
+  same at 9538e0fc8); thread-shares reran on the fix.
+
+  | File | Pass/fail |
+  |---|---|
+  | thread-shares | 16/0 on 9538e0fc8 (15/1 before the fix) |
+  | schema | 1/0 |
+  | sessions | 7/0 |
+  | user-principal | 22/0 |
+  | account-migration | 3/0 |
+  | chief-of-staff | 42/0 |
+  | comment-migration | 5/0 |
+  | gitea-migration | 5/0 |
+  | grant-migration | 6/0 |
+  | name-migration | 1/0 |
+  | spec-migration | 1/0 |
+  | thread-migration | 3/0 |
+  | usage-migration | 1/0 |
+  | cli stack-release.test | 218/0, 580 s |
+
+- Mutants on 9538e0fc8 (19:28Z). Each is one exact edit on a copy of the tree (the edit must
+  match once), running thread-shares.test.mjs. All are killed on ERR_ASSERTION in the named test:
+
+  | Mutant | Result | Failing tests | Assertion message |
+  |---|---|---|---|
+  | M2 | 14/2 | "mutant 2" and the `*` test | |
+  | M3 | 15/1 | "mutant 3" | "removed" |
+  | M4 | 14/2 | "mutant 4" and the trail test | "human" |
+  | M7 | 15/1 | the first test | "thread.send" |
+  | M8 | 15/1 | "mutant 8" | "user:carol" |
+  | M9 | 14/2 | the first test and "a share target is..." | "thread.share" |
+  | Q2 probe | 15/1 | "only a human principal" | "agent after" |
+
+- Suites on 9538e0fc8, 19:28:23Z to 19:40:25Z, all rc=0:
+
+  | Suite | Pass/fail |
+  |---|---|
+  | bus | 850/0 |
+  | cli | 869/0 |
+  | test-auth | 15/0 |
+  | test-conductor | 17/0 |
+  | test-config | 31/0 |
+  | test-discord | 81/0 |
+  | test-extension-package | 18/0 |
+  | test-foundation | 44/0 |
+  | test-land-work | 86/0 |
+  | test-queue | 156/0 |
+  | test-release | 14/0 |
+  | test-task | 91/0 |
+
+  The skip lines are by design. test-queue skips "verify and render --check" because the worktree
+  isn't the canonical root. test-task skips the "live provider cases" twice (row 244: no provider
+  call in the gate). No Docker group skipped.
+- Result: GREEN.