@plasius/gpu-renderer 0.2.39 → 0.2.41

package/CHANGELOG.md

@@ -23,6 +23,49 @@ All notable changes to this project will be documented in this file.
 - **Security**
   - (placeholder)
 
+## [0.2.41] - 2026-08-30
+
+- **Added**
+  - Added opt-in fixed-SPP ray-count and timing telemetry to awaited
+    `renderFrame({ readStats: true })` results, including exact primary,
+    continuation, total path-segment, and per-bounce counts plus WebGPU
+    timestamp-query timing with an explicit queue-completion fallback.
+
+- **Changed**
+  - Switched WGSL preflight diagnostics to the standard
+    `GPUShaderModule.getCompilationInfo()` API and request the 21 sampled
+    textures already required by the final material shader when the adapter
+    exposes that limit.
+
+- **Fixed**
+  - Fixed final assembled WGSL compilation by making triangle initialization
+    resilient to record-field additions and aligning the trace bind-group
+    layout with all declared material-extension textures.
+
+- **Security**
+  - (placeholder)
+
+## [0.2.40] - 2026-08-30
+
+- **Added**
+  - (placeholder)
+
+- **Changed**
+  - Updated internal GPU dependencies to their surviving clean lines and refreshed the esbuild resolution.
+
+- **Fixed**
+  - (placeholder)
+
+- **Security**
+  - Added permanent fail-closed Zero-Three validation for manifests, source,
+    locks, installed dependency graphs, declarations, bundles, npm tarballs,
+    CycloneDX SBOMs, and active documentation, with digest-bound evidence
+    retained and attested by CI/CD.
+  - Pinned patched transitive npm dependencies to clear the current audit baseline.
+  - Replaced token-based npm publication with a two-phase exact-main OIDC workflow, immutable tarball/SBOM hand-off, isolated pull-request validation, and fail-closed integrity checks.
+  - Added fail-closed source and npm-package admission for the administrative contributor registry and pinned the CI/CD runtime to Node.js 24.18.0 LTS.
+  - (placeholder)
+
 ## [0.2.39] - 2026-07-10
 
 - **Added**
@@ -984,3 +1027,5 @@ All notable changes to this project will be documented in this file.
 [0.2.37]: https://github.com/Plasius-LTD/gpu-renderer/releases/tag/v0.2.37
 [0.2.38]: https://github.com/Plasius-LTD/gpu-renderer/releases/tag/v0.2.38
 [0.2.39]: https://github.com/Plasius-LTD/gpu-renderer/releases/tag/v0.2.39
+[0.2.40]: https://github.com/Plasius-LTD/gpu-renderer/releases/tag/v0.2.40
+[0.2.41]: https://github.com/Plasius-LTD/gpu-renderer/releases/tag/v0.2.41

package/README.md

@@ -27,6 +27,21 @@ Apache-2.0. ESM + CJS builds.
 npm install @plasius/gpu-renderer
 ```
 
+## Permanent Zero-Three boundary
+
+This WebGPU renderer and its complete production, development, test, tooling,
+peer, optional, and artifact dependency graphs permanently prohibit Three.js,
+R3F, TSL, their related packages, and any dependency path reaching them. There
+is no compatibility mode, fallback, waiver, or rollback to those renderers.
+
+Run `npm run zero-three:source` before installing dependencies, or run
+`npm run build && npm run zero-three` after `npm ci` for the installed graph,
+built bundle, actual npm tarball, and generated CycloneDX evidence. The full
+command writes digest-bound package/version evidence to
+`release-artifacts/zero-three-evidence.json`. CI retains it, and production CD
+passes it by immutable artifact ID, verifies it again, attaches it to the
+GitHub release, and attests it.
+
 ## Usage
 
 ```js
@@ -435,7 +450,47 @@ drop in jobs/submission or jobs/s versus the approved baseline as a
 release-validation failure unless a linked ticket explicitly approves the
 regression; `submission-batching` warns when the renderer falls back to roughly
 one GPU job per submission despite a higher pass ceiling.
-submitting work that can occupy more than one GPU execution unit. After each
+
+Awaited fixed-SPP renders can opt into exact ray and timing evidence:
+
+```js
+const frame = await renderer.renderFrame({
+  readStats: true,
+  readOutputProbe: false,
+});
+
+console.log({
+  primaryRays: frame.primaryRays,
+  secondaryRays: frame.secondaryRays,
+  totalPathSegments: frame.totalPathSegments,
+  bounceHistogram: frame.rayCounts.bounceHistogram,
+  gpuTimeMs: frame.timings.totalGpuTimeMs,
+  renderJobTimeMs: frame.timings.totalRenderJobTimeMs,
+  timingSource: frame.timings.source,
+});
+```
+
+`primaryRays` is the exact number of camera samples. `secondaryRays` is the
+sum of active continuation records intersected after bounce zero, including
+bounded reflection/transmission branches, and `totalPathSegments` is their sum.
+The renderer copies the existing active-queue counter once per bounce into a
+lazily allocated telemetry buffer; it does not add diagnostic shader atomics or
+change WGSL transport. `rayCounts.status` distinguishes available,
+unavailable, failed, and not-requested evidence. A mismatch between scheduled
+and observed primary rays fails the `ray-count-telemetry` transport guardrail.
+
+When the adapter exposes `timestamp-query`, the device requests it
+opportunistically and two timestamps measure the GPU span from the first
+primary pass through presentation. Set `gpuTimestamps: false` at renderer
+creation to prevent that optional feature request. Where timestamp queries are
+not exposed or fail, `timings` reports `source: "queue-completion"`, leaves
+`totalGpuTimeMs` null, and retains the awaited
+`totalRenderJobTimeMs`. Classification, compaction, and sampling sub-pass times
+remain null until the corresponding adaptive passes exist. Without
+`readStats: true`, and for `renderOnce()`, the fixed dispatcher creates no
+telemetry buffers, query sets, readbacks, or timestamped pass descriptors.
+
+After each
 primary-ray or compaction pass, the GPU writes the active-ray workgroup count
 into the counter buffer and the encoder copies it into an indirect-dispatch
 argument buffer. Intersection and surface-resolution passes therefore scale
@@ -580,3 +635,18 @@ npm run pack:check
 - `docs/design/worker-manifest-integration.md`: renderer frame-stage DAG model.
 - `docs/adrs/*`: architecture decisions for renderer runtime design.
 - `docs/tdrs/*`: technical direction for frame hook integration.
+
+<!-- BEGIN PLASIUS RELEASE INTEGRITY -->
+## Release integrity
+
+CI keeps the administrative contributor registry outside Git and npm package
+artifacts using exact, case-normalised path checks. External fork heads are
+rejected; same-repository pull requests validate on GitHub-hosted runners and
+main pushes validate on approved self-hosted runners. Release preparation and
+publication use a two-run exact-main protocol on GitHub-hosted Node.js 24.18.0
+LTS. A read-only job seals the package tarball and SBOM before a dependency-free
+production job publishes that exact artifact through npm OIDC with provenance;
+there is no npm write-token fallback. CD remains disabled until the npm trusted
+publisher binding and protected-branch-only production environment are
+independently verified.
+<!-- END PLASIUS RELEASE INTEGRITY -->