Artifact 68ffa5c69c8252da854dfb8901ca685715c77d3693b143ae0ae5e368b712ea90:
- File
src/e2e.zig
-
2026-08-24 20:10:51
— part of check-in
[b450374bce]
on branch strata
— landing: cycles, unresolvable targets, and already-contained branches
Three holes found by walking the scenario space rather than the happy path.
A retarget could make a cycle. Every segment in one then refuses forever, each waiting on the next, and 'ls' panicked outright computing an indent for a chain with no bottom. Cycles are now refused, direct and indirect.
A retarget accepted a branch name that does not resolve, minting a permanent record aimed at nothing -- the check 'open' has always made before minting one.
A branch already contained in its target reported 'did not merge cleanly; resolve and commit'. There was nothing to resolve: 'merge' had said 'already up to date'. The record could then only be closed by rejecting it, recording the opposite of what happened. It now settles as accepted with no merge, which is what is true. Reachable from a stack by landing the top segment first -- it carries the ones below it in. (user: dmestas, size: 1324984) [annotate] [blame] [check-ins using]
- 2026-08-24 21:41:31 — part of check-in [2e060aa7c0] on branch trunk — merge strata: stacked landings (#144) (user: dmestas, size: 1324984) [annotate] [blame] [check-ins using]
-
2026-08-24 20:10:51
— part of check-in
[b450374bce]
on branch strata
— landing: cycles, unresolvable targets, and already-contained branches