@plasius/gpu-shader 0.1.2 → 0.1.4

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/README.md CHANGED
@@ -52,6 +52,29 @@ strict manifest parsers and versioned contracts. The build APIs
52
52
  `reflectGpuInterface`, `validateAssembledGpuInterface`, and
53
53
  `generateGpuInterfaceArtifacts` are exposed only from the Node subpath.
54
54
 
55
+ ### Bounded contract snapshot boundary
56
+
57
+ Every browser-safe manifest, compatibility, matrix, inventory, qualification,
58
+ evidence, and runtime-reference parser snapshots contract data before reading
59
+ schema fields. The snapshot accepts only JSON primitives, local-realm plain
60
+ objects, and dense ordinary arrays whose fields are own enumerable data
61
+ properties. Accessors, symbols, hidden fields, behavioral prototypes, sparse
62
+ or custom arrays, cycles, invalid Unicode, and over-limit graphs fail closed.
63
+
64
+ The snapshot never invokes a property getter or Proxy `get` trap. JavaScript
65
+ cannot portably detect a transparent Proxy, so its `getPrototypeOf`, `ownKeys`,
66
+ and `getOwnPropertyDescriptor` reflection traps may run. Any reflection failure
67
+ is replaced by a fixed bounded diagnostic; the thrown provider value is not
68
+ interpolated or retained as `error.cause`. Cross-realm or behavioral values
69
+ must first be JSON-decoded or structured-cloned into the current realm.
70
+
71
+ Runtime/model contracts and complete qualification products use separate
72
+ finite policies. The exact depth, node, property, element, per-string,
73
+ aggregate-string, aggregate-data, and encoded-input ceilings are recorded in
74
+ [TDR 0003](docs/tdrs/tdr-0003-bounded-contract-snapshot-policies.md). Valid
75
+ plain JSON retains byte-identical canonical JSON and ABI hashes. Changing a
76
+ policy requires affected shader requalification.
77
+
55
78
  ## Installation
56
79
 
57
80
  After an approved GitHub CD release publishes the package:
@@ -107,11 +130,9 @@ npm SLSA provenance for the immutable release commit and protected-main
107
130
  non-draft release point to that release commit. Recovery does not create new
108
131
  tarball or SBOM attestations under the newer validation commit.
109
132
 
110
- The first public version requires the production-environment `NPM_TOKEN`
111
- because npm trusted publishing cannot be configured until the package exists.
112
- After that version is published, configure npm trusted publishing for
113
- `Plasius-LTD/gpu-shader`, workflow `cd.yml`, environment `production`, and
114
- remove `NPM_TOKEN`. See the
133
+ Publication uses npm trusted publishing for `Plasius-LTD/gpu-shader`, workflow
134
+ `cd.yml`, and environment `production`; no reusable npm write token is stored.
135
+ See the
115
136
  [fleet and repository setup runbook](docs/operations/physical-fleet-readiness.md#repository-configuration).
116
137
 
117
138
  ## Reflect final assembled WGSL
@@ -211,6 +232,19 @@ The codec is little-endian, bounds checked, strict about unknown or missing
211
232
  members, and writes deterministic zero padding. Unsupported or non-finite
212
233
  values fail before upload.
213
234
 
235
+ For network/storage input, prefer `parseJsonBytes` followed by the strict
236
+ manifest parser. Both encoded bytes and the resulting data graph are bounded;
237
+ syntax, UTF-8, snapshot, and schema failures do not retain parser/provider
238
+ causes.
239
+
240
+ Byte input is brand-checked and copied with captured TypedArray intrinsics, so
241
+ `Buffer`, Uint8Array subclasses, and cross-realm Uint8Arrays remain supported
242
+ without reading caller `byteLength`, `constructor`, iterator, or index
243
+ properties. Proxy-wrapped typed arrays fail the intrinsic brand check. Runtime
244
+ style-load request fields and catalog asset-result fields must likewise be
245
+ enumerable own data properties; catalog and attestation callback failures are
246
+ reported with fixed cause-free diagnostics.
247
+
214
248
  ## Validate a model and shader
215
249
 
216
250
  ```ts
@@ -458,3 +492,16 @@ standing line-coverage exception, replaced by 100% compile-unit inventory and
458
492
  ## License
459
493
 
460
494
  Apache-2.0. See [LICENSE](LICENSE).
495
+
496
+ <!-- BEGIN PLASIUS RELEASE INTEGRITY -->
497
+ ## Release integrity
498
+
499
+ CI keeps the administrative contributor registry outside Git and npm package
500
+ artifacts using exact, case-normalised path checks. CI runs on approved
501
+ GitHub-hosted runners for same-repository pull requests and `main`, with
502
+ package-manager cache finalization disabled; fork PR code is denied.
503
+ Publication uses the GitHub-hosted `production` job with Node 24 and a pinned
504
+ npm 11.6.2 client. It is token-free and proceeds only while the prepared SHA
505
+ is the exact `main` head after successful push-triggered CI. Do not dispatch CD
506
+ until the npm trusted-publisher binding is verified.
507
+ <!-- END PLASIUS RELEASE INTEGRITY -->