@fusion.dev/helix-docs 0.187.0 → 0.189.0

package/content/building-on-the-headless-tier.mdx

@@ -53,11 +53,11 @@ open.
 
 [//]: # (renders)
 
-**32 of the 99 headless families interpolate another family's tag**, across 22 distinct children.
+**34 of the 101 headless families interpolate another family's tag**, across 22 distinct children.
 
 | Family | Renders |
 |---|---|
-| `area-chart`, `bar-chart`, `copy-button`, `donut-chart`, `heatmap`, `isometric-heatmap`, `line-chart`, `scatter-chart` | `tooltip` |
+| `area-chart`, `bar-chart`, `copy-button`, `donut-chart`, `heatmap`, `line-chart`, `scatter-chart`, `spatial-heatmap`, `spatial-scatter-chart`, `spatial-surface-chart` | `tooltip` |
 | `breadcrumbs` | `breadcrumb` |
 | `chat` | `chat-message` |
 | `checkbox-group`, `table` | `checkbox` |
@@ -155,6 +155,48 @@ TypeScript declares custom elements this way. The interface merges from your
 source, and a generated file cannot name a class that is not in the same
 program.
 
+## Check your components with `helix component`
+
+`helix component` checks the components you write on Helix's base classes. Name
+the folders that hold them in `helix.json` at your project's root:
+
+```json
+{ "tiers": ["src/components"] }
+```
+
+Then run it:
+
+```sh
+helix component audit
+helix component check
+```
+
+`audit` prints each rule and what it found, and `check` prints nothing when
+there is nothing to report. Both exit 1 on a finding, and `--json` prints the
+findings as data. The rules check what your components document and write:
+
+| Rule | What it checks |
+|---|---|
+| `tier` | A component built on a headless one that renders children sets `tier`, so its children are yours and not Helix's |
+| `registered` | Every element a component's base renders is registered under the prefix it sets |
+| `composed` | A module that renders one of your elements, by its base or in its own template, imports the module that registers it |
+| `slots` | A `@slot` you document is one the Helix class under it takes, or one your template renders |
+| `exportparts` | A `::part()` written at your elements or at Helix's names a part that element publishes |
+| `words` | A component with `static words` declares its English defaults `@words`, and joins no word into a sentence outside the message |
+| `dispatched` | An event your component sends by name, with `new CustomEvent` or `new Event`, is documented with `@event` |
+| `parts` | A `@csspart` you document is rendered, and a `part` you render is documented |
+| `states` | A custom state you record is documented with `@cssstate`, and a documented one is recorded |
+| `hooks` | A `@cssproperty` you document is read, and one you read is documented |
+| `restated` | A part, a slot, or an event is declared once |
+| `reflected` | A property that reflects has no default, so a host carries no attribute nobody wrote |
+| `reflected-defaults` | A reflected property writes no attribute on upgrade that a server did not send |
+| `attribute-names` | A property that mirrors a platform attribute answers to the platform's spelling |
+| `constructed` | No class field reads the element's attributes in its initializer, where a parsed element has none yet |
+| `observers` | An observer built once is not torn down by a lifecycle that runs many times |
+| `leaks` | A listener on something the element does not own is removed when the element is |
+
+`--only parts,states` runs a few of them.
+
 ## What the headless tier handles for you
 
 ### Tree-shaking

package/content/charting.mdx

@@ -12,9 +12,11 @@ Helix has these chart families, and each one has its own API page:
 - `Line Chart`
 - `Area Chart`
 - `Scatter Chart`
+- `Spatial Scatter Chart`, drawn in three dimensions by `@fusion.dev/helix-plot`
+- `Spatial Surface Chart`, drawn in three dimensions by `@fusion.dev/helix-plot`
 - `Donut Chart`
 - `Heatmap`
-- `Isometric Heatmap`
+- `Spatial Heatmap`
 - `Sparkline`
 - `Trend`
 - `Legend`, which all of the charts share
@@ -38,9 +40,23 @@ Choose a chart by the question it answers.
   overlaps the series, and `Area Chart` adds them.
 - **Parts of one whole, at one moment.** `Donut Chart`.
 - **Whether two measures relate.** `Scatter Chart`, with one point per row.
+- **Where rows fall on three measures, and which gather together.** `Scatter
+  3D`, with one point per row in a box you can turn. Use it for data that has
+  three dimensions, such as clusters or embeddings. Its table and its flat
+  scatter carry the exact values.
+- **How one measure rises and falls over two others.** `Spatial Surface Chart`, with one
+  row per place on a grid, drawn as a surface you can turn. Use it for a measure
+  over two ranges, such as load by hour and by day. Its table carries the exact
+  values.
+
+The spatial charts and `Spatial Heatmap` draw themselves in 3D in SVG, which a
+server, a print, and a page without WebGL all show. Shift with an arrow turns
+the spatial charts' drawing. `@fusion.dev/helix-plot` draws all three with
+three.js instead, lit and in perspective, in a view you can drag round and
+zoom.
 - **How each day or check went.** `Heatmap`, for uptime, contributions, or
   activity.
-- **The same days, as a relief.** `Isometric Heatmap` reads the same table as
+- **The same days, as a relief.** `Spatial Heatmap` reads the same table as
   `Heatmap` and draws each reading as a prism as tall as its value. Use it where
   the overall shape matters more than any one exact value, such as a busy
   stretch in a year of commits. The tooltip and the table carry the exact

package/content/coding-agents.mdx

@@ -154,7 +154,7 @@ the file your client reads and keeps every other server in it:
 | `vscode` | `.vscode/mcp.json` |
 
 The server runs `npx @fusion.dev/helix-cli mcp`, which is the copy in your
-project. It has eight tools:
+project. It has nine tools:
 
 | Tool | What it returns |
 |---|---|
@@ -164,6 +164,7 @@ project. It has eight tools:
 | `helix_imports` | The import lines for a list of tags, and the closest tag to any unknown one |
 | `helix_tokens` | The semantic tokens, by a word in the name or description and by category |
 | `helix_check` | The findings `helix scan` reports for the files you name, or for a snippet before you write it |
+| `helix_check_page` | The findings the page diagnostics report for each address you name, opened headless, with what the library logged as the page ran |
 | `helix_audit_theme` | Every foreground and background pair a brand color derives to, with its ratio and target |
 | `helix_derive_theme` | The theme's CSS |