three-slicer 0.3.0 → 0.3.1

package/CHANGELOG.md

@@ -1,5 +1,45 @@
 # Changelog
 
+## 0.3.1 — 2026-09-16
+
+### Added
+
+- `three-slicer-viewer/settings` (and so `three-slicer/settings`) exports the kernel derivation's own fallbacks:
+  `FFF_FALLBACKS`, `SLA_FALLBACKS`, `AUTO_LINE_WIDTH`, `BED_FALLBACK`, `MACHINE_LIMITS`. Frozen; they are the values
+  `deriveKernelParams` / `deriveSlaParams` use when neither the settings map nor the schema gives one, and they are
+  deliberately not the schema defaults.
+- Theming: both shadow roots take their colours from 43 custom properties (`--vp-accent`, `--vp-dark-surface`,
+  `--vp-light-text`, …) a host can set on any ancestor. `VIEWER.md` ("Theming") lists them with their defaults.
+
+### Changed
+
+- `deriveKernelParams` with an empty or malformed `printable_area` now derives a 200 x 200 bed (the schema's own
+  default), not 256 x 256. Every viewer fallback already assumed 200; a well-formed value is unaffected.
+- `buildSegmentData(layers)` without a default line width falls back to 0.42 (the kernel's auto width), not 0.4.
+  Callers that pass one, as the viewer does, are unaffected.
+- One grey for "no colour to read": a blank filament slot, a stats swatch past the palette, an unparseable hex in
+  the toolpath palette and an unpainted facet (`UNPAINTED_COLOR`) are all `#888888` (were four different greys).
+- The toolpath legend (speed / fan / temperature views) falls back to the schema default for a value the settings
+  map holds but cannot parse, instead of literals that disagreed with it (support speed 35 vs 80, nozzle 210 vs 200).
+- The stylesheets carried 152 literal colours, many of them near-identical shades of one role; each group now uses
+  its most common member, so a few shades move slightly. Visible: the "advanced" badge is the info blue
+  (`#2b6cff`, was `#3673c3`), the "simple" badge the accent green, and the prime-tower card's number inputs are
+  light like every other sidebar input (they were styled for the dark viewport).
+- Vendor process presets now carry `support_type`, so applying one sets the support type it was authored with.
+
+### Fixed
+
+- Importing a project that places objects on more than one plate failed with "dropPlateResult is not defined"
+  and left every object on the selected plate (since 0.2.5). `test_3mf_project.mjs` now loads a two-plate project
+  through the model loader.
+- The Process card's Global|Plate toggle has the ↺ that drops the plate's whole override, like the other settings
+  cards; the viewer never passed it the handler.
+- Importing a project kept its filament colours in the viewer but not in the settings map, so a blank entry saved
+  back as blank and a list past 16 filaments saved whole.
+- `three-slicer@0.3.0` shipped a tool-state file under `types/.omc/`, and `three-slicer-viewer` would have shipped
+  one from `src/settings/.omc/`. Both `files` lists now end in `!**/.omc`, and `pack_check.sh` fails on any
+  dot-path in either tarball.
+
 ## 0.3.0 — 2026-09-08
 
 The viewer is its own package. Everything that displays — model loading, G-code parsing, the GPU toolpath
@@ -33,7 +73,7 @@ split followed is `packages/RELICENSE.md`.
 - The two packages publish as a **locked pair**: same version, and `three-slicer` pins `three-slicer-viewer`
   exactly (`test_version_lockstep.mjs`). A release goes through the root `Makefile` (`make publish`), which
   publishes the viewer first — the pin means `three-slicer@0.3.0` cannot be installed before it exists.
-- `packages-mit/` is mirrored to `github.com/kimgh06/three-slicer-viewer` (a `git subtree split`); the monorepo
+- `viewer-package/` is mirrored to `github.com/kimgh06/three-slicer-viewer` (a `git subtree split`); the monorepo
   stays the source of truth.
 
 ### Fixed

package/README.md

@@ -4,7 +4,7 @@ Browser/WASM 3D-printing slicer package derived from [OrcaSlicer](https://github
 
 The package is published as a single npm package, `three-slicer`, with subpath exports for the engine, viewer, components, worker, and extracted OrcaSlicer data.
 
-![A sliced Benchy in the viewer's Preview tab — organic tree supports, per-feature toolpath colors, dual layer-range slider, filament and print-time estimates](https://raw.githubusercontent.com/kimgh06/Web_Three_Slicer/main/web/viewer/public/usage.png)
+![A sliced Benchy in the viewer's Preview tab — organic tree supports, per-feature toolpath colors, dual layer-range slider, filament and print-time estimates](https://raw.githubusercontent.com/kimgh06/Three_Slicer/main/web/viewer/public/usage.png)
 
 ## Links
 
@@ -14,7 +14,7 @@ The package is published as a single npm package, `three-slicer`, with subpath e
   composition. Which code carries which licence, and why: [`PROVENANCE.md`](PROVENANCE.md).
 
 - Package: [npmjs.com/package/three-slicer](https://www.npmjs.com/package/three-slicer)
-- Source: [kimgh06/Web_Three_Slicer](https://github.com/kimgh06/Web_Three_Slicer)
+- Source: [kimgh06/Three_Slicer](https://github.com/kimgh06/Three_Slicer)
 - Demo: [slicer.kimgh06.com](https://slicer.kimgh06.com/)
 
 ## Start Here
@@ -25,7 +25,7 @@ reading whole; everything else is lookup.
 | Your case | Path | Copy this | Then read |
 | --- | --- | --- | --- |
 | "Just the numbers" — quotes, farms, automation. No UI, no React | **Headless** | [Quick Start: Headless Slicing](#quick-start-headless-slicing) | [engine/README](engine/README.md) (134 lines), params via [PARAMS.md](engine/PARAMS.md) as lookup |
-| A slicer inside your existing page | **Embed** | [Quick Start: React Viewer](#quick-start-react-viewer) | [viewer/README](../packages-mit/VIEWER.md) (330 lines — the props contracts live there) |
+| A slicer inside your existing page | **Embed** | [Quick Start: React Viewer](#quick-start-react-viewer) | [viewer/README](../viewer-package/VIEWER.md) (330 lines — the props contracts live there) |
 | The full slicer UI — viewport + settings panel | **Full UI** | [Full React Example](#full-react-example) | viewer/README + [components/README](components/README.md) |
 
 Whichever path: read [Before You Ship](#before-you-ship) before deploying — those traps return plausible
@@ -172,7 +172,7 @@ export default function App() {
 `position: relative` and a real height. In a plain static `<div>` it escapes to the page instead. There is no width
 or height prop.
 
-The viewer handles model loading, drag and drop, transform controls, multi-plate layout, worker slicing, GPU toolpath preview, and G-code export. Its keyboard and mouse bindings, the undo boundary, and what a host cannot drive are documented in [../packages-mit/VIEWER.md](../packages-mit/VIEWER.md). It supports STL, OBJ, 3MF (including the production extension used by Orca/Bambu/Prusa), AMF, and PLY out of the box; other formats such as STEP can be added with `registerLoader()`. A `.3mf` written by a slicer is treated as a project, not just geometry: its plate layout, project settings, and support/material painting are restored on import (where a facet carries both paint kinds, material paint wins and the dropped support paint is reported). Viewer and component styles are bundled into their Shadow DOM roots, so host app CSS does not need to import package CSS.
+The viewer handles model loading, drag and drop, transform controls, multi-plate layout, worker slicing, GPU toolpath preview, and G-code export. Its keyboard and mouse bindings, the undo boundary, and what a host cannot drive are documented in [../viewer-package/VIEWER.md](../viewer-package/VIEWER.md). It supports STL, OBJ, 3MF (including the production extension used by Orca/Bambu/Prusa), AMF, and PLY out of the box; other formats such as STEP can be added with `registerLoader()`. A `.3mf` written by a slicer is treated as a project, not just geometry: its plate layout, project settings, and support/material painting are restored on import (where a facet carries both paint kinds, material paint wins and the dropped support paint is reported). Viewer and component styles are bundled into their Shadow DOM roots, so host app CSS does not need to import package CSS.
 
 ## Quick Start: Settings Panel
 
@@ -277,7 +277,7 @@ Some of the connections are not imports, and knowing which is which explains mos
 | --- | --- | --- |
 | `wasm-core` → `engine` | `build.sh` (emscripten) commits its output into `engine/src/` | not an import — the golden byte-identical gate and the invariant suite verify kernel changes against the engine's output |
 | `data` → `engine`/`components`/`viewer` | `/data` subpath imports | the source of truth is `extract_all.py` over the upstream checkout |
-| `types` → `engine` | the generator **executes** `deriveKernelParams` (probing) and writes `engine/PARAMS.md` + `../packages-mit/src/settings/kernel_setting_keys.js` back into the engine | `test_kernel_params.mjs` is the staleness gate |
+| `types` → `engine` | the generator **executes** `deriveKernelParams` (probing) and writes `engine/PARAMS.md` + `../viewer-package/src/settings/kernel_setting_keys.js` back into the engine | `test_kernel_params.mjs` is the staleness gate |
 | `types` → `data` | `gen_settings_types.mjs` generates `settings-keys.d.ts` (976 keys) from the schema | run automatically by the build |
 | `viewer` ↔ `components` | **no direct link** | the host shares one settings map with both as props, and mounts `<SettingsPanel embedded/>` into the viewer's panel slots |
 | inside `viewer` | `core` (pure, node-runnable) ← `scene` (three/DOM) ← `actions` ← `ui` | `test_layers.mjs` enforces the boundary |
@@ -392,7 +392,7 @@ options as arrays of strings — the same shape [3MF Projects](#3mf-projects) us
 through the same serializer.
 
 The viewer adds the zip forms and a UI: the printer card's **Load** and **Save** read and write these files, and a
-save routes through [`onExport`](../packages-mit/VIEWER.md#taking-the-saves) like every other download.
+save routes through [`onExport`](../viewer-package/VIEWER.md#taking-the-saves) like every other download.
 
 ## Settings UI: Enable/Disable Rules
 
@@ -787,7 +787,7 @@ the layout by hand.
 
 ## Before You Ship
 
-The traps below were all hit while building the [integration demos](https://github.com/kimgh06/Web_Three_Slicer/tree/main/examples)
+The traps below were all hit while building the [integration demos](https://github.com/kimgh06/Three_Slicer/tree/main/examples)
 and the live landing embed — each one returns something plausible instead of an error, which is why they
 are listed **in the order they bite**, not by topic. The later a trap fires, the more it costs — and none of
 them fails a build or throws, so nothing surfaces them for you.
@@ -837,4 +837,4 @@ production while `npm run dev` passed. The no-argument form now emits a real wor
 
 ## License
 
-AGPL-3.0-or-later. This package is derived from OrcaSlicer. Source is available at [kimgh06/Web_Three_Slicer](https://github.com/kimgh06/Web_Three_Slicer). If you embed it in a web app, make sure your app complies with the AGPL network-use requirements, including offering source code to users where required.
+AGPL-3.0-or-later. This package is derived from OrcaSlicer. Source is available at [kimgh06/Three_Slicer](https://github.com/kimgh06/Three_Slicer). If you embed it in a web app, make sure your app complies with the AGPL network-use requirements, including offering source code to users where required.