hygiene(tick-history): 2026-05-03T09:52Z — #1369 merged (non-null assertion)

docs/hygiene-history/ticks/2026/05/03/0952Z.md

@@ -0,0 +1 @@
+| 2026-05-03T09:52:00Z | opus-4-7 / autonomous-loop continuation | a2e2cc3a | **#1369 (tsc-strict fix on no-op-cadence.ts) merged 09:51:43Z — gap-close shard before Step 0a threshold fires.** PR #1369 review correction: `m2[1]!` / `m2[2]!` non-null assertions preserve regex-required-groups invariant explicitly (vs `?? ""` silent-fallback that would mask regex breakage). Reviewer's catch: `?? ""` IS a valid TS strict-mode fix but masks the real invariant; non-null assertion documents the regex guarantee. Composes with the substrate-claim-checker discipline at the type-system layer: assertion-of-invariant beats silent-fallback. Step 0a tick gap was 14 min (threshold 15) — wrote this shard to document the merge before threshold-warning fires. **Pattern observation**: the .ts port discipline now has 3 review iterations under it (#1366 with 6 P1/P0/P2 findings → #1369 tsc-strict fallback initial fix → #1369 review reframed `?? ""` to non-null assertion). Each iteration sharpened the type-correctness expression. Composes with Aaron's "carved sentence = compression" discipline at the code layer: code style should express invariants as tightly as the type system permits, not paper over them. | #1369 (tsc-strict + review reframe) MERGED `09:51:43Z` | This tick teaches **non-null assertion preserves invariant; silent fallback masks bug surface**. When a regex match is conditional on the regex matching at all (truthy `m2`), the captured groups are guaranteed by the regex shape. Use `m2[1]!` / `m2[2]!` to express that guarantee in the type system; reserve `?? "default"` for cases where the default IS the legitimate fallback. Future-Otto: when TS strict-mode complains about regex-match-group access inside an `if (match)` block, prefer non-null assertion over `?? ""`. CADENCE-TRACK: per-tick mechanical-check + write-on-substantive-observation discipline applied this tick. |