row 249: BUILD.md for the rebase onto row 248's landing 8a04f4aa4

agents/gizmoduck/work/queue-249/BUILD.md

@@ -2,9 +2,9 @@
 
 Gitea #1751, Vikunja P19 445 under #436. Brief: docs/plans/2026-10-20_host-credentials.md, section
 "Machine grant row b follow-up: the undo can't prove the remote add has ended" (6de1ebc62). Reviewer
-Duckworth, gate owner Sage. Branch gizmoduck/row249 from origin/refactor bc579f7a8. No file under
-packages/bus/src changed between 6d5545d44 and bc579f7a8, so the brief's line numbers hold on the base.
-Line numbers below are on this branch.
+Duckworth, gate owner Sage. Branch gizmoduck/row249-on-8a04, on row 248's landing 8a04f4aa4 (sage-2012).
+No file under packages/bus/src changed between 6d5545d44 and 8a04f4aa4, so the brief's src line numbers
+hold on the base. Line numbers below are on this branch.
 
 ## Correction to the brief
 
@@ -50,26 +50,26 @@ deletes the local key file. There is no remote add to outlive a kill, and no rem
 
 packages/bus/tests/grant-executor.test.mjs:
 
-- `lateAdd` (:450) is the shared tail. After the grant ends it asserts the code, `hostLineLeft` on
+- `lateAdd` (:451) is the shared tail. After the grant ends it asserts the code, `hostLineLeft` on
   grant.failed, the sweep line in the notice, and that the undo's remove was the last request. Then it
   writes `release`, so the held add writes its line and exits 0, and waits for the line in `granted`. It
   checks there's no record, `hosts.status` lists the tag in `hostLineLeft`, `hosts.remove` refuses
   host-line-left, `hosts.sweep` returns `removed: [tag]` and the line is gone, then `hosts.remove`
   succeeds.
-- :467, the abort case. `hold-add`, the human approves, the add holds, `abortClaim` aborts the
+- :468, the abort case. `hold-add`, the human approves, the add holds, `abortClaim` aborts the
   executor's claim. Ends revoked.
-- :479, the timeout case. A 30 s wait is too long for the file, and making the timeout an option would
+- :480, the timeout case. A 30 s wait is too long for the file, and making the timeout an option would
   add a src seam, so the test wraps `install` through `opts.wrap` instead. The wrapper passes install its
   own AbortController signal, waits for `holding`, aborts it, which SIGKILLs the local ssh group as the
   timer does, then throws as a timed-out request does. The executor's signal isn't aborted, so it ends
   host-failed. Nothing under src changes for it.
-- G8 (:282) changes. fail-list and fail-add now carry `hostLineLeft` and the sweep line. noop-add fails at
+- G8 (:283) changes. fail-list and fail-add now carry `hostLineLeft` and the sweep line. noop-add fails at
   verify, after install returned, so it keeps no hint and the old message.
-- The comment at :435 (was :432) now says `skip` makes the held add exit without writing and that a
+- The comment at :436 (:432 at 6d5545d44) now says `skip` makes the held add exit without writing and that a
   killed session's add can still write. G13 has no such comment.
 
 Both new tests write `release`, so their held stub exits before `t.after` removes the dir. Row 248's dir
-check isn't needed for them.
+check (:67, :72) is the backstop.
 
 ## Mutant
 
@@ -80,3 +80,10 @@ once.
 ## Runs
 
 Pending Sage's slot: grant-executor.test.mjs whole, then C1. The bus suite runs on Sage's gate.
+
+## Rebase onto 8a04f4aa4 (sage-2012)
+
+The first commit, 02bfd184b, sat on bc579f7a8 as gizmoduck/row249, which was never pushed. Row 248 landed
+as 8a04f4aa4, changing grant-executor.test.mjs at :54, :67 and :72. gizmoduck/row249-on-8a04 starts at
+8a04f4aa4 and cherry-picks 02bfd184b with no conflict. 248's lines stay as landed. The patch-id is the
+same on both (c33823941e61). Test line numbers moved down by one, and this file was updated for that.