gosalyn: row 221 BUILD.md, cherry-picked onto 213's landing tip 62ddc96cc as 48f044ccc, patch-id eb094ae78 unchanged, singles 419/0 (sage-1925, sage-1932)

2026-10-21 05:30:50 -05:00
parent 48f044ccc2
commit 8f403d0d4c
1 changed files with 17 additions and 0 deletions
@@ -139,3 +139,20 @@ files 2
 profile default: lines 3, lines starting "# " or "## " 0, lines naming a Hermes tool or channel 0
 profile chet: lines 2, lines starting "# " or "## " 0, lines naming a Hermes tool or channel 0
 ```
+
+## Rebase onto 213's landing (sage-1925)
+
+213 landed as 361ba2387, with the same `git patch-id --stable` as r4 2b3e67e36, f313e69b6f7e. The
+refactor tip was 62ddc96cc. I cherry-picked 2d7a99aee onto it under the new branch gosalyn/c2-20-r2 as
+48f044ccc. The patch-id is eb094ae783e9 before and after. None of the 22 paths changed between 2b3e67e36
+and 62ddc96cc. The fence export from sage-1836 Q1 was already in the commit: `personaTextFault` from
+packages/harness/src/bundle.mjs, called by the script. I checked the test list again on the new base by
+grepping tests and scripts/test-*.sh for each non-test path's basename. The new hits name other packages'
+package.json files or write lockfiles in temp dirs, so the 18 files stand. 231 landed after that as
+29ce1e360. It touches only packages/library and the queue-231 packet, none of these 22 paths.
+
+Rerun on 48f044ccc, slot grant sage-1932, 10:18:09Z to 10:30:14Z, after a busy check. All 18 files ran
+whole, one `node --test` each, every rc 0: 419 pass, 0 fail, 0 cancelled, summed by awk. That's two more
+than the 417 above, both from the base. stack-release went from 195 to 196 and stack-upgrade from 20 to 21,
+and rows 238 and 240 changed those test files. Every other file has the count in the table above. The dry
+run printed the same three lines, rc 0.