@photivra/engine 1.0.0 → 1.0.1

package/AGENTS.md

@@ -44,7 +44,7 @@ Treat this repository as a complete, standalone open-source scientific/business-
 
 - Scientific equations and behavior are defined by implementation plus tests; documentation must agree with them.
 - Public API shape and semantics are defined by exported TypeScript contracts, tests, and `docs/API_STYLE.md`.
-- Root engine compatibility is versioned by `ENGINE_API_VERSION`; the composed `simulatePocCamera()` request/response contract is separately versioned by `POC_SIMULATION_API_VERSION`. Never conflate either with the npm package version.
+- Root engine compatibility is versioned by `ENGINE_API_VERSION`; the composed `simulatePocCamera()` request/response contract is separately versioned by `POC_SIMULATION_API_VERSION`. From 1.0.1, ENGINE_API_VERSION must equal the npm package version; the POC contract stays independent.
 - If documentation, tests, and implementation disagree, do not guess. Determine the intended contract, fix the stale source, and add a regression test when behavior is involved.
 - UI or downstream clients are never authoritative sources for camera science.
 
@@ -418,7 +418,7 @@ Backward compatibility matters.
 - Prefer typed/config-object inputs for multi-parameter functions.
 - Follow the conventions in `docs/API_STYLE.md`.
 - Keep result/provenance structures consistent across modules.
-- Keep `ENGINE_API_VERSION`, `POC_SIMULATION_API_VERSION`, package version, and any schema version semantically distinct.
+- Keep `ENGINE_API_VERSION` aligned with the package version; keep `POC_SIMULATION_API_VERSION` and schema/model versions independent.
 - Runtime parsers must fail closed on unknown enum/string values; TypeScript unions are not validation.
 - Do not silently reinterpret an existing field or unit.
 - If behavior must change, add regression tests and document compatibility impact.
@@ -576,7 +576,7 @@ Any further foundation composition still requires an explicit `POC_SIMULATION_AP
 - Preserve full destination-to-source Jacobians, compatible-domain groups, resampler identity, prefilter requirements and valid-source masks/joint crops. Invalid support remains unavailable.
 - Corrections warp already-sampled blur/noise; gain changes downstream signal/variance without rewriting photons. RAW metadata intent, camera mandatory settings and educational reference bypass are separate states.
 - The bounded RGB executor accepts reconstructed-linear geometry/CA followed by gain only. Reject incompatible-domain or geometry-across-gain execution rather than reorder it. Production #111/#112 require their own explicit composition.
-- Reconcile root API versions against other pending API branches before merge; schemas and package/POC versions remain independent.
+- Reconcile root API versions against other pending API branches before merge; the root API and package versions stay aligned while schemas and POC versions remain independent.
 ### Authoritative linear capture container
 
 - #15A `SimulatedCapture` is a standalone immutable data commitment, not a radiance generator, virtual-camera color transform, quantizer, file serializer or production-stage activation.

package/CHANGELOG.md

@@ -1,5 +1,10 @@
 # Changelog
 
+## 1.0.1 candidate — publication pending
+
+- Expand Node support to maintained 22/24 LTS plus 26 Current, with patched-major CI and the existing 22.13 minimum job, reviewed lifecycle windows and updated tooling guidance. Keep Node 24 build/typings baseline.
+- Align the npm package and `ENGINE_API_VERSION` at 1.0.1 and enforce equality in source metadata, generated references and isolated packed consumers. Schema/model/POC/plan versions and scientific calculations are unchanged. New capture/plan creator identities and hashes can differ; archived records and acceptance artifacts retain their original versions. See `docs/RELEASE_1_0_1.md`.
+
 ## 1.0.0 candidate — publication pending owner tag
 
 - Prepare the stable public distribution after all 32 V1 feature/science items and defect #178 are reviewed and merged. Package/lock/citation become 1.0.0; root contract 0.116.0 and every independent model/schema/POC/plan identity remain unchanged. No scientific arithmetic, seed, fixture hash, exported signature or accepted execution envelope changes.

package/CITATION.cff

@@ -9,7 +9,7 @@ abstract: "An open TypeScript engine for the science and mathematics of photogra
 repository-code: "https://github.com/photivra/photivra"
 url: "https://photivra.com"
 license: "Apache-2.0"
-version: "1.0.0"
+version: "1.0.1"
 keywords:
   - photography
   - camera optics

package/CONTRIBUTING.md

@@ -4,7 +4,7 @@ Contributions are welcome when they preserve scientific integrity, source proven
 
 ## Development setup
 
-Node.js 22.13 or newer is required for the repository's development/tooling workflow. The reproducible npm path is:
+Use a supported Node.js release: maintained 22 (minimum 22.13), maintained 24, or 26 Current. Prefer patched Node 24 for development/build tooling. The reproducible npm path is:
 
 ```sh
 npm ci
