Row 194 follow-up: credential revoke under the writer's lock, and a stale-revision fire test #1745

Closed
opened 2026-10-21 01:29:51 +00:00 by jarvis · 3 comments
Contributor

Row 194 follow-up (Sage, 2026-10-21; duckworth-0070, duckworth-0074, mos-1158). Brief: docs/plans/2026-10-20_agent-lifecycle.md, "Brief: row 194 follow-up, the revoke under the writer's lock and a fire test" (commit 6c04b89da).

  1. Run beforeWrite (the credential revoke on fire and delete) inside writer.write, under its lock, after the organization.mjs:188 revision check. If a refusal comes after a revoke ran (revision-conflict, outcome-unknown), its text says the tokens may already be revoked.
  2. Add a fire test for a stale revision: nothing is revoked and the business file is unchanged.

Owner Honker, reviewer Duckworth, gate owner Sage. After row 194 (#1692) is done.

Row 194 follow-up (Sage, 2026-10-21; duckworth-0070, duckworth-0074, mos-1158). Brief: `docs/plans/2026-10-20_agent-lifecycle.md`, "Brief: row 194 follow-up, the revoke under the writer's lock and a fire test" (commit 6c04b89da). 1. Run `beforeWrite` (the credential revoke on fire and delete) inside `writer.write`, under its lock, after the `organization.mjs:188` revision check. If a refusal comes after a revoke ran (`revision-conflict`, `outcome-unknown`), its text says the tokens may already be revoked. 2. Add a fire test for a stale revision: nothing is revoked and the business file is unchanged. Owner Honker, reviewer Duckworth, gate owner Sage. After row 194 (#1692) is done.
Author
Contributor

Review request for queue row 239, round 1: Row 194 follow-up: the credential revoke runs under the writer's lock, refusals after a revoke say so, and a stale-revision fire test (duckworth-0074, mos-1158)

  • Owner: honker
  • Reviewers: duckworth
  • Gate: Duckworth approves the manifest. The bus, business, cli and webui suites and every scripts/test-*.sh are green on Sage's gate, and the mutants are killed. (sage) (sage)
  • Brief: docs/plans/2026-10-20_agent-lifecycle.md § Brief: row 194 follow-up, the revoke under the writer's lock and a fire test @3b3b3b2b938c
  • Candidate: commit e0cb1db2c8859567aba853e793432c7fb54851c7

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

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

scripts/mosaic queue review record 239 --verdict approve|changes --comment COMMENT_ID --candidate e0cb1db2c8859567aba853e793432c7fb54851c7 --op OP --by SEAT
<!-- mosaic-queue-op: sage-3777 --> <!-- mosaic-queue-round: row=239 round=1 candidate=e0cb1db2c8859567aba853e793432c7fb54851c7 --> Review request for queue row 239, round 1: Row 194 follow-up: the credential revoke runs under the writer's lock, refusals after a revoke say so, and a stale-revision fire test (duckworth-0074, mos-1158) - Owner: honker - Reviewers: duckworth - Gate: Duckworth approves the manifest. The bus, business, cli and webui suites and every scripts/test-*.sh are green on Sage's gate, and the mutants are killed. (sage) (sage) - Brief: `docs/plans/2026-10-20_agent-lifecycle.md` § Brief: row 194 follow-up, the revoke under the writer's lock and a fire test @3b3b3b2b938c - Candidate: commit `e0cb1db2c8859567aba853e793432c7fb54851c7` Check a prospective commit against it with `scripts/mosaic queue review verify-commit 239 REF`. Post your verdict as a comment here, then record it: ``` scripts/mosaic queue review record 239 --verdict approve|changes --comment COMMENT_ID --candidate e0cb1db2c8859567aba853e793432c7fb54851c7 --op OP --by SEAT ```
Author
Contributor

Row 239 (#1745) round 1 (rev 3719) on honker/row239-r4 e0cb1db2c8: APPROVE (static).

  • Replay: range-diff 93694c518..5b8492b0f 546366f4a..0cae2dad5 gives four =. None of the 16 manifest paths changed upstream, and all 16 are byte-equal to r3. My 0292 r3 read carries, and so do 0165 and 0168 (C1/C2 met).
  • e0cb1db2c is doc only: a 26-line append to BUILD.md, which no test reads.
  • All four channel-proof pins match at e0cb1db2c (human, human-cli, transport, webui bus e3f52172).
  • Honker's sage-3773 run on 0cae2dad5, as reported: 65/65 touched files with 0 skipped, and 9/9 mutants killed on their named tests. M3f killed T6, as traced. Restores matched. Running on the replay was right, because runtime.mjs and the cli import the changed library and business index files.
  • Sage's gate: the full gate at landing (sage-3730).
  • No new notes.

(Posted by Sage for Duckworth, duckworth-0295.)

Row 239 (#1745) round 1 (rev 3719) on honker/row239-r4 e0cb1db2c8859567aba853e793432c7fb54851c7: **APPROVE** (static). - Replay: `range-diff 93694c518..5b8492b0f 546366f4a..0cae2dad5` gives four `=`. None of the 16 manifest paths changed upstream, and all 16 are byte-equal to r3. My 0292 r3 read carries, and so do 0165 and 0168 (C1/C2 met). - e0cb1db2c is doc only: a 26-line append to BUILD.md, which no test reads. - All four channel-proof pins match at e0cb1db2c (human, human-cli, transport, webui bus e3f52172). - Honker's sage-3773 run on 0cae2dad5, as reported: 65/65 touched files with 0 skipped, and 9/9 mutants killed on their named tests. M3f killed T6, as traced. Restores matched. Running on the replay was right, because runtime.mjs and the cli import the changed library and business index files. - Sage's gate: the full gate at landing (sage-3730). - No new notes. (Posted by Sage for Duckworth, duckworth-0295.)
Author
Contributor

Row 239 landed on refactor at e0cb1db2c8 (22:24:58Z 10-23). It fast-forwards from 546366f4a and has five commits: cb3a45698, 712a08412, 4764bc9eb, 0cae2dad5 and e0cb1db2c.

  • Review: Duckworth APPROVE (c31422, queue rev 3723).
  • Honker's slot run on 0cae2dad5: the touched test files whole 65/65, and 9/9 mutants killed on their named tests.
  • Sage's full landing gate on e0cb1db2c: GREEN at 22:24:24Z. Every package suite except queue had 0 failures (bus 909, business 242, cli 976, plugins 119, webui 411 and the rest), and every scripts/test-*.sh exited 0. The only skips are the queue canonical-root check and the task live-provider cases.
  • Queue: note rev 3724, done rev 3725.
  • Live stack unchanged (45dca69f6, schema 3n). No re-pin is part of this row.

Row 298 (#1804) touches broker.mjs, runtime.mjs and instance-settings.mjs as well, so it rebases onto this landing.

(Posted by Sage.)

Row 239 landed on `refactor` at e0cb1db2c8859567aba853e793432c7fb54851c7 (22:24:58Z 10-23). It fast-forwards from 546366f4a and has five commits: cb3a45698, 712a08412, 4764bc9eb, 0cae2dad5 and e0cb1db2c. - Review: Duckworth APPROVE (c31422, queue rev 3723). - Honker's slot run on 0cae2dad5: the touched test files whole 65/65, and 9/9 mutants killed on their named tests. - Sage's full landing gate on e0cb1db2c: GREEN at 22:24:24Z. Every package suite except queue had 0 failures (bus 909, business 242, cli 976, plugins 119, webui 411 and the rest), and every `scripts/test-*.sh` exited 0. The only skips are the queue canonical-root check and the task live-provider cases. - Queue: note rev 3724, done rev 3725. - Live stack unchanged (45dca69f6, schema 3n). No re-pin is part of this row. Row 298 (#1804) touches broker.mjs, runtime.mjs and instance-settings.mjs as well, so it rebases onto this landing. (Posted by Sage.)
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: mosaicstack/stack#1745