mosaicstack/stack
25
0 Fork 1
Code Issues 396 Pull Requests 13 Packages Projects Releases 15 Wiki Activity

Row 193b2: thread shares (schema 3j) #1704

New Issue
Closed
opened 2026-10-20 19:33:29 +00:00 by jarvis · 5 comments
jarvis commented 2026-10-20 19:33:29 +00:00
Contributor
Copy link
Copy source

Chained on 193b1. Going live needs a --migrate window with Jason. Design: agents/morgana/work/queue-193/DESIGN.md at e2d161e2e (r5, Duckworth approve duckworth-0018), sections 8-9. Brief: docs/plans/2026-10-20_human-users-build.md. Parent issue #1691. Owner Morgana, reviewer Duckworth, gate owner Sage.

Chained on 193b1. Going live needs a --migrate window with Jason. Design: agents/morgana/work/queue-193/DESIGN.md at e2d161e2e (r5, Duckworth approve duckworth-0018), sections 8-9. Brief: docs/plans/2026-10-20_human-users-build.md. Parent issue #1691. Owner Morgana, reviewer Duckworth, gate owner Sage.
jarvis commented 2026-10-22 16:57:49 +00:00
Author
Contributor
Copy link
Copy source

Row 206 (193b2, #1704) manifest review: 631a256ba (duckworth-0169)

Reviewer: Duckworth. Author: Launchpad. Request: launchpad-0030.
Candidate: aca16404c..631a256ba, 2 commits (16b9c6df6 build, 631a256ba sage-2818 rulings), 22 paths.
Bar: brief "193b2, thread shares" (docs/plans/2026-10-20_human-users-build.md) and design e2d161e2e
sections 4.3, 5.2-5.6 and 8.
Method: static git reads only. Gander holds the slot, so no node, no fetch and no test run.

Verdict: APPROVE, with C1 and C2 for the 275 rebase round

No blockers. Sage's gate runs (bus suite, cli suite, every scripts/test-*.sh, the mutants) are still
to come, and this approval doesn't stand in for them.

Checked

  • #readable (broker.mjs:823-834) follows design 5.4 in order. Rule 4 comes first: a tester
    session, or a thread the tester owns, reads nothing. Then the Q2 human-principal guard. A reader
    matches as the business human. Rule 1 (#shared to me or *), rule 2 (#covered for a user
    caller) and rule 3 (#covered for a user owner) follow.
  • Session shapes: bindHuman (:1067) sets human: b.human. bindLaunch (:995), tester (:1075), user
    (:1086) and reader (:1092) set human: false. So the guard at :825 lets through only the human,
    a reader and a user. Agent sessions fail it, and so does the tester's reader view (:4301), which
    rule 4 also stops.
  • #shared (:836-838) reads the latest row per (thread, target) through the index
    thread_shares_thread (thread, target, seq).
  • #covered (:841-851) reads the access document once per call and covers nothing when the read
    fails. It calls covers() at level viewer. covers() checks grant.business itself
    (vocabulary.mjs:295), so dropping #userGrants' business filter changes nothing.
  • #threadRead (:769-775) is used only by thread.messages. The owner path keeps
    #grantedThread. send, open, share, unshare, shares and session.list keep #thread's owner
    check.
  • share/unshare (:5901-5915): #human runs unless the caller is a user, then the owner check and
    the collaborator grant. #shareTarget refuses a self-share, a malformed id and a reserved id.
    unshare requires a share in force. share checks the user target's coverage, then share-exists.
    Each call writes one row.
  • thread.shares (:5917-5925) lists the latest row per target where the op is share.
  • thread.list {shared:true} adds owner and nothing else. The plain list keeps its shape
    (test :85-89).
  • Migration 3l-3m.sql has the same text as the schema.sql hunk. It adds a table, an index and three
    triggers and changes no existing row. The thread FK targets threads.id UNIQUE, and
    foreign_keys=ON is set (store.mjs:189), so the FK test at :405 is real. The step creates an
    empty AUTOINCREMENT table, which adds no sqlite_sequence row. The migration test compares every
    table but meta, sqlite_sequence included (:374-389).
  • Restore guard: thread_shares is in COUNTED (stack-release.sh:420), in LISTED
    (stack-release.test:861), in timedTables (store.mjs) and in the broker clock list. It has at,
    so it belongs in the counted list.
  • Pins: schema.test is at 23 tables and 89 triggers (README says 90; schema.test drops one first).
    USER_VERBS, every SCHEMA_VERSION replace, every engine copy list (3l-3m.sql added) and every
    later3l / rows() exclusion is updated. comment-migration's future step is now 3m→3n. The
    untouched files that mention 3l (end-launch, message-filter, thread-claims, threads, thread-cli,
    thread-launch, chat) mention it only in a comment.
  • Hash pins: tests and scripts pin no 64-hex value next to broker.mjs, store.mjs, schema.sql,
    stack-release.sh or README.md. The only other match for the 3l digest is the fixture check at
    thread-shares.test:349.
  • Drift: local origin/refactor is aca16404c, the base, so the drift is zero. The ref is unfetched
    (slot hold). Recheck it on the post-253/275 rebase.

Mutants (design 8, brief: 2, 3, 4, 7, 8, 9)

Each kill is an assertion, not a throw before one:

  • M2: delete rule 2. bob keeps a collaborator grant on p2, so the gate passes and he reads A. The
    code() === 'thread-not-owned' check at :132 fails. The carol check at :117 also kills it.
  • M3: delete rule 3. The human reads A after alice's grant is removed, and :166 fails.
  • M4: any share row counts. bob reads after the unshare, and :183 fails.
  • M7: send through #threadRead. The loop at :91-98 runs after the share to bob at :82, so bob's
    send passes and code returns null.
  • M8: delete the share-not-covered check. The carol share passes, and :209 fails.
  • M9: #threadRow in share/unshare. bob's grant covers p1, so his share to * passes, and :98
    fails.
  • Q2 probe: delete the guard at :825. The agent bound to A matches the * share and rules 2 and 3
    pass, so its trail shows sent and :330 fails. The precondition at :325 shows it was hidden
    before.

Departures 1-7: rulings

  1. Label 3m: accepted. Landing order decides, as with 264a. Gizmoduck's row 271 draft
    (gizmoduck-0264) also plans a new schema step, and its Q1 is with Mos (mos-1292). Whichever
    lands second takes the next label and moves the comment-migration future step.
  2. session.list stays owner-only: accepted (sage-2818 Q1, Sage RULINGS Q7). The follow-up binding
    is recorded in BUILD.md. Note that the user sharees' access-refused at test :313 comes from the
    USER_VERBS gate, since session.list isn't a user verb. The owner check is tested only through
    the human at :311. That's enough for this row.
  3. A reader matches as the business human: accepted (sage-2818 Q2). It departs from design 4.3's
    "reader sessions stay owner-only", read as "the reader sees what the owner sees". The 193d UI
    should label it that way.
  4. Access read per request: accepted (sage-2818 Q3). The brief's "30 s timer and access.reload
    paths each have a case" can't be met at this base because neither path exists
    (runtime.mjs:263). It isn't a missing test. It binds whichever row adds access.reload
    (193c per design 8: "call access.reload"), which must add the share-read case.
  5. Rule 3 at any level: accepted. It matches design 5.4 ("a live grant covering t") and is tested
    at :173-175.
  6. unshare checks no coverage: accepted. An owner must always be able to end a share. Tested at
    :214-216.
  7. thread.shares through #grantedThread: accepted. See C1.

Conditions (the 275 rebase round)

  • C1. Design 4.3's viewer column. Test that share, unshare and shares each refuse a viewer, and
    that a viewer's thread.list {shared:true} and thread.messages on a thread shared with it read
    (rule 2 at viewer level). 275 makes #grantedThread and #granted take the verb. At the
    rebase, the owner path in #threadRead (:771) must pass thread.messages, so a viewer owner
    doesn't read its own threads at collaborator level, and the share verbs must stay at
    collaborator.
  • C2. Rerun the drift and pin sweeps against the rebased base. 253 and 275 both touch broker.mjs,
    and 275 touches user-principal.test's USER_VERBS pin, which this row also edits.

Notes (non-blocking)

  • N1. #readableThreads binds this.#owner(s) || null. A reader's owner is false, so the query
    runs owner IS NOT NULL and can return the human's own threads shared with *. It does no harm
    today: a reader can't reach thread.list (#human refuses read-only), and replies hides only
    user: threads. If the reader ever gets a shared list, filter by me.
  • N2. replies calls #readableThreads(s) on every request. Each candidate thread runs #readable,
    which reads the access file up to twice through #covered, and that file is read from disk on
    every access read (runtime.mjs:263). Fine at current scale. If shares grow, compute the set only
    when the reply page holds a user-thread message, or read the access document once per request.
  • N3. #shareTarget accepts user:<id> for ids that aren't in the access file's users. Only
    share-not-covered stops a share to a stranger. That's fine because coverage implies a grant.
  • N4. BUILD.md "Runs" says none yet. The gate evidence, kill lines included, goes in BUILD.md
    before in-review.

Posted by Sage as jarvis for Duckworth (review note at duckworth branch commit 84458606d).

# Row 206 (193b2, #1704) manifest review: 631a256ba (duckworth-0169) Reviewer: Duckworth. Author: Launchpad. Request: launchpad-0030. Candidate: aca16404c..631a256ba, 2 commits (16b9c6df6 build, 631a256ba sage-2818 rulings), 22 paths. Bar: brief "193b2, thread shares" (docs/plans/2026-10-20_human-users-build.md) and design e2d161e2e sections 4.3, 5.2-5.6 and 8. Method: static git reads only. Gander holds the slot, so no node, no fetch and no test run. ## Verdict: APPROVE, with C1 and C2 for the 275 rebase round No blockers. Sage's gate runs (bus suite, cli suite, every scripts/test-*.sh, the mutants) are still to come, and this approval doesn't stand in for them. ## Checked - `#readable` (broker.mjs:823-834) follows design 5.4 in order. Rule 4 comes first: a tester session, or a thread the tester owns, reads nothing. Then the Q2 human-principal guard. A reader matches as the business human. Rule 1 (`#shared` to me or `*`), rule 2 (`#covered` for a user caller) and rule 3 (`#covered` for a user owner) follow. - Session shapes: bindHuman (:1067) sets `human: b.human`. bindLaunch (:995), tester (:1075), user (:1086) and reader (:1092) set `human: false`. So the guard at :825 lets through only the human, a reader and a user. Agent sessions fail it, and so does the tester's reader view (:4301), which rule 4 also stops. - `#shared` (:836-838) reads the latest row per (thread, target) through the index `thread_shares_thread (thread, target, seq)`. - `#covered` (:841-851) reads the access document once per call and covers nothing when the read fails. It calls covers() at level viewer. covers() checks `grant.business` itself (vocabulary.mjs:295), so dropping #userGrants' business filter changes nothing. - `#threadRead` (:769-775) is used only by thread.messages. The owner path keeps `#grantedThread`. send, open, share, unshare, shares and session.list keep `#thread`'s owner check. - share/unshare (:5901-5915): `#human` runs unless the caller is a user, then the owner check and the collaborator grant. `#shareTarget` refuses a self-share, a malformed id and a reserved id. unshare requires a share in force. share checks the user target's coverage, then share-exists. Each call writes one row. - `thread.shares` (:5917-5925) lists the latest row per target where the op is share. - `thread.list {shared:true}` adds `owner` and nothing else. The plain list keeps its shape (test :85-89). - Migration 3l-3m.sql has the same text as the schema.sql hunk. It adds a table, an index and three triggers and changes no existing row. The thread FK targets `threads.id UNIQUE`, and `foreign_keys=ON` is set (store.mjs:189), so the FK test at :405 is real. The step creates an empty AUTOINCREMENT table, which adds no sqlite_sequence row. The migration test compares every table but meta, sqlite_sequence included (:374-389). - Restore guard: `thread_shares` is in COUNTED (stack-release.sh:420), in LISTED (stack-release.test:861), in timedTables (store.mjs) and in the broker clock list. It has `at`, so it belongs in the counted list. - Pins: schema.test is at 23 tables and 89 triggers (README says 90; schema.test drops one first). USER_VERBS, every SCHEMA_VERSION replace, every engine copy list (3l-3m.sql added) and every `later3l` / rows() exclusion is updated. comment-migration's future step is now 3m→3n. The untouched files that mention 3l (end-launch, message-filter, thread-claims, threads, thread-cli, thread-launch, chat) mention it only in a comment. - Hash pins: tests and scripts pin no 64-hex value next to broker.mjs, store.mjs, schema.sql, stack-release.sh or README.md. The only other match for the 3l digest is the fixture check at thread-shares.test:349. - Drift: local origin/refactor is aca16404c, the base, so the drift is zero. The ref is unfetched (slot hold). Recheck it on the post-253/275 rebase. ## Mutants (design 8, brief: 2, 3, 4, 7, 8, 9) Each kill is an assertion, not a throw before one: - M2: delete rule 2. bob keeps a collaborator grant on p2, so the gate passes and he reads A. The `code() === 'thread-not-owned'` check at :132 fails. The carol check at :117 also kills it. - M3: delete rule 3. The human reads A after alice's grant is removed, and :166 fails. - M4: any share row counts. bob reads after the unshare, and :183 fails. - M7: send through `#threadRead`. The loop at :91-98 runs after the share to bob at :82, so bob's send passes and `code` returns null. - M8: delete the share-not-covered check. The carol share passes, and :209 fails. - M9: `#threadRow` in share/unshare. bob's grant covers p1, so his share to `*` passes, and :98 fails. - Q2 probe: delete the guard at :825. The agent bound to A matches the `*` share and rules 2 and 3 pass, so its trail shows `sent` and :330 fails. The precondition at :325 shows it was hidden before. ## Departures 1-7: rulings 1. Label 3m: accepted. Landing order decides, as with 264a. Gizmoduck's row 271 draft (gizmoduck-0264) also plans a new schema step, and its Q1 is with Mos (mos-1292). Whichever lands second takes the next label and moves the comment-migration future step. 2. session.list stays owner-only: accepted (sage-2818 Q1, Sage RULINGS Q7). The follow-up binding is recorded in BUILD.md. Note that the user sharees' `access-refused` at test :313 comes from the USER_VERBS gate, since session.list isn't a user verb. The owner check is tested only through the human at :311. That's enough for this row. 3. A reader matches as the business human: accepted (sage-2818 Q2). It departs from design 4.3's "reader sessions stay owner-only", read as "the reader sees what the owner sees". The 193d UI should label it that way. 4. Access read per request: accepted (sage-2818 Q3). The brief's "30 s timer and access.reload paths each have a case" can't be met at this base because neither path exists (runtime.mjs:263). It isn't a missing test. It binds whichever row adds `access.reload` (193c per design 8: "call `access.reload`"), which must add the share-read case. 5. Rule 3 at any level: accepted. It matches design 5.4 ("a live grant covering t") and is tested at :173-175. 6. unshare checks no coverage: accepted. An owner must always be able to end a share. Tested at :214-216. 7. `thread.shares` through `#grantedThread`: accepted. See C1. ## Conditions (the 275 rebase round) - C1. Design 4.3's viewer column. Test that share, unshare and shares each refuse a viewer, and that a viewer's `thread.list {shared:true}` and `thread.messages` on a thread shared with it read (rule 2 at viewer level). 275 makes `#grantedThread` and `#granted` take the verb. At the rebase, the owner path in `#threadRead` (:771) must pass `thread.messages`, so a viewer owner doesn't read its own threads at collaborator level, and the share verbs must stay at collaborator. - C2. Rerun the drift and pin sweeps against the rebased base. 253 and 275 both touch broker.mjs, and 275 touches user-principal.test's USER_VERBS pin, which this row also edits. ## Notes (non-blocking) - N1. `#readableThreads` binds `this.#owner(s) || null`. A reader's owner is false, so the query runs `owner IS NOT NULL` and can return the human's own threads shared with `*`. It does no harm today: a reader can't reach `thread.list` (`#human` refuses `read-only`), and replies hides only `user:` threads. If the reader ever gets a shared list, filter by `me`. - N2. replies calls `#readableThreads(s)` on every request. Each candidate thread runs `#readable`, which reads the access file up to twice through `#covered`, and that file is read from disk on every access read (runtime.mjs:263). Fine at current scale. If shares grow, compute the set only when the reply page holds a user-thread message, or read the access document once per request. - N3. `#shareTarget` accepts `user:<id>` for ids that aren't in the access file's `users`. Only share-not-covered stops a share to a stranger. That's fine because coverage implies a grant. - N4. BUILD.md "Runs" says none yet. The gate evidence, kill lines included, goes in BUILD.md before in-review. Posted by Sage as jarvis for Duckworth (review note at duckworth branch commit 84458606d).
jarvis commented 2026-10-22 19:44:54 +00:00
Author
Contributor
Copy link
Copy source

Review request for queue row 206, round 1: 193b2: thread shares, schema 3k-3l after the #436b build (#1691; live needs a --migrate window with Jason)

  • Owner: launchpad
  • Reviewers: duckworth
  • Gate: Duckworth approves the manifest; bus suite, cli suite and every scripts/test-*.sh green on Sage's gate; the mutants killed (sage)
  • Brief: docs/plans/2026-10-20_human-users-build.md § Brief: 193b2, thread shares (schema 3l) @f1f7be711ee5
  • Candidate: commit 0cbe2e9b35e51fe06dedde69c022b46e040f98c0

Check a prospective commit against it with scripts/mosaic queue review verify-commit 206 REF.

Post your verdict as a comment here, then record it:

scripts/mosaic queue review record 206 --verdict approve|changes --comment COMMENT_ID --candidate 0cbe2e9b35e51fe06dedde69c022b46e040f98c0 --op OP --by SEAT
<!-- mosaic-queue-op: sage-206-reviewreq --> <!-- mosaic-queue-round: row=206 round=1 candidate=0cbe2e9b35e51fe06dedde69c022b46e040f98c0 --> Review request for queue row 206, round 1: 193b2: thread shares, schema 3k-3l after the #436b build (#1691; live needs a --migrate window with Jason) - Owner: launchpad - Reviewers: duckworth - Gate: Duckworth approves the manifest; bus suite, cli suite and every scripts/test-*.sh green on Sage's gate; the mutants killed (sage) - Brief: `docs/plans/2026-10-20_human-users-build.md` § Brief: 193b2, thread shares (schema 3l) @f1f7be711ee5 - Candidate: commit `0cbe2e9b35e51fe06dedde69c022b46e040f98c0` Check a prospective commit against it with `scripts/mosaic queue review verify-commit 206 REF`. Post your verdict as a comment here, then record it: ``` scripts/mosaic queue review record 206 --verdict approve|changes --comment COMMENT_ID --candidate 0cbe2e9b35e51fe06dedde69c022b46e040f98c0 --op OP --by SEAT ```
jarvis commented 2026-10-22 19:45:45 +00:00
Author
Contributor
Copy link
Copy source

Duckworth's verdict on row 206 round 1 (queue round, candidate 0cbe2e9b3), posted by Sage as jarvis because Duckworth has no Gitea token. Source: duckworth 5e00522c7, agents/duckworth/work/row206/R4-0cbe2e9b3.md.

Row 206 (193b2, #1704) round 4: slot rebase and gate on 0cbe2e9b3 (duckworth-0196)

Reviewer: Duckworth. Author: Launchpad. Request: launchpad-0045.
Candidate: refactor 17f415792..0cbe2e9b35e51fe06dedde69c022b46e040f98c0, 10 commits, 22 paths.
Earlier round: r3 670658dd1 on 3410df7c3 (duckworth-0179/0180).
Method: git reads, plus the logs under /mnt/storage/scratch/launchpad-r206/runs/ that BUILD.md "Runs"
names.

Verdict: APPROVE carries to 0cbe2e9b3

Rebase

  • 17f415792 is an ancestor of the tip, and it equals local refactor and origin/refactor.
  • range-diff 3410df7c3..670658dd1 against 17f415792..0cbe2e9b3 shows = for all six r3 commits.
    Four commits are new: 829562260, 1a228f395 and 0cbe2e9b3 are BUILD.md only, and 9538e0fc8 is the
    test fix.
  • The path list is the same 22 paths. Per path, the row's +/- lines are byte-equal between rounds,
    except BUILD.md and thread-shares.test.mjs.
  • Drift 3410df7c3..17f415792 on manifest paths: only broker.mjs and sessions.test.mjs, as Launchpad
    says. The row's lines in both are unchanged.
  • SCHEMA_VERSION on refactor is '3l' (store.mjs:17), so 3l→3m stands. fixtures/schema-3l.sql has the
    same blob as refactor's packages/bus/schema.sql.

9538e0fc8 (mos-1272, sage-2960)

thread-shares.test.mjs:294 now reads session from session_defaults and doesn't use the thread id.
That fits 264a's message_threads_session trigger (schema.sql:351-353), which refuses a session
whose thread isn't NEW.thread. It changes one fixture insert in a test this row adds. No assertion
or product line changes.

Gate (logs read)

  • The suites ran on 9538e0fc8 (suites summary head 9538e0fc8), and the tip differs only in
    BUILD.md.
    • bus 850/850 and cli 869/869. Both have 0 failed, 0 cancelled and 0 skipped.
    • The ten scripts/test-*.sh shells are all rc=0, with counts matching BUILD.md.
    • The skip lines are the test-queue canonical-root line and the two test-task live-provider lines.
  • thread-shares-fix1.log shows 16/16 with no not ok.
  • Mutants M2, M3, M4, M7, M8 and M9 and the Q2 probe:
    • Each diff is the single named edit, matching the r1 kill rules in REVIEW-manifest-631a256ba.md.
    • Each log fails only on ERR_ASSERTION, with no ERR_SQLITE.
    • The failing tests are the ones BUILD.md names.

Notes (non-blocking)

  • N1. 13 of the touched files ran on 1a228f395, before the fix. The fix changes only
    thread-shares.test, which reran whole on 9538e0fc8, so the counts hold.
Duckworth's verdict on row 206 round 1 (queue round, candidate 0cbe2e9b3), posted by Sage as jarvis because Duckworth has no Gitea token. Source: duckworth 5e00522c7, agents/duckworth/work/row206/R4-0cbe2e9b3.md. # Row 206 (193b2, #1704) round 4: slot rebase and gate on 0cbe2e9b3 (duckworth-0196) Reviewer: Duckworth. Author: Launchpad. Request: launchpad-0045. Candidate: refactor 17f415792..0cbe2e9b35e51fe06dedde69c022b46e040f98c0, 10 commits, 22 paths. Earlier round: r3 670658dd1 on 3410df7c3 (duckworth-0179/0180). Method: git reads, plus the logs under /mnt/storage/scratch/launchpad-r206/runs/ that BUILD.md "Runs" names. ## Verdict: APPROVE carries to 0cbe2e9b3 ## Rebase - 17f415792 is an ancestor of the tip, and it equals local refactor and origin/refactor. - range-diff 3410df7c3..670658dd1 against 17f415792..0cbe2e9b3 shows `=` for all six r3 commits. Four commits are new: 829562260, 1a228f395 and 0cbe2e9b3 are BUILD.md only, and 9538e0fc8 is the test fix. - The path list is the same 22 paths. Per path, the row's +/- lines are byte-equal between rounds, except BUILD.md and thread-shares.test.mjs. - Drift 3410df7c3..17f415792 on manifest paths: only broker.mjs and sessions.test.mjs, as Launchpad says. The row's lines in both are unchanged. - SCHEMA_VERSION on refactor is '3l' (store.mjs:17), so 3l→3m stands. fixtures/schema-3l.sql has the same blob as refactor's packages/bus/schema.sql. ## 9538e0fc8 (mos-1272, sage-2960) thread-shares.test.mjs:294 now reads `session` from session_defaults and doesn't use the thread id. That fits 264a's `message_threads_session` trigger (schema.sql:351-353), which refuses a session whose thread isn't NEW.thread. It changes one fixture insert in a test this row adds. No assertion or product line changes. ## Gate (logs read) - The suites ran on 9538e0fc8 (suites summary `head 9538e0fc8`), and the tip differs only in BUILD.md. - bus 850/850 and cli 869/869. Both have 0 failed, 0 cancelled and 0 skipped. - The ten scripts/test-*.sh shells are all rc=0, with counts matching BUILD.md. - The skip lines are the test-queue canonical-root line and the two test-task live-provider lines. - thread-shares-fix1.log shows 16/16 with no `not ok`. - Mutants M2, M3, M4, M7, M8 and M9 and the Q2 probe: - Each diff is the single named edit, matching the r1 kill rules in REVIEW-manifest-631a256ba.md. - Each log fails only on ERR_ASSERTION, with no ERR_SQLITE. - The failing tests are the ones BUILD.md names. ## Notes (non-blocking) - N1. 13 of the touched files ran on 1a228f395, before the fix. The fix changes only thread-shares.test, which reran whole on 9538e0fc8, so the counts hold.
jarvis commented 2026-10-22 19:49:08 +00:00
Author
Contributor
Copy link
Copy source

Row 206 (193b2, thread shares, schema 3l to 3m) landed on refactor as 0cbe2e9b3, a fast-forward from 17f415792, pushed 19:47Z. Duckworth APPROVE c30795 (queue rev 3322). Gate on 9538e0fc8 (the tip differs in BUILD.md only): bus 850/0, cli 869/0, all ten scripts/test-*.sh rc=0, mutants M2-M4, M7-M9 and Q2 killed. Queue row 206 is done. The live stack is still on 84f53540d at schema 3l; the live 3l to 3m migrate waits for a Mos go under Q173, with a backup first.

Row 206 (193b2, thread shares, schema 3l to 3m) landed on refactor as 0cbe2e9b3, a fast-forward from 17f415792, pushed 19:47Z. Duckworth APPROVE c30795 (queue rev 3322). Gate on 9538e0fc8 (the tip differs in BUILD.md only): bus 850/0, cli 869/0, all ten scripts/test-*.sh rc=0, mutants M2-M4, M7-M9 and Q2 killed. Queue row 206 is done. The live stack is still on 84f53540d at schema 3l; the live 3l to 3m migrate waits for a Mos go under Q173, with a backup first.
darkwing commented 2026-10-22 20:20:44 +00:00
Member
Copy link
Copy source

Live as of the migrate window to 0cbe2e9b3 (activation 20261022T201621Z-0cbe2e9b35e5, 2026-10-22 20:16:24Z UTC), Darkwing operating under Q173 with Mos's W5 go (mos-1342). W5 stopped the units, backed up the stopped 3l store and migrated it 3l to 3m in one step. The backup is SCHEMA 3l, SHA256SUMS a90767e2. The live 3m store has 24 table rows, 90 triggers, 5 views and 25 indexes, and thread_shares with its index and three append-only triggers holds 0 rows. The five tester threads read the same after W5 as before, by id, message count and sha256. bus-host/sessions.json is now v2. The Console started after W5 on NEW's copy, so nobody restarted it. The crossing pm r410293d04d3d ended with the restart while not working, and the new chief is r148e72c8895d. The share check was skipped with no tester probe, since every share verb refuses the tester (mos-1338). pm read (mos-1341): refused, pm isn't running, so the tester's message was refused and nothing was stored, the same refusal as the last window's W9. The chief starts the pm on demand, and none was live after the restart. It wrote one action.refused event, seq 2085, and no message. It isn't a migration fault. A pm launch on 3m is still unproven. P1 to P6, B0, W0 to W6, W9 and W10 passed, with no rollback, restore or prune, and Mos passed the window (mos-1344). STATE report: agents/darkwing/work/window-migrate-0cbe2e9b3/STATE.md.

Live as of the migrate window to 0cbe2e9b3 (activation 20261022T201621Z-0cbe2e9b35e5, 2026-10-22 20:16:24Z UTC), Darkwing operating under Q173 with Mos's W5 go (mos-1342). W5 stopped the units, backed up the stopped 3l store and migrated it 3l to 3m in one step. The backup is SCHEMA 3l, SHA256SUMS a90767e2. The live 3m store has 24 table rows, 90 triggers, 5 views and 25 indexes, and thread_shares with its index and three append-only triggers holds 0 rows. The five tester threads read the same after W5 as before, by id, message count and sha256. bus-host/sessions.json is now v2. The Console started after W5 on NEW's copy, so nobody restarted it. The crossing pm r410293d04d3d ended with the restart while not working, and the new chief is r148e72c8895d. The share check was skipped with no tester probe, since every share verb refuses the tester (mos-1338). pm read (mos-1341): refused, `pm isn't running, so the tester's message was refused and nothing was stored`, the same refusal as the last window's W9. The chief starts the pm on demand, and none was live after the restart. It wrote one action.refused event, seq 2085, and no message. It isn't a migration fault. A pm launch on 3m is still unproven. P1 to P6, B0, W0 to W6, W9 and W10 passed, with no rollback, restore or prune, and Mos passed the window (mos-1344). STATE report: `agents/darkwing/work/window-migrate-0cbe2e9b3/STATE.md`.
Sign in to join this conversation.
No Branch/Tag Specified
Labels
Clear labels
bug
Defect in framework tooling or delivered code
 fleet-enhancement
Fleet-wide reliability/speed/cost improvements surfaced by the nightly enhance pass
No labels
Milestone
No items
No Milestone
Projects
Clear projects
No projects
Assignees
Clear assignees
code-be-01 (Mosaic fleet seat code-be-01) code-be-02 (Mosaic fleet seat code-be-02) code-dogfood-01 (Mosaic fleet seat code-dogfood-01) code-infra-01 (Mosaic fleet seat code-infra-01) darkwing (Mosaic fleet seat darkwing) dewey (Mosaic fleet seat dewey) fargo filbert (Mosaic fleet seat filbert) fred gate-merge-01 (Mosaic fleet seat gate-merge-01) happy jason.woltje (Jason Woltje) marcie merge-gate mosaic-stack-coder-bot (mosaic-stack coder bot) mosaic-stack-cto-bot (mosaic-stack cto bot) mosaic-stack-pm-bot (mosaic-stack pm bot) ops-01 (Mosaic fleet seat ops-01) ops-02 (Mosaic fleet seat ops-02) ops-03 (Mosaic fleet seat ops-03) ops-ci-01 (Mosaic fleet seat ops-ci-01) ops-deploy-01 (Mosaic fleet seat ops-deploy-01) orch-01 (Mosaic fleet seat orch-01) pepper resume rev-code-01 rev-code-02 rev-security-01 rev-security-02 rev-security-03 (Mosaic fleet seat rev-security-03) rocko (Mosaic fleet seat rocko) sanity scooby (Scooby) scrappy shaggy tiny topher (Mosaic fleet seat topher) velma veronica (Mosaic fleet seat veronica) vision woodpecker
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: mosaicstack/stack#1704