@@ -14,7 +14,7 @@ npm run build
 npm run pack:check
 ```
 
-CI verifies maintained Node.js 22 (including minimum 22.13) and 24; prefer patched Node 24 under [the runtime policy](NODE_SUPPORT.md). For release preparation also run `npm run docs:check` and `npm run release:consumer-check` after build. The generated API reference must match root exports; regenerate with `node scripts/generate-api-reference.mjs` when public contracts change.
+CI verifies maintained Node.js 22 (including minimum 22.13), 24, and Node.js 26 Current; prefer patched Node 24 under [the runtime policy](NODE_SUPPORT.md). See [1.0.1 migration and release preparation](docs/RELEASE_1_0_1.md). For release preparation also run `npm run docs:check` and `npm run release:consumer-check` after build. The generated API reference must match root exports; regenerate with `node scripts/generate-api-reference.mjs` when public contracts change.
 
 ## Before submitting
 
@@ -24,7 +24,7 @@ CI verifies maintained Node.js 22 (including minimum 22.13) and 24; prefer patch
 - Add meaningful analytical/regression tests.
 - Update concise documentation when behavior, assumptions, limitations, schemas, version surfaces, or public APIs change.
 - Preserve the browser-safe published-package boundary; Node-only transport code is repository-only contributor tooling and must not become a public package export.
-- Keep npm/package version, `ENGINE_API_VERSION`, `POC_SIMULATION_API_VERSION`, and schema-specific versions distinct.
+- Keep npm/package version and `ENGINE_API_VERSION` equal; keep `POC_SIMULATION_API_VERSION` and schema/model versions independent.
 - For sensor/capture work, preserve native coordinate conventions, active-capture vs output-crop separation, optical-axis offsets, and independent X/Y sampling.
 - For provenance/calibration work, keep evidence origin separate from reuse rights and never treat geometric sample pitch as photon-collection area.
 - Do not submit copied or adapted third-party code/data unless its license and provenance are explicitly compatible and recorded.

package/NODE_SUPPORT.md

@@ -2,9 +2,9 @@
 
 Adopted: 2026-09-26. Applies to every Node.js repository in the Photivra organization, including contributor tooling, CI, build/deployment tooling, and supported Node.js execution environments. It does not change browser support or the browser-safe engine boundary.
 
-## Maintained LTS only
+## Maintained LTS plus Current
 
-"Actively maintained LTS" means an official Node.js release line in either **Active LTS** or **Maintenance LTS**, before its upstream end-of-life date. Current, prerelease/nightly, end-of-life, and commercial extended-support-only releases are not supported.
+"Actively maintained LTS" means an official Node.js release line in either **Active LTS** or **Maintenance LTS**, before its upstream end-of-life date. Starting with the 1.0.1 candidate, this repository supports all upstream-supported Active/Maintenance LTS lines plus the official Current release line. Prerelease/nightly, end-of-life, and commercial extended-support-only releases are not supported.
 
 Use the official lifecycle, not "latest", a version-number parity rule, or an open-ended minimum version as evidence of support:
 
@@ -12,26 +12,26 @@ Use the official lifecycle, not "latest", a version-number parity rule, or an op
 - https://github.com/nodejs/Release
 - https://github.com/nodejs/Release/blob/main/schedule.json
 
-As reverified against the official schedule on 2026-10-02 (original policy review 2026-09-26), Node 24 is Active LTS and Node 22 is Maintenance LTS. Node 26 is Current and is not eligible yet. Future dates must be reverified; entering LTS makes a line eligible for review, not automatically supported by every repository.
+As reverified against the official schedule on 2026-10-02 (original policy review 2026-09-26), Node 24 is Active LTS and Node 22 is Maintenance LTS. Node 26 is Current and is included in the support set. This is a dated snapshot: future lines must be reviewed and tested as the official lifecycle changes. Node 26 remains supported when it enters LTS, with its runtime LTS marker required from that date.
 
 ## Repository baselines
 
-An eligible upstream line is not an untested repository compatibility claim. Each repository must explicitly record and test its supported subset. Prefer the newest qualified Active LTS line for normal development and builds; retain a qualified Maintenance LTS line where compatibility is already supported.
+An eligible upstream line is not an untested repository compatibility claim. This repository must explicitly record and test every line covered by the maintained-LTS-plus-Current policy. Prefer the newest qualified Active LTS line for normal development and builds; retain a qualified Maintenance LTS line where compatibility is already supported.
 
-This repository preserves its existing Node 22 and Node 24 CI coverage, including the Node 22.13.0 minimum-version regression job. The normal tooling baseline and pinned `@types/node` major remain **24**. Use current patched releases for ordinary development/deployment; a historical minimum-version regression job is not a deployment recommendation.
+This repository tests Node 22, 24 and 26, including current patched releases of each line and the Node 22.13.0 minimum-version regression job. The normal tooling baseline and pinned `@types/node` major remain **24**. Use current patched releases for ordinary development/deployment; a historical minimum-version regression job is not a deployment recommendation.
 
-Node 22-compatible code must not assume Node 24-only APIs merely because contributor tooling uses Node 24 typings. Keep the Node 22 runtime tests and the public browser-safe package boundary. A broad existing `engines.node` range is a compatibility hint, not permission to claim support for Current or EOL lines. Any manifest-range change must update its lockfile and follow package compatibility/release review; this policy does not rewrite already-published packages.
+Node 22-compatible code must not assume Node 24-only APIs merely because contributor tooling uses Node 24 typings. Keep the Node 22 runtime tests and the public browser-safe package boundary. A broad existing `engines.node` range is a compatibility hint, not evidence of support for untested or EOL lines. Any manifest-range change must update its lockfile and follow package compatibility/release review; this policy does not rewrite already-published packages.
 
 ## CI and dependency enforcement
 
-`.github/node-lts-policy.mjs` checks the actual Node build's LTS marker, this repository's approved major set, a reviewed upstream LTS date window, and the approved pinned typings major before dependency installation. `.github/test-node-lts-policy.mjs` covers acceptance and rejection boundaries. Both run in existing CI jobs; no additional CI matrix or service is introduced.
+`.github/node-lts-policy.mjs` checks the actual Node build's LTS marker, this repository's approved major set, reviewed upstream LTS and Current date windows, and the approved pinned typings major before dependency installation. `.github/test-node-lts-policy.mjs` covers acceptance and rejection boundaries. Both run before dependency installation in every verification matrix job.
 
-The lifecycle snapshot is intentionally local and reviewed, not fetched from the network during ordinary CI. It uses UTC dates and fails closed on the recorded end-of-life date. Reverify the official schedule before changing the snapshot, before a baseline/release decision, and during regular dependency maintenance. Do not extend an expired window or add a Current line merely to pass CI.
+The lifecycle snapshot is intentionally local and reviewed, not fetched from the network during ordinary CI. It uses UTC dates and fails closed on the recorded end-of-life date. Reverify the official schedule before changing the snapshot, before a baseline/release decision, and during regular dependency maintenance. Do not extend an expired window or admit an unreviewed line merely to pass CI. The Current window ends when the line enters LTS; the runtime must then carry an LTS marker. A new Current line requires a coordinated snapshot and matrix review.
 
 Routine minor/patch updates within an approved major may follow normal green-PR rules. Do not auto-merge a Node runtime, Node image, or `@types/node` major upgrade independently. Where Dependabot is configured, keep Node typings major upgrades out of its routine update queue while allowing supported-major updates.
 
 ## Lifecycle changes
 
-Add a newly eligible LTS line through one coordinated review of the support policy/guard, CI, local version files, build environments, typings, manifest/lockfile compatibility, and tests. Update only files that exist and are relevant; do not introduce a new runtime or infrastructure merely for uniformity. Remove a line from the support set and CI before upstream EOL, documenting downstream compatibility implications. Never silently raise a library's minimum runtime or advertise an untested line.
+Add a newly supported LTS or Current line through one coordinated review of the support policy/guard, CI, local version files, build environments, typings, manifest/lockfile compatibility, and tests. Update only files that exist and are relevant; do not introduce a new runtime or infrastructure merely for uniformity. Remove a line from the support set and CI before upstream EOL, documenting downstream compatibility implications. Never silently raise a library's minimum runtime or advertise an untested line.
 
 All existing scientific, security, provenance, regression, artifact, and release gates remain in force. This rule does not authorize npm publication, tags, public release, or a default runtime-major upgrade.

package/README.md

@@ -17,10 +17,10 @@ The standalone [SDR rendering foundation](https://github.com/Photivra/photivra/b
 
 ## Quick start
 
-After owner publication, install the ESM package below. During candidate review, use the verified tarball from the [release guide](https://github.com/Photivra/photivra/blob/main/docs/RELEASE_1_0.md):
+After owner publication, install the ESM package below. During candidate review, use the verified tarball from the [release guide](https://github.com/Photivra/photivra/blob/main/docs/RELEASE_1_0_1.md):
 
 ```sh
