@patterkit/runtime 0.10.0 → 0.12.0

package/CHANGELOG.md

@@ -33,6 +33,32 @@ version number always means the same runtime behaviour. This package is versione
 
 ## [Unreleased]
 
+## [0.12.0] - 2026-09-04
+
+### Changed
+
+- **`patterplay.min.js` moved to `@patterkit/play-helpers`, and carries the helpers.** The browser
+  drop-in used to be this package's own build, runtime alone, so a plain page with no bundler could
+  play but not write the family's save text. It is now built by the play-helpers package (the one
+  that depends on both) with the runtime AND the helpers under the one `Patterplay` global. The
+  play-js release still ships it loose and in the zip; on a CDN it now lives at
+  `@patterkit/play-helpers/dist/patterplay.min.js`, and this npm package no longer contains it.
+  (Asked for by the Storylets side, whose drop-in took the same shape the same day.)
+
+## [0.11.0] - 2026-09-03
+
+### Changed
+
+- **The `patter/save@0` shape is the family's contract, and its types live in `@patterkit/model`.**
+  `SaveEnvelope`, `SaveGame`, `FlowSnapshot`, `FlowCursor` and the rest are exported from the model
+  with `SAVE_SCHEMA`, and re-exported here so existing imports keep working. Nothing this runtime
+  writes has changed: its output was always this shape. The three native ports now write and read
+  it too, so a save crosses engines, and the conformance corpus carries a save this runtime wrote
+  that every runtime must load, write back with the same key paths, and continue.
+- **A host-scope declaration's `writable: false` is pinned as the story's promise**, refused whether
+  the scope is bound by the game or self-backed. This runtime always did so; the test now says it
+  in one place, and the three native ports match it from this version.
+
 ## [0.10.0] - 2026-09-02
 
 ### Added

package/README.md

@@ -15,11 +15,13 @@ Three equivalent channels - pick whichever fits how you work; **no npm is requir
 - **Release zip**: `patterplay-js-<version>.zip` on every
   [`play-js-v*` GitHub Release](https://github.com/patterkit/patter/releases) - this
   runtime as a plain download, symmetric with the Unity / Unreal / Godot plugin zips.
-  It carries `patterplay.min.js` (the `<script>` drop-in), the module builds under
-  `dist/` (ESM + CJS + types, for vendoring into your own build), this README, the
-  CHANGELOG, and two `demos/` (the zero-build drop-in page and the interactive tour).
+  It carries `patterplay.min.js` (the `<script>` drop-in: this runtime plus
+  `@patterkit/play-helpers` under one global), the module builds under `dist/` (ESM + CJS +
+  types, for vendoring into your own build), this README, the CHANGELOG, and two `demos/`
+  (the zero-build drop-in page and the interactive tour).
 - **npm**: `npm install @patterkit/runtime` (same version as the zip).
-- **CDN**: `patterplay.min.js` via unpkg/jsDelivr, or loose on the same Release.
+- **CDN**: `patterplay.min.js` via unpkg/jsDelivr from `@patterkit/play-helpers` (the package
+  that builds it), or loose on the same Release.
 
 ## Use it (npm / bundler)
 
@@ -58,19 +60,22 @@ its own system, then applies `{@ref}` replacement with **`flow.interpolate(yourS
 ## Drop-in (`<script>`)
 
 `patterplay.min.js` is a single self-contained, minified IIFE - every dependency
-inlined - for plain HTML pages with no bundler:
+inlined - for plain HTML pages with no bundler. It carries this runtime AND
+[`@patterkit/play-helpers`](../play-helpers) on the one `Patterplay` global, so a plain
+page can also write and read the family's save text:
 
 ```html
-<script src="https://unpkg.com/@patterkit/runtime/dist/patterplay.min.js"></script>
+<script src="https://unpkg.com/@patterkit/play-helpers/dist/patterplay.min.js"></script>
 <script>
-  const { Engine } = window.Patterplay;     // also: Flow, gameDataFields, gameDataValue, effectiveGameData
-  const flow = new Engine(BUNDLE).openFlow("main", { scene: "square" });
-  // ...advance() / choose() exactly as above.
+  const { Engine, serializeState, deserializeState } = window.Patterplay; // also: Flow, gameDataFields, createStateLogger, ...
+  const engine = new Engine(BUNDLE);
+  const flow = engine.openFlow("main", { scene: "square" });
+  // ...advance() / choose() exactly as above; localStorage.setItem("slot1", serializeState(engine)) to save.
 </script>
 ```
 
-Build it locally with `npm run build -w @patterkit/runtime` (emits
-`dist/patterplay.min.js`).
+It is built by the play-helpers package, the one that depends on both: `npm run build -w
+@patterkit/play-helpers` (emits `packages/play-helpers/dist/patterplay.min.js`).
 
 ## Demos