Skip to content

docs(drift): a remedy that landed in the suite and not in the document, parked - #621

Merged
JulienMartel merged 1 commit into
mainfrom
worktree-check-yml-census-fails
Sep 23, 2026
Merged

JulienMartel merged 1 commit into
mainfrom
worktree-check-yml-census-fails

Conversation

@JulienMartel

Copy link
Copy Markdown
Contributor

What

One entry appended to docs/drift.md under Seen once, not yet a row. No row number added, the table is untouched.

A DRIFT REMEDY that lands in the suite and not in the document, so the copy a reader reaches first is the one nothing holds.

Why

haus#762 deleted the hand census of which checks CI covers and replaced it with checks-platform-split, which subtracts the two systems' attrNames. Right fix, and a check that cannot go stale. On haus 893bb427 the same exemption was still stated in words in five other places — four of them in .github/workflows/check.yml, the file a person opens to find out what CI runs — and the suite had been told about none of them. A comment beside an unrelated check in the same flake then rotted pointing at "the census", which by then named neither the list nor the check.

Parked rather than numbered: one sighting, and the numbering is frozen.

Verify

  • Claims checked against haus main at 893bb427: df478382 (#762) is the only commit touching checks-platform-split; the fixture is at flake.nix:6507; the rotted pointer is at flake.nix:6785-6786; grep -c brew-bundle-guarded .github/workflows/check.yml is 4, plus flake.nix:614.
  • "at least seven separate times" is attributed to haus's own comment, not asserted as a count.
  • Entry wraps ≤82, the file's prose runs to 86. Trailing newline intact.
  • Pre-PR assurance pass run on a clean-context subagent. It raised three findings ≥3/5 — row 20 unnamed as the nearer neighbour, a false "written down twice" count, and a Caught by that implied one fix closes the shape. All three are fixed in this branch; the entry now names both row 20 and row 33 and says the partial remedy out loud.
  • scruff overlap: no other lanes on workshop.

Watch out

  • The entry's first line goes stale the moment checks: check.yml's census is a fixture now, and the eval reads it haus#769 merges — it is anchored on 893bb427 for that reason, and drift.md's exemption for "used to / no longer naming a shape" is what keeps the past tense legal here.
  • A second sighting promotes this to row 35 and deletes the entry, per the section's own contract.

…t, parked

Parked under *Seen once, not yet a row*, not appended as row 35 — the numbering
is frozen and one sighting is not yet a general form.

The sighting is haus's census. #762 deleted the hand list of which checks CI
covers and replaced it with `checks-platform-split`, which subtracts the two
systems' `attrNames`. Right fix, and a check that cannot go stale. On haus
`893bb427` the same exemption was still stated in words in five other places,
four of them in `.github/workflows/check.yml` — the file a person opens to find
out what CI runs — and the suite had been told about none of them. A comment
beside an unrelated check in the same flake then rotted pointing at "the
census", which by then named neither the list nor the check.

Names both neighbours. Row 20 is the nearest: its check compares a snapshot of
the same data the prose describes, so re-blessing puts green back over a live
falsehood, where this one derives its fact from the population and is right
every run — what fails is jurisdiction, not freshness. Row 33 is the other: its
remedy IS the check that walks the population, and here that had already landed.

The **Caught by** says the partial remedy out loud rather than implying one
fix closes it: holding the reader's copy to the eval leaves every other copy
exactly as unheld, which is why the clause is to count them first.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
@JulienMartel
JulienMartel merged commit add72fd into main Sep 23, 2026
1 check passed
@JulienMartel
JulienMartel deleted the worktree-check-yml-census-fails branch September 23, 2026 08:01
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