Merge pull request #61 from gridaco/chore/consolidation-web-first

feat(consolidation): the n0 path becomes the SVG engine of record

Author: softmarshmallow

.agents/skills/dev-render-htmlcss-feature/SKILL.md

@@ -15,7 +15,7 @@ over `/research`, `/fixtures`, and `/render-reftest` — those auto-trigger
 on their own for narrower work.
 
 **Sibling skill.** For features in the SVG path
-(`crates/grida/src/htmlcss/svg/`, `resvg-test-suite` corpus,
+(`crates/htmlcss/src/svg/`, `resvg-test-suite` corpus,
 multi-oracle scoring against expected.png + baked Chrome PNG), use
 [`dev-render-htmlcss-svg-feature`](../dev-render-htmlcss-svg-feature/SKILL.md)
 instead. Same five-phase shape, different tooling.
@@ -50,7 +50,7 @@ coincidentally-correctly but by the wrong path?
 
 **Actions.**
 
-- Scan `crates/grida/src/htmlcss/` for the property name in
+- Scan `crates/htmlcss/src/` for the property name in
   stylo enum mapping, paint emit, layout feed. A property can be
   parsed-but-dropped, emitted-but-wrong, or unhandled — each has a
   different fix shape.
@@ -147,7 +147,7 @@ the suite config is wrong and the score will be zero.
 ### 4. Implement — "what code change realizes the behavior?"
 
 **Question.** What is the minimum set of edits in
-`crates/grida/src/htmlcss/` to make the fixture match?
+`crates/htmlcss/src/` to make the fixture match?
 
 **Actions.**
 
@@ -232,7 +232,7 @@ pick up, and no context is lost. The durable artifacts:
 | Audit     | Current-state note, priority bucket                      | PR description / task prompt                           |
 | Ground    | Research note (spec + engine cross-ref)                  | PR description or `docs/wg/feat-2d/`                   |
 | Fixture   | `.html` fixture(s), suite entries, viewport measurement  | `fixtures/test-html/L0/`, `fixtures/test-html/suites/` |
-| Implement | Code change, data tests, behavior summary                | `crates/grida/src/htmlcss/`                            |
+| Implement | Code change, data tests, behavior summary                | `crates/htmlcss/src/`                                  |
 | Verify    | Before/after scores, diff PNG review, divergence surface | PR description                                         |
 
 If a phase's artifact is missing, the phase isn't done — even if

.agents/skills/dev-render-htmlcss-svg-feature/SKILL.md

@@ -11,8 +11,15 @@ description: >
 
 # grida-htmlcss::svg — feature loop
 
+> **Status (2026-07-24): the target module is a frozen donor.** Per
+> [D-N, the SVG engine of record](../../../docs/wg/consolidation/svg-engine-of-record.md),
+> no new behavior lands in `htmlcss::svg`; SVG capability evolves as rungs
+> on the engine of record (`websem → rframe → n0`), Chromium-baked under
+> `fixtures/web-first/`. Use this loop only for owner-directed wire-back or
+> donor study — not for new feature work.
+
 **What this is.** A heavy, manually-invoked loop for driving a single
-SVG feature forward in `crates/grida/src/htmlcss/svg/`. Do not
+SVG feature forward in `crates/htmlcss/src/svg/`. Do not
 auto-trigger; load only when the user explicitly runs it.
 
 **Sister skill.** [`dev-render-htmlcss-feature`](../dev-render-htmlcss-feature/SKILL.md)
@@ -22,7 +29,7 @@ shape, but different corpus and different scoring policy.
 
 | Aspect          | HTML/CSS sister skill                        | This (SVG) skill                                                    |
 | --------------- | -------------------------------------------- | ------------------------------------------------------------------- |
-| Renderer module | `crates/grida/src/htmlcss/` (excl. `svg/`)   | `crates/grida/src/htmlcss/svg/`                                     |
+| Renderer module | `crates/htmlcss/src/` (excl. `svg/`)         | `crates/htmlcss/src/svg/`                                           |
 | Corpus          | `fixtures/test-html/L0/` (we author)         | `fixtures/local/resvg-test-suite/` (vendored, 1679 fixtures)        |
 | Oracle          | Playwright Chromium (refbrowser, on-the-fly) | `expected.png` (suite author) **+** baked Chrome PNG                |
 | Scoring         | Single oracle, gate=`L0.exact` floor 1.0     | Multi-oracle: consensus / disputed / UB; gate = consensus pass-rate |
@@ -73,7 +80,7 @@ oracle buckets?
 
 **Actions.**
 
-- Scan `crates/grida/src/htmlcss/svg/` for the property/element name
+- Scan `crates/htmlcss/src/svg/` for the property/element name
   in dom/parse, style/cascade, layout, paint. SVG features can be
   parsed-but-dropped, computed-but-misrouted, or just unhandled —
   each has a different fix shape.
@@ -97,7 +104,7 @@ oracle buckets?
     --renderer htmlcss --threshold 0.1 \
     --filter 'filters_feSpecularLighting'
   ```
-- Cross-reference [`crates/grida/src/htmlcss/svg/README.md`](../../../crates/grida/src/htmlcss/svg/README.md)
+- Cross-reference [`crates/htmlcss/src/svg/README.md`](../../../crates/htmlcss/src/svg/README.md)
   for the Blink module map and any prior decision.
 
 **Deliverable.** A short audit note (PR draft / task prompt):
@@ -189,7 +196,7 @@ known starting score against the chosen oracle.
 ### 4. Implement — "what code change realizes the behavior?"
 
 **Question.** What is the minimum diff in
-`crates/grida/src/htmlcss/svg/` to make the targets pass?
+`crates/htmlcss/src/svg/` to make the targets pass?
 
 **Actions.**
 
@@ -285,7 +292,7 @@ moved against, and whether anything regressed.
 | Audit     | Current-state note, oracle-partitioned fixture list       | PR description / task prompt                                    |
 | Ground    | Research note (spec + Blink/resvg cross-ref)              | PR description or `docs/wg/feat-2d/`                            |
 | Fixture   | Target fixture list with oracle status; baked chrome.png  | `fixtures/local/resvg-test-suite/chrome-baseline/` (gitignored) |
-| Implement | Code change, data tests, spec-language behavior summary   | `crates/grida/src/htmlcss/svg/`                                 |
+| Implement | Code change, data tests, spec-language behavior summary   | `crates/htmlcss/src/svg/`                                       |
 | Verify    | Before/after summary, per-fixture scores, diff PNG review | PR description                                                  |
 
 ---
@@ -466,7 +473,7 @@ Produce, in order:
    different — explain which oracle the implementation targets).
 3. Fixture list: 1-3 target fixtures with rel paths, oracle status,
    baked chrome.png present (yes/no).
-4. Implementation: minimal diff in crates/grida/src/htmlcss/svg/.
+4. Implementation: minimal diff in crates/htmlcss/src/svg/.
    Data tests where assertable.
 5. Verify report:
    - before/after consensus pass-rate (from `reftest summary`)
@@ -500,5 +507,5 @@ Use /research for phase 2.
 | `reftest view <result-dir>`                              | Serve the dashboard.                                                                                                          |
 
 See [`crates/grida_dev/AGENTS.md`](../../../crates/grida_dev/AGENTS.md) and
-[`crates/grida/src/htmlcss/svg/README.md`](../../../crates/grida/src/htmlcss/svg/README.md)
+[`crates/htmlcss/src/svg/README.md`](../../../crates/htmlcss/src/svg/README.md)
 for the underlying contracts.

.agents/skills/render-reftest/SKILL.md

@@ -339,12 +339,12 @@ Everything is driven by **suite JSON files** at
 `fixtures/test-html/suites/`. A suite enumerates fixtures, their
 per-fixture render config, and the gate policy.
 
-| Suite              | What it contains                                                                              | Gate                       |
-| ------------------ | --------------------------------------------------------------------------------------------- | -------------------------- |
-| `L0.exact.json`    | Fixtures currently at 100.00% byte-exact parity with Chromium. Any drop is a real regression. | `floor: 1.0`, strict diff. |
-| `L0.coverage.json` | All aspirational L0 fixtures — the full backlog. Scores land wherever they land.              | Informational only.        |
+| Suite              | What it contains                                                                                                       | Gate                                           |
+| ------------------ | ---------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------- |
+| `L0.exact.json`    | Fixtures currently at 1.0 configured Chromium similarity. Any scored-pixel drop is a real regression.                 | `floor: 1.0`, threshold 0, AA exclusion active |
+| `L0.coverage.json` | All aspirational L0 fixtures — the full backlog. Scores land wherever they land.                                       | Informational only                             |
 
-**Promoting a fixture to `exact`** — once a fixture reaches 100.00%
+**Promoting a fixture to `exact`** — once a fixture reaches 1.0
 against the current suite config, move its entry from `coverage` →
 `exact`. Do **not** lower the exact suite's floor to fit new entries;
 the bar exists so regressions are loud.
@@ -357,7 +357,7 @@ per-fixture `.reftest.json` sidecars.
 ```json
 {
   "name": "L0.exact",
-  "description": "Byte-exact fixtures; any drop = regression.",
+  "description": "Configured-exact fixtures; any scored-pixel drop = regression.",
   "gate": { "threshold": 0, "aa": true, "floor": 1.0 },
   "defaults": {
     "wait_for": ["fonts", "networkidle"],
@@ -374,7 +374,7 @@ per-fixture `.reftest.json` sidecars.
 - `defaults` — applied to every fixture. Each fixture entry can override any field.
 - `fixtures[].path` and every `extra_css[]` path resolve **relative to the suite file**.
 - `gate.threshold` / `gate.aa` are inputs to the pixelmatch diff; `gate.floor` is the aggregate pass bar on similarity.
-- **`aa: true` (default)** → pixelmatch `includeAA: false`. Pixelmatch's AA detector fires and excludes anti-aliased edge pixels from the diff count, separating rasterizer edge noise (Skia vs. Blink) from real divergence. Set `aa: false` for strict byte-exact accounting (e.g. probing an AA-class regression).
+- **`aa: true` (default)** → pixelmatch `includeAA: false`. Pixelmatch's AA detector fires and excludes anti-aliased edge pixels from the diff count, separating rasterizer edge noise (Skia vs. Blink) from real divergence. Set `aa: false` for strict AA-inclusive accounting inside the scoring mask (e.g. probing an AA-class regression).
 
 #### The three-step pipeline
 
@@ -419,9 +419,9 @@ Default refbrowser diff: **`--threshold 0`** (pixelmatch's tightest
 color-delta) with **AA-ignore mode on by default** (`aa: true` →
 `includeAA: false`; pixelmatch's Vysniauskas AA detector fires and
 excludes edge AA pixels from the diff count). Pass `--no-aa` to flip
-to strict byte-exact accounting. Pass each fixture's similarity
-against the suite's `gate.floor` — for `L0.exact`, that's `1.0`
-(100.00% similarity with AA detection active).
+to strict AA-inclusive accounting inside the scoring mask. Pass each
+fixture's similarity against the suite's `gate.floor` — for
+`L0.exact`, that's `1.0` (100.00% similarity with AA detection active).
 
 ```sh
 pnpm -C packages/grida-reftest exec reftest \
@@ -545,10 +545,12 @@ diff image, not the numeric score.
 5. Run the refbrowser producer + diff against the same suite. Review
    the diff PNG — if the diff is dominated by a known divergence zone
    (see below), record it in the PR description, don't suppress it.
-6. If the fixture reaches 100.00% byte-exact, move its entry from
-   `L0.coverage.json` to `L0.exact.json`.
+6. If the fixture reaches 1.0 under the exact suite's configured
+   threshold, AA-exclusion, and content-mask policy, move its entry
+   from `L0.coverage.json` to `L0.exact.json`.
 
-**Known divergence surfaces** — areas where grida is not yet Blink-exact.
+**Known divergence surfaces** — areas where grida does not yet meet the
+configured Blink bar.
 These are **backlog items, not tolerance excuses**. Do not tune
 thresholds to suppress them. Document the specific divergence in the
 PR description; let the score carry the truth.

.github/workflows/consolidation-gates.yml

@@ -73,6 +73,9 @@ jobs:
           fetch-depth: 0
           ref: ${{ needs.scope.outputs.head }}
 
+      - name: Check the gate still refuses what it must
+        run: python3 bin/test-check-cargo-lock-additions-only
+
       - name: Gate workspace crate cuts
         run: >-
           python3 bin/check-cargo-lock-additions-only
@@ -134,16 +137,19 @@ jobs:
           cache-workspace-crates: true
           cache-on-failure: true
 
-      - name: Run the five legacy seam locks
+      - name: Run the legacy and extracted Web seam locks
         env:
           FORCE_SKIA_BINARIES_DOWNLOAD: "1"
         run: |
           cargo test --locked -p grida \
             --test cg_architecture \
             --test svg_import_architecture \
             --test html_import_architecture \
-            --test htmlcss_svg_architecture \
             --test painter_architecture
+          cargo test --locked -p htmlcss \
+            --test architecture \
+            --test svg_architecture
+          cargo test --locked -p n0_cli --test architecture
 
   legacy_pixel_sweep:
     name: legacy pixel sweep

.gitignore

@@ -126,3 +126,4 @@ docs/_build/
 *.plan.md
 *.todo.md
 .claude/launch.json
+.DS_Store

AGENTS.md

@@ -25,11 +25,14 @@ brew install ninja            # macOS
 
 ```sh
 # check (each crate must pass independently)
-cargo check -p grida -p grida-canvas-wasm -p grida_dev -p n0 -p n0-model
+cargo check -p htmlcss -p grida -p grida-canvas-wasm -p grida_dev -p n0 -p n0-model \
+  -p websem -p rframe -p animation-sampling -p n0_cli
 
 # tests
 cargo test -p grida     # legacy engine tests
+cargo test -p htmlcss   # extracted Web renderer tests
 cargo test -p n0-model -p n0   # v2 engine tests (model is skia-free, fast)
+cargo test -p n0_cli    # thin product command host + HTML/SVG render probes
 cargo test              # all
 
 # lint / format (enforced)
@@ -48,14 +51,19 @@ python3 bin/activate-flatc -- --rust -o crates/grida/src/io/generated format/gri
 
 | directory                   | notes                                                                                      |
 | --------------------------- | ------------------------------------------------------------------------------------------ |
-| `crates/grida`              | the engine core (rendering, node model, io, text, svg/html import)                         |
+| `crates/grida`              | legacy engine compatibility consumer (node model, io, text, import/export, editor-era runtime) |
 | `crates/cg`                 | the backend-neutral canvas-graphics vocabulary                                             |
+| `crates/htmlcss`            | extracted mature static HTML/CSS/SVG renderer; transitional direct-Skia Web implementation |
 | `crates/grida_editor`       | editor core — document working copy, invertible mutations, history, commands               |
 | `crates/grida-canvas-wasm`  | WASM bindings + the `@grida/canvas-wasm` npm package (see its `PUBLISHING.md`)             |
 | `crates/math2` · `csscascade` · `fonts` | foundations                                                                    |
 | `crates/grida_dev`          | dev CLI, benchmarks, reftest tooling                                                       |
 | `crates/grida_wpt`          | web-platform-tests harness                                                                 |
 | `crates/n0` · `n0-model` · `n0_dev` | the v2 engine family (the `anchor` model): skia-free model crate, resolve→drawlist→paint engine, winit/egui dev shell — promoted from the `model-v2-anchor` branch (gridaco/nothing#9) |
+| `crates/websem`             | the Web semantic compiler: an SVG or HTML source → one namespace-aware document → one Stylo cascade → `rframe::Frame`. Owns no parser and no painter; decides what the engine will and will not render |
+| `crates/rframe`             | the resolved render contract (`Frame`): the visual facts a producer states after resolving its source. Contract-only and backend-free — no document, no cascade, no paint call |
+| `crates/animation-sampling` | the time axis: Base or one exact signed-nanosecond Sample, with no ambient clock                        |
+| `crates/n0_cli`             | thin `n0` file-render command on the SVG engine of record (`websem → rframe → n0`): Base and exact-time SVG/HTML renders at WxH-as-initial-viewport — best-effort by default (constructs outside the admitted slice declared on stderr), `--strict` refuses loudly. Its README is the statement of record for that slice |
 | `archive/model-v2/`                 | the frozen v2 workbench archive (phase papers, experiment verdicts, demo pages); paths inside the frozen papers refer to the pre-promotion layout — see its README's map |
 | `format/`                   | the FlatBuffers schema (`grida.fbs`) — **source of truth**; see `format/AGENTS.md`         |
 | `docs/wg/`                  | the engine's normative working-group specs (canvas, format, research, feat-*) — same-repo  |