@woosh/meep-engine 3.14.0 → 3.14.2

package/README.md

@@ -31,21 +31,8 @@ tiers to author, no per-device profiles, no exposure value to pick, no shadow ca
 hand-tune. You put a scene together, it looks right, and it holds its frame rate across a wide
 range of hardware without you doing anything about it.
 
-<!--
-PLACEHOLDER - two claims were removed from the opening because nothing in the repository
-supports them. Both may be true; neither is verifiable from source. Restore with specifics.
-
-1. "shipped in commercial Steam releases" - needs the titles. Verified 2026-09-01: zero Steam app
-   IDs, zero steamworks/steam_api references, zero named shipped products anywhere in the tree.
-   The only game the repo names is the codename "mir", whose own README says it is unpublished.
-   Every other occurrence of "Steam" is Steam Audio cited as a design reference. Naming even one
-   title is worth more than the generic sentence was.
-
-2. "Built over 10+ years" - git history runs 2020-04-19 to 2026-09-01 (6y4m, 7,652 commits), with
-   no earlier commit by author or committer date. If the 10 years predates this repository, say
-   so; otherwise "in development since 2020" is defensible as written.
--->
-
+In development since 2013, shipped in a commercial Steam release, and held to **~15,000 tests** -
+determinism, adversarial and shader-emulation suites among them.
 
 ---
 
@@ -77,8 +64,9 @@ type names come from.
   extend the frame by declaring where your work goes, not by patching the renderer.
 
 If you want the mechanisms behind these - visibility buffer, meshlet clustering, clustered lighting,
-occlusion culling, the frame graph - they are in **[the renderer contract](src/shade/RENDERER_CONTRACT.md)**,
-which also covers how to put a model on the screen and how to add your own work to the frame.
+occlusion culling, the frame graph - they are in **the renderer contract**, which ships in the
+package at `src/shade/RENDERER_CONTRACT.md`. It also covers how to put a model on the screen and
+how to add your own work to the frame.
 
 ## How the features interact
 
@@ -140,8 +128,8 @@ Two things to know. Anti-aliasing is the only thing that upscales, so switching
 resolution scale is below full leaves the frame un-upscaled. And if you drive the `Renderer`
 directly rather than through `Engine`, none of this is wired for you.
 
-A neural upscaler ships alongside the default one - a port of ARM's Neural Super Sampling, weights
-included, no setup needed - one assignment away at `renderer.upscale_type = ShadeUpscalerType.NSS`.
+A neural network-based upscaler ships alongside the default one, weights included and no setup
+needed - one assignment away at `renderer.upscale_type = ShadeUpscalerType.NSS`.
 
 ## Correct by default
 
@@ -182,7 +170,11 @@ targets WebGPU, and everything above follows from that.
 The floor is fixed and checked before anything is created: WebGPU plus a small set of capabilities
 that mainstream desktop GPUs have had for years. Hardware that does not clear it gets a clear
 failure message written to be shown to a person, rather than a degraded picture. The exact features
-and limits are in [§2 of the contract](src/shade/RENDERER_CONTRACT.md).
+and limits are in §2 of `src/shade/RENDERER_CONTRACT.md`.
+
+To see what a given browser and GPU actually report, open
+**[webgpu.report](https://webgpu.report/)** on the machine in question - it lists the adapter's
+features and limits, which is what the floor is checked against.
 
 ## Numbers
 
@@ -195,30 +187,7 @@ The renderer records `.sgpt` GPU profile captures - per-pass timings, and at hig
 the frame-graph structure, dispatch and draw counts. Assign a
 `GPUProfileSession({ level: GPUProfileLevel.WORKLOAD })` to `renderer.profile_session`, call
 `start()`, run frames, and `stop()` returns an `ArrayBuffer` to write out. The recorder and the
-[format specification](src/shade/device/timing/profile/SGPT_FORMAT.md) both ship in this package.
-
-<!--
-BENCHMARK TABLE - do not fill from memory or estimate. Needs a real measured run.
-Verified 2026-09-01: no end-to-end renderer frame-time measurement exists anywhere in this
-repository, and no measurement against three.js / PlayCanvas / Unity / Babylon exists in any form.
-Do not write "several times faster than three.js" until there is a reproducible run behind it.
-
-| Scene | Hardware | Resolution | Frame time | Draw calls | Triangles | Lights |
-|---|---|---|---|---|---|---|
-|   |   |   |   |   |   |   |
-
-To fill this, the following must be measured and recorded:
-  1. A PUBLIC scene. None currently exists - all four playground entry points are dev-server-only
-     and three need assets from the gitignored, unpublished `test_assets/`. Publishing one scene
-     the reader can open is a prerequisite for every row of this table.
-  2. Whole-frame time at a named resolution on a NAMED GPU (not "4070-class"), with the swap chain
-     confirmed not to be the limiter - volumetrics_froxel/README.md:83 records 1080p reading a flat
-     ~16.5 ms under presentation throttling, which is what makes its 28 ms figure at :189 unusable.
-  3. Draw-call and triangle counts from the same run - both are already in an .sgpt capture.
-  4. The same scene at two or three resolutions, to show the dynamic-resolution curve.
-  5. Optional and unusually strong: publish the .sgpt capture itself alongside the numbers.
-     The writer already ships; the viewer needs deploying (it is currently `"private": true`).
--->
+format specification (`src/shade/device/timing/profile/SGPT_FORMAT.md`) both ship in this package.
 
 ---
 
@@ -233,39 +202,39 @@ The rest of what a game needs, in the same package. Each links out to its own do
   with the determinism covered by replay tests - which is what lets it sit under rollback netcode.
   Convex and mesh collision, continuous collision detection for fast movers, and bodies that stop
   costing anything once they settle. A raycast vehicle, a character controller that handles stairs
-  and slopes, and inverse kinematics. [Fluid simulation](src/engine/physics/mls-mpm/README.md) is
+  and slopes, and inverse kinematics. [Fluid simulation](https://meep.company-named.com/docs/physics/fluid/) is
   separate and can run off the main thread.
 * **Audio.** The Wwise/FMOD feature set without the middleware: events, a mixer bus tree, real-time
   parameters, voice stealing, snapshots and ducking, all authored as engine data you can serialize.
-  Opt-in [acoustic simulation](src/engine/sound/simulation/README.md) adds occlusion, transmission
+  Opt-in [acoustic simulation](https://meep.company-named.com/docs/audio/overview/) adds occlusion, transmission
   and reverb driven by the scene's own geometry.
-* **[Networking](src/engine/network/README.md).** Server-authoritative rollback: client-side
-  prediction, reconciliation, and binary snapshots. Transports for WebRTC, WebTransport, WebSocket
-  and Node UDP, plus loopback and deliberately lossy ones for tests. Bandwidth metering, packet
-  record and replay, and cross-peer desync detection.
-* **Navigation & AI.** Grid A\*, and a [navigation mesh](src/engine/navigation/mesh/README.md) with
-  any-angle paths and obstacle carving at build time. Behaviour trees and blackboards, [Monte-Carlo
-  tree search](src/engine/intelligence/mcts/README.md) for agents that search a game tree rather
-  than follow one, and a planner for spending limited resources. Ray, box, frustum and point queries
-  against the scene.
-* **Procedural generation.** [A rule-driven grid generator](src/generation): cellular automata,
-  layered grids, rule sets that place markers and spawn entities, theme-driven selection. Generation
+* **[Networking](https://meep.company-named.com/docs/platform/networking/).** Server-authoritative
+  rollback: client-side prediction, reconciliation, and binary snapshots. Transports for WebRTC,
+  WebTransport, WebSocket and Node UDP, plus loopback and deliberately lossy ones for tests.
+  Bandwidth metering, packet record and replay, and cross-peer desync detection.
+* **Navigation & AI.** Grid A\*, and a [navigation
+  mesh](https://meep.company-named.com/docs/physics/navigation-meshes/) with any-angle paths and
+  obstacle carving at build time. Behaviour trees and blackboards, [Monte-Carlo tree
+  search](https://meep.company-named.com/docs/ai-and-simulation/) for agents that search a game tree
+  rather than follow one, and a planner for spending limited resources. Ray, box, frustum and point
+  queries against the scene.
+* **Procedural generation.** [A rule-driven grid
+  generator](https://meep.company-named.com/docs/generation/overview/): cellular automata, layered
+  grids, rule sets that place markers and spawn entities, theme-driven selection. Generation
   composes as tasks over shared state, so building a world is a graph of steps rather than a script.
 * **Assets & codecs.** glTF, including meshopt compression, loading into **entities** rather than
   one opaque tree. PNG, JPEG and AVIF decoded in-engine - the AV1 codec is a from-scratch encoder
   *and* decoder in pure JavaScript, no WebAssembly. Web-first asset streaming, and binary
   serialization that upgrades across versions.
-* **Tooling.** An in-app editor that attaches to and detaches from a running engine. [GPU profile
-  capture](src/shade/device/timing/profile/SGPT_FORMAT.md) that records per-pass timings and leaves
-  the build entirely when you don't import it. A software WebGPU implementation and a WGSL
-  interpreter, so shaders and pipelines are testable on machines with no GPU.
+* **Tooling.** An in-app editor that attaches to and detaches from a running engine. GPU profile
+  capture that records per-pass timings and leaves the build entirely when you don't import it. A
+  software WebGPU implementation and a WGSL interpreter, so shaders and pipelines are testable on
+  machines with no GPU.
 * **Everything smaller.** Input across touch, mouse, keyboard and gamepad behind one abstraction ·
   an optional DOM UI layer, replaceable with React or Vue · colour management with perceptual
   spaces, HDR transfer functions, tone mapping and gamut clipping · node graphs · achievements ·
   localisation · key-value storage over IndexedDB.
 
-Held to **~15,000 tests** - determinism, adversarial and shader-emulation suites among them.
-
 ---
 
 ## Shipping a build
@@ -298,5 +267,5 @@ raise that ceiling for a one-time fee per project, and add 24 months of major-ve
 Short version: ship anything you like, just don't redistribute the source and don't build a
 competing engine.
 
-See [LICENSE](LICENSE) for the terms covering this package, and the
+See the `LICENSE` file in the package for the terms covering this package, and the
 [pricing page](https://meep.company-named.com/pricing/) for the tier ladder.

package/package.json

@@ -6,7 +6,7 @@
   "description": "Advanced 3D game engine",
   "type": "module",
   "author": "Alexander Goldring",
-  "version": "3.14.0",
+  "version": "3.14.2",
   "exports": {
     "./build/*": "./build/*",
     "./src/*": "./src/*",