@plasius/gpu-renderer 0.2.44 → 0.2.46

package/CHANGELOG.md

@@ -18,6 +18,47 @@ All notable changes to this project will be documented in this file.
   - (placeholder)
 
 - **Fixed**
+  - (placeholder)
+
+- **Security**
+  - (placeholder)
+
+## [0.2.46] - 2026-09-29
+
+- Add native showcase surface drawing with filtered shadows, HDR planar water
+  reflections, analytic waves, four-sample antialiasing and bounded resource ownership.
+- Add an optional multipass `encodeFrame` hook to the existing renderer lifecycle.
+
+- **Added**
+  - Internal reflected adaptive budget/count metadata, optional bounded classifier
+    and packed-history buffers, and lazy allocation admission with a 128 MiB cap.
+    This is infrastructure only; per-pixel dispatch and site controls remain pending.
+  - (placeholder)
+
+- **Changed**
+  - (placeholder)
+
+- **Fixed**
+  - (placeholder)
+
+- **Security**
+  - (placeholder)
+
+## [0.2.45] - 2026-09-07
+
+- **Added**
+  - (placeholder)
+
+- **Changed**
+  - Refreshed compatible @plasius/* lockfile resolutions to the latest published releases.
+ - (placeholder)
+
+- **Fixed**
+  - Documented verified locked-branch runner admission for trusted push checks,
+    including exact-commit verification and removal before branch updates.
+  - Restored trusted-push-only CI on explicit self-hosted runners, preserving
+    required check names and excluding external fork execution; bounded scheduled
+    dependency validation to self-hosted main runs.
   - Preserved hosted pull-request isolation, bounded validation runtime, and
     disabled package-manager cache finalization on self-hosted main validation.
   - (placeholder)
@@ -1106,3 +1147,5 @@ All notable changes to this project will be documented in this file.
 [0.2.42]: https://github.com/Plasius-LTD/gpu-renderer/releases/tag/v0.2.42
 [0.2.43]: https://github.com/Plasius-LTD/gpu-renderer/releases/tag/v0.2.43
 [0.2.44]: https://github.com/Plasius-LTD/gpu-renderer/releases/tag/v0.2.44
+[0.2.45]: https://github.com/Plasius-LTD/gpu-renderer/releases/tag/v0.2.45
+[0.2.46]: https://github.com/Plasius-LTD/gpu-renderer/releases/tag/v0.2.46

package/README.md

@@ -1,5 +1,26 @@
 # @plasius/gpu-renderer
 
+## Native animated showcase surfaces
+
+`createNativeSceneRenderer({ canvas })` draws interleaved world-space triangles
+with depth testing, four-sample antialiasing, filtered directional shadows and
+animated water with a planar reflection. Call `render({ vertices, camera, time,
+wakes })` from the caller's animation loop and `destroy()` on teardown. Each vertex
+has twelve floats: position XYZ, normal XYZ, linear colour RGB, roughness,
+metalness, and procedural detail kind (0 plain, 1 wood, 2 mineral/cloth, 3 terrain).
+`camera` supplies `eye`, `target` and optional vertical `fov`. At most four wakes
+contain `[x, z, headingRadians]`; water can be disabled with `water: false`.
+
+The input limit defaults to 300,000 vertices. Colour/depth targets are reused and
+render dimensions are capped at 3840 per axis and a 1080p pixel budget. Snapshots identify `webgpu-raster`
+and count submitted frames; they do not claim ray tracing, GPU completion or
+photorealism. Native initialization failures reject; device loss changes
+`available` and calls `onUnavailable`. The existing wavefront APIs are unchanged.
+
+Enable only through the consumer's remote `gpu-demo.scene-fidelity.enabled`
+decision and existing access capability. See [design](docs/design/native-showcase-surfaces.md)
+and [ADR-0030](docs/adrs/adr-0030-native-showcase-surfaces.md) for rollout and limits.
+
 [![npm version](https://img.shields.io/npm/v/@plasius/gpu-renderer.svg)](https://www.npmjs.com/package/@plasius/gpu-renderer)
 [![Build Status](https://img.shields.io/github/actions/workflow/status/Plasius-LTD/gpu-renderer/ci.yml?branch=main&label=build&style=flat)](https://github.com/Plasius-LTD/gpu-renderer/actions/workflows/ci.yml)
 [![coverage](https://img.shields.io/codecov/c/github/Plasius-LTD/gpu-renderer)](https://codecov.io/gh/Plasius-LTD/gpu-renderer)
@@ -58,6 +79,21 @@ diagnostic capture or network/storage operation, and never registers
 `/player-system`. Disabling the flag preserves ordinary structured-only bug
 reporting.
 
+## Adaptive per-pixel implementation status
+
+Per-pixel adaptive rendering is not yet exposed by the public renderer API.
+The internal [metadata foundation](docs/design/adaptive-metadata.md) now provides
+reflected requested/completed count storage and lazy, bounded allocation.
+`@plasius/gpu-shader` validates the final initialization WGSL in development;
+the reflector does not enter browser bundles. The normal `npm test` suite checks
+generated byte constants, count packing, allocation admission and cleanup.
+
+The fixed renderer and its whole-frame budget adjustment are unchanged. Actual
+completed-count normalization, compact primary scheduling, foveation and shared
+integration must land before a site comparison can claim per-pixel adaptation.
+No image-quality, performance or net-memory-saving claim follows from the
+metadata-only WebGPU execution fixture. See [ADR 0029](docs/adrs/adr-0029-reflected-adaptive-metadata-admission.md).
+
 ## Install
 
 ```sh
@@ -691,9 +727,23 @@ npm run pack:check
 ## 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
+artifacts using exact, case-normalised path checks. CI runs only for pushes to
+repository-owned branches on explicit `[self-hosted, Linux, X64]` runners.
+External fork pull requests trigger no CI execution; a maintainer must review
+and move a contribution to a repository-owned branch to produce required checks.
+Before branch CI starts, an authorised maintainer reviews the exact commit and
+locks its repository branch as read-only, enforcing the lock for administrators
+and disabling force pushes, deletion, and fork syncing. After reading back the
+lock and commit SHA, admit only that branch's fully qualified workflow ref for
+`gpu-renderer/.github/workflows/ci.yml` in `Public CI - Quarantined`. Top-level
+push jobs identify their workflow by branch ref; SHA-only admission did not
+schedule the reviewed job. Remove the temporary workflow entry and verify its
+removal before unlocking or updating the branch, and after delivery. Preserve all
+other group restrictions. Never admit mutable branch or PR refs. See
+[ADR-0028](docs/adrs/adr-0028-locked-branch-runner-admission.md) for the procedure.
+The trusted admission, build-test, and artifact-integrity checks keep their
+existing names for branch protection. Scheduled dependency validation also uses
+bounded self-hosted capacity and accepts only `main`. 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;