-npm install @photivra/engine@1.0.0
+npm install @photivra/engine@1.0.1
 ```
 
 Calculate horizontal field of view for a 36 mm sensor dimension and 50 mm focal length:
@@ -37,7 +37,7 @@ console.log(horizontal.value.degrees);
 console.log(horizontal.provenance);
 ```
 
-Start with the [Developer Guide](https://github.com/Photivra/photivra/blob/main/docs/DEVELOPERS.md), then use the [Usage Guide](https://github.com/Photivra/photivra/blob/main/docs/USAGE.md) and [export-derived API reference](https://github.com/Photivra/photivra/blob/main/docs/API_REFERENCE.md). These documents describe the 1.0.0 candidate; installation by version becomes available only after owner publication.
+Start with the [Developer Guide](https://github.com/Photivra/photivra/blob/main/docs/DEVELOPERS.md), then use the [Usage Guide](https://github.com/Photivra/photivra/blob/main/docs/USAGE.md) and [export-derived API reference](https://github.com/Photivra/photivra/blob/main/docs/API_REFERENCE.md). These documents describe the 1.0.1 candidate. The published 1.0.0 release remains available; installation of 1.0.1 becomes available after owner publication.
 
 ## Documentation
 
@@ -265,13 +265,13 @@ The calling application can then use those results while keeping the underlying
 
 ## Status
 
-- Repository package version: `1.0.0` (release candidate; publication is separate)
-- Engine API contract: `0.116.0`
+- Repository package version: `1.0.1` (release candidate; publication is separate)
+- Engine API contract: `1.0.1`
 - Versioned generic tier reference assets: [GENERIC_TIER_PRESETS.md](https://github.com/Photivra/photivra/blob/main/docs/GENERIC_TIER_PRESETS.md).
 - Composed POC simulation API contract: `0.20.0`
 - Stability: 1.0 root-package compatibility policy; bounded scientific models and independent POC contract
 
-Package version and engine API version are intentionally separate. The 1.0 distribution retains root contract ID 0.116.0 to preserve serialized identity. Breaking root contracts now require a package major release; additive and corrective changes follow [compatibility and migration](https://github.com/Photivra/photivra/blob/main/docs/RELEASE_1_0.md). A 1.0 package is not a claim of calibrated physical accuracy.
+From 1.0.1, package version and `ENGINE_API_VERSION` are equal. New captures/plans record 1.0.1; existing archives retain their original creator identities. Schema, model and POC contract versions remain independent. Breaking root contracts now require a package major release; additive and corrective changes follow [compatibility and migration](https://github.com/Photivra/photivra/blob/main/docs/RELEASE_1_0_1.md). A 1.0 package is not a claim of calibrated physical accuracy.
 
 Creating a GitHub release/tag and publishing `@photivra/engine` are separate release actions. The tag-triggered publish workflow verifies that the `vX.Y.Z` tag matches the package version before publishing.
 
@@ -343,7 +343,7 @@ When the package is installed directly from a Git repository using normal npm li
 
 ## Development
 
-Development and Node-only tooling require Node.js 22.13 or newer. CI verifies Node.js 22.13 and Node.js 24; both are LTS release lines as of this documentation audit.
+Development and Node-only tooling support maintained Node.js 22 (minimum 22.13), maintained 24, and 26 Current. Prefer patched Node 24 for builds. CI verifies Node.js 22.13 (minimum), patched 22 and 24 LTS, and 26 Current under [the runtime policy](NODE_SUPPORT.md).
 
 The reproducible npm workflow uses the committed lockfile:
 

package/SECURITY.md

@@ -4,7 +4,7 @@ Please do not open a public issue containing vulnerability details.
 
 ## Supported versions
 
-The 1.0.0 candidate establishes the 1.x root-package compatibility line. Security fixes target the current maintained development/release line; older snapshots and pre-1.0 releases should not be assumed to receive fixes. Candidate preparation does not establish npm publication or a new support service.
+The published 1.0.0 release established the 1.x root-package compatibility line. Security fixes target the current maintained development/release line; older snapshots and pre-1.0 releases should not be assumed to receive fixes. The current 1.0.1 candidate is not yet published. Node runtime support follows [NODE_SUPPORT.md](NODE_SUPPORT.md), covering maintained LTS lines plus Current; older/EOL runtimes are not qualified.
 
 ## Reporting a vulnerability
 

package/dist/core/version.d.ts

@@ -1,14 +1,9 @@
 /**
- * The root contract identity is embedded in capture/plan data. Package 1.0.0 deliberately retains
- * 0.116.0 so documentation/release metadata changes do not alter serialized scientific identity.
- * Distribution SemVer and independent model/schema versions remain separate.
- * @see docs/RELEASE_1_0.md and the corresponding domain guide.
+ * Version of the public root-engine release, aligned with the npm package since 1.0.1.
+ * New captures and plans record this creator identity; archived records retain theirs.
+ * POC, schema and model contracts keep their independent versions.
+ * Release checks enforce equality with package.json and the packed distribution.
+ * @see docs/RELEASE_1_0_1.md
  */
-/**
- * Version of the public root-engine API contract.
- *
- * This is distinct from the npm package version and all subsystem/schema
- * contract versions.
- */
-export declare const ENGINE_API_VERSION: "0.116.0";
+export declare const ENGINE_API_VERSION: "1.0.1";
 //# sourceMappingURL=version.d.ts.map

package/dist/core/version.d.ts.map

@@ -1 +1 @@
-{"version":3,"file":"version.d.ts","sourceRoot":"","sources":["../../src/core/version.ts"],"names":[],"mappings":"AAEA;;;;;GAKG;AAEH;;;;;GAKG;AACH,eAAO,MAAM,kBAAkB,EAAG,SAAkB,CAAC"}
+{"version":3,"file":"version.d.ts","sourceRoot":"","sources":["../../src/core/version.ts"],"names":[],"mappings":"AAEA;;;;;;GAMG;AACH,eAAO,MAAM,kBAAkB,EAAG,OAAgB,CAAC"}

package/dist/core/version.js

@@ -1,15 +1,10 @@
 // SPDX-License-Identifier: Apache-2.0
 /**
- * The root contract identity is embedded in capture/plan data. Package 1.0.0 deliberately retains
- * 0.116.0 so documentation/release metadata changes do not alter serialized scientific identity.
- * Distribution SemVer and independent model/schema versions remain separate.
- * @see docs/RELEASE_1_0.md and the corresponding domain guide.
+ * Version of the public root-engine release, aligned with the npm package since 1.0.1.
+ * New captures and plans record this creator identity; archived records retain theirs.
+ * POC, schema and model contracts keep their independent versions.
+ * Release checks enforce equality with package.json and the packed distribution.
+ * @see docs/RELEASE_1_0_1.md
  */
-/**
- * Version of the public root-engine API contract.
- *
- * This is distinct from the npm package version and all subsystem/schema
- * contract versions.
- */
-export const ENGINE_API_VERSION = "0.116.0";
+export const ENGINE_API_VERSION = "1.0.1";
 //# sourceMappingURL=version.js.map

package/dist/core/version.js.map

@@ -1 +1 @@
-{"version":3,"file":"version.js","sourceRoot":"","sources":["../../src/core/version.ts"],"names":[],"mappings":"AAAA,sCAAsC;AAEtC;;;;;GAKG;AAEH;;;;;GAKG;AACH,MAAM,CAAC,MAAM,kBAAkB,GAAG,SAAkB,CAAC"}
+{"version":3,"file":"version.js","sourceRoot":"","sources":["../../src/core/version.ts"],"names":[],"mappings":"AAAA,sCAAsC;AAEtC;;;;;;GAMG;AACH,MAAM,CAAC,MAAM,kBAAkB,GAAG,OAAgB,CAAC"}

package/docs/API_REFERENCE.md

@@ -1,6 +1,6 @@
 # Public API reference
 
-Generated from the exact root exports for **@photivra/engine 1.0.0 / root contract 0.116.0** by `node scripts/generate-api-reference.mjs`. No module deep import is supported.
+Generated from the exact root exports for **@photivra/engine 1.0.1 / root contract 1.0.1** by `node scripts/generate-api-reference.mjs`. No module deep import is supported.
 
 Use [the developer guide](DEVELOPERS.md) for executable paths and scientific boundaries. Types are contracts, not runtime validation: parse untrusted data, preserve units/reference frames, read assessment blockers, and retain evidence/limitations. Optional properties do not imply a universal default. Model/schema IDs remain independent of the distribution.
 

package/docs/API_STYLE.md

@@ -1,6 +1,6 @@
 # Public API Style
 
-Release context: **package 1.0.0 candidate / root API 0.116.0**. Subsystem/model versions and dated introduction or measurement records below are independent historical identities; they are not distribution versions. See [developer navigation](DEVELOPERS.md) and [release contract](RELEASE_1_0.md).
+Release context: **package 1.0.1 candidate / root API 1.0.1**. Subsystem/model versions and dated introduction or measurement records below are independent historical identities; they are not distribution versions. See [developer navigation](DEVELOPERS.md) and [release contract](RELEASE_1_0_1.md).
 
 The open engine should feel like one coherent library.
 
@@ -89,14 +89,14 @@ Do **not** automatically sum, average, add in quadrature, or otherwise collapse
 
 ## Versioning
 
-Photivra has multiple independent version surfaces:
+From 1.0.1, Photivra aligns its release and root API identities:
 
 - npm/package version: distribution/release version;
-- `ENGINE_API_VERSION`: root browser-safe engine/public-contract version;
+- `ENGINE_API_VERSION`: the same full version as the npm package;
 - `POC_SIMULATION_API_VERSION`: composed `simulatePocCamera()` request/response contract;
 - schema-specific versions such as sensor-architecture or radiometry-readiness schemas.
 
-Do not reuse one version as a proxy for another. A change to a parser/schema does not necessarily require changing the POC contract, and a POC response change does not necessarily mean the npm package has been released.
+The release checker enforces package/root equality. Subsystem, schema and POC versions remain independent. A change to a parser/schema does not necessarily require changing the POC contract, and a POC response change does not necessarily mean the npm package has been released.
 
 Before 1.0, public APIs may evolve with documented changes. Breaking or semantically meaningful contract changes must update the relevant version surface, tests, changelog, and migration/compatibility documentation. After 1.0, breaking public-contract changes require an appropriate major-version transition.
 
@@ -160,7 +160,7 @@ serialization keeps its existing validated JSON.stringify representation.
 
 ## Compatibility and deprecation policy
 
-Photivra has independent compatibility surfaces. Update only the surface whose observable contract changed.
+The package and root API share a release version. Update independent schema/model/POC versions only when their observable contracts change.
 
 ### Package version
 
@@ -168,7 +168,7 @@ The npm package version identifies a published distribution. It is not a proxy f
 
 ### `ENGINE_API_VERSION`
 
-Bump when the browser-safe root public engine contract changes materially, including a breaking or semantically meaningful exported API change.
+Set to the npm package version for every release, including patches. New records use this creator identity; parsers preserve historical archive identities.
 
 ### Subsystem/schema versions
 
@@ -228,4 +228,8 @@ Audit rule:
 
 ## Stable 1.0 distribution transition
 
-Package 1.0.0 intentionally retains `ENGINE_API_VERSION = "0.116.0"`: this independent root contract identity is already embedded in serialized captures and does not itself signal a published distribution. The package 1.0 policy now governs breaking changes despite that historical root ID. No schema/model/POC/plan version is reset. See [migration and release procedure](RELEASE_1_0.md).
+Historically, package 1.0.0 retained `ENGINE_API_VERSION = "0.116.0"`: this independent root contract identity is already embedded in serialized captures and does not itself signal a published distribution. The package 1.0 policy now governs breaking changes despite that historical root ID. No schema/model/POC/plan version is reset. See [migration and release procedure](RELEASE_1_0.md).
+
+## Aligned 1.0.1 release transition
+
+Starting with 1.0.1, `ENGINE_API_VERSION` equals the full npm package version. Package and root API follow one SemVer release sequence; schema/model/POC/plan versions remain independent. Archived capture identities and measured artifacts are preserved. Newly created capture/plan bytes and identity hashes can change because their creator API field now records 1.0.1. See [migration and release procedure](RELEASE_1_0_1.md).

package/docs/ARCHITECTURE.md

@@ -1,6 +1,6 @@
 # Architecture
 
-Release context: **package 1.0.0 candidate / root API 0.116.0**. Subsystem/model versions and dated introduction or measurement records below are independent historical identities; they are not distribution versions. See [developer navigation](DEVELOPERS.md) and [release contract](RELEASE_1_0.md).
+Release context: **package 1.0.1 candidate / root API 1.0.1**. Subsystem/model versions and dated introduction or measurement records below are independent historical identities; they are not distribution versions. See [developer navigation](DEVELOPERS.md) and [release contract](RELEASE_1_0_1.md).
 
 Photivra separates a reusable scientific core from optional composition and transport layers.
 

package/docs/AUTOMATION_COORDINATION.md

@@ -1,6 +1,6 @@
 # Public-engine automation coordination
 
-Release context: **package 1.0.0 candidate / root API 0.116.0**. Subsystem/model versions and dated introduction or measurement records below are independent historical identities; they are not distribution versions. See [developer navigation](DEVELOPERS.md) and [release contract](RELEASE_1_0.md).
+Release context: **package 1.0.1 candidate / root API 1.0.1**. Subsystem/model versions and dated introduction or measurement records below are independent historical identities; they are not distribution versions. See [developer navigation](DEVELOPERS.md) and [release contract](RELEASE_1_0_1.md).
 
 This document coordinates the two recurring automation lanes that work only in the public
 `Photivra/photivra` repository. It is process guidance, not a scientific roadmap. Open issues and

package/docs/CAPTURE_COLOR.md

@@ -1,6 +1,6 @@
 # Virtual-camera linear color: #15B
 
-Release context: **package 1.0.0 candidate / root API 0.116.0**. Subsystem/model versions and dated introduction or measurement records below are independent historical identities; they are not distribution versions. See [developer navigation](DEVELOPERS.md) and [release contract](RELEASE_1_0.md).
+Release context: **package 1.0.1 candidate / root API 1.0.1**. Subsystem/model versions and dated introduction or measurement records below are independent historical identities; they are not distribution versions. See [developer navigation](DEVELOPERS.md) and [release contract](RELEASE_1_0_1.md).
 
 `resolveCaptureColorModel()` defines an ideal CIE 1931 2-degree colorimetric camera: co-sited red/green/blue channels are an invertible encoding of XYZ in the linear-sRGB primary basis, with D65 reference white. They are relative linear values, not electrons, spectral response measurements or commercial-camera RGB. Choosing this profile is an upstream producer assertion about sample meaning; naming arbitrary sensor data with its ID does not establish validity.
 

package/docs/CAPTURE_CORRECTED_SDR.md

@@ -1,6 +1,6 @@
 # Capture-bound corrections and SDR: #112 integration slice
 
-Release context: **package 1.0.0 candidate / root API 0.116.0**. Subsystem/model versions and dated introduction or measurement records below are independent historical identities; they are not distribution versions. See [developer navigation](DEVELOPERS.md) and [release contract](RELEASE_1_0.md).
+Release context: **package 1.0.1 candidate / root API 1.0.1**. Subsystem/model versions and dated introduction or measurement records below are independent historical identities; they are not distribution versions. See [developer navigation](DEVELOPERS.md) and [release contract](RELEASE_1_0_1.md).
 
 `calculateCaptureCorrectedSdr()` consumes the same immutable `SimulatedCapture` and explicit source/color/WB choice as `calculateCaptureSdr()`, then executes existing #117/#118 corrections before the existing SDR renderer. This bounded reference bridge does not replace the #111 composer, activate production stages, or complete #112/V1.
 

package/docs/CAPTURE_EXPORT_METADATA.md

@@ -1,6 +1,6 @@
 # Capture export metadata foundation (#16B)
 
-Release context: **package 1.0.0 candidate / root API 0.116.0**. Subsystem/model versions and dated introduction or measurement records below are independent historical identities; they are not distribution versions. See [developer navigation](DEVELOPERS.md) and [release contract](RELEASE_1_0.md).
+Release context: **package 1.0.1 candidate / root API 1.0.1**. Subsystem/model versions and dated introduction or measurement records below are independent historical identities; they are not distribution versions. See [developer navigation](DEVELOPERS.md) and [release contract](RELEASE_1_0_1.md).
 
 `createCaptureExportMetadataPair()` is a browser-safe, deterministic **semantic metadata projection**, not an image exporter or proof of RAW/JPEG pixel derivation. Both future writers consume its single shared object; each resource has a distinct caller-owned document UUID and saved-incarnation UUID. `imageDataPairing = "not-verified"` prevents metadata agreement being mistaken for image agreement.
 

package/docs/CAPTURE_SDR.md

@@ -1,6 +1,6 @@
 # Capture-to-SDR adapter
 
-Release context: **package 1.0.0 candidate / root API 0.116.0**. Subsystem/model versions and dated introduction or measurement records below are independent historical identities; they are not distribution versions. See [developer navigation](DEVELOPERS.md) and [release contract](RELEASE_1_0.md).
+Release context: **package 1.0.1 candidate / root API 1.0.1**. Subsystem/model versions and dated introduction or measurement records below are independent historical identities; they are not distribution versions. See [developer navigation](DEVELOPERS.md) and [release contract](RELEASE_1_0_1.md).
 
 Current integration: [processed camera output](PROCESSED_OUTPUT.md) documents
 the shared preview/export path and explicit plan 0.6.0 post-RAW activation.

package/docs/DEVELOPERS.md

@@ -1,29 +1,29 @@
 # Developer guide
 
-This is the entry point for **@photivra/engine 1.0.0 candidate**, root API contract **0.116.0**. The candidate becomes an installable 1.0.0 distribution only after the owner tags and publishes it. Repository `main` may later describe newer development; use a published release's packaged docs or its exact tag for the stable contract. [Release notes and migration](RELEASE_1_0.md) explain the version distinction.
+This is the entry point for **@photivra/engine 1.0.1 candidate**, root API contract **1.0.1**. The candidate becomes an installable 1.0.1 distribution only after the owner tags and publishes it. Repository `main` may later describe newer development; use a published release's packaged docs or its exact tag for the stable contract. [Release notes and migration](RELEASE_1_0_1.md) explain the transition to aligned package/root versions.
 
 Photivra is an Apache-2.0 ESM TypeScript calculation library with no runtime npm dependencies. It exposes explicit units, deterministic data, provenance and bounded scientific approximations. The package supplies no hosted API, renderer installation, UI, commercial camera calibration or automatic agent service. [Photivra's public site](https://photivra.com) is separate from the engine's license; public engine documentation is available here without an application account.
 
 ## Install and calculate
 
-After publication, install `npm install @photivra/engine@1.0.0`. During candidate review, use the verified tarball described in [release preparation](RELEASE_1_0.md).
+After publication, install `npm install @photivra/engine@1.0.1`. During candidate review, use the verified tarball described in [release preparation](RELEASE_1_0_1.md).
 
 ```ts
 import { calculateFieldOfView, ENGINE_API_VERSION } from "@photivra/engine";
 
 const horizontal = calculateFieldOfView({ focalLengthMm: 50, sensorDimensionMm: 36 });
-console.log(ENGINE_API_VERSION); // 0.116.0: independent root contract identity
+console.log(ENGINE_API_VERSION); // 1.0.1: matches the package version
 console.log(horizontal.value.degrees); // approximately 39.60, ideal infinity-focus geometry
 console.log(horizontal.provenance); // read assumptions/status with the value
 ```
 
-The root is browser-safe. Supported Node execution/tooling is Node 22.13+ within the maintained 22 line and the maintained 24 line; prefer patched Node 24. The broad manifest minimum does not qualify Node Current/EOL lines. A browser backend must supply the documented ES APIs (including `structuredClone`, typed arrays and Web Crypto where used); a browser-safe import graph is not a promise about every browser version or rendering speed. See [runtime policy](../NODE_SUPPORT.md).
+The root is browser-safe. Supported Node execution/tooling is Node 22.13+ within the maintained 22 line, the maintained 24 line, and Node 26 Current; prefer patched Node 24. The broad manifest minimum does not qualify untested or EOL lines. A browser backend must supply the documented ES APIs (including `structuredClone`, typed arrays and Web Crypto where used); a browser-safe import graph is not a promise about every browser version or rendering speed. See [runtime policy](../NODE_SUPPORT.md).
 
 Primitive calculations normally return `CalculationResult<T>` with `value`, `provenance` and optional `quality`. Parsers return validated values; plans/snapshots return their independently versioned records; assessments return explicit blockers; paired export returns a Promise because hashing is asynchronous. Do not infer calibrated accuracy from successful parsing, a complete stage graph, a generic tier name or deterministic replay.
 
 ## Find the operation by scientific task
 
-Every row applies to package 1.0.0/root 0.116.0. Direct calculations are synchronous/browser-safe unless the row says otherwise. A listed primitive is not automatically an app feature or supported in every production combination. The [API reference](API_REFERENCE.md) resolves all root exports and exact signatures; the linked guides own equations, inputs, defaults, errors and limits.
+Every row applies to package/root API 1.0.1. Direct calculations are synchronous/browser-safe unless the row says otherwise. A listed primitive is not automatically an app feature or supported in every production combination. The [API reference](API_REFERENCE.md) resolves all root exports and exact signatures; the linked guides own equations, inputs, defaults, errors and limits.
 
 | Task | Start here / executable evidence | Qualified boundary |
 | --- | --- | --- |
@@ -57,4 +57,4 @@ Malformed configurations/non-finite values throw the established domain errors.
 
 See [provenance](PROVENANCE.md), [license](../LICENSE), [NOTICE](../NOTICE), [third-party inventory](../THIRD_PARTY.md), [contributing](../CONTRIBUTING.md) and [security reporting](../SECURITY.md). Engine code/docs do not license the commercial application or its private assets. Report reproducible engine defects through [public issues](https://github.com/Photivra/photivra/issues).
 
-Website navigation/documentation hosting belongs to [the app-side discovery ticket #45](https://github.com/Photivra/photivra-apps/issues/45), with navigation #298 and environments #300. Handoff: link the public engine repository, this developer guide, the eventual verified npm 1.0.0 package and capability examples from the public site. No unpublished `/developers` destination is linked here. Website launch is not an engine release prerequisite; access to the site returned HTTP 403 during this audit, so its content/navigation was not verified.
+Website navigation/documentation hosting belongs to [the app-side discovery ticket #45](https://github.com/Photivra/photivra-apps/issues/45), with navigation #298 and environments #300. Handoff: link the public engine repository, this developer guide, the verified npm release package and capability examples from the public site. No unpublished `/developers` destination is linked here. Website launch is not an engine release prerequisite; access to the site returned HTTP 403 during this audit, so its content/navigation was not verified.

package/docs/DIGITAL_OPTICS_FOUNDATION.md

@@ -1,6 +1,6 @@
 # Stray light and digital lens correction foundations
 
-Release context: **package 1.0.0 candidate / root API 0.116.0**. Subsystem/model versions and dated introduction or measurement records below are independent historical identities; they are not distribution versions. See [developer navigation](DEVELOPERS.md) and [release contract](RELEASE_1_0.md).
+Release context: **package 1.0.1 candidate / root API 1.0.1**. Subsystem/model versions and dated introduction or measurement records below are independent historical identities; they are not distribution versions. See [developer navigation](DEVELOPERS.md) and [release contract](RELEASE_1_0_1.md).
 
 Issues #114, #118 and #117 add standalone browser-safe primitives. They do not enable a production-plan stage, change the POC, or supply a calibrated camera/lens preset. The public root API advances from 0.94.0 to 0.95.0; each new profile/prepared-map schema is 0.1.0. Package, POC, production-plan and PSF versions are unchanged. This branch incorporates merged polygon-diffraction PR #157 and reconciles the root API increment with that predecessor.
 

package/docs/ENVIRONMENT_RAW_CAPTURE.md

@@ -1,6 +1,6 @@
 # Executed environment capture to native RAW
 
-Release context: **package 1.0.0 candidate / root API 0.116.0**. Subsystem/model versions and dated introduction or measurement records below are independent historical identities; they are not distribution versions. See [developer navigation](DEVELOPERS.md) and [release contract](RELEASE_1_0.md).
+Release context: **package 1.0.1 candidate / root API 1.0.1**. Subsystem/model versions and dated introduction or measurement records below are independent historical identities; they are not distribution versions. See [developer navigation](DEVELOPERS.md) and [release contract](RELEASE_1_0_1.md).
 
 `calculateEnvironmentSensorPhotoSignal()` executes one destination site's
 bounded environment exposure. `simulateEnvironmentSensorRawFrame()` applies that

package/docs/EXPORT_ACCEPTANCE.md

@@ -1,6 +1,6 @@
 # Simulated Sensor RAW DNG / JPEG acceptance
 
-Release context: **package 1.0.0 candidate / root API 0.116.0**. Subsystem/model versions and dated introduction or measurement records below are independent historical identities; they are not distribution versions. See [developer navigation](DEVELOPERS.md) and [release contract](RELEASE_1_0.md).
+Release context: **package 1.0.1 candidate / root API 1.0.1**. Subsystem/model versions and dated introduction or measurement records below are independent historical identities; they are not distribution versions. See [developer navigation](DEVELOPERS.md) and [release contract](RELEASE_1_0_1.md).
 
 This record separates implemented export behavior, reproducible independent
 checks and external application acceptance for #16. The files are synthetic

package/docs/GENERIC_TIER_PRESETS.md

@@ -1,6 +1,6 @@
 # Generic equipment tier reference assets
 
-Release context: **package 1.0.0 candidate / root API 0.116.0**. Subsystem/model versions and dated introduction or measurement records below are independent historical identities; they are not distribution versions. See [developer navigation](DEVELOPERS.md) and [release contract](RELEASE_1_0.md).
+Release context: **package 1.0.1 candidate / root API 1.0.1**. Subsystem/model versions and dated introduction or measurement records below are independent historical identities; they are not distribution versions. See [developer navigation](DEVELOPERS.md) and [release contract](RELEASE_1_0_1.md).
 
 `resolveGenericEquipmentTierCatalog({ presetVersion: "1.0.0" })` returns immutable
 Consumer, Prosumer and Professional body/lens reference bundles. These are
@@ -139,7 +139,7 @@ There is no separate tier-specific browser approximation to compare here; the
 public implementation remains browser-safe and uses the ordinary reference APIs.
 No private application acceptance is invented.
 
-Initial tier assets landed at root API 0.105.0; the current root API is 0.116.0.
+Initial tier assets landed at root API 0.105.0; the current root API is 1.0.1.
 This acceptance-only extension does not change runtime/API or asset definitions. Selection schema 0.1.0, asset version 1.0.0, npm package,
 POC and production contracts remain independent. Human scientific/provenance
 review and contribution-specific DCO certification are still required.

package/docs/GEOMETRIC_PREPARATION_REUSE.md

@@ -1,6 +1,6 @@
 # Call-local geometry preparation reuse: #43
 
-Release context: **package 1.0.0 candidate / root API 0.116.0**. Subsystem/model versions and dated introduction or measurement records below are independent historical identities; they are not distribution versions. See [developer navigation](DEVELOPERS.md) and [release contract](RELEASE_1_0.md).
+Release context: **package 1.0.1 candidate / root API 1.0.1**. Subsystem/model versions and dated introduction or measurement records below are independent historical identities; they are not distribution versions. See [developer navigation](DEVELOPERS.md) and [release contract](RELEASE_1_0_1.md).
 
 `calculateGeometricSamplingPlan()` already parses and copies a complete transform
 list at its public boundary. It previously called the public scalar mapping API

package/docs/IMAGE_FORMATION.md

@@ -1,6 +1,6 @@
 # Image-Formation Contract
 
-Release context: **package 1.0.0 candidate / root API 0.116.0**. Subsystem/model versions and dated introduction or measurement records below are independent historical identities; they are not distribution versions. See [developer navigation](DEVELOPERS.md) and [release contract](RELEASE_1_0.md).
+Release context: **package 1.0.1 candidate / root API 1.0.1**. Subsystem/model versions and dated introduction or measurement records below are independent historical identities; they are not distribution versions. See [developer navigation](DEVELOPERS.md) and [release contract](RELEASE_1_0_1.md).
 
 Photivra's image-formation contract defines **scientific ownership, coordinate semantics, and dependency/coupling boundaries** for current and future camera effects.
 

package/docs/LINEAR_CAPTURE_ENCODING.md

@@ -1,6 +1,6 @@
 # Deterministic linear capture encoding: #15C
 
-Release context: **package 1.0.0 candidate / root API 0.116.0**. Subsystem/model versions and dated introduction or measurement records below are independent historical identities; they are not distribution versions. See [developer navigation](DEVELOPERS.md) and [release contract](RELEASE_1_0.md).
+Release context: **package 1.0.1 candidate / root API 1.0.1**. Subsystem/model versions and dated introduction or measurement records below are independent historical identities; they are not distribution versions. See [developer navigation](DEVELOPERS.md) and [release contract](RELEASE_1_0_1.md).
 
 `calculateLinearCaptureEncoding()` produces format-neutral unsigned 16-bit linear codes from one bounded inline `SimulatedCapture` plane. The exact plane/image-state identity is mandatory. The master stays unchanged; color, WB application, source reference value and upstream capture-saturation history accompany the encoded data. It neither chooses a file format nor invents a color conversion.
 

package/docs/MOTION_AND_SIGNAL.md

@@ -1,6 +1,6 @@
 # Motion and Signal Foundation
 
-Release context: **package 1.0.0 candidate / root API 0.116.0**. Subsystem/model versions and dated introduction or measurement records below are independent historical identities; they are not distribution versions. See [developer navigation](DEVELOPERS.md) and [release contract](RELEASE_1_0.md).
+Release context: **package 1.0.1 candidate / root API 1.0.1**. Subsystem/model versions and dated introduction or measurement records below are independent historical identities; they are not distribution versions. See [developer navigation](DEVELOPERS.md) and [release contract](RELEASE_1_0_1.md).
 
 ## Projected subject motion
 

package/docs/NUMERICAL_CORRECTNESS.md

@@ -1,6 +1,6 @@
 # Numerical Correctness and Physical Units
 
-Release context: **package 1.0.0 candidate / root API 0.116.0**. Subsystem/model versions and dated introduction or measurement records below are independent historical identities; they are not distribution versions. See [developer navigation](DEVELOPERS.md) and [release contract](RELEASE_1_0.md).
+Release context: **package 1.0.1 candidate / root API 1.0.1**. Subsystem/model versions and dated introduction or measurement records below are independent historical identities; they are not distribution versions. See [developer navigation](DEVELOPERS.md) and [release contract](RELEASE_1_0_1.md).
 
 Photivra is a scientific engine. Numerical behavior and physical-unit meaning are public-contract concerns, not implementation details.
 

package/docs/PERFORMANCE_BASELINE.md

@@ -1,6 +1,6 @@
 # Measured-performance baseline: #43 / #45
 
-Release context: **package 1.0.0 candidate / root API 0.116.0**. Subsystem/model versions and dated introduction or measurement records below are independent historical identities; they are not distribution versions. See [developer navigation](DEVELOPERS.md) and [release contract](RELEASE_1_0.md).
+Release context: **package 1.0.1 candidate / root API 1.0.1**. Subsystem/model versions and dated introduction or measurement records below are independent historical identities; they are not distribution versions. See [developer navigation](DEVELOPERS.md) and [release contract](RELEASE_1_0_1.md).
 
 This independent first slice records merged main `83a99a4c1ec525fd1add7cccff134fcee0f5159b`, root API 0.93.0, POC API 0.20.0, in `docs/benchmarks/2026-10-01-main-baseline.json`. No pending capture/output/correction/preset implementation is consumed. It does not close either issue or justify an optimization by itself.
 

package/docs/PHOTOGRAPHIC_EXPORT.md

@@ -1,6 +1,6 @@
 # Simulated Sensor RAW DNG / JPEG export
 
-Release context: **package 1.0.0 candidate / root API 0.116.0**. Subsystem/model versions and dated introduction or measurement records below are independent historical identities; they are not distribution versions. See [developer navigation](DEVELOPERS.md) and [release contract](RELEASE_1_0.md).
+Release context: **package 1.0.1 candidate / root API 1.0.1**. Subsystem/model versions and dated introduction or measurement records below are independent historical identities; they are not distribution versions. See [developer navigation](DEVELOPERS.md) and [release contract](RELEASE_1_0_1.md).
 
 Current producer-derived files and external closure gates are recorded in
 [Export acceptance](EXPORT_ACCEPTANCE.md). The new reproducible generator uses

package/docs/PHYSICS_FOUNDATION.md

@@ -1,6 +1,6 @@
 # Physics Foundation
 
-Release context: **package 1.0.0 candidate / root API 0.116.0**. Subsystem/model versions and dated introduction or measurement records below are independent historical identities; they are not distribution versions. See [developer navigation](DEVELOPERS.md) and [release contract](RELEASE_1_0.md).
+Release context: **package 1.0.1 candidate / root API 1.0.1**. Subsystem/model versions and dated introduction or measurement records below are independent historical identities; they are not distribution versions. See [developer navigation](DEVELOPERS.md) and [release contract](RELEASE_1_0_1.md).
 
 Photivra starts with analytical models that can be independently tested and whose assumptions can be stated explicitly.
 

package/docs/POC_API.md

@@ -1,6 +1,6 @@
 # Local POC Simulation API
 
-Release context: **package 1.0.0 candidate / root API 0.116.0**. Subsystem/model versions and dated introduction or measurement records below are independent historical identities; they are not distribution versions. See [developer navigation](DEVELOPERS.md) and [release contract](RELEASE_1_0.md).
+Release context: **package 1.0.1 candidate / root API 1.0.1**. Subsystem/model versions and dated introduction or measurement records below are independent historical identities; they are not distribution versions. See [developer navigation](DEVELOPERS.md) and [release contract](RELEASE_1_0_1.md).
 
 Photivra includes a minimal Node HTTP transport for proof-of-concept development and integration testing.
 

package/docs/POC_PROJECTION_REUSE.md

@@ -1,6 +1,6 @@
 # Request-local defocus projection reuse: #45
 
-Release context: **package 1.0.0 candidate / root API 0.116.0**. Subsystem/model versions and dated introduction or measurement records below are independent historical identities; they are not distribution versions. See [developer navigation](DEVELOPERS.md) and [release contract](RELEASE_1_0.md).
+Release context: **package 1.0.1 candidate / root API 1.0.1**. Subsystem/model versions and dated introduction or measurement records below are independent historical identities; they are not distribution versions. See [developer navigation](DEVELOPERS.md) and [release contract](RELEASE_1_0_1.md).
 
 The measured candidate reuses the focus-plane image distance already calculated
 inside `simulatePocCamera()` for its subject and defocus sweep. It is a small

package/docs/PROCESSED_OUTPUT.md

@@ -1,6 +1,6 @@
 # Processed camera output
 
-Release context: **package 1.0.0 candidate / root API 0.116.0**. Subsystem/model versions and dated introduction or measurement records below are independent historical identities; they are not distribution versions. See [developer navigation](DEVELOPERS.md) and [release contract](RELEASE_1_0.md).
+Release context: **package 1.0.1 candidate / root API 1.0.1**. Subsystem/model versions and dated introduction or measurement records below are independent historical identities; they are not distribution versions. See [developer navigation](DEVELOPERS.md) and [release contract](RELEASE_1_0_1.md).
 
 Root API 0.115.0 completes the bounded SDR post-capture handoff for #112.
 Production plan 0.6.0 adds explicit committed RAW processing. At introduction, package 0.6.0,