HOTSPOT-SPLIT 2/2: per-feature fixture groups and regen steps; sorted .gitattributes

.gitattributes

@@ -1,33 +1,33 @@
 # Generated outputs of `pnpm regen` (scripts/regen.ts): a merge keeps this side of each, and `pnpm regen` then rebuilds them
 # from the merged sources. The driver needs `pnpm setup:git` once per clone; without it git merges these files as text.
-# packages/parity/test/regen.test.ts keeps this list equal to the regen steps' outputs.
-packages/dragon/src/css/grammar.generated.ts merge=dragon-generated
+# packages/parity/test/regen.test.ts keeps this list equal to the regen steps' outputs, sorted, so features add lines in different places.
 THIRD_PARTY_NOTICES.md merge=dragon-generated
-packages/dragon/src/ua/*.generated.ts merge=dragon-generated
-packages/parity/expected/darwin-arm64/** merge=dragon-generated
-packages/parity/emitted/** merge=dragon-generated
-packages/parity/expected-fonts/** merge=dragon-generated
-packages/dragon/src/profiles/ios.ts merge=dragon-generated
+examples/music-player/dragon/north-star-check.json merge=dragon-generated
+packages/dragon/src/css/grammar.generated.ts merge=dragon-generated
 packages/dragon/src/profiles/android.ts merge=dragon-generated
-packages/dragon/src/profiles/web.ts merge=dragon-generated
+packages/dragon/src/profiles/ios.ts merge=dragon-generated
 packages/dragon/src/profiles/native-lanes.ts merge=dragon-generated
-packages/parity/expected-dpr/** merge=dragon-generated
-packages/parity/expected-hit/*.hit.json merge=dragon-generated
+packages/dragon/src/profiles/web.ts merge=dragon-generated
+packages/dragon/src/ua/*.generated.ts merge=dragon-generated
+packages/layout/break-vectors/** merge=dragon-generated
+packages/layout/generated/** merge=dragon-generated
+packages/layout/paint-vectors/*/vectors.json merge=dragon-generated
+packages/layout/rt-vectors/animator/** merge=dragon-generated
+packages/layout/rt-vectors/hit/** merge=dragon-generated
 packages/layout/vectors/*.json merge=dragon-generated
 packages/layout/vectors/dpr-*/** merge=dragon-generated
-packages/layout/rt-vectors/hit/** merge=dragon-generated
-packages/layout/break-vectors/** merge=dragon-generated
+packages/parity/emitted/** merge=dragon-generated
 packages/parity/expected-breaks/** merge=dragon-generated
-packages/parity/expected-pixels/** merge=dragon-generated
+packages/parity/expected-dpr/** merge=dragon-generated
+packages/parity/expected-fonts/** merge=dragon-generated
 packages/parity/expected-frames/** merge=dragon-generated
-packages/layout/rt-vectors/animator/** merge=dragon-generated
-packages/layout/paint-vectors/*/vectors.json merge=dragon-generated
-packages/layout/generated/** merge=dragon-generated
-packages/translate/corpus.json merge=dragon-generated
-packages/translate/corpus-dpr.json merge=dragon-generated
-examples/music-player/dragon/north-star-check.json merge=dragon-generated
-packages/wpt/snapshots/** merge=dragon-generated
-packages/tailwind-sweep/snapshot/** merge=dragon-generated
 packages/parity/expected-glyphs/bottom-scanlines.json merge=dragon-generated
+packages/parity/expected-hit/*.hit.json merge=dragon-generated
 packages/parity/expected-media/** merge=dragon-generated
+packages/parity/expected-pixels/** merge=dragon-generated
+packages/parity/expected/darwin-arm64/** merge=dragon-generated
 packages/parity/out/lanes.json merge=dragon-generated
+packages/tailwind-sweep/snapshot/** merge=dragon-generated
+packages/translate/corpus-dpr.json merge=dragon-generated
+packages/translate/corpus.json merge=dragon-generated
+packages/wpt/snapshots/** merge=dragon-generated

AGENTS.md

@@ -23,7 +23,7 @@ Code reaches `master` only through a pull request that Macroscope has reviewed.
 4. **Read the review.** Run `pnpm pr:review <number> --wait`. It waits for CI and then for Macroscope's correctness review of the latest commit, and lists failed checks and every Macroscope finding nobody has answered. Macroscope only posts findings of Medium severity or higher, so every one it lists matters. When Macroscope skips with its monthly spending limit, the owner's standing directive lets the PR land without that review once CI passes and every earlier finding is answered; `pr:review` reports it as UNREVIEWED. The landing driver then requires a Claude correctness review of the PR's own diff (step 7) and stops the PR on any finding of Medium severity or higher.
 5. **Answer every finding.** Fix it, push, and reply `Fixed in <sha>` in its thread; or reply with why the code is intentional. Reply with `gh api repos/compiled-run/dragoncss/pulls/<number>/comments/<id>/replies -f body='...'`. Never reply only to clear the list, and never edit `.macroscope/` to silence a finding. If a fix would break a rule above, find another fix that keeps the rule, or reply with why the finding doesn't apply.
 6. **Repeat until Macroscope is done.** Every push gets a new, paid review, which may find new issues, so batch a whole round's fixes into one push. A round's fix needs a regen only when it changes generator inputs, and never a device run. From the third round on, re-audit every file that has had a finding, end to end, and fix every instance of each class before pushing. Go back to step 4 until a review of the latest commit leaves nothing unanswered. The loop runs unattended, with no round limit and no report to the owner. When a file keeps drawing findings, replace point fixes with a check that covers the whole class, such as a differential test against Chrome, before the next push.
-7. **Land through the driver.** Only the landing driver (`pnpm land <queue-file>`, run by the PM) merges code into `master`, one PR at a time, in queue order; the queue file holds one `<branch>:<pr>:<clean-head>` per line. For each PR it merges the PR into the current `origin/master`, runs `pnpm regen`, runs the device lanes unless the tree's device evidence stamp equals `master`'s (device-evidence.ts, `pnpm evidence:stamp --compare origin/master`), regenerates what the device record feeds, runs `pnpm typecheck` and `pnpm test`, pushes that commit to the PR branch, waits for CI and for `pnpm pr:review` to exit 0, and, while `pr:review` reports UNREVIEWED (Macroscope at its spending limit), requires a Claude correctness review of the PR's own diff (reviewed paths only) and stops on any finding of Medium severity or higher. For that, before the driver lands a queued PR, the PM has a review agent review the PR's diff at the queue line's clean head and write `/tmp/land-reviews/precomputed/<pr>.json` as `{ "pr": <n>, "head": "<clean-head sha>", "findings": [{ "severity", "file", "line", "summary", "failure_scenario" }] }`; the driver's default reviewer (`pnpm land:review-lookup`) fails the PR when that file is missing, malformed, for another PR or for another head. It then merges with `gh pr merge --merge --match-head-commit <sha>`, checks that `master`'s tree equals the commit's (docs/goals/** excepted), moves every open PR based on the merged branch to `master`, and deletes the branch last (GitHub closes a PR whose base branch is deleted). Every `master` merge commit therefore carries device evidence from its own tree. A failed check, a finding or a tree mismatch takes that PR out of the queue and back to its worker (steps 4–6), with the `landing-failed` label and a comment naming the failed step; the queue continues with the next PR. Never retry a failed check until it goes green; fix the cause or report it (the driver retries only transient gh and git network errors). After each merge the driver runs `git pull --ff-only` in the main checkout.
+7. **Land through the driver.** Only the landing driver (`pnpm land <queue-file>`, run by the PM) merges code into `master`, in queue order, in batches of up to `LAND_BATCH` PRs (default 4); the queue file holds one `<branch>:<pr>:<clean-head>` per line. It first checks each PR's CI and its review at its current head (a PR whose review is not clean is ejected before any build). It then builds one position per PR, each on the one before it (the first on the current `origin/master`): it merges the PR, runs `pnpm regen` and `pnpm typecheck`, runs the device lanes unless the position's device evidence stamp equals the previous position's (device-evidence.ts, `pnpm evidence:stamp --compare <previous>`), regenerates what the device record feeds, and checks the regen commit is regen-only and no floor falls. A conflict or a failed step ejects that PR and the chain continues. `pnpm test` runs once, on the top position; when it fails, the driver bisects the prefixes (proving `master` itself before it blames the first PR, and stopping with "master is red" if `master` fails), lands the passing prefix, fails the first failing PR with its own failing run, and requeues the PRs after it. Positions below the top get no full test of their own, so when publishing stops part-way the driver proves the tree `master` now rests on, and stops (label, comment, status) if it fails. An error outside the test while proving (install, checkout) stops the driver rather than blaming a PR. Then, PR by PR and only after the PR before it has merged, it pushes the PR's position to the PR branch, waits for CI and for `pnpm pr:review` to exit 0, and, while `pr:review` reports UNREVIEWED (Macroscope at its spending limit), requires a Claude correctness review of the PR's own diff (reviewed paths only) and stops on any finding of Medium severity or higher. For that, before the driver lands a queued PR, the PM has a review agent review the PR's diff at the queue line's clean head and write `/tmp/land-reviews/precomputed/<pr>.json` as `{ "pr": <n>, "head": "<clean-head sha>", "findings": [{ "severity", "file", "line", "summary", "failure_scenario" }] }`; the driver's default reviewer (`pnpm land:review-lookup`) fails the PR when that file is missing, malformed, for another PR or for another head. It then merges with `gh pr merge --merge --match-head-commit <sha>`, checks that `master`'s tree equals the commit's (docs/goals/** excepted), moves every open PR based on the merged branch to `master`, and deletes the branch last (GitHub closes a PR whose base branch is deleted). Every `master` merge commit therefore carries device evidence from its own tree. A failed check, a finding or a tree mismatch takes that PR out of the queue and back to its worker (steps 4–6), with the `landing-failed` label and a comment naming the failed step; the PRs after it in its batch are rebuilt on the new `master`, and the queue continues. Never retry a failed check until it goes green; fix the cause or report it (the driver retries only transient gh and git network errors). After each merge the driver runs `git pull --ff-only` in the main checkout. To reorder or pause the queue, `touch /tmp/dragon-land.stop` (or `kill -USR1` the pid in `/tmp/dragon-land.lock/pid`): the driver lands what it can of its current batch and exits without starting another. `kill -TERM` on that pid (the supervisor's) interrupts: the running step is killed with the driver's process group, the status says INTERRUPTED and names what merged, and no PR is failed. A merge in progress (from `gh pr merge` to the post-merge checks) finishes first; a second `kill -TERM` kills it at once. If an interrupted run left `master` on a merged position no full test has passed, the next run proves `master` first and logs a red result loudly, then carries on; a passing proof that contains that position clears the record.
 
 **Staying current while agents run.** `master` moves every time a PR merges, so: