archilyzer

commit 9a7d7e1e27969ce2834c8cbe710996db6572d100
parent e0eff0ebe997b81a3297e27a2bd1e8ade97f7dcf
Author: I Mean I'm Just Saying <imeanimjustsaying@kiwifarms.st>
Date:   Tue, 29 Sep 2026 23:01:13 -0400

plans: UT's gates after the review and the merge of main — tsc; common 2,229; test:scripts 195 + 1 skipped (196); the capped umtool build passes the post-build check, and the same build with its BUILD_ID set back skips it, saying why

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>

Diffstat:
M
plans/release-15.md
 | 
18
+++++++++++++++++-

1 file changed, 17 insertions(+), 1 deletion(-)
diff --git a/plans/release-15.md b/plans/release-15.md
@@ -352,7 +352,9 @@ reached was the fixture's real files.
 | `a4d100b4` | `scripts:` review M1: the post-build check skips a build older than the code it judges |
 | `c3e8a2c7` | `scripts:` review L1 (only the build's own `cache/` and `dev/` unread, pinned), L2 (the check's comment says what it can see), L3 |
 | `b4d6607d` | `umtool:` review L3 in the `ignoreIssue` comment |
-| this commit | `plans:` the review's findings to their commits; FACTS (M1, L2, L3, L4); the changelog (M1); the rollout note |
+| `31bb0f8c` | `plans:` the review's findings to their commits; FACTS (M1, L2, L3, L4); the changelog (M1); the rollout note |
+| `7c6d4969` | merge of `main` (`721ed0eb`, release 14 HS and S1); clean, the changelog bullet still under `[Unreleased]` |
+| this commit | `plans:` the gates after the review and the merge |
 
 #### Gates (logs `$T/ut-*.log`)
 
@@ -389,6 +391,20 @@ reached was the fixture's real files.
   case once (`S1E1S3E3S2E2`) under a load average of about 26; it passed on the rerun, and this
   slice does not touch the queue lock.
 - **Numbers tool:** none.
+- **After the review and the merge of `main`** (at `7c6d4969`):
+  - tsc clean, 98 s;
+  - common **2,229/2,229** (`main`'s 2,229), 108 s;
+  - `test:scripts` **195 passed, 1 skipped (196)**: `main`'s 191 + 1 and the guard's four new
+    tests. The two runs before it each failed `queue-lock.test.mjs`'s "prints a banner naming the
+    holder while waiting" under a load average of about 26, the known flake (alone, 11/11 twice);
+    this slice does not touch the queue lock;
+  - umtool's build, capped, with the corpus linked and this worktree's own e2e fixture present:
+    48 s wall, max RSS 796 MB, the audio route 463, none under a dot-directory; the post-build
+    check passes on it;
+  - the same build with its `BUILD_ID` set back to 2026-09-01 (in place, then put back; nothing
+    committed): the check skips, `umtool/.next was built 2026-09-01T04:00:00.000Z, before
+    umtool/next.config.ts (219 changed since); rebuild umtool (…) to check its traces`. With the
+    mtime put back it passes again.
 
 #### Found and left