@lokascript/planner 4.0.0 → 4.0.1

package/CHANGELOG.md

@@ -7,6 +7,40 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 
 ## [Unreleased]
 
+## [4.0.1] - 2026-10-05
+
+Fixes for 4.0.0: the per-language adapter bundles read every language again, and the MCP server's
+documentation and core's metadata describe the 4.0 engine.
+
+### Fixed
+
+- **`@lokascript/hyperscript-adapter`: the self-contained per-language and regional bundles read
+  German, French, Quechua and Chinese again.** `hyperscript-i18n-<lang>.global.js` and the regional
+  bundles installed a generate-only pattern generator over the one `@lokascript/semantic/core`
+  provides, discarding its hand-crafted patterns: in de, fr, qu and zh even
+  `on click toggle .active` stayed untranslated (the host then rejected it), and other languages
+  lost shapes such as `toggle … on #target`; 1106 of the corpus's 3772 translations read
+  differently from the full package. Published 3.x and 4.0.0 bundles alike; the all-languages
+  `hyperscript-i18n.global.js` was unaffected. The bundles now keep `/core`'s generator (sizes
+  unchanged: the ~23 KB 4.0.0 added was this generator, unused until now). Their English renderer
+  also drops only an implicit `me` now, so `put "x" into me` no longer renders as the
+  engine-invalid `put "x"` in every language. New gate: every built bundle runs translated
+  handlers on the engine (`test/adapter-iife.test.ts`).
+- **`@hyperfixi/mcp-server`'s documentation resources teach upstream's spelling.**
+  `hyperscript://docs/commands`, `/expressions`, `/events` and `hyperscript://examples/common` still
+  taught core 3.x: `on submit.prevent`, `on input.debounce(300ms)`, `on keydown.enter`,
+  `swap #t innerHTML`, `while …`, a bare `[attr]` selector, a `parent` keyword, `you` as the event
+  target. The engine rejects those, or reads them as something else (`on click.prevent` listens for
+  an event named `click.prevent`). A test now parses every example on the engine. The repo's
+  `hyperfixi-developer` skill, generated from them, follows (`generate:skills` had been writing to
+  the wrong directory).
+- **`@hyperfixi/core/metadata` describes 4.0.** `packageInfo.description` still said "Modern
+  hyperscript engine with fixi/htmx integration" and `compatibility` "~85% official _hyperscript",
+  both 3.x claims. `packageInfo.upstreamSuite` (`{ version, passed, total }`) now publishes the
+  engine's result on upstream _hyperscript's own test suite (1401 of 1467 in 0.9.93), and
+  `compatibility` is derived from it; `verify:reference` fails when it disagrees with
+  `packages/engine/upstream-suite/known-failures.json`. `ecosystem` drops "212 LLM examples".
+
 ## [4.0.0] - 2026-10-04
 
 `@hyperfixi/core`'s own hyperscript engine is gone: its root re-exports `@hyperfixi/engine`, and
@@ -1061,7 +1095,9 @@ _Synchronized version release. See git history for details._
 - npm access token stored in GitHub Secrets
 - 2FA recommended for npm organization
 
-[Unreleased]: https://github.com/codetalcott/hyperfixi/compare/v3.3.0...HEAD
+[Unreleased]: https://github.com/codetalcott/hyperfixi/compare/v4.0.1...HEAD
+[4.0.1]: https://github.com/codetalcott/hyperfixi/compare/v4.0.0...v4.0.1
+[4.0.0]: https://github.com/codetalcott/hyperfixi/compare/v3.3.0...v4.0.0
 [3.3.0]: https://github.com/codetalcott/hyperfixi/compare/v3.2.0...v3.3.0
 [3.2.0]: https://github.com/codetalcott/hyperfixi/compare/v3.1.0...v3.2.0
 [3.1.0]: https://github.com/codetalcott/hyperfixi/compare/v3.0.0...v3.1.0

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@lokascript/planner",
-  "version": "4.0.0",
+  "version": "4.0.1",
   "description": "BFS planner over affordance graphs — cost-aware planning with preconditions, effects, and template parameters",
   "type": "module",
   "main": "dist/index.cjs",