forma-dsl-mcp 0.3.8 → 0.4.0

package/src/reference/reference/align.md

@@ -46,13 +46,13 @@ the *minimum* face at that coordinate. `z = 5` means "sit this on a surface at h
 
 #### Returns
 
-The children, unioned and translated. Dimensionality passes through — a 2D child accepts
+The children, unioned and translated. Dimensionality passes through - a 2D child accepts
 `x` and `y` only.
 
 #### Caveats
 
 - **`align` needs a kernel context.** It is the one block that cannot be evaluated without
-  one: `align needs a kernel context — render the model rather than building it`. Building a
+  one: `align needs a kernel context - render the model rather than building it`. Building a
   node tree with a bare `Evaluator` and no context will fail on it.
 - **It costs a kernel round-trip.** The child has to be solved before the alignment can be
   computed, so the subtree is evaluated at build time rather than lazily. The digest cache
@@ -60,7 +60,7 @@ The children, unioned and translated. Dimensionality passes through — a 2D chi
 - It measures the **bounding box**, not the geometry. For anything that is not
   axis-aligned, the box is larger than the shape.
 - Children are unioned first, so several blocks inside one `align` move together.
-- A label — `align "name" { }` — is accepted and silently ignored.
+- A label - `align "name" { }` - is accepted and silently ignored.
 
 ---
 
@@ -81,7 +81,7 @@ align {
 }
 ```
 
-Most shapes take a `center = true` attribute, which is cheaper — it changes how the shape is
+Most shapes take a `center = true` attribute, which is cheaper - it changes how the shape is
 built rather than measuring it afterwards. Reach for `align` when the thing being centred is
 a **composition** rather than a single shape, and there is no one attribute to set.
 
@@ -131,9 +131,9 @@ align {
 
 | Approach | When |
 | --- | --- |
-| `center = true` on the shape | A single primitive. Free — it changes how the shape is built |
+| `center = true` on the shape | A single primitive. Free - it changes how the shape is built |
 | `translate` by a known amount | You already know the dimensions, usually because they are params |
-| `align` | The extent is **computed** — a hull, a composition, an offset outline — and writing the arithmetic would mean duplicating it |
+| `align` | The extent is **computed** - a hull, a composition, an offset outline - and writing the arithmetic would mean duplicating it |
 
 A model that knows its own dimensions should use them:
 
@@ -154,7 +154,7 @@ kernel round-trip. For anything small, prefer clarity.
 
 ## Troubleshooting
 
-### `align needs a kernel context — render the model rather than building it`
+### `align needs a kernel context - render the model rather than building it`
 
 An `Evaluator` was constructed without a `context`, and the document contains an `align`.
 [`render`](../api/render.md) always supplies one, so this only comes up when driving the
@@ -170,12 +170,12 @@ unaffected.
 
 ### `align: "x" must be "min", "center", "max" or a number`
 
-The value is a string that is not one of the three keywords — `"middle"` and `"centre"` are
+The value is a string that is not one of the three keywords - `"middle"` and `"centre"` are
 the usual culprits. The spelling is `"center"`.
 
 ### `align needs at least one shape inside it`
 
-The body produced nothing — an `if` that took no branch, or a `for` over an empty list.
+The body produced nothing - an `if` that took no branch, or a `for` over an empty list.
 
 ### `align: unknown attribute "z"` on a 2D shape
 

package/src/reference/reference/booleans.md

@@ -27,7 +27,7 @@ None.
 
 - **Usually unnecessary.** Sibling blocks are already implicitly unioned, so
   `part "p" { a  b }` and `part "p" { union { a  b } }` are the same. Write `union`
-  explicitly when it makes the grouping clearer — typically as one operand of a
+  explicitly when it makes the grouping clearer - typically as one operand of a
   `difference`.
 - The order of the children does not affect the result, and does not affect the digest
   either: union members are sorted by subtree size before hashing, so two unions written in a
@@ -86,7 +86,7 @@ None.
 
 #### Caveats
 
-- With one child, it is that child. With none, it is an error —
+- With one child, it is that child. With none, it is an error -
   `"intersection" needs at least one shape inside it`.
 - Order does not affect the result.
 
@@ -149,7 +149,7 @@ intersection {
 }
 ```
 
-For a single flat cut, [`trim`](refinement.md#trim) is cheaper — it cuts with a half-space
+For a single flat cut, [`trim`](refinement.md#trim) is cheaper - it cuts with a half-space
 and needs no second solid.
 
 ### Grouping so a transform applies to several shapes
@@ -164,7 +164,7 @@ translate {
 }
 ```
 
-Inside a `difference`, though, each child is separate — so to subtract two shapes *as one
+Inside a `difference`, though, each child is separate - so to subtract two shapes *as one
 body*, group them explicitly:
 
 ```hcl
@@ -178,7 +178,7 @@ difference {
 ```
 
 Here the `union` is not decorative: without it the two cylinders would be two separate
-cutters, which happens to give the same result for a difference — but not for an
+cutters, which happens to give the same result for a difference - but not for an
 `intersection`, where it changes the answer entirely.
 
 ---

package/src/reference/reference/component.md

@@ -27,7 +27,7 @@ model "m" {
 Declares a block named `NAME`. Its body is ordinary geometry; its `param` declarations are
 the attributes a call site may pass.
 
-Once declared, it is called like any other block — the call site cannot tell a component
+Once declared, it is called like any other block - the call site cannot tell a component
 from a builtin, which is the point.
 
 #### Body
@@ -41,7 +41,7 @@ from a builtin, which is the point.
 
 #### Returns
 
-One geometry node — everything in the body, unioned. The dimensionality is whatever the body
+One geometry node - everything in the body, unioned. The dimensionality is whatever the body
 produced, so a component may return 2D or 3D geometry and be used wherever that fits.
 
 #### Caveats
@@ -60,8 +60,8 @@ produced, so a component may return 2D or 3D geometry and be used wherever that
   branch, fails with `component "c" produced no geometry`.
 - **Recursion is not supported.** A component that calls itself has no base case the
   evaluator can see, and hits the nesting limit:
-  `nesting deeper than 64 blocks — is a component using itself?`
-- A label on a call — `my_component "label" { }` — is accepted and silently ignored.
+  `nesting deeper than 64 blocks - is a component using itself?`
+- A label on a call - `my_component "label" { }` - is accepted and silently ignored.
   Do not rely on it.
 
 ---
@@ -88,7 +88,7 @@ component "tray" {
 }
 ```
 
-Note the empty braces on `lid`. `param lid` on its own is a **syntax error** — a param needs
+Note the empty braces on `lid`. `param lid` on its own is a **syntax error** - a param needs
 either `= expression` or a braced body, even an empty one.
 
 Inside the body, a param is read by its bare name. There is no `var.` for component params;
@@ -172,7 +172,7 @@ model "m" {
 ### Reuse is free
 
 Identity in the geometry tree is content identity, so a component called twenty times with
-the same arguments is **evaluated once** — its digest is the same each time, and the kernel
+the same arguments is **evaluated once** - its digest is the same each time, and the kernel
 sees one node. Calling it twenty times with twenty different sizes does cost twenty
 evaluations, because the content genuinely differs.
 
@@ -190,7 +190,7 @@ A `param` with no default and no body:
 
 ```hcl
 component "c" {
-  param s          // ✗ syntax error — the parser is looking for `=` or `{`
+  param s          // ✗ syntax error - the parser is looking for `=` or `{`
   box { size = [s, s, s] }
 }
 
@@ -207,19 +207,19 @@ the call site, or give the declaration a default.
 
 ### `c: unknown param "t"`
 
-The call passed an attribute the component does not declare — usually a typo, or an
+The call passed an attribute the component does not declare - usually a typo, or an
 attribute meant for a block inside the component. Components have no pass-through: every
 value they need must be declared.
 
 ### `component "box" shadows a builtin block`
 
-The name is already a builtin. Pick another — `rounded_box`, `my_box`, `case_body`. See the
+The name is already a builtin. Pick another - `rounded_box`, `my_box`, `case_body`. See the
 [full block list](../README.md#shapes) for what is taken.
 
 ### `a component cannot declare parts`
 
 A [`part`](part.md) is a piece of the scene, not geometry an enclosing block can operate on,
-so it cannot come out of a component. Invert it — put the part in the model and call the
+so it cannot come out of a component. Invert it - put the part in the model and call the
 component inside it:
 
 ```hcl
@@ -231,7 +231,7 @@ component "c" { box { size = [1, 1, 1] } }
 model "m" { part "p" { c { } } }
 ```
 
-### `nesting deeper than 64 blocks — is a component using itself?`
+### `nesting deeper than 64 blocks - is a component using itself?`
 
 Almost always direct or mutual recursion. There is no base case the evaluator can detect,
 because a component's body is expanded before any condition inside it is known. Rewrite the
@@ -239,7 +239,7 @@ recursion as a [`for`](../language/control-flow.md#for) loop.
 
 ### `component "c" produced no geometry`
 
-The body evaluated to nothing — an empty body, a loop over an empty list, or an `if` with no
+The body evaluated to nothing - an empty body, a loop over an empty list, or an `if` with no
 `else` whose condition was false. A component must return something; guard at the call site
 instead:
 

package/src/reference/reference/conversions.md

@@ -49,7 +49,7 @@ extrude {
 - A `height` of `0` or less yields empty geometry rather than an error, so a parameter
   sweeping to zero does not break the model.
 - `scale_top = [0, 0]` gives a point, which is one way to build a pyramid from any profile.
-- The profile is swept as drawn — `extrude` does not centre it. A `rect` that is not centred
+- The profile is swept as drawn - `extrude` does not centre it. A `rect` that is not centred
   produces a box in the positive quadrant.
 
 ---
@@ -76,7 +76,7 @@ revolve { angle = 180  segments = 64  polygon { points = profile } }
   radius. A profile drawn from `[0, 0]` upwards produces a solid standing on the XY plane.
 - **Every X must be ≥ 0.** A profile that crosses the axis revolves through itself and the
   result is not what you drew.
-- The profile does not have to touch the axis. One that does not produces a tube — which is
+- The profile does not have to touch the axis. One that does not produces a tube - which is
   how [`torus`](shapes-3d.md#torus) is built internally.
 - An `angle` of `0` or less yields empty geometry rather than an error.
 
@@ -84,7 +84,7 @@ revolve { angle = 180  segments = 64  polygon { points = profile } }
 
 ## `project`
 
-The shadow a solid casts on the XY plane — its full outline, from any Z.
+The shadow a solid casts on the XY plane - its full outline, from any Z.
 
 ```hcl
 project { bracket { } }
@@ -120,7 +120,7 @@ slice { z = 12  bracket { } }
 
 - Takes 3D geometry and produces 2D.
 - A plane that misses the solid gives an empty cross-section, not an error.
-- A plane exactly on a flat face is ambiguous — offset it slightly.
+- A plane exactly on a flat face is ambiguous - offset it slightly.
 
 ---
 
@@ -129,7 +129,7 @@ slice { z = 12  bracket { } }
 ### Profiles are where the modelling happens
 
 Most shapes are easier to describe in 2D and then given thickness. A rounded box, for
-instance, has no primitive — it is a rounded rectangle with a height:
+instance, has no primitive - it is a rounded rectangle with a height:
 
 ```hcl
 extrude {
@@ -215,7 +215,7 @@ model "m" {
 
 ### Inspecting a cross-section
 
-`slice` is a debugging tool as much as a modelling one — extrude the slice thinly to see
+`slice` is a debugging tool as much as a modelling one - extrude the slice thinly to see
 where the walls actually fell:
 
 ```hcl
@@ -243,7 +243,7 @@ extrude { height = 10  rect { size = [1, 1] } }          // ✓
 Two children of different dimensionality. Extrude each profile separately, or union the
 profiles before extruding.
 
-### `part "body" is 2D — extrude or revolve it before rendering`
+### `part "body" is 2D - extrude or revolve it before rendering`
 
 A profile reached the renderer. Somewhere the `extrude` or `revolve` is missing, or is
 wrapped around the wrong block.
@@ -261,7 +261,7 @@ have X ≥ 0.
 ### My revolved solid is lying down
 
 `revolve` maps the profile's **Y** to the result's **Z**. A profile written as (x, z) with
-the height in the first component produces a solid on its side — swap the components.
+the height in the first component produces a solid on its side - swap the components.
 
 ### `revolve` produced nothing
 

package/src/reference/reference/functions.md

@@ -1,7 +1,7 @@
 # Functions
 
 Thirty builtin functions, callable in any [expression](../language/expressions.md). They take
-**positional arguments only** — named arguments are an error — and there are no user-defined
+**positional arguments only** - named arguments are an error - and there are no user-defined
 functions: to name a value declare a [`local`](local.md), and to name geometry declare a
 [`component`](component.md).
 
@@ -103,7 +103,7 @@ local bolts = max(3, min(16, var.bolts))
 
 `len(value)` → number
 
-The length of a list or a string. Anything else gives `0` — it does not raise.
+The length of a list or a string. Anything else gives `0` - it does not raise.
 
 ```hcl
 len([1, 2, 3])      // 3
@@ -168,7 +168,7 @@ range(4)              // [0, 1, 2, 3]
 range(2, 6)           // [2, 3, 4, 5]
 range(0, 10, 2.5)     // [0, 2.5, 5, 7.5]
 range(5, 0, -1)       // [5, 4, 3, 2, 1]
-range(0, -5)          // []  — backwards with a positive step is empty, not infinite
+range(0, -5)          // []  - backwards with a positive step is empty, not infinite
 ```
 
 This is what drives most [`for`](../language/control-flow.md#for) loops.
@@ -211,14 +211,14 @@ String interpolation already converts, so `str` is mostly useful when building a
 | `pi` | 3.141592653589793 |
 | `e` | 2.718281828459045 |
 
-They are ordinary names in the root scope, so they can be shadowed by a param or a local —
+They are ordinary names in the root scope, so they can be shadowed by a param or a local -
 avoid doing so.
 
 ```hcl
 local circumference = 2 * pi * var.radius
 ```
 
-Since every angle in the language is in degrees, `pi` comes up less than it would elsewhere —
+Since every angle in the language is in degrees, `pi` comes up less than it would elsewhere -
 mostly in arc lengths and areas rather than in rotations.
 
 ---
@@ -281,8 +281,8 @@ model "m" {
 
 ### `len takes 1 argument(s), got 2`
 
-A fixed-arity function got the wrong count. The variadic ones — `min`, `max`, `sum`,
-`concat`, `range` — accept any number; the rest do not.
+A fixed-arity function got the wrong count. The variadic ones - `min`, `max`, `sum`,
+`concat`, `range` - accept any number; the rest do not.
 
 ### `pow: functions take positional arguments`
 
@@ -305,7 +305,7 @@ allocating until the tab dies.
 
 ### `... must be a finite number`
 
-Something upstream produced `NaN` or `Infinity` — `sqrt` of a negative, `min()` of nothing,
+Something upstream produced `NaN` or `Infinity` - `sqrt` of a negative, `min()` of nothing,
 `num("abc")`. The error names the block and attribute that read it, not where it was
 produced, so work backwards from there.
 

package/src/reference/reference/local.md

@@ -13,7 +13,7 @@ local radius = var.diameter / 2
 
 ### `local NAME = expression`
 
-Binds a name to the result of an expression. Locals hold values, never geometry — to name a
+Binds a name to the result of an expression. Locals hold values, never geometry - to name a
 piece of geometry, declare a [`component`](component.md).
 
 #### Parameters
@@ -30,7 +30,7 @@ Nothing. A local binds a name; it produces no geometry.
 #### Caveats
 
 - **Locals are ordered at the top level.** A local may refer to params, to constants and to
-  locals declared *above* it — never below. `local a = b` before `local b = 2` fails with
+  locals declared *above* it - never below. `local a = b` before `local b = 2` fails with
   `unknown name "b"`.
 - **Locals inside a body are not ordered.** Every local in one block body is resolved before
   any of that body's blocks are built, so a block may use a local declared after it. See
@@ -130,7 +130,7 @@ model "frame" {
 
 | Use | When |
 | --- | --- |
-| [`param`](param.md) | The value is an **input** — someone outside the document should be able to change it |
+| [`param`](param.md) | The value is an **input** - someone outside the document should be able to change it |
 | `local` | The value is **derived** from params or is a fixed table, and should never be a control |
 | [`component`](component.md) | You are naming **geometry**, not a value |
 
@@ -152,7 +152,7 @@ local cavity_top = top + 2      // runs past the opening so the neck is not capp
 
 ### `unknown name "b"`
 
-A top-level local referred to something declared below it. Move the declaration up — locals
+A top-level local referred to something declared below it. Move the declaration up - locals
 are resolved strictly in source order:
 
 ```hcl

package/src/reference/reference/model.md

@@ -38,7 +38,7 @@ A scene: a list of parts, each with a name, a colour, an opacity and a geometry
 #### Caveats
 
 - **Every part must be 3D.** A 2D part is rejected before it is solved:
-  `part "body" is 2D — extrude or revolve it before rendering`.
+  `part "body" is 2D - extrude or revolve it before rendering`.
 - **A model must produce something.** An empty body, or one whose only loop ran zero times,
   fails with `model "m" produced no geometry`.
 - **Declaring the same model twice is an error**: `model "m" is declared twice`.
@@ -63,7 +63,7 @@ Naming one that does not exist fails with `no model named "exploded"`. In the ed
 first model is the one shown.
 
 Several models in one document is the idiomatic way to keep variants of the same object
-together — a printable part and the assembly it belongs to, say:
+together - a printable part and the assembly it belongs to, say:
 
 ```hcl
 component "bracket" { ... }
@@ -81,7 +81,7 @@ model "assembly" {                  // what it looks like assembled
 
 ### Parts, and geometry without them
 
-Geometry written straight into a model — outside any `part` — becomes **one default part
+Geometry written straight into a model - outside any `part` - becomes **one default part
 named after the model**, coloured `#b8c4d0`:
 
 ```hcl
@@ -101,7 +101,7 @@ model "m" {
 // parts: "pin", then "m"
 ```
 
-Prefer explicit parts once there is more than one piece — they are what the viewer colours
+Prefer explicit parts once there is more than one piece - they are what the viewer colours
 and lists, and what an exporter can write out separately.
 
 ### Model params
@@ -119,10 +119,10 @@ model "bracket" {
 
 | | Document `param` | Model `param` |
 | --- | --- | --- |
-| Default required | No — may be required instead | **Yes**: `model "m": param "s" needs a default` |
+| Default required | No - may be required instead | **Yes**: `model "m": param "s" needs a default` |
 | Settable by the caller | Yes, via `render(source, { params })` | No |
 | Appears in `describeParameters` | Yes | No |
-| Readable as `var.NAME` | Yes | No — bare name only |
+| Readable as `var.NAME` | Yes | No - bare name only |
 
 Use them to give one model's fixed numbers a name without adding a control to the editor.
 For anything the caller should change, declare the param at the top level.
@@ -142,7 +142,7 @@ model "stacked_trays" {
 }
 ```
 
-An optional part goes behind an `if` **around** the part, never inside it — a part with no
+An optional part goes behind an `if` **around** the part, never inside it - a part with no
 geometry is an error:
 
 ```hcl
@@ -174,13 +174,13 @@ model "assembly" {
 The body evaluated to nothing. Usual causes:
 
 - an empty body;
-- a `for` over an empty list — `range(0, var.n)` where `n` is `0`;
+- a `for` over an empty list - `range(0, var.n)` where `n` is `0`;
 - an `if` with no `else` whose condition was false.
 
 Guard the degenerate case so something is always produced, or make the parameter's minimum
 exclude it.
 
-### `part "body" is 2D — extrude or revolve it before rendering`
+### `part "body" is 2D - extrude or revolve it before rendering`
 
 A part ended up holding a cross-section rather than a solid. 2D shapes cannot be rendered
 directly:
@@ -209,5 +209,5 @@ Two models share a name, so `render(source, { model: 'm' })` would be ambiguous.
 ### My `render(source, { params })` value is ignored
 
 The param is probably declared inside the model rather than at the top level. Only top-level
-params are settable. Check with [`describeParameters`](../api/describe-parameters.md) — it
+params are settable. Check with [`describeParameters`](../api/describe-parameters.md) - it
 lists exactly the params a caller can set.

package/src/reference/reference/param.md

@@ -29,7 +29,7 @@ param bolts {
 
 #### Attributes
 
-Every attribute is optional. **Only `default` affects geometry** — the rest describe the
+Every attribute is optional. **Only `default` affects geometry** - the rest describe the
 control the editor should build, and are returned verbatim by
 [`describeParameters`](../api/describe-parameters.md).
 
@@ -43,7 +43,7 @@ control the editor should build, and are returned verbatim by
 | `description` | string | Help text |
 | `options` | list | A fixed set of choices, for a dropdown rather than a free field |
 
-Unknown attributes are **not** rejected here — a param block is metadata, and anything in it
+Unknown attributes are **not** rejected here - a param block is metadata, and anything in it
 is passed through to the descriptor. This is the one block in the language that does not
 reject attributes it does not understand.
 
@@ -55,13 +55,13 @@ Nothing. A param binds a name; it produces no geometry.
 
 - **`min`, `max`, `step` and `options` are not enforced.** They shape the editor's control
   and nothing else. `render(source, { params: { bolts: 9999 } })` succeeds on a param
-  declared `max = 16`. Validate in the model if a bound matters —
+  declared `max = 16`. Validate in the model if a bound matters -
   `local n = min(max(var.bolts, 3), 16)`.
 - A param block may contain **attributes only**. Nested blocks inside it are an error:
   `a param block holds attributes, not nested blocks`.
 - Declaring the same param twice is an error: `param "a" is declared twice`.
 - A param's `default` may refer to params declared **above** it by their bare name, but not
-  to `var` — `var` is assembled after every param has resolved. See
+  to `var` - `var` is assembled after every param has resolved. See
   [Scope](../language/scope.md#the-root-scope).
 - A param declared inside a `model` is a different thing: it must have a default and cannot
   be set from outside. See [`model`](model.md#model-params).
@@ -124,7 +124,7 @@ When `type` is omitted it is inferred from the default: a number gives `number`,
 `bool`, a string `string`, a list `vector`. A param with neither a `type` nor a `default`
 falls back to `number`.
 
-An `angle` param is an ordinary number as far as the language is concerned — every angle in
+An `angle` param is an ordinary number as far as the language is concerned - every angle in
 forma is in degrees, and the type only tells the editor to label the control that way.
 
 ### Declaring a required input
@@ -155,7 +155,7 @@ param bore     = diameter / 2 - wall * 4     // ✓ bare names of earlier params
 ```
 
 For a value that is always derived and should never be a control, use a
-[`local`](local.md) instead — locals are computed after every param and may use `var.`.
+[`local`](local.md) instead - locals are computed after every param and may use `var.`.
 
 ### Offering a fixed set of choices
 
@@ -191,7 +191,7 @@ give it a default, or supply one:
 await render(source, { params: { height: 20 } });
 ```
 
-[`describeParameters`](../api/describe-parameters.md) works on such a document — it is built
+[`describeParameters`](../api/describe-parameters.md) works on such a document - it is built
 to be callable before any value exists, so a front end can discover what to ask for.
 
 ### `param "a" is declared twice`
@@ -201,7 +201,7 @@ overwritten, because a duplicated input would make the editor's control ambiguou
 
 ### `a param block holds attributes, not nested blocks`
 
-Something inside the braces was parsed as a block rather than an attribute — usually a
+Something inside the braces was parsed as a block rather than an attribute - usually a
 missing `=`:
 
 ```hcl

package/src/reference/reference/part.md

@@ -19,7 +19,7 @@ Groups geometry into one named, coloured piece of the scene. Parts are solved in
 and drawn in their own colour.
 
 A part is **not an operand**. It does not contribute geometry to the block around it, and an
-enclosing `translate` will not move it — which is why a part belongs directly in a
+enclosing `translate` will not move it - which is why a part belongs directly in a
 [`model`](model.md), or inside a `for` or `if` in one.
 
 #### Label
@@ -57,7 +57,7 @@ Nothing, to the enclosing block. The part travels separately and lands in the sc
 - **A part cannot come out of a [`component`](component.md)**:
   `a component cannot declare parts`. Call the component inside a part instead.
 - **Every part must be 3D** by the time it renders:
-  `part "body" is 2D — extrude or revolve it before rendering`.
+  `part "body" is 2D - extrude or revolve it before rendering`.
 - Several blocks inside a part are implicitly unioned, exactly as anywhere else.
 - Nothing rejects two parts with the same name; the viewer will simply list two entries
   called the same thing.
@@ -121,7 +121,7 @@ if var.show_label {
   part "label" { color = "#f4f1e4"  label_band { } }
 }
 
-// ✗ — when show_label is false this is an empty part, which is an error
+// ✗ - when show_label is false this is an empty part, which is an error
 part "label" {
   if var.show_label { label_band { } }
 }
@@ -159,13 +159,13 @@ for (const part of result.parts) {
   part.name;      // "bottle"
   part.color;     // "#8fd3e8"
   part.opacity;   // 1
-  part.node;      // the GeometryNode — what context.collect() wants
+  part.node;      // the GeometryNode - what context.collect() wants
   part.concrete;  // the solved Manifold solid, owned by the context
   part.mesh;      // positions and normals, ready to upload
 }
 ```
 
-Parts are solved independently, so two parts that share a subtree still solve it once — the
+Parts are solved independently, so two parts that share a subtree still solve it once - the
 digest cache is keyed on content, not on which part asked.
 
 To export one part, pass its `concrete` to [`toBinarySTL`](../api/export.md#tobinarystl).
@@ -176,7 +176,7 @@ To export one part, pass its `concrete` to [`toBinarySTL`](../api/export.md#tobi
 
 ### `a part needs at least one shape inside it`
 
-The part's body produced nothing — usually an `if` inside it that took no branch, or a `for`
+The part's body produced nothing - usually an `if` inside it that took no branch, or a `for`
 over an empty list. Move the condition outside the part.
 
 ### `a part cannot contain another part`
@@ -194,9 +194,9 @@ component "shell" { ... }                    // geometry only
 model "m" { part "shell" { shell { } } }     // the part lives here
 ```
 
-### `part "body" is 2D — extrude or revolve it before rendering`
+### `part "body" is 2D - extrude or revolve it before rendering`
 
-The part holds a cross-section. Extrude or revolve it first — see
+The part holds a cross-section. Extrude or revolve it first - see
 [2D ↔ 3D](conversions.md).
 
 ### A part inside an operation disappears
@@ -208,7 +208,7 @@ depends on whether the operation had anything else to work with:
 // ✗ fails: "translate" needs at least one shape inside it
 translate { offset = [0, 0, 10]  part "p" { box { size = [1, 1, 1] } } }
 
-// ✗ worse — renders, but part "p" is silently gone from the scene
+// ✗ worse - renders, but part "p" is silently gone from the scene
 translate {
   offset = [0, 0, 10]
   box { size = [1, 1, 1] }
@@ -220,10 +220,10 @@ part "p" { translate { offset = [0, 0, 10]  box { size = [1, 1, 1] } } }
 ```
 
 Nothing warns about the second case. If a part you declared is missing from the render,
-check that it is written directly in the [`model`](model.md) — or inside a `for` or `if` in
-one — and not nested inside a transform or a boolean.
+check that it is written directly in the [`model`](model.md) - or inside a `for` or `if` in
+one - and not nested inside a transform or a boolean.
 
 ### Two parts have the same name
 
 Nothing rejects it. Part names come from an expression, so a loop that computes the same
-label twice produces duplicates — include the loop index: `part "leg_${i}"`.
+label twice produces duplicates - include the loop index: `part "leg_${i}"`.