| Comment: | Accepted. The guards go in before the work they guard. |
|---|---|
| Timelines: | family | ancestors | descendants | both | trunk |
| Files: | files | file ages | folders |
| SHA3-256: |
547cb92c6f49f026174943c984a5df8c |
| User & Date: | dmestas on 2026-08-25 21:08:13.570 |
| Other Links: | manifest | tags |
|
2026-08-25
| ||
| 21:08 | Accepted. History, with the cgo cost taken knowingly and the wasm path verified intact. check-in: 61c32a8057 user: dmestas tags: trunk | |
| 21:08 | Accepted. The guards go in before the work they guard. check-in: 547cb92c6f user: dmestas tags: trunk | |
| 19:05 |
tests: the regression guards that were never added
Seven test files were written this session, reported as landed, and never committed: `zit commit` with no paths captures TRACKED files, and new files need `zit add` first. make check passed every time because they were on disk in the worktree, which proves nothing about what is in the check-in. What was missing: - search kinds, held in agreement across four places (the index list, two ops validators, the scope chips, hitOf). This is the guard that caught `doc` and again `file` the moment each was added; without it the validator silently refused a kind the chips offered. - technote edits collapsing to one timeline row, folded in three different orders, because a clone delivers artifacts in wire order. - wiki and technote search matching the CURRENT revision only, the "terrified" case. - Contributors(0) meaning every contributor rather than a silent 100. - the ops phase states, the stalled-store trap, and an empty fleet. Verified by removing them and running the suite: it stays green, which is precisely the problem — trunk has been passing on their absence. closed check-in: 24fdaa723a user: dmestas tags: search-guards | |
| 19:03 | land ops-phase check-in: 96b30ad4f5 user: dmestas tags: trunk | |