Skip to content

Say what the state/ canary does not catch - #13

Merged
LucideLarp merged 1 commit into
mainfrom
otto/state-canary-caveats
Jul 25, 2026
Merged

Say what the state/ canary does not catch#13
LucideLarp merged 1 commit into
mainfrom
otto/state-canary-caveats

Conversation

@LucideLarp

Copy link
Copy Markdown
Collaborator

Comment-only in the tests. The canary that asserts the repository's state/ is untouched by a run has two properties worth writing down, because the obvious improvement to either would make it catch less:

  • it compares each file's length, not its content, so a rewrite landing on the same size passes;
  • both driver suites run it, in their own processes, against the one shared directory, so a stray write fails both and the reporting file need not be the causing file.

Both are the price of measuring the real directory, which is the one thing a harness bug cannot route around.

Separately, reconcile-subs.js cited the local fulfillment runner as prior art for the lock design. That script is being retired, so the pointer goes and the reasoning stays. Nothing should send a reader to a file that no longer exists.

Suite unchanged: 402 tests, 400 pass, 0 fail, 2 skipped.

It compares file length rather than content, and both driver suites run it
against the one shared directory so either can be failed by the other's writes.
Written beside it because the obvious tidy-up, watching only this file's own
writes, would miss the bug it exists to catch.

reconcile-subs.js no longer points at the retired local runner for the lock
design. The reasoning it was citing stays.
@LucideLarp
LucideLarp merged commit 7153056 into main Jul 25, 2026
12 checks passed
@LucideLarp
LucideLarp deleted the otto/state-canary-caveats branch July 25, 2026 13:30
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant