nurb 0.1.0__tar.gz

nurb-0.1.0/LICENSE

@@ -0,0 +1,110 @@
+# Functional Source License, Version 1.1, MIT Future License
+
+## Abbreviation
+
+FSL-1.1-MIT
+
+## Notice
+
+Copyright 2026 Ordinary Systems LLC
+
+## Terms and Conditions
+
+### Licensor ("We")
+
+The party offering the Software under these Terms and Conditions.
+
+### The Software
+
+The "Software" is each version of the software that we make available under
+these Terms and Conditions, as indicated by our inclusion of these Terms and
+Conditions with the Software.
+
+### License Grant
+
+Subject to your compliance with this License Grant and the Patents,
+Redistribution and Trademark clauses below, we hereby grant you the right to
+use, copy, modify, create derivative works, publicly perform, publicly display
+and redistribute the Software for any Permitted Purpose identified below.
+
+### Permitted Purpose
+
+A Permitted Purpose is any purpose other than a Competing Use. A Competing Use
+means making the Software available to others in a commercial product or
+service that:
+
+1. substitutes for the Software;
+
+2. substitutes for any other product or service we offer using the Software
+   that exists as of the date we make the Software available; or
+
+3. offers the same or substantially similar functionality as the Software.
+
+Permitted Purposes specifically include using the Software:
+
+1. for your internal use and access;
+
+2. for non-commercial education;
+
+3. for non-commercial research; and
+
+4. in connection with professional services that you provide to a licensee
+   using the Software in accordance with these Terms and Conditions.
+
+### Patents
+
+To the extent your use for a Permitted Purpose would necessarily infringe our
+patents, the license grant above includes a license under our patents. If you
+make a claim against any party that the Software infringes or contributes to
+the infringement of any patent, then your patent license to the Software ends
+immediately.
+
+### Redistribution
+
+The Terms and Conditions apply to all copies, modifications and derivatives of
+the Software.
+
+If you redistribute any copies, modifications or derivatives of the Software,
+you must include a copy of or a link to these Terms and Conditions and not
+remove any copyright notices provided in or with the Software.
+
+### Disclaimer
+
+THE SOFTWARE IS PROVIDED "AS IS" AND WITHOUT WARRANTIES OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING WITHOUT LIMITATION WARRANTIES OF FITNESS FOR A PARTICULAR
+PURPOSE, MERCHANTABILITY, TITLE OR NON-INFRINGEMENT.
+
+IN NO EVENT WILL WE HAVE ANY LIABILITY TO YOU ARISING OUT OF OR RELATED TO THE
+SOFTWARE, INCLUDING INDIRECT, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES,
+EVEN IF WE HAVE BEEN INFORMED OF THEIR POSSIBILITY IN ADVANCE.
+
+### Trademarks
+
+Except for displaying the License Details and identifying us as the origin of
+the Software, you have no right under these Terms and Conditions to use our
+trademarks, trade names, service marks or product names.
+
+## Grant of Future License
+
+We hereby irrevocably grant you an additional license to use the Software under
+the MIT license that is effective on the second anniversary of the date we make
+the Software available. On or after that date, you may use the Software under
+the MIT license, in which case the following will apply:
+
+Permission is hereby granted, free of charge, to any person obtaining a copy of
+this software and associated documentation files (the "Software"), to deal in
+the Software without restriction, including without limitation the rights to
+use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies
+of the Software, and to permit persons to whom the Software is furnished to do
+so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

nurb-0.1.0/PKG-INFO

@@ -0,0 +1,302 @@
+Metadata-Version: 2.4
+Name: nurb
+Version: 0.1.0
+Summary: Agentic CAD for 3D printing
+Keywords: cad,3d-printing,parametric,build123d,occt
+Author: Josh Pigford
+Author-email: Josh Pigford <josh@joshpigford.com>
+License-Expression: LicenseRef-FSL-1.1-MIT
+License-File: LICENSE
+Classifier: Development Status :: 3 - Alpha
+Classifier: Intended Audience :: Manufacturing
+Classifier: Topic :: Multimedia :: Graphics :: 3D Modeling
+Classifier: Programming Language :: Python :: 3.13
+Requires-Dist: build123d>=0.11.1
+Requires-Dist: trimesh>=4.12.2
+Requires-Dist: watchdog>=6.0.0
+Requires-Dist: websockets>=16.1.1
+Requires-Dist: playwright>=1.49 ; extra == 'render'
+Requires-Python: >=3.13
+Provides-Extra: render
+Description-Content-Type: text/markdown
+
+# nurb
+
+Agentic CAD for 3D printing.
+
+A part is a Python function. Its keyword defaults are its parameters. `nurb dev`
+watches your parts, rebuilds them on save, and pushes new geometry to a browser
+without moving your camera.
+
+Built on [build123d](https://build123d.readthedocs.io) (OCCT), so parts are real
+B-rep solids with working chamfers, fillets, and STEP export.
+
+## Try it
+
+```bash
+uv run nurb new dispenser
+uv run nurb dev            # http://127.0.0.1:7373, or the next free port
+```
+
+Edit `parts/dispenser.py` and watch it update.
+
+## A part
+
+```python
+from nurb import *
+
+@part
+def dispenser(width=80.0, height=120.0, wall=2.0, draft=False):
+    body = Box(width, height, wall)
+    if draft:
+        return body
+    bed = body.bounding_box().min.Z
+    keep = body.edges().filter_by(lambda e: e.bounding_box().min.Z > bed)
+    return polish(body, keep, 1.0)
+```
+
+`draft` is optional and passed by the runtime, not the caller. When it's true the
+part should skip its polish pass. `nurb dev` builds in draft by default: on this
+trivial part it's 18ms polished vs 1ms draft, and on a real one the saving is
+nearer 20%.
+
+## Commands
+
+```
+nurb new <name>     create parts/<name>.py and its card
+nurb dev            watch, rebuild, serve the viewer
+nurb build [part]   build once and report size
+nurb check [part]   run the printability rules
+nurb rules          print the design doctrine
+nurb card [part]    regenerate a card's AUTO block
+nurb verify [part]  run the doctrine's verification list
+nurb render [part]  write a PNG into build/
+nurb export [part]  write STL and STEP into build/, --formats for GLB
+nurb extract        find duplication across parts
+```
+
+A project is any directory with a `parts/` folder. There's no init step, and there's
+no such thing as being outside a project: `mkdir -p thing/parts && cd thing && nurb new
+clip` is the whole setup for a one-off.
+
+`nurb dev` serves one project, so two projects means two of them. It takes 7373 if that
+is free and walks up if it is not, printing where it landed, and the sidebar and the
+browser tab both carry the project name so two of them are not mistakable for each
+other.
+
+Names are deliberately boring. The primary user is a language model, and a model that
+has never seen this tool can guess `build`, `check` and `export`. It cannot guess a
+themed alias.
+
+## Why a long-lived process
+
+Importing build123d costs 45s cold and 2.3s warm, and that is the whole argument: the
+dev server pays it once instead of on every save.
+
+What a rebuild costs after that depends on the part. A simple one is 29ms to build and
+1ms to tessellate. The heaviest part in `examples/` is 401ms and 30ms. Draft mode is
+not the lever it looks like: chamfers are 23% of that build, not most of it.
+
+Tessellation used to be the larger half, at 620ms on that part, and almost none of it
+was geometry. `Shape.tessellate` reads its triangles with `for t in poly.Triangles()`,
+and OCP's iterator over that array costs 536ms where reading the same 7790 triangles by
+index costs 6.8ms. `builder._triangulate` does the latter and returns bit-identical
+vertices and faces. It is worth knowing before optimising the wrong thing.
+
+## Layout
+
+```
+parts/<name>.py     the part
+parts/<name>.md     its card: what it is, why, what not to retry
+system.py           optional: shared constants and geometry, importable from a part
+measurements.toml   optional: real-world dimensions with how they were obtained
+printer.toml        optional: which machine this project prints on
+build/              generated, gitignored
+```
+
+Cards are colocated with parts and share a basename. That's the whole link; a
+rename is `git mv` on two files.
+
+## Checks
+
+`nurb check` runs the printability rules against the solid rather than an exported
+mesh, so it sees real faces with exact areas and normals instead of triangles.
+
+```
+overhang          downward faces past 45 degrees, bridges told from cantilevers
+min_wall          thinnest section, ray cast corrected by an inscribed sphere
+sliver            faces too small to print as anything but a smear
+concave_cosmetic  polish laid into an inside corner
+bed_bevel         polish laid on the edges that meet the build plate
+stability         center of mass outside the footprint
+projection_ratio  reach over height, for a part cantilevered off a wall
+build_volume      does it fit the printer at all
+```
+
+`min_wall`'s ray is exact on flat parallel walls and measures the slant through a skewed
+one, so any chord thin enough to change the verdict is corrected by the largest sphere
+tangent at that point, computed against the solid with exact kernel distances. A sphere
+whose far contact is a graze rather than a wall is rejected by the same 0.3 cosine floor
+the ray's exit filter uses, which is what keeps a detent dimple's bowl from reading as a
+thin section of the web it is pressed into.
+
+The bed size belongs to the machine, not to a part, so it is not written on cards.
+A project picks a shipped profile once, in `printer.toml` at the root:
+
+```toml
+profile = "bambu_a1_mini"
+```
+
+Any check setting can be overridden in the same file, machine-wide. A card still wins
+for what its part has justified. `nurb check --printer prusa_mk4s` answers "does this
+fit that machine" without touching the file, and naming a profile that does not exist
+lists the ones that do.
+
+Every part carries what it has already justified on its card, so a known finding is
+silent and a new one is a regression:
+
+```toml
+[part]
+min_wall = 1.0
+
+[accepted]
+sliver = 6
+```
+
+It reports by default and takes `--strict` for CI, on the grounds that a warning which
+blocks work gets switched off. Findings also show up in `nurb dev`, with a pin on the
+geometry at each one.
+
+## Variants
+
+Some parts in a catalog are the same function flexed rather than new geometry. Those
+ship as variants on the card, not as copies of the file:
+
+```toml
+[variants.shelf_gridfinity_3x2.params]
+grid_x = 3
+bracket_count = 6
+
+[variants.shelf_gridfinity_3x2.accepted]
+sliver = 26
+```
+
+`build`, `check`, `card` and `export` all walk a part's variants the same way they walk
+its default, so a variant gets its own STL, its own baselines and its own line in the
+card's generated block. Four of the sixteen parts in `examples/notch` are variants; the
+alternative was four near-copies of two files, free to drift.
+
+## For an agent
+
+The doctrine lives in the package and prints with `nurb rules`: printability, load paths,
+the polish pass, the kernel traps, and what to verify. `SKILL.md` and `AGENTS.md` are ten
+lines each pointing at it, so there is one copy and it cannot drift.
+
+A part explains itself in a card next to it, same basename. Most of it is written by
+hand, including a `## Don't` section that records what was tried and rejected, which is
+the only place that information exists. One fenced block is generated:
+
+```
+nurb card
+```
+
+That block holds what only a build can tell you: bounding box, volume, solid count,
+sliver count against the accepted baseline, projection ratio, check verdict. It carries
+no timestamp, so regenerating it on unchanged geometry produces no diff and a stale card
+shows up in `git diff`. It deliberately does not repeat the parameters, because the
+signature is the parameters and copying them would be the drift the contract forbids.
+
+Dimensions an agent cannot derive go in `measurements.toml` with how they were obtained:
+
+```toml
+[bracket_pitch]
+value = 25.16
+unit = "mm"
+how = "on-center spacing across a run of brackets, measured on the wall"
+```
+
+```python
+from nurb import measured
+pitch = measured("bracket_pitch")
+```
+
+Asking for something that isn't there raises and says so. That failure is the point: a
+guessed dimension produces a part that builds, checks clean, and prints.
+
+`nurb render <part>` writes `build/<part>.png` by screenshotting the viewer, so the image
+is what a human would see. It needs the optional extra, which is the only part of nurb
+that wants a browser:
+
+```
+uv sync --extra render && uv run playwright install chromium
+```
+
+## Tests
+
+```
+uv run pytest
+```
+
+The parts in `examples/` are part of the suite, asserted against the dimensions and
+baselines their catalog cards recorded in Fusion. `tests/test_notch_fit.py` is the
+hanging interface: every channel floor on exact pitch, at full span, one per bracket and
+no more, for every shipped configuration. Its numbers are literals rather than imports
+from the part's own constants, because a fit test that reads the same constant the part
+built from agrees with the part however wrong the constant is.
+
+## The viewer is the configurator
+
+A part's parameters were always introspectable, so the sliders come from the signature
+and nothing else. The `stl` and `step` buttons build the part at whatever the sliders
+are holding, at full polish whatever the preview economy, and hand back the file: what
+is on screen is what lands in the slicer. Point somebody at your `nurb dev` and they
+can configure and download a part without touching Python.
+
+## Not built yet
+
+- A hosted configurator. `nurb dev` already is one for anybody who can reach it, but
+  publishing without a running kernel is a different problem: MakerWorld's customizer
+  runs OpenSCAD, which build123d does not transpile to.
+- Measurement tools in the viewer. The section view shows an interior; it does not
+  yet measure it.
+- `min_wall` probes sample faces, so a pinch nothing lands near is still missed. A
+  clean result means "no thin walls found", not "no thin walls".
+
+## Debugging the viewer
+
+`window.__nurb` exposes `{ THREE, scene, camera, controls, mesh, ready }`.
+
+The URL takes `?part=<name>` to open a part, `?view=iso|front|back|left|right|top` to
+frame it deterministically, and `?bare` to hide the chrome. `nurb render` drives exactly
+that, and waits on `ready`.
+
+three.js is vendored in `src/nurb/vendor/three`, so the viewer needs no network. See the
+README beside it before changing versions: the import graph has grown since r169 and the
+files it added fail as a blank canvas rather than as an error.
+
+## License
+
+[FSL-1.1-MIT](LICENSE). Source-available for any purpose except building a competing
+product, and converts to plain MIT two years after each release.
+
+Copyright 2026 Ordinary Systems LLC.
+
+### Third-party notices
+
+nurb uses **Open CASCADE Technology** (OCCT) for all B-rep geometry, reached through
+[build123d](https://github.com/gumyr/build123d) (Apache-2.0) and the `OCP` bindings
+(Apache-2.0). OCCT is licensed under
+[LGPL-2.1 with an additional exception](https://dev.opencascade.org/resources/licensing).
+
+nurb does not redistribute OCCT. It is installed separately as a dependency, and
+dynamically linked at runtime. If you ever bundle nurb into a single-file
+distribution that embeds the OCCT binaries, ship a copy of the OCCT license with it
+and keep the library replaceable, per LGPL.
+
+nurb **does** redistribute [three.js](https://threejs.org) r169 (MIT), vendored in
+`src/nurb/vendor/three` so the viewer works without a network. Its `LICENSE` ships
+beside it and the `@license` header stays on the build file, which is what MIT asks for.
+
+Other dependencies: trimesh (MIT), watchdog (Apache-2.0), websockets (BSD-3-Clause),
+numpy (BSD-3-Clause). Optional, for `nurb render` only: playwright (Apache-2.0), which
+downloads its own browser build.

nurb-0.1.0/README.md

@@ -0,0 +1,280 @@
+# nurb
+
+Agentic CAD for 3D printing.
+
+A part is a Python function. Its keyword defaults are its parameters. `nurb dev`
+watches your parts, rebuilds them on save, and pushes new geometry to a browser
+without moving your camera.
+
+Built on [build123d](https://build123d.readthedocs.io) (OCCT), so parts are real
+B-rep solids with working chamfers, fillets, and STEP export.
+
+## Try it
+
+```bash
+uv run nurb new dispenser
+uv run nurb dev            # http://127.0.0.1:7373, or the next free port
+```
+
+Edit `parts/dispenser.py` and watch it update.
+
+## A part
+
+```python
+from nurb import *
+
+@part
+def dispenser(width=80.0, height=120.0, wall=2.0, draft=False):
+    body = Box(width, height, wall)
+    if draft:
+        return body
+    bed = body.bounding_box().min.Z
+    keep = body.edges().filter_by(lambda e: e.bounding_box().min.Z > bed)
+    return polish(body, keep, 1.0)
+```
+
+`draft` is optional and passed by the runtime, not the caller. When it's true the
+part should skip its polish pass. `nurb dev` builds in draft by default: on this
+trivial part it's 18ms polished vs 1ms draft, and on a real one the saving is
+nearer 20%.
+
+## Commands
+
+```
+nurb new <name>     create parts/<name>.py and its card
+nurb dev            watch, rebuild, serve the viewer
+nurb build [part]   build once and report size
+nurb check [part]   run the printability rules
+nurb rules          print the design doctrine
+nurb card [part]    regenerate a card's AUTO block
+nurb verify [part]  run the doctrine's verification list
+nurb render [part]  write a PNG into build/
+nurb export [part]  write STL and STEP into build/, --formats for GLB
+nurb extract        find duplication across parts
+```
+
+A project is any directory with a `parts/` folder. There's no init step, and there's
+no such thing as being outside a project: `mkdir -p thing/parts && cd thing && nurb new
+clip` is the whole setup for a one-off.
+
+`nurb dev` serves one project, so two projects means two of them. It takes 7373 if that
+is free and walks up if it is not, printing where it landed, and the sidebar and the
+browser tab both carry the project name so two of them are not mistakable for each
+other.
+
+Names are deliberately boring. The primary user is a language model, and a model that
+has never seen this tool can guess `build`, `check` and `export`. It cannot guess a
+themed alias.
+
+## Why a long-lived process
+
+Importing build123d costs 45s cold and 2.3s warm, and that is the whole argument: the
+dev server pays it once instead of on every save.
+
+What a rebuild costs after that depends on the part. A simple one is 29ms to build and
+1ms to tessellate. The heaviest part in `examples/` is 401ms and 30ms. Draft mode is
+not the lever it looks like: chamfers are 23% of that build, not most of it.
+
+Tessellation used to be the larger half, at 620ms on that part, and almost none of it
+was geometry. `Shape.tessellate` reads its triangles with `for t in poly.Triangles()`,
+and OCP's iterator over that array costs 536ms where reading the same 7790 triangles by
+index costs 6.8ms. `builder._triangulate` does the latter and returns bit-identical
+vertices and faces. It is worth knowing before optimising the wrong thing.
+
+## Layout
+
+```
+parts/<name>.py     the part
+parts/<name>.md     its card: what it is, why, what not to retry
+system.py           optional: shared constants and geometry, importable from a part
+measurements.toml   optional: real-world dimensions with how they were obtained
+printer.toml        optional: which machine this project prints on
+build/              generated, gitignored
+```
+
+Cards are colocated with parts and share a basename. That's the whole link; a
+rename is `git mv` on two files.
+
+## Checks
+
+`nurb check` runs the printability rules against the solid rather than an exported
+mesh, so it sees real faces with exact areas and normals instead of triangles.
+
+```
+overhang          downward faces past 45 degrees, bridges told from cantilevers
+min_wall          thinnest section, ray cast corrected by an inscribed sphere
+sliver            faces too small to print as anything but a smear
+concave_cosmetic  polish laid into an inside corner
+bed_bevel         polish laid on the edges that meet the build plate
+stability         center of mass outside the footprint
+projection_ratio  reach over height, for a part cantilevered off a wall
+build_volume      does it fit the printer at all
+```
+
+`min_wall`'s ray is exact on flat parallel walls and measures the slant through a skewed
+one, so any chord thin enough to change the verdict is corrected by the largest sphere
+tangent at that point, computed against the solid with exact kernel distances. A sphere
+whose far contact is a graze rather than a wall is rejected by the same 0.3 cosine floor
+the ray's exit filter uses, which is what keeps a detent dimple's bowl from reading as a
+thin section of the web it is pressed into.
+
+The bed size belongs to the machine, not to a part, so it is not written on cards.
+A project picks a shipped profile once, in `printer.toml` at the root:
+
+```toml
+profile = "bambu_a1_mini"
+```
+
+Any check setting can be overridden in the same file, machine-wide. A card still wins
+for what its part has justified. `nurb check --printer prusa_mk4s` answers "does this
+fit that machine" without touching the file, and naming a profile that does not exist
+lists the ones that do.
+
+Every part carries what it has already justified on its card, so a known finding is
+silent and a new one is a regression:
+
+```toml
+[part]
+min_wall = 1.0
+
+[accepted]
+sliver = 6
+```
+
+It reports by default and takes `--strict` for CI, on the grounds that a warning which
+blocks work gets switched off. Findings also show up in `nurb dev`, with a pin on the
+geometry at each one.
+
+## Variants
+
+Some parts in a catalog are the same function flexed rather than new geometry. Those
+ship as variants on the card, not as copies of the file:
+
+```toml
+[variants.shelf_gridfinity_3x2.params]
+grid_x = 3
+bracket_count = 6
+
+[variants.shelf_gridfinity_3x2.accepted]
+sliver = 26
+```
+
+`build`, `check`, `card` and `export` all walk a part's variants the same way they walk
+its default, so a variant gets its own STL, its own baselines and its own line in the
+card's generated block. Four of the sixteen parts in `examples/notch` are variants; the
+alternative was four near-copies of two files, free to drift.
+
+## For an agent
+
+The doctrine lives in the package and prints with `nurb rules`: printability, load paths,
+the polish pass, the kernel traps, and what to verify. `SKILL.md` and `AGENTS.md` are ten
+lines each pointing at it, so there is one copy and it cannot drift.
+
+A part explains itself in a card next to it, same basename. Most of it is written by
+hand, including a `## Don't` section that records what was tried and rejected, which is
+the only place that information exists. One fenced block is generated:
+
+```
+nurb card
+```
+
+That block holds what only a build can tell you: bounding box, volume, solid count,
+sliver count against the accepted baseline, projection ratio, check verdict. It carries
+no timestamp, so regenerating it on unchanged geometry produces no diff and a stale card
+shows up in `git diff`. It deliberately does not repeat the parameters, because the
+signature is the parameters and copying them would be the drift the contract forbids.
+
+Dimensions an agent cannot derive go in `measurements.toml` with how they were obtained:
+
+```toml
+[bracket_pitch]
+value = 25.16
+unit = "mm"
+how = "on-center spacing across a run of brackets, measured on the wall"
+```
+
+```python
+from nurb import measured
+pitch = measured("bracket_pitch")
+```
+
+Asking for something that isn't there raises and says so. That failure is the point: a
+guessed dimension produces a part that builds, checks clean, and prints.
+
+`nurb render <part>` writes `build/<part>.png` by screenshotting the viewer, so the image
+is what a human would see. It needs the optional extra, which is the only part of nurb
+that wants a browser:
+
+```
+uv sync --extra render && uv run playwright install chromium
+```
+
+## Tests
+
+```
+uv run pytest
+```
+
+The parts in `examples/` are part of the suite, asserted against the dimensions and
+baselines their catalog cards recorded in Fusion. `tests/test_notch_fit.py` is the
+hanging interface: every channel floor on exact pitch, at full span, one per bracket and
+no more, for every shipped configuration. Its numbers are literals rather than imports
+from the part's own constants, because a fit test that reads the same constant the part
+built from agrees with the part however wrong the constant is.
+
+## The viewer is the configurator
+
+A part's parameters were always introspectable, so the sliders come from the signature
+and nothing else. The `stl` and `step` buttons build the part at whatever the sliders
+are holding, at full polish whatever the preview economy, and hand back the file: what
+is on screen is what lands in the slicer. Point somebody at your `nurb dev` and they
+can configure and download a part without touching Python.
+
+## Not built yet
+
+- A hosted configurator. `nurb dev` already is one for anybody who can reach it, but
+  publishing without a running kernel is a different problem: MakerWorld's customizer
+  runs OpenSCAD, which build123d does not transpile to.
+- Measurement tools in the viewer. The section view shows an interior; it does not
+  yet measure it.
+- `min_wall` probes sample faces, so a pinch nothing lands near is still missed. A
+  clean result means "no thin walls found", not "no thin walls".
+
+## Debugging the viewer
+
+`window.__nurb` exposes `{ THREE, scene, camera, controls, mesh, ready }`.
+
+The URL takes `?part=<name>` to open a part, `?view=iso|front|back|left|right|top` to
+frame it deterministically, and `?bare` to hide the chrome. `nurb render` drives exactly
+that, and waits on `ready`.
+
+three.js is vendored in `src/nurb/vendor/three`, so the viewer needs no network. See the
+README beside it before changing versions: the import graph has grown since r169 and the
+files it added fail as a blank canvas rather than as an error.
+
+## License
+
+[FSL-1.1-MIT](LICENSE). Source-available for any purpose except building a competing
+product, and converts to plain MIT two years after each release.
+
+Copyright 2026 Ordinary Systems LLC.
+
+### Third-party notices
+
+nurb uses **Open CASCADE Technology** (OCCT) for all B-rep geometry, reached through
+[build123d](https://github.com/gumyr/build123d) (Apache-2.0) and the `OCP` bindings
+(Apache-2.0). OCCT is licensed under
+[LGPL-2.1 with an additional exception](https://dev.opencascade.org/resources/licensing).
+
+nurb does not redistribute OCCT. It is installed separately as a dependency, and
+dynamically linked at runtime. If you ever bundle nurb into a single-file
+distribution that embeds the OCCT binaries, ship a copy of the OCCT license with it
+and keep the library replaceable, per LGPL.
+
+nurb **does** redistribute [three.js](https://threejs.org) r169 (MIT), vendored in
+`src/nurb/vendor/three` so the viewer works without a network. Its `LICENSE` ships
+beside it and the `@license` header stays on the build file, which is what MIT asks for.
+
+Other dependencies: trimesh (MIT), watchdog (Apache-2.0), websockets (BSD-3-Clause),
+numpy (BSD-3-Clause). Optional, for `nurb render` only: playwright (Apache-2.0), which
+downloads its own browser build.