decision(NAME): name the SVG import IR crate and choose its math vocabulary

[softmarshmallow]

Tracks registry decision NAME under #43. Filing this issue records the question; it does not answer it. Explicit owner GO is required.

Decision question

At the Phase 3 cut:

1. what end-state name does the model-agnostic SVG import IR crate publish under;
2. does its geometry vocabulary use math2 or kurbo/the chassis math vocabulary; and
3. does the owner confirm the topology's two distinct SVG surfaces: import-to-document and render-to-pixels?

Decision time

At Phase 3 entry, after the Phase 1 crate cut and Phase 2 exit. The name was deferred once and is decided at this cut, not earlier or again later.

Evidence bar

A naming exercise covering scope refusal, consumers, dependency closure, public-name fanout, deletion/rename cost, and the math choice's conversion boundaries. It must use the established IR seam and both real surface consumers as evidence.

Guardrails

• Do not perform the extraction or grant SVG import to the chassis here.
• Do not merge import-to-document with render-to-pixels merely because both consume SVG.
• The IR remains model-agnostic; the adapter depends on IR + n0-model, while n0-model depends on neither.
• No plan-sequence name, silent shim, format/grida.fbs change, or wasm freeze-contract change.

Context

• The consolidation program — one engine by extraction #43 — program position and Phase 3 gates
• seam: SVG sink inversion — the IR is the product, pack.rs is the v1 adapter #29 — established model-agnostic IR seam
• anchor — the v2 node model #9 — chassis and authored-model context
• Grida SVG renderer: own the svg-in/png-out path — a resvg replacement shipped as CLI + npm #13 — distinct render-to-pixels product surface
• end-state topology

Done

Owner GO records the exact crate name, math vocabulary, and two-surface disposition; the charter is updated; the Phase 3 crate cut can proceed without reopening naming.