@hatiolab/figure-model 0.1.95 → 0.2.1

package/dist/words.d.ts.map

@@ -1 +1 @@
-{"version":3,"file":"words.d.ts","sourceRoot":"","sources":["../src/words.ts"],"names":[],"mappings":"AAUA,eAAO,MAAM,IAAI,0BAA2B,CAAA;AAC5C,MAAM,MAAM,IAAI,GAAG,CAAC,OAAO,IAAI,CAAC,CAAC,MAAM,CAAC,CAAA;AAExC,MAAM,WAAW,IAAI;IACnB,CAAC,EAAE,MAAM,CAAA;IACT,CAAC,EAAE,MAAM,CAAA;IACT,CAAC,EAAE,MAAM,CAAA;CACV;AAED;;;;;;;;;;GAUG;AACH,eAAO,MAAM,mBAAmB,+DAAgE,CAAA;AAChG,MAAM,MAAM,gBAAgB,GAAG,CAAC,OAAO,mBAAmB,CAAC,CAAC,MAAM,CAAC,CAAA;AAEnE;;;GAGG;AACH,eAAO,MAAM,gBAAgB,EAAE,QAAQ,CAAC,MAAM,CAAC,MAAM,EAAE,SAAS,gBAAgB,EAAE,CAAC,CAEjF,CAAA;AAEF,gFAAgF;AAChF,eAAO,MAAM,gBAAgB,gFAAiF,CAAA;AAC9G,MAAM,MAAM,cAAc,GAAG,CAAC,OAAO,gBAAgB,CAAC,CAAC,MAAM,CAAC,CAAA;AAE9D;;;GAGG;AACH,eAAO,MAAM,YAAY,MAAM,CAAA;AAE/B;;;;;;;;GAQG;AACH,eAAO,MAAM,aAAa,0BAA2B,CAAA;AACrD,MAAM,MAAM,WAAW,GAAG,CAAC,OAAO,aAAa,CAAC,CAAC,MAAM,CAAC,CAAA;AAExD,2CAA2C;AAC3C,eAAO,MAAM,UAAU,EAAE,MAAM,CAAC,WAAW,EAAE,MAAM,CAAyB,CAAA;AAE5E;;;GAGG;AACH,eAAO,MAAM,IAAI,MAAM,CAAA;AAEvB,MAAM,MAAM,WAAW,GAAG,GAAG,GAAG,GAAG,GAAG,GAAG,GAAG,GAAG,CAAA;AAE/C;;;GAGG;AACH,eAAO,MAAM,MAAM;IACjB,2GAA2G;;IAE3G,qEAAqE;;IAErE,0EAA0E;;IAE1E;;;;OAIG;;IAEH;;;OAGG;;IAEH;;;;OAIG;;IAEH,mDAAmD;;IAEnD,mGAAmG;;IAEnG,iDAAiD;;CAEzC,CAAA;AAEV;;;;GAIG;AACH,eAAO,MAAM,eAAe,EAAE,SAAS,MAAM,EAA4B,CAAA;AAEzE,iEAAiE;AACjE,eAAO,MAAM,kBAAkB,EAAE,QAAQ,CAAC,MAAM,CAAC,IAAI,EAAE,MAAM,CAAC,CAA4D,CAAA;AAE1H;;;;GAIG;AACH,eAAO,MAAM,YAAY,QAAkC,CAAA;AAC3D,eAAO,MAAM,WAAW;;;CAA+B,CAAA;AAEvD;;;;GAIG;AACH,wBAAgB,eAAe,CAAC,GAAG,GAAE,MAAmB,GAAG,MAAM,CAEhE;AAID,iFAAiF;AACjF,wBAAgB,iBAAiB,CAAC,IAAI,EAAE,MAAM,GAAG,OAAO,CAEvD"}
+{"version":3,"file":"words.d.ts","sourceRoot":"","sources":["../src/words.ts"],"names":[],"mappings":"AAUA,eAAO,MAAM,IAAI,0BAA2B,CAAA;AAC5C,MAAM,MAAM,IAAI,GAAG,CAAC,OAAO,IAAI,CAAC,CAAC,MAAM,CAAC,CAAA;AAExC,MAAM,WAAW,IAAI;IACnB,CAAC,EAAE,MAAM,CAAA;IACT,CAAC,EAAE,MAAM,CAAA;IACT,CAAC,EAAE,MAAM,CAAA;CACV;AAED;;;;;;;;;;GAUG;AACH,eAAO,MAAM,mBAAmB,+DAAgE,CAAA;AAChG,MAAM,MAAM,gBAAgB,GAAG,CAAC,OAAO,mBAAmB,CAAC,CAAC,MAAM,CAAC,CAAA;AAEnE;;;GAGG;AACH,eAAO,MAAM,gBAAgB,EAAE,QAAQ,CAAC,MAAM,CAAC,MAAM,EAAE,SAAS,gBAAgB,EAAE,CAAC,CAEjF,CAAA;AAEF,gFAAgF;AAChF,eAAO,MAAM,gBAAgB,gFAAiF,CAAA;AAC9G,MAAM,MAAM,cAAc,GAAG,CAAC,OAAO,gBAAgB,CAAC,CAAC,MAAM,CAAC,CAAA;AAE9D;;;GAGG;AACH,eAAO,MAAM,YAAY,MAAM,CAAA;AAE/B;;;;;;;;GAQG;AACH,eAAO,MAAM,aAAa,0BAA2B,CAAA;AACrD,MAAM,MAAM,WAAW,GAAG,CAAC,OAAO,aAAa,CAAC,CAAC,MAAM,CAAC,CAAA;AAExD,2CAA2C;AAC3C,eAAO,MAAM,UAAU,EAAE,MAAM,CAAC,WAAW,EAAE,MAAM,CAAyB,CAAA;AAE5E;;;GAGG;AACH,eAAO,MAAM,IAAI,MAAM,CAAA;AAEvB,MAAM,MAAM,WAAW,GAAG,GAAG,GAAG,GAAG,GAAG,GAAG,GAAG,GAAG,CAAA;AAE/C;;;GAGG;AACH,eAAO,MAAM,MAAM;IACjB,2GAA2G;;IAE3G,qEAAqE;;IAErE,0EAA0E;;IAE1E;;;;OAIG;;IAEH;;;OAGG;;IAEH;;;;OAIG;;IAEH,mDAAmD;;IAEnD,mGAAmG;;IAEnG,iDAAiD;;CAEzC,CAAA;AAEV;;;;GAIG;AACH,eAAO,MAAM,eAAe,EAAE,SAAS,MAAM,EAA4B,CAAA;AAEzE,iEAAiE;AACjE,eAAO,MAAM,kBAAkB,EAAE,QAAQ,CAAC,MAAM,CAAC,IAAI,EAAE,MAAM,CAAC,CAA4D,CAAA;AAE1H;;;;GAIG;AACH,eAAO,MAAM,YAAY,QAAkC,CAAA;AAC3D,eAAO,MAAM,WAAW;;;CAA+B,CAAA;AAEvD;;;;GAIG;AACH,wBAAgB,eAAe,CAAC,GAAG,GAAE,MAAmB,GAAG,MAAM,CAEhE;AAID,iFAAiF;AACjF,wBAAgB,iBAAiB,CAAC,IAAI,EAAE,MAAM,GAAG,OAAO,CAEvD;AAED;;;;;GAKG;AACH,eAAO,MAAM,0BAA0B,OAAO,CAAA"}

package/dist/words.js

@@ -113,4 +113,11 @@ const PLACEHOLDER_TYPE = /^FIGURE_[0-9A-Z]{8}$/;
 export function isPlaceholderType(type) {
     return PLACEHOLDER_TYPE.test(type);
 }
+/**
+ * The most nodes one figure's graph may have: a fence against a malformed document, set large (designer's ruling,
+ * docs/shape-contract.md Q10, 2026-09-29). The 1 MiB document limit binds first -- stored nodes run 125 to 190 bytes, so a
+ * mebibyte holds some 5,500 to 8,400 -- and the largest stored figure has 517. A graph this size compiles in about 25 ms and
+ * evaluates in about 2 ms.
+ */
+export const FIGURE_DOCUMENT_NODE_LIMIT = 8192;
 //# sourceMappingURL=words.js.map

package/dist/words.js.map

@@ -1 +1 @@
-{"version":3,"file":"words.js","sourceRoot":"","sources":["../src/words.ts"],"names":[],"mappings":"AAAA;;GAEG;AAEH;;;;GAIG;AAEH,MAAM,CAAC,MAAM,IAAI,GAAG,CAAC,GAAG,EAAE,GAAG,EAAE,GAAG,CAAU,CAAA;AAS5C;;;;;;;;;;GAUG;AACH,MAAM,CAAC,MAAM,mBAAmB,GAAG,CAAC,UAAU,EAAE,UAAU,EAAE,cAAc,EAAE,UAAU,CAAU,CAAA;AAGhG;;;GAGG;AACH,MAAM,CAAC,MAAM,gBAAgB,GAA0D,MAAM,CAAC,MAAM,CAAC;IACnG,YAAY,EAAE,CAAC,UAAU,EAAE,UAAU,CAAC;CACvC,CAAC,CAAA;AAEF,gFAAgF;AAChF,MAAM,CAAC,MAAM,gBAAgB,GAAG,CAAC,SAAS,EAAE,OAAO,EAAE,OAAO,EAAE,SAAS,EAAE,MAAM,EAAE,SAAS,EAAE,QAAQ,CAAU,CAAA;AAG9G;;;GAGG;AACH,MAAM,CAAC,MAAM,YAAY,GAAG,GAAG,CAAA;AAE/B;;;;;;;;GAQG;AACH,MAAM,CAAC,MAAM,aAAa,GAAG,CAAC,GAAG,EAAE,GAAG,EAAE,GAAG,CAAU,CAAA;AAGrD,2CAA2C;AAC3C,MAAM,CAAC,MAAM,UAAU,GAAgC,EAAE,CAAC,EAAE,CAAC,EAAE,CAAC,EAAE,CAAC,EAAE,CAAC,EAAE,EAAE,EAAE,CAAA;AAE5E;;;GAGG;AACH,MAAM,CAAC,MAAM,IAAI,GAAG,GAAG,CAAA;AAIvB;;;GAGG;AACH,MAAM,CAAC,MAAM,MAAM,GAAG;IACpB,2GAA2G;IAC3G,iBAAiB,EAAE,CAAC;IACpB,qEAAqE;IACrE,cAAc,EAAE,IAAI;IACpB,0EAA0E;IAC1E,iBAAiB,EAAE,OAAO;IAC1B;;;;OAIG;IACH,eAAe,EAAE,GAAG;IACpB;;;OAGG;IACH,gBAAgB,EAAE,EAAE;IACpB;;;;OAIG;IACH,oBAAoB,EAAE,MAAM;IAC5B,mDAAmD;IACnD,oBAAoB,EAAE,CAAC;IACvB,mGAAmG;IACnG,eAAe,EAAE,CAAC;IAClB,iDAAiD;IACjD,WAAW,EAAE,CAAC;CACN,CAAA;AAEV;;;;GAIG;AACH,MAAM,CAAC,MAAM,eAAe,GAAsB,CAAC,CAAC,EAAE,EAAE,EAAE,EAAE,EAAE,EAAE,EAAE,EAAE,EAAE,EAAE,CAAC,CAAA;AAEzE,iEAAiE;AACjE,MAAM,CAAC,MAAM,kBAAkB,GAAmC,MAAM,CAAC,MAAM,CAAC,EAAE,CAAC,EAAE,QAAQ,EAAE,CAAC,EAAE,QAAQ,EAAE,CAAC,EAAE,QAAQ,EAAE,CAAC,CAAA;AAE1H;;;;GAIG;AACH,MAAM,CAAC,MAAM,YAAY,GAAG,+BAA+B,CAAA;AAC3D,MAAM,CAAC,MAAM,WAAW,GAAG,EAAE,GAAG,EAAE,CAAC,EAAE,GAAG,EAAE,EAAE,EAAW,CAAA;AAEvD;;;;GAIG;AACH,MAAM,UAAU,eAAe,CAAC,MAAc,IAAI,CAAC,GAAG,EAAE;IACtD,OAAO,UAAU,GAAG,CAAC,QAAQ,CAAC,EAAE,CAAC,CAAC,WAAW,EAAE,EAAE,CAAA;AACnD,CAAC;AAED,MAAM,gBAAgB,GAAG,sBAAsB,CAAA;AAE/C,iFAAiF;AACjF,MAAM,UAAU,iBAAiB,CAAC,IAAY;IAC5C,OAAO,gBAAgB,CAAC,IAAI,CAAC,IAAI,CAAC,CAAA;AACpC,CAAC"}
+{"version":3,"file":"words.js","sourceRoot":"","sources":["../src/words.ts"],"names":[],"mappings":"AAAA;;GAEG;AAEH;;;;GAIG;AAEH,MAAM,CAAC,MAAM,IAAI,GAAG,CAAC,GAAG,EAAE,GAAG,EAAE,GAAG,CAAU,CAAA;AAS5C;;;;;;;;;;GAUG;AACH,MAAM,CAAC,MAAM,mBAAmB,GAAG,CAAC,UAAU,EAAE,UAAU,EAAE,cAAc,EAAE,UAAU,CAAU,CAAA;AAGhG;;;GAGG;AACH,MAAM,CAAC,MAAM,gBAAgB,GAA0D,MAAM,CAAC,MAAM,CAAC;IACnG,YAAY,EAAE,CAAC,UAAU,EAAE,UAAU,CAAC;CACvC,CAAC,CAAA;AAEF,gFAAgF;AAChF,MAAM,CAAC,MAAM,gBAAgB,GAAG,CAAC,SAAS,EAAE,OAAO,EAAE,OAAO,EAAE,SAAS,EAAE,MAAM,EAAE,SAAS,EAAE,QAAQ,CAAU,CAAA;AAG9G;;;GAGG;AACH,MAAM,CAAC,MAAM,YAAY,GAAG,GAAG,CAAA;AAE/B;;;;;;;;GAQG;AACH,MAAM,CAAC,MAAM,aAAa,GAAG,CAAC,GAAG,EAAE,GAAG,EAAE,GAAG,CAAU,CAAA;AAGrD,2CAA2C;AAC3C,MAAM,CAAC,MAAM,UAAU,GAAgC,EAAE,CAAC,EAAE,CAAC,EAAE,CAAC,EAAE,CAAC,EAAE,CAAC,EAAE,EAAE,EAAE,CAAA;AAE5E;;;GAGG;AACH,MAAM,CAAC,MAAM,IAAI,GAAG,GAAG,CAAA;AAIvB;;;GAGG;AACH,MAAM,CAAC,MAAM,MAAM,GAAG;IACpB,2GAA2G;IAC3G,iBAAiB,EAAE,CAAC;IACpB,qEAAqE;IACrE,cAAc,EAAE,IAAI;IACpB,0EAA0E;IAC1E,iBAAiB,EAAE,OAAO;IAC1B;;;;OAIG;IACH,eAAe,EAAE,GAAG;IACpB;;;OAGG;IACH,gBAAgB,EAAE,EAAE;IACpB;;;;OAIG;IACH,oBAAoB,EAAE,MAAM;IAC5B,mDAAmD;IACnD,oBAAoB,EAAE,CAAC;IACvB,mGAAmG;IACnG,eAAe,EAAE,CAAC;IAClB,iDAAiD;IACjD,WAAW,EAAE,CAAC;CACN,CAAA;AAEV;;;;GAIG;AACH,MAAM,CAAC,MAAM,eAAe,GAAsB,CAAC,CAAC,EAAE,EAAE,EAAE,EAAE,EAAE,EAAE,EAAE,EAAE,EAAE,EAAE,CAAC,CAAA;AAEzE,iEAAiE;AACjE,MAAM,CAAC,MAAM,kBAAkB,GAAmC,MAAM,CAAC,MAAM,CAAC,EAAE,CAAC,EAAE,QAAQ,EAAE,CAAC,EAAE,QAAQ,EAAE,CAAC,EAAE,QAAQ,EAAE,CAAC,CAAA;AAE1H;;;;GAIG;AACH,MAAM,CAAC,MAAM,YAAY,GAAG,+BAA+B,CAAA;AAC3D,MAAM,CAAC,MAAM,WAAW,GAAG,EAAE,GAAG,EAAE,CAAC,EAAE,GAAG,EAAE,EAAE,EAAW,CAAA;AAEvD;;;;GAIG;AACH,MAAM,UAAU,eAAe,CAAC,MAAc,IAAI,CAAC,GAAG,EAAE;IACtD,OAAO,UAAU,GAAG,CAAC,QAAQ,CAAC,EAAE,CAAC,CAAC,WAAW,EAAE,EAAE,CAAA;AACnD,CAAC;AAED,MAAM,gBAAgB,GAAG,sBAAsB,CAAA;AAE/C,iFAAiF;AACjF,MAAM,UAAU,iBAAiB,CAAC,IAAY;IAC5C,OAAO,gBAAgB,CAAC,IAAI,CAAC,IAAI,CAAC,CAAA;AACpC,CAAC;AAED;;;;;GAKG;AACH,MAAM,CAAC,MAAM,0BAA0B,GAAG,IAAI,CAAA"}

package/docs/document-contract.md

@@ -35,7 +35,7 @@ JSON Schema는 필드 구조·자료형·기본 enum·버전을 검사한다. op
 - 알 수 없는 문서/계약 버전과 추가 필드를 거부한다. 현재 capability V3는 transform 또는 표면 참조 pose를 허용한다. V1/V2를 추측 변환하지 않는다.
 - JSON 키 중복은 마지막 값으로 덮지 않고 거부한다. Unicode escape로 같은 키가 표현된 경우도 포함한다.
 - 잘린 JSON, 비유한 수, undefined, 함수, Date, 순환, sparse array, accessor·숨겨진 속성 등 JSON으로 손실되는 입력을 거부한다.
-- 실험 자원 제한: 1MiB UTF-8, 객체 깊이64, 그래프 node512. 제품 용량 정책으로 확정된 값이 아니다.
+- 실험 자원 제한: 1MiB UTF-8, 객체 깊이64, 그래프 node 8192(`FIGURE_DOCUMENT_NODE_LIMIT`, 2026-09-29 판정 — shape-contract Q10: 충분히 크게. 실제로는 1MiB 가 먼저 걸린다).
 - 선언 공간(occupancy)의 경계는 `affine-bounds@1` 한 노드의 출력 여섯이다. 압축 인자 모양(`layout` = `L` + 여섯 묶음 + 후보별 항 수)은 [연산 계약 §4](operator-contracts.md#4-연산-catalog)에 적었다 — AI 저작·내보내기는 거기서 풀어 읽는다.
 - round-trip은 의미·수치·선언 동일성을 대상으로 한다. 원본 JSON의 공백·키 표기·서식은 보존하지 않는다.
 - 함수는 파일/DB에 직접 쓰지 않는다. 저장 API의 원자성, 권한, 버전 충돌, 마이그레이션은 제품 통합 시 별도로 구현해야 한다.

package/docs/shape-contract.md

@@ -0,0 +1,439 @@
+# Shape contract — sections, pushes, cavities and their named features
+
+Status: **contract, Q1–Q9 ruled by the designer as recommended (2026-09-29, 「추천대로 진행하라」).** Stage 1 is being
+built against it. The 2026-09-22 Bézier-corner ruling is replaced by Q4: a corner is an elliptic quarter.
+
+Stage 0 record: Nothing here is wired into the asset, the compiler,
+the renderer or the modeller yet. What is code today:
+
+- `src/section.ts`: a section's meaning. Validity, the one written form, side ids, topology change, area and bounds,
+  and the inside section of a cavity.
+- `src/shape-features.ts`: the named features of a pushed section and its cavity.
+
+Both are tested against figures worked out by hand (`src/section.test.ts`, `src/shape-features.test.ts`). Every
+choice this document still needs from the designer is marked **Qn** and listed in §12. The Korean question sheet for
+the user is `operato-application/packages/operato-figure/docs/shape-editing-stage0-2026-09-29.md`.
+
+This contract replaces the eleven shape operators (`box-shape@1` … `polygon-shape@1`) and their provider names. It
+does not sit beside them. Old assets are rewritten once, and nothing reads the old operators after the switch
+(ADR-0100 decision 9, §10).
+
+## What a person sees
+
+An author adds a **상자** (box). They type a width, a height and a depth, and the box is done. They drag the corner
+radius from 0 to 10. The four corners round off, the box keeps its outer size, and the lid fastened to its top stays
+where it is. They turn on **속 공간** (inside space) with a 10 mm wall, a 15 mm floor and the top open. The box
+becomes a tote. The lid now sits on a rim, and the rim highlights as a ring, not as a filled square. A divider can be
+fastened to the tote's inside floor. Then they open both ends: the floor goes and the tote becomes a duct. Nothing
+is left behind at the bottom.
+
+A second author starts from **단면 그려 만들기** (draw a section) and gets a triangle. They click a side to add a
+point and drag it out, and the triangle becomes a trapezoid. They drag one point across the opposite side. The two
+crossing sides turn red, the message reads 「두 선이 교차합니다. 표시된 점을 옮겨 주세요」, and `적용` (apply) is
+disabled. The last valid shape stays drawn, faded, labelled 「마지막으로 유효했던 모양」. They press Esc, and the
+part is exactly what it was before.
+
+A third author deletes a point of a section whose side has a bracket fastened to it. Before anything changes, the
+screen names the bracket and the side it is fastened to. It asks which new side to use, or offers to leave the
+bracket where it is, unfastened. It never picks the nearest side on its own.
+
+## 0. As built (stage 1, 2026-09-29)
+
+What the kernel does now, where it differs from the text below, and why. Branch `shape-extrude`, unpublished.
+
+- **The node is the record.** A shape is one graph node, `extrude@1` or `revolve@1`. Its params say what it is: the
+  axis, the section kind, the point names, and whether it has an inside and which ends are open. Its arguments are the
+  values that size it, in an order the params fix (`figureExtrudeLayoutOf`). There is no second record beside it, so
+  there is no drift to check. Every reader asks `figureShapeDescriptionOf(node)` which argument is which, and never
+  reads an argument by its place.
+- **A push is `start` and `length`**, and its end is `start + length` (Q1's two ends). A new part's start is one node,
+  `<start> = <length> × −0.5`, so it is centred on its origin as parts always were. Given the graph, such a push's ends
+  are written as ±half its length, which keeps the joints of a rewritten figure made of the same nodes. A later
+  "keep this face" edit writes an explicit start instead (`set-extrusion`, not built yet).
+- **Section kinds:** `rectangle` (with `corner: round`), `ellipse`, `polygon`, and **`portal`**. A portal is a door
+  frame's Π section (width, height, jamb, head) with its faces `opening-left`, `opening-right` and `opening-top`. It is
+  the one section Q5 ruled, named so that DRY_ROOM's doors keep the faces they hang on and follow its size.
+- **Faces keep the modeller's words in stage 1:** the six outer faces by axis, `inside-*` for an inside and
+  `opening-*` for a portal. Renaming them to feature ids (`start-face`, `side-face:<id>` … §4) is its own step, done
+  once for every joint and binding reference. A plane touching a curved side is marked `contact: 'line'` (Q3): it can
+  be fastened to, it is not a surface a binding holds things on, and its preview is a line.
+- **Commands built:** `set-section-corner` and `set-cavity` (§7). An edit that takes away a face something refers to
+  is refused with `FEATURE_MAPPING_REQUIRED`. Mapping to another face is not built yet.
+- **The one-time rewrite:** `scripts/rewrite-shapes.ts` and `scripts/rewrite-shapes-files.ts`. A file is written only
+  when every body's world box and pose agree with the old kernel's (0.1.95) at the drawn values, at half and twice
+  the size, and at each state input's ends. All 24 fixtures agree.
+- **Q10 (ruled 2026-09-29, "make it large enough"):** the node limit is 8192 (`FIGURE_DOCUMENT_NODE_LIMIT`), a fence against malformed documents; the 1 MiB limit binds first. No start shorthand.
+  A start node per part took two stored figures, of 493 and 497 nodes, past 512. The alternative is a `start` left out
+  for a centred push, which is a stored shorthand and a change of format.
+
+## 1. The record
+
+The shape of a part is a record in the asset, **the canon**. Its graph nodes are generated from it, the way a joint's
+nodes are generated from its record (ADR-0093 decision 2). No command edits the nodes directly, and an asset whose
+nodes disagree with its records is refused when read.
+
+Every length in a record is a `FigureMeasure`, the same type a joint's gap uses. It is a number, or
+`{ from, times, plus }` read from the instance's size, a design input or another part's dimension. So a section's
+size and a drawn section's corner can follow the figure exactly as a box's width does today.
+
+```ts
+interface FigurePartShape {
+  part: string // the part id (the place node's id, as today)
+  body: FigureExtrude | FigureRevolve | FigureLoft
+  cavities?: FigureCavityRecord[] // at most one, and only on an extrude, in the first contract (§3)
+}
+
+interface FigureExtrude {
+  op: 'extrude'
+  axis: 'x' | 'y' | 'z' // the part's own axis the section is pushed along
+  section: FigureSectionRecord
+  start: FigureMeasure // E(S, a, b): a and b, measured from the part's origin along axis
+  end: FigureMeasure // start < end over the whole declared range
+}
+
+type FigureSectionRecord =
+  | { kind: 'rectangle'; size: PlaneRecord<FigureMeasure>; corner?: PlaneRecord<FigureMeasure> }
+  | { kind: 'ellipse'; radius: PlaneRecord<FigureMeasure> }
+  | { kind: 'polygon'; points: Array<{ id: string } & PlaneRecord<FigureMeasure>> }
+
+interface FigureCavityRecord {
+  id: string
+  wall: Record<'<a>-' | '<a>+' | '<b>-' | '<b>+', FigureMeasure> // one per flat side of the outer section
+  start: 'open' | { closed: FigureMeasure } // thickness left at the start end
+  end: 'open' | { closed: FigureMeasure }
+}
+```
+
+`PlaneRecord<T>` holds the two plane axes by name, for example `{ x, z }` for a push along Y (§2).
+
+**Q1 — extent as two ends, not a length and an anchor.** ADR-0100 §4.1 writes the push as `E(S, a, b)` and says the
+origin is never recentred by a shape edit. Storing `start` and `end` says exactly that. A centred box is
+`start = -h/2, end = h/2`. A box standing on its origin is `start = 0, end = h`. The box's height is `end - start`
+and is shown as one value (ADR-0100 §3.1). When a length is edited, the edit command decides which end stays, and it
+reads that choice from the part's current fastening (§7). The choice is not stored on the shape. A height that
+follows the instance links both ends, for example `start = {from: instance.y, times: -0.5}` and
+`end = {from: instance.y, times: 0.5}`, and the linking command writes that pair.
+
+The part's record replaces its `<part>.shape` node and nothing else. The pose (`<part>.pose`), the place
+(`<part>`), the appearance, the joints and the bindings keep their ids.
+
+## 2. The section
+
+### 2.1 Kinds
+
+| kind        | written                                                                           | round when  | first stage |
+| ----------- | --------------------------------------------------------------------------------- | ----------- | ----------- |
+| `rectangle` | size along each plane axis, centred on the part's origin; `corner` per plane axis | —           | 1           |
+| `ellipse`   | radius along each plane axis, centred                                             | radii equal | 1           |
+| `polygon`   | one closed loop of straight sides, points by id, not recentred                    | —           | 2           |
+
+A rectangle and an ellipse are never stored as a list of points (ADR-0100 §4.1). Turning a rectangle into points is
+an explicit command, `convert-section`, which the author runs (「점으로 편집」). A polygon becomes a rectangle again only
+when it is one: four points, axis-aligned, centred.
+
+**Corners are per plane axis.** The designer's rule of 2026-09-22 (shape-dimension contract §1) is that every round
+thing has per-axis dimensions. A corner therefore has a reach along each plane axis. Equal reaches make a round
+corner, and unequal reaches an elliptic one. The screen shows one radius and writes it to both axes. The per-axis
+value appears in the detail view only when the two differ. A corner rounded along one axis and not the other is
+refused (`CORNER_ONE_AXIS`).
+
+**Q4 — which curve is a corner.** The 2026-09-22 ruling also says a corner is the quadratic Bézier with the square
+corner as its control point, which is what things-scene's `roundedRect` draws. That ruling was made so V2's
+drawings would match. The new canon is free to choose again, and the choice matters for cavities. The inward offset
+of a quarter circle by `t` is a quarter circle of `r - t`, so an even wall is exact. The inward offset of a Bézier
+corner is not a Bézier. **Recommended: a quarter of the ellipse the two reaches span.** `figureSectionAreaOf` is
+written that way now, and it is the one function to change if the Bézier is kept.
+
+### 2.2 The plane and the one written form
+
+A section pushed along `n` lies across the two other local axes, `(u, v)`, chosen so that `(u, v, n)` is
+right-handed:
+
+| push along | plane axes (u, v) |
+| ---------- | ----------------- |
+| X          | (Y, Z)            |
+| Y          | (Z, X)            |
+| Z          | (X, Y)            |
+
+**Q2 — points keep the axes' own names.** A point for a push along Y is written `{ id, x, z }`, not `{ u, v }`. A
+reader of the JSON never has to know which axis is u, and today's drawn sections, which are X–Z pushed along Y, keep
+their numbers. Only the winding test uses `(u, v)`.
+
+The kernel keeps a drawn loop one way: counter-clockwise seen from `+n`, which means a positive signed area over
+`(u, v)`. Seen from +Y, X runs right and Z runs down the page, as in the modeller's top view. Normalising reverses
+the loop and keeps its first point first. It never moves, adds or removes a point, so every point and side keeps its
+id (ADR-0100 §4.2).
+
+### 2.3 Validity (ADR-0100 §4.2)
+
+`checkFigureSection(section, axis)` returns every fault by the point, side or field that has it. It returns an empty
+list when the section is valid. Nothing is clamped, snapped, reordered or thinned to pass.
+
+| code                                                     | fault                                                                                        |
+| -------------------------------------------------------- | -------------------------------------------------------------------------------------------- |
+| `NON_FINITE`                                             | a coordinate, size, radius or corner that is missing or not a finite number                  |
+| `BAD_POINT_ID`, `DUPLICATE_POINT_ID`                     | a point's name is not an identifier, or is used twice                                        |
+| `TOO_FEW_POINTS`, `TOO_MANY_POINTS`                      | fewer than 3 points, or more than `FIGURE_SECTION_POINT_LIMIT`                               |
+| `ZERO_LENGTH_SIDE`                                       | two points in a row at one place                                                             |
+| `SIDES_FOLD`                                             | a side runs back over the one before it                                                      |
+| `SIDES_CROSS`                                            | two sides pass through each other                                                            |
+| `SIDES_TOUCH`                                            | two sides that are not neighbours meet at a point, or run along each other, without crossing |
+| `ZERO_AREA`                                              | the loop encloses nothing                                                                    |
+| `SIZE_NOT_POSITIVE`                                      | a rectangle's size or an ellipse's radius is 0 or less                                       |
+| `CORNER_NEGATIVE`, `CORNER_ONE_AXIS`, `CORNER_TOO_LARGE` | a corner reach below 0, on one axis only, or past half its side (`max` given)                |
+
+A point added on a side before it is moved is valid: sides may meet at a straight angle. This lets "add a point,
+then drag it" be two steps.
+
+## 3. Cavities (ADR-0100 §4.3)
+
+A cavity is `C = E(I, c, d)` inside `E(S, a, b)`, and the body is `E(S, a, b) \ C`. Its record does not store `I`,
+`c` or `d`. It stores what the author sets:
+
+- **`wall`**: how far in from each flat side of the outer section the inside begins. The screen shows one thickness
+  and writes it to all four sides. It shows the four sides separately only when the author asks for different ones
+  (ADR-0100 §3.3).
+- **`start` / `end`**: `open`, or `{ closed: t }` for a thickness `t` left at that end. Whether an end is open is
+  written in the record. It is never inferred from two numbers happening to be equal. Open at both ends makes a
+  pipe, open at one end a container, and closed at both a sealed space. These are three results of one rule, not
+  three shapes. The floor thickness is the `closed` value, not a separate kind of shape.
+
+`figureCavitySectionOf(outer, axis, wall)` gives the inside section:
+
+- **Rectangle.** The size less the two walls on each axis. The inside is off-centre by half the difference when the
+  walls are uneven. Each corner reach goes in by the thicker of the two walls on its axis, `max(r - t, 0)`, which is
+  the rule the renderer draws today. With a round corner and even walls this is the exact inward offset. Otherwise it
+  is a declared rule, and it does not claim an even thickness around the bend. A corner that goes in to nothing on
+  one axis leaves the inside sharp.
+- **Ellipse.** Each radius less the walls on its axis. This is not an inward offset of an ellipse and is not called
+  one. For a circle with even walls it is exact, which covers a pipe.
+- **Polygon.** Refused (`SECTION_KIND`). A drawn loop's inside needs an inward offset with its own contract for
+  concave corners, narrow necks and regions that vanish or split. That is ADR-0100 stage 4. Until then the screen
+  shows 「이 윤곽에는 속 공간을 만들 수 없습니다」 with the reason, and offers no button.
+
+Refused, never thinned: `WALL_NOT_POSITIVE` (with the side), `NO_ROOM_INSIDE`, `CAVITY_END_NOT_POSITIVE`,
+`CAVITY_NO_LENGTH`.
+
+**One cavity per part** in the first contract (`CAVITY_COUNT`). Two cavities raise questions about whether they
+overlap and what wall lies between them, which nothing asks for yet. A part with two compartments is two parts, or a
+divider fastened to the inside floor.
+
+The body is one closed mesh. The renderer builds the outer walls, the inner walls, the rim and the closing faces as
+one surface. It does not overlay a slab and a ring. Today's `hollowBoxXZ` does that (things-scene
+`figure-geometry.ts:95-111`): the ring of walls stands on the full floor slab, so the walls' bottom and the slab's top lie
+on each other inside the body.
+
+A thing placed inside is a separate part with an `inside` relation (ADR-0100 §4.3). That relation is **not part of
+this stage**. Until it has its own contract, a divider is fastened to `cavity-start:<id>` by an ordinary joint.
+
+## 4. Named features (ADR-0100 §4.1.1)
+
+`figureExtrusionFeaturesOf(extrusion, cavities)` lists what a pushed section offers:
+
+| id                                             | kind            | what it is                                                                          |
+| ---------------------------------------------- | --------------- | ----------------------------------------------------------------------------------- |
+| `start-face`, `end-face`                       | plane           | the two ends; `open: true` when the cavity reaches through, so only the rim is left |
+| `side-face:<side>`                             | plane or curved | each side of the section pushed along the axis                                      |
+| `edge:start:<side>`, `edge:end:<side>`         | edge            | where a side meets an end                                                           |
+| `edge:<point>`                                 | edge            | a drawn section's corner, along the axis                                            |
+| `edge:<a>±<b>±`                                | edge            | a sharp rectangle's corner, along the axis                                          |
+| `cavity-wall:<cavity>:<side>`                  | plane or curved | the inside of each wall, facing into the cavity                                     |
+| `cavity-start:<cavity>`, `cavity-end:<cavity>` | plane           | the face closing the cavity at that end, when it is closed                          |
+| `centre`                                       | point           | the middle of the span, at the section's origin                                     |
+
+**Side ids.**
+
+- **Rectangle.** Each side is named by the plane axis it faces along and the direction: `x-`, `x+`, `z-`, `z+` for
+  a push along Y. A rounded corner is named by the two sides it joins, for example `corner:x-z+`, and exists only
+  while the corner is rounded.
+- **Ellipse.** One curved side, `round`.
+- **Drawn section.** A side is named by **the pair of points it joins**, in name order: `a~b`. So the name does not
+  depend on the loop's direction or on its first point. Moving a point keeps every side. Adding a point on side
+  `c~a` removes that side and adds `c~d` and `a~d`; neither half inherits the old name. Removing a point removes its
+  two sides and adds the side that joins its neighbours. **Every split, merge or deletion is a topology change, and
+  it is reported, not resolved**: `figureSectionTopologyChange(before, after)` lists the sides kept, removed and
+  added (ADR-0100 §5).
+
+**Q9 — what a point is called, and what a screen shows.** The prototype first numbered points by their place in the
+loop. Deleting a point then renumbered the others, and the side the author picked as 「옆면 1–3」 in the editor showed
+as 「옆면 1–2」 once applied. **Recommended:** a drawn point's id is `p<n>`, and a new point takes the highest `n` in
+the loop plus one. Every screen shows `n`, so point 3 is 「3」 before and after any edit, and deleting 2 leaves 1, 3
+and 4. The kernel still accepts any identifier; the rule is for the commands that make points.
+
+**What a box's six faces become** (the modeller's current words):
+
+| today (`FIGURE_FACES`) | box pushed along Y              |
+| ---------------------- | ------------------------------- |
+| `bottom` / `top`       | `start-face` / `end-face`       |
+| `left` / `right`       | `side-face:x-` / `side-face:x+` |
+| `back` / `front`       | `side-face:z-` / `side-face:z+` |
+| `centre`               | `centre`                        |
+
+This is a one-time rewrite of the joint and binding references. It is not an alias kept at runtime.
+
+**Q3 — curved sides and the 22 joints that use them.** Today a cylinder offers six box faces, and four of them lie
+on its curved side (`cylinder-shape@1` uses `centredFaces`). In the development database, **22 joint ends are
+fastened to a cylinder's `left`, `right`, `front` or `back`** (§11). ADR-0100 §5 says a curved face is never taken
+for a plane. **Recommended:** a curved side offers **tangent planes**, `tangent:<axis>±`, defined as the plane that
+touches the curve at its extreme along that axis, with the normal along it. Fastening to one is a line contact, and
+the screen says so (「곡면에 닿는 선으로 붙습니다」). The alternative is to allow only `centre` on round parts and to
+re-author the 22.
+
+## 5. The other operations
+
+ADR-0100 names six operations. Their contracts differ in how settled they are. **None of the four below is offered on
+screen until its row in §9 says so.**
+
+- **`revolve`**: a half-section in `(r, h)` about the part's axis, a full turn only in the first contract. It has
+  three profile kinds, each keeping its dimensions as they are named:
+  - `half-ellipse { radial, axial }` makes a sphere or a spheroid.
+  - `taper { start: {at, radius}, end: {at, radius} }` makes a cone or a frustum.
+  - `polygon` of `(r, h)` points with `r ≥ 0` makes a turned profile.
+
+  A cylinder is `extrude(ellipse)`, never a taper with equal radii. The taper allows equal radii for a moment while
+  it is edited, and does not become a cylinder on its own.
+
+- **`loft`**: stations in order along the axis. Each station is a section of the same kind and the same point ids,
+  and the stations are matched by id. The last station may be a `point`. A **tetrahedron** is a triangle and one
+  point, and a pyramid is a rectangle and one point. There is no tetrahedron shape. The contract still needs: loop
+  correspondence when the kinds differ, twist between stations, the normal at a degenerate point, and
+  self-intersection between stations. So loft stays off until those are written.
+- **`sweep`**: a section along a path. The path frame, twist, curvature limit and self-intersection are not
+  contracted. It stays off. This is the "curved shapes" item already ranked after render batching in the app status.
+- **`assembly`**: several parts as one product structure, held by fixed joints. It keeps each child's meaning,
+  relations and material, and it is never a merged mesh. **Q5** asks whether the door frame, the one assembly in
+  ADR-0100's representative list, needs it. A door frame is also one `extrude` of a drawn Π section along Z. That is
+  one body with named inside faces, and it needs no assembly contract.
+
+**Q6 — an ellipsoid with three different radii.** `sphere-shape@1` takes three radii. `revolve` makes only
+spheroids, with the two radial radii equal. Three live figures use spheres (여의봉 and 작업자 by expression, 화성
+충방전기 at 85/85/85). **Recommended:** rewrite them as `revolve(half-ellipse)`. If an evaluated pair of radial radii
+differs at any size in the declared range, the rewrite reports that asset and does not convert it. The ellipsoid
+does not become a seventh operation without a new ADR.
+
+## 6. Numbers
+
+| name                         | value                          | what it decides                                                                | status                                                         |
+| ---------------------------- | ------------------------------ | ------------------------------------------------------------------------------ | -------------------------------------------------------------- |
+| `FIGURE_SECTION_TOLERANCE`   | 1e-6 mm                        | whether two points coincide, a side has length, two sides touch; topology only | proposed                                                       |
+| `FIGURE_SECTION_POINT_LIMIT` | 256                            | points in one drawn loop                                                       | proposed, to be measured (below)                               |
+| tessellation                 | `appearance.segments` as today | how many segments a curve is drawn with                                        | unchanged; no segment choice on the first screen (ADR-0100 §7) |
+
+The tolerance is not a snapping distance, not the magnet's pixel tolerance, and not a tolerance for comparing
+drawings (ADR-0100 §4.2). The point limit is to be confirmed by measuring the validity check (O(n²) over the sides),
+triangulation and a full re-evaluation of the figure at 64, 256 and 1024 points on the modeller's machine class.
+
+## 7. Commands
+
+All of them go through the authoring session, which checks the model and revision, applies atomically, and undoes
+in one step. The modeller, the AI and the templates use them and nothing else (ADR-0100 decision 6).
+
+| command                                                              | what it changes                                                                      |
+| -------------------------------------------------------------------- | ------------------------------------------------------------------------------------ |
+| `edit-section { part, section, mapping? }`                           | the whole section, as one step: what the 2D editor's `적용` sends                    |
+| `set-extrusion { part, length, keep: 'start' \| 'centre' \| 'end' }` | `end - start`; `keep` defaults to what the part's fastening holds                    |
+| `set-section-corner { part, corner }`                                | the corner reaches of a rectangle                                                    |
+| `set-cavity { part, cavity \| null, mapping? }`                      | the part's inside space: add, change, remove                                         |
+| `convert-section { part, to, mapping? }`                             | rectangle to points, points to rectangle (only when it is one), ellipse to rectangle |
+
+`mapping` names, for each removed feature something refers to, the feature that takes its place, or `release`.
+`release` unfastens the part and leaves it at its current rest pose, under ADR-0093 decision 7. A command without
+the mapping it needs is refused with `FEATURE_MAPPING_REQUIRED` and the list of references. Nothing is mapped in
+passing.
+
+**The plan.** `planFigureShapeEdit(asset, command)` returns, without changing anything:
+
+- the context (model, revision)
+- the section's validity issues
+- the topology change (§4)
+- every reference to a removed feature, with its owner (joint, binding, occupancy contact, material, capability)
+- the parts that will move, and by how much
+- the clips that would be lost, which are refused under ADR-0099
+- the evaluated result, for the preview
+
+The preview and the apply use the same plan. A plan made against another revision is refused when applied.
+
+## 8. What an edit keeps (ADR-0100 §5)
+
+- The part's id, origin and rest pose never change with its shape. A fastened child is evaluated again against the
+  changed feature, and the plan shows the move before it is applied.
+- A dimension linked to something stays linked. Setting a linked value to a number is `unlink-dimension`, shown
+  first.
+- State may change a length, never the topology. No state input may change the number of points or cavities, or
+  whether an end is open. The compiler refuses such a dependence under the operator's `state` policy.
+- A reference is to a feature id, never to a side's index, a triangle or a point's place in a list.
+
+## 9. What is on when
+
+| row                                                 | stage 1 (rectangle family) | stage 2 (drawn section) | stage 3 (product path) | later          |
+| --------------------------------------------------- | -------------------------- | ----------------------- | ---------------------- | -------------- |
+| extrude · rectangle / ellipse                       | on                         |                         |                        |                |
+| corner (per axis)                                   | on                         |                         |                        |                |
+| cavity on rectangle / ellipse                       | on                         |                         |                        |                |
+| extrude · polygon, 2D editor                        |                            | on                      |                        |                |
+| `convert-section`                                   | rectangle ↔ points         | on                      |                        |                |
+| revolve (half-ellipse, taper)                       | on, no editor beyond sizes |                         |                        |                |
+| revolve · polygon profile                           |                            |                         |                        | contract first |
+| loft (point station: pyramid, tetrahedron)          |                            |                         | on, after its contract |                |
+| loft · section to section                           |                            |                         |                        | contract first |
+| sweep                                               |                            |                         |                        | contract first |
+| assembly                                            |                            |                         | Q5                     |                |
+| cavity on a drawn section                           |                            |                         |                        | stage 4        |
+| AI grammar, templates, board, rewrite of all assets |                            |                         | on                     |                |
+
+## 10. What changes where
+
+Surveyed 2026-09-29 (read-only):
+
+- **figure-model.** It gains the record and its compiler, the gate reading features, the commands above, and the
+  proposal grammar. It loses the eleven shape operators, `feature@1`'s provider switch (`graph.ts` 863–), the
+  provider table (`shape-provider.ts`), `FOLLOWS_NOW`, `create.ts`'s recipe table, and `FIGURE_FACES` as the words
+  for a fastening.
+- **things-scene** (about 150 lines). The provider switch in `figure-geometry.ts:73-134` becomes one mesh builder per
+  operation. The geometry cache key (`keyOf`) becomes the record's content. The top view (`figure-top-view.ts:87-108`)
+  reads the section instead of the provider. There is no per-face picking today, so features need picking added,
+  not moved.
+- **figure-ui** (about 220 lines in about a dozen tables). The palette (`palette.ts`, `figure-parts.ts`) moves to
+  starting shapes. The gizmo's `BOXES` and round-scaling tables (`gizmo.ts:33`, `:68-76`) move to the record's own
+  sizes. `links.ts` `KIND_OF_SHAPE` and `placeFacesOf` move to features. The icons, the material panel's `ROUND`,
+  maturity's copy of the geometry key and `ROUND_FOOTPRINT`, and `faceHighlightOf` also change. The face `<select>`
+  lists of six names become feature lists. The 2D section editor is new.
+- **figure-service** (no shape code on the server). The proposal grammar comes from figure-model. The 101 recipes'
+  `build.mts` use `kind` primitives through `addFigurePrimitive`, so the recipes are rebuilt and the 123 generated
+  models regenerated.
+- **operato-figure.** Two landing scripts push raw `box-shape@1` nodes. The maturity row "polygon/shape editing:
+  planned" changes.
+
+## 11. The assets to rewrite
+
+The development database, read-only on 2026-09-29, has 58 live figures:
+
+| operator           | nodes | figures | becomes                                                                                                                                            |
+| ------------------ | ----- | ------- | -------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `box-shape@1`      | 257   | 47      | extrude · rectangle                                                                                                                                |
+| `cylinder-shape@1` | 117   | 34      | extrude · ellipse                                                                                                                                  |
+| `rounded-box@2`    | 52    | 11      | extrude · rectangle with corner per axis (in 7 one reach is a number and the other an expression; whether they differ is evaluated at the rewrite) |
+| `rounded-box@1`    | 25    | 8       | extrude · rectangle with corner                                                                                                                    |
+| `cylinder-shape@2` | 10    | 3       | extrude · ellipse                                                                                                                                  |
+| `sphere-shape@1`   | 5     | 3       | revolve · half-ellipse (Q6)                                                                                                                        |
+| `hollow-box@2`     | 2     | 2       | extrude · rectangle + cavity, end open                                                                                                             |
+| `polygon-shape@1`  | 2     | 1       | extrude · polygon; point ids are given at the rewrite                                                                                              |
+
+Joint ends on a cylinder's side faces: `left` 6, `right` 6, `front` 5, `back` 5 (Q3). Joint ends on a cylinder's
+`bottom` 23 and `top` 26 become `start-face` and `end-face`. The 101 templates use box 177, cylinder 36, hollow-box
+10, portal 6, rounded-box 3 and frustum 2 steps, and are rebuilt from their `build.mts`.
+
+## 12. Questions for the designer
+
+|     | question                                                                                                                   | recommended                                 |
+| --- | -------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------- |
+| Q1  | Store a push as its two ends, not a length and an anchor                                                                   | two ends (§1)                               |
+| Q2  | Points keep the axes' own names; `(u, v, n)` right-handed                                                                  | yes (§2.2)                                  |
+| Q3  | Curved sides: tangent planes for the 22 joints, or `centre` only                                                           | tangent planes, said as line contact (§4)   |
+| Q4  | A corner's curve: elliptic quarter, or keep the Bézier of 2026-09-22                                                       | elliptic quarter (§2.1)                     |
+| Q5  | Door frame: one Π-section extrude, or an assembly                                                                          | one extrude; assembly after (§5)            |
+| Q6  | Three-radius ellipsoid: rewrite as spheroid and report the rest, or keep it                                                | rewrite and report (§5)                     |
+| Q7  | One cavity per part in the first contract                                                                                  | yes (§3)                                    |
+| Q8  | Tolerance 1e-6 mm and 256 points, pending the measurement in §6                                                            | yes                                         |
+| Q9  | A drawn point's id is `p<n>`, a new point takes the highest n + 1, and screens show n, never the point's place in the loop | yes (§4)                                    |
+| Q10 | The node limit, or a centred push written without its start | **Ruled: 8192**, no shorthand |

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@hatiolab/figure-model",
-  "version": "0.1.95",
+  "version": "0.2.1",
   "description": "The figure format (figure-asset-1): a kernel that evaluates a figure from its declared relations, the authoring commands a modeller and an AI share, the release gate and the score.",
   "keywords": [
     "figure",
@@ -49,6 +49,7 @@
     "build": "tsc -p tsconfig.build.json",
     "check": "tsc -p tsconfig.json --noEmit",
     "test": "npm run check && node --test src/*.test.ts",
+    "test:rewrite": "node --test scripts/*.test.ts",
     "test:coverage": "node --test --experimental-test-coverage --test-coverage-lines=100 --test-coverage-branches=95 --test-coverage-functions=100 src/*.test.ts",
     "format": "prettier --write \"src/**/*.ts\" \"docs/**/*.md\" \"*.md\" \"*.json\"",
     "format:check": "prettier --check \"src/**/*.ts\" \"docs/**/*.md\" \"*.md\" \"*.json\"",