kimi was right that inline_undo_is_sealed matched itself: it grepped the whole file for a string that appears inside its own body, so it succeeded on every tree forever. Their suggested anchoring had the identical flaw for the identical reason — any literal this function searches for necessarily appears in this function — which I only found by running their probe and watching the pin stay green while the behavioural test went red. So it locates the real check by line number and reads only that block. head -1 takes the site at :202, never this body at :3311. Driven, since a pin nobody has watched fail is not a pin: deleting the :205 wiring now fails exactly this check, and deleting all three seals fails all three. That is the third vacuous guard I have written on this branch family; the comment says why the obvious shapes do not work, so the next person does not rediscover it a fourth time. Refs #136 Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> |
||
|---|---|---|
| .. | ||
| cli.sh | ||
| db-integration.sh | ||
| drill.sh | ||
| install-lifecycle.sh | ||
| release.sh | ||