GoogleChromeLabs · paulirish · Aug 12, 2026 · Aug 11, 2026 · Aug 11, 2026 · Aug 11, 2026
diff --git a/.agents/skills/champ/SKILL.md b/.agents/skills/champ/SKILL.md
@@ -16,7 +16,7 @@ The subagent persona is a superstar senior SWE. They love concrete specification
 
 ## Subagent Workflow
 1.  **Pick a Task**: Select an uncompleted task from `PLAN.md`. Mark it as in progress `[/]` using the `plan-manager` skill if available.
-2.  **Diagnostic Cluster Triage (for WPT tasks)**: When tackling WPT conformance tasks, run `node scripts/wpt_cluster_failures.ts --spec=<target>` to inspect top failure clusters and prioritize high-frequency patterns.
+2.  **Diagnostic Cluster Triage (for WPT tasks)**: When tackling WPT conformance tasks, run `node scripts/wpt/node/cluster.ts --spec=<target>` to inspect top failure clusters and prioritize high-frequency patterns.
 3.  **Red Phase**: Write a failing test in the appropriate test file (or create a new one in `tests/`) that demonstrates the missing feature or bug.
 4.  **Green Phase**: Implement the code in `src/` to make the test pass, adding explicit spec anchor citations in comments.
 5.  **Verify**: Run the targeted test to ensure it passes.

diff --git a/.agents/skills/coherence-auditor/SKILL.md b/.agents/skills/coherence-auditor/SKILL.md
@@ -43,11 +43,11 @@ Use this skill when you need to audit the consistency, link integrity, codebase
        - **Generated Code Separation**: Verify that all machine-generated spec files reside in `src/data/gen/` (e.g. `src/data/gen/properties.ts`, `src/data/gen/units.ts`, etc.). Flag any generated files placed directly in `src/data/` or other non-gen folders.
        - **Extraction Scripts Directory**: Verify that all external test suite extraction scripts reside in `scripts/external_suites/` and use the `extract_<suite>.ts` naming pattern. Flag any extraction scripts placed directly in `scripts/` or missing the `extract_` verb prefix.
        - **Filename Case Standard**:
-         - Enforce **snake_case** for administrative/utility scripts in `scripts/` (e.g. `prune_resolved_failures.ts`, `generate_all.ts`) and codegen scripts in `scripts/codegen/`.
+         - Enforce **snake_case** for administrative/utility scripts in `scripts/` (e.g. `scripts/baselines/prune_resolved_failures.ts`, `scripts/codegen/generate_all.ts`) and codegen scripts in `scripts/codegen/`.
          - Enforce **kebab-case** for public package files, test runners in `tests/` (e.g., `external-lightning.test.ts`, `wpt-extracted.test.ts`), JSON fixtures in `tests/fixtures/`, and baseline files (which must reside in `tests/fixtures/baselines/`).
          - Flag any deviations or inconsistent mixing of case conventions within the same category.
-       - **Test Failure & Skip Taxonomy**: Audit terms used for skipping/categorizing failures (`exclude` for unexecutable HTML suites, `knownFailures` for baseline failures checked and pruned by `prune_resolved_failures.ts`, and `knownSkips` for mapped skips with explicit spec reason strings).
-       - **Script & Command Alignment**: Ensure script filenames correspond logically to npm script names in `package.json` (e.g. `codegen` $\to$ `scripts/generate_all.ts`, `external:extract` $\to$ `scripts/extract_external_suites.ts`, `baselines:prune` $\to$ `scripts/prune_resolved_failures.ts`).
+       - **Test Failure & Skip Taxonomy**: Audit terms used for skipping/categorizing failures (`exclude` for unexecutable HTML suites, `knownFailures` for baseline failures checked and pruned by `scripts/baselines/prune_resolved_failures.ts`, and `knownSkips` for mapped skips with explicit spec reason strings).
+       - **Script & Command Alignment**: Ensure script filenames correspond logically to npm script names in `package.json` (e.g. `codegen` $\to$ `scripts/codegen/generate_all.ts`, `external:extract` $\to$ `scripts/external_suites/extract_all.ts`, `baselines:prune` $\to$ `scripts/baselines/prune_resolved_failures.ts`).
 
   3. **Index & Link Integrity Verification**:
      - **Automated Link & Spec Path Validation**: Run `node .agents/skills/coherence-auditor/scripts/validate_links.ts` to automatically detect broken relative markdown links, invalid spec submodule paths, and missing script/source file references across all docs.

diff --git a/.gemini/context.md b/.gemini/context.md
diff --git a/.vscode/settings.json b/.vscode/settings.json
diff --git a/AGENTS.md b/AGENTS.md
@@ -46,7 +46,7 @@ We intentionally deviate from some specifications for pragmatism, performance, o
 ### Automation Over Hardcoding
 As CSS specifications evolve, this codebase must evolve with them. We prioritize automation over manual maintenance for spec-derived data.
 - **Rule**: Whenever adding support for new properties, values, units, or features that are documented in external data sources (like `mdn-data` or `@webref/css`), ALWAYS prefer updating or creating a code generation script in `scripts/codegen/` rather than hardcoding lists in implementation files.
-- **Rule**: Ensure that any new generation script is added to the master script `scripts/generate_all.ts` and that the `pnpm run codegen` command functions correctly.
+- **Rule**: Ensure that any new generation script is added to the master script `scripts/codegen/generate_all.ts` and that the `pnpm run codegen` command functions correctly.
 - **Rule**: The `maintain` script in `package.json` must always include `pnpm run codegen` to ensure that updating submodules automatically updates our generated data.
 
 ## Instructions for Agents

diff --git a/LOOP.md b/LOOP.md
@@ -27,7 +27,7 @@ graph TD
     *   *Role*: Implements features, writes tests, runs `pnpm run preflight`, and commits changes to git following the [champ skill](file:///usr/local/google/home/paulirish/code/cssom/.agents/skills/champ/SKILL.md).
     *   *Standards*:
         *   **Spec Anchor Citations**: Must cite exact normative specification anchors in code comments (e.g. `// cssom-1 § 6.5.3 #insert-a-css-rule`) mapping implementation to standard algorithms.
-        *   **Mandatory Pre/Post Cluster Triage & Delta Reconciliation**: When working on WPT conformance waves, start with `node scripts/wpt_cluster_failures.ts --spec=<target>` to record the baseline failure cluster. After implementation, run `wpt_cluster_failures` again. If the test increase is noticeably smaller than the targeted cluster, the developer **MUST diagnose the top remaining failure cluster** and fix any near-miss harness/serialization gaps (e.g. computed color formatting) before declaring the phase complete.
+        *   **Mandatory Pre/Post Cluster Triage & Delta Reconciliation**: When working on WPT conformance waves, start with `node scripts/wpt/node/cluster.ts --spec=<target>` to record the baseline failure cluster. After implementation, run `cluster.ts` again. If the test increase is noticeably smaller than the targeted cluster, the developer **MUST diagnose the top remaining failure cluster** and fix any near-miss harness/serialization gaps (e.g. computed color formatting) before declaring the phase complete.
         *   *Constraint*: Naturally optimistic. Wants compilation and test runs to pass as quickly as possible.
 3.  **The Reviewer (`codex_reviewer_cmd`)**:
     *   *Role*: Senior engineer persona. Has command execution permissions and runs `git show HEAD` to audit styling, typing, spec citations, and safety.

diff --git a/MAINTENANCE.md b/MAINTENANCE.md
@@ -36,7 +36,7 @@ This runs `git submodule update --init --remote && pnpm run submodules:update` t
 ```bash
 pnpm run fixtures:generate
 ```
-This runs `node scripts/extract_external_suites.ts`.
+This runs `node scripts/external_suites/extract_all.ts`.
 
 **3. Run Tests:**
 ```bash