altium-toolkit 1.4.16 → 1.4.17

package/docs/api.md

@@ -552,8 +552,18 @@ ids, layer roles, cutouts, and pad/via drill render state (`open`, `covered`,
 `PcbSvgRenderer.renderLayerSvgs()` uses the same semantic sidecar shape with
 `view.kind: 'layer'` and a layer-specific `layerSet`.
 
+Native PCB layer summaries collect source layer keys without constructing hit-test
+geometry. Interaction indexes resolve component ownership once per build, and
+hit tests normalize visibility filters once per query. These preparations are
+scoped to each invocation so edits to documents and filters remain visible.
+
 ## 3D Scene Data
 
+Copper scene detail excludes numeric non-copper region kinds (`KIND=1` polygon
+cutouts, outlines, and cavities) as well as explicit clearance flags. Authored
+region arcs carry a signed `sweepAngle` in normalized coordinates, preserving
+angle wrapping, major arcs, and traversal from either endpoint.
+
 ```js
 import {
     PcbScene3dBuilder,
@@ -582,6 +592,13 @@ import {
 The library intentionally does not create Three.js objects, canvases, controls,
 or event listeners.
 
+Native Altium scene construction indexes pad ownership once per build and
+prepares drilled-pad anchor candidates only when owner recovery needs them.
+Placement repair searches nearby authored-body positions before comparing
+identity metadata. These indexes preserve mounted-surface pad preference and
+source-order ties, and are rebuilt for every invocation so later document
+edits are visible.
+
 ## Read-only CLI Examples
 
 The `examples/` directory includes small Node.js scripts for common

package/docs/migration.md

@@ -6,9 +6,19 @@ SPDX-License-Identifier: CC-BY-SA-4.0
 # Migration from 1.1.41 to 1.2.0
 
 Version 1.2.0 adds the canonical ECAD toolkit API. Existing Altium
-exports are retained under `altium-toolkit/extensions`; the native
-`src/core` and `src/ui` implementations remain byte-identical to the
-pinned 1.1.41 source tree.
+exports are retained under `altium-toolkit/extensions`.
+
+Starting with 1.4.17, native implementations and assets are maintained:
+reviewed bug fixes and performance improvements may change their source and
+corrected behavior. Historical export signatures and public asset
+entrypoints and targets remain checked. The immutable 1.1.41 source tree and manifest
+remain provenance evidence, not a claim of current byte equality.
+
+The release gate retains every historical implementation path and
+compares every packed source file against a snapshot of the tested
+checkout, including new helpers and workers. Public contract and
+synthetic regression tests validate maintained behavior. See
+[testing](testing.md) for the complete release checks.
 
 The paged appendix maps every frozen export, static member, prototype
 member, public asset, and the native implementation tree:

package/docs/testing.md

@@ -11,7 +11,8 @@ streams. Do not add native customer files or provider-derived raw fixtures.
 When exercising source lookup, inject a fake fetcher/client and assert emitted
 entries, progress events, checkpoints, diagnostics, and OLE round trips.
 
-Run the complete suite:
+Run the complete suite from a Git checkout containing the historical release
+tags (`git fetch --tags` if needed):
 
 ```bash
 npm test
@@ -31,12 +32,23 @@ The strict feature check creates an isolated packed install and packs the
 currently installed CircuitJSON dependency beside the Altium candidate. This
 keeps the isolated contract gate aligned with the dependency declared by the
 active release instead of a stale version-specific fixture. It verifies all
-historical native source and extension contracts, checks the exact
-package/subpath layout, and runs the shared observable toolkit contract against
-the packed package.
+historical baseline provenance, extension signatures, and public asset paths.
+Native implementations and assets may evolve through tested fixes starting with 1.4.17; historical
+source and asset hashes are never rewritten to approve a candidate. The gate requires
+every historical implementation path, captures all current `src/` files before
+packing, and compares exact file inventories and bytes before importing the
+packed candidate. It rejects changed, missing, additional, or symlinked source,
+including new helpers. It also checks the exact package/subpath layout and runs
+the shared observable toolkit contract against the packed package. A final
+source comparison catches changes made during validation.
 
 The performance check is bound to the immutable 1.1.41 commit, source tree,
-and native-source manifest. It measures legacy and canonical projections of
+and native-source manifest. It verifies the complete local dependency graph of
+the measured historical parser and schematic renderer, checking each module's
+bytes before following its imports and re-exports. Computed dynamic imports
+are rejected because their full dependency graph cannot be verified statically.
+Source outside that baseline graph can evolve without changing the historical
+manifest. It measures legacy and canonical projections of
 the same synthetic inputs. Default canonical parsing must stay inside both a
 relative budget and a small envelope-construction allowance scaled by actual
 project document count. Direct async execution, metadata/full asset modes, and

package/package.json

@@ -1,6 +1,6 @@
 {
     "name": "altium-toolkit",
-    "version": "1.4.16",
+    "version": "1.4.17",
     "description": "Altium document parsing and non-interactive rendering utilities",
     "keywords": [
         "altium",
@@ -67,7 +67,7 @@
         "check:features": "node scripts/check-feature-preservation.mjs"
     },
     "dependencies": {
-        "circuitjson-toolkit": "^1.4.2",
+        "circuitjson-toolkit": "^1.4.3",
         "fflate": "^0.8.2"
     },
     "devDependencies": {