Relock quire#1112 (it moved `.github/bats-version`, `.github/repository-version` and `bats.lock`) ran its merge-group check (run 43139237328, 2026-11-12 02:07:50Z to about 03:32Z) for 85 minutes. The merge-group run of #1111 (run 43127503194, 00:28Z) took 37 minutes. CI speed is p0.

## What the two runs show

* The caches were read: `build` restored `quire-build@e5334330...` and `quire-static@e5334330...` (main's caches, as the merge group is given its base's). They did not help, because of the line `bats: dropping build/ (made by another bats: bats differs)` at 02:30:23Z: the compiler moved, the stamp differs, and bats rebuilt everything. `build` took 2804 s against 354 s, "Check the app" 22 minutes against 46 seconds. That is bats's stamp rule working as designed (CLAUDE.md, "No cache key is relied on for correctness").
* `static (mutation-bytesarr-cut)` went from 5 s to 1854 s for another reason. In run 43127503194 the step "The plan names this group" was skipped (the change was docs only), so the group ran nothing: the 5 s was a skipped job, not a memo hit. In run 43139237328 the plan selected every group, and the step "Restore the fixtures' memo" printed `Cache not found for input keys: quire-static-memo-mutation-bytesarr-cut@5acafb5a..., quire-static-memo-mutation-bytesarr-cut@`: not even the prefix key matched, so no memo of this group exists in any cache the run can read. The group then ran its mutants from nothing (`mutation/bytesarr` 12 mutants in 3 min 12 s, `mutation/cut` 31 mutants until 03:25:31Z).
* Hypothesis, not yet shown: a group saves its `static-memo-<group>` only when it ran and passed, in the run it ran in, and a cache saved in a merge-group run (ref `gh-readonly-queue/...`) is readable only by that ref; main's push ends the static groups after their first step when the queue passed the commit (queue-passed, `.claude/rules/ci.md` "Who restores"), so main never saves a memo and no later run can read one. Every pin move or `check.yml` change then runs the long mutation groups from nothing.

## Done-when

1. A merge-group run for a pull request that changes a pin (`.github/bats-version` or `bats.lock`) restores a memo for each `static (mutation-*)` group that ran before, demonstrated by the step "Restore the fixtures' memo" of that run printing `Cache restored from key: quire-static-memo-<group>@` for each group the plan selected, found with `gh api repos/bats-lang/quire/actions/runs/<run>/jobs` for the first such run after the change merges.
2. The cold run of a pin move is bounded, demonstrated by each job's own log printing one line with how long the job took (`job took <seconds> s`, written by the job itself in its last step), and by a grep of that line from the log of each job of the run of item 1 showing every job under 1800 s (owner, 2026-11-12T05:52Z: "THE CI LOG ITSELF CAN HAVE A LINE THAT SAYS HOW LONG IT TOOK. Then you just grep it from the log.").

## Notes

The comparison of the two runs' job durations is in the conversation of the queue thread of 2026-11-12 (jobs of both runs via `gh api repos/bats-lang/quire/actions/runs/<run>/jobs`).

Item 2 of the earlier text (the reason stated in `.claude/rules/ci.md`) is dropped by the owner (2026-11-12T05:27Z: "yes, drop it ... by the time you finish the ticket, you've done that in code and that's the real documentation."): the reason is the code's comments.



---
_Generated by [Claude Code](https://claude.ai/code)_
