archilyzer

commit c9b7c309c1aab50a67a3a12eb1643329fd1da1eb
parent 0d8a6f276d4faefb5a2f7b0b8d9fdbea0cc223fb
Author: I Mean I'm Just Saying <imeanimjustsaying@kiwifarms.st>
Date:   Sat, 12 Sep 2026 02:49:09 -0400

plans: the S2b note names its own sha

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

Diffstat:
M
plans/one-core-phase-2.md
 | 
4
++--

1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/plans/one-core-phase-2.md b/plans/one-core-phase-2.md
@@ -386,7 +386,7 @@ is S3's gate, after the search pipeline lands.
 ### S2b — shipped 2026-09-12
 
 Branch `one-core/phase-2-s2b`, off `7f86aef` (the `integrate/2026-09-storage-priority`
-tip with S1 merged). Two commits, `745677f` → `RECSHA` (this note), unmerged. Nothing
+tip with S1 merged). Two commits, `745677f` → `fa3873a` (this note), unmerged. Nothing
 outside `umtool/report-to-video/` moved except one comment in `common/lib/channelMedia.ts`
 and this note. **No URL shape, no `corpus.json` byte, no CONTRACT version, no
 architecture allow-list entry.**
@@ -394,7 +394,7 @@ architecture allow-list entry.**
 | commit | what |
 |---|---|
 | `745677f` | `checkChannelReachable` in `cues.mjs` + 7 test cases; the cross-reference comment |
-| `RECSHA` | this note |
+| `fa3873a` | this note |
 
 #### What the guard actually refuses, and what it deliberately does not