Repository navigation
Give the Surface repair its own migration timestamp - #14777
thebytorsnowdog wants to merge 1 commit into
Conversation
|
|
Giving the Surface repair its own timestamp ( |
|
Reviewed by Claude Opus 5.5 against the source, with nothing run on a worker. There was no second opinion: Codex Medium, the configured reviewer, refused because today's review budget is spent. So this one has no class label yet; it gets one when a second model has looked at it. The collision you found is real. That fix is already on the pull request that will land instead. #14541 lost to the older #8151, and #8151 now carries the same Surface migration as The ordered-runner tests here exercise This waits on the maintainer, who decides #8151; once that lands, this and #14541 can be closed. |
Follow-up to #14541. This PR targets
fix/issue-7111, the existing PR's branch inomacom/omarchy, and contains only our correction on top ofc501b37e3d22. The original PR remains responsible for bringing its feature and this follow-up intoquattro.Give the Surface module repair a migration filename separate from the repository-priority repair already shipped at 1791403252. The renamed 1791403253 migration keeps its behavior and ordering, with a matching machine-wide marker and fixture reference.
Add real ordered-runner regressions proving both migrations complete independently, an old priority marker does not hide Surface work, and failed rebuilds remain pending before later work. Mock the fixture DMI identity so these checks run headlessly. All 25 focused checks and the same 25 on a clean merge with Quattro 2519fd9 pass; the original filename still causes an add/add conflict and fails the new queue regression. The old per-user 3252 completion marker is ambiguous for old unmerged-branch testers; the old global marker remains specifically Surface-owned because repository priority uses no global marker. Neither is reused or deleted automatically, so old testers may receive one conservative extra Surface rebuild.
Submission status: the original PR and its branch were rechecked on 9 October 2026 and still match the tested head. Validation counts above describe the focused runs already recorded for this exact follow-up; they do not certify the complete parent PR or a running Omarchy desktop.