@woosh/meep-engine 3.14.0 → 3.14.1

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.
 
 ---
 
@@ -197,29 +184,6 @@ the frame-graph structure, dispatch and draw counts. Assign a
 `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`).
--->
-
 ---
 
 ## Everything else
@@ -264,8 +228,6 @@ The rest of what a game needs, in the same package. Each links out to its own do
   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

package/package.json

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