@hyperfixi/types-browser 7.2.0 → 7.4.0

package/CHANGELOG.md

@@ -7,6 +7,90 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 
 ## [Unreleased]
 
+## [7.4.0] - 2026-10-21
+
+Content htmx or fixi swaps in runs its hyperscript, as it does on upstream `_hyperscript`: the
+engine has upstream's htmx integration in every bundle, and loading the engine twice no longer
+binds every handler twice. A minor: new behavior and a deprecated option, nothing removed.
+
+### Fixed
+
+- **`@hyperfixi/engine`: content htmx or fixi swaps in runs its hyperscript, and htmx content a
+  script puts in issues its requests.** Upstream `_hyperscript` has this integration in its core
+  runtime and the engine had none: a `_="on click …"` that htmx swapped in did nothing, and an
+  `hx-get` that a script `put` into the page was never wired. The engine now has upstream's
+  integration (0.9.93's `htmx-compat.js`), installed by `boot()` in every bundle, the Vite
+  plugin's included: `htmx:load` (htmx 2) and `htmx:after:process` (htmx 4) process the content,
+  an after-process hook hands what a script inserts to `htmx.process`, and on htmx 4 it
+  registers upstream's `hs-include` extension (`hs-include=":id"` sends element-scoped variables
+  with the request; `htmx.config.extensions = "hs-include"` enables it). Two additions upstream
+  lacks: fixi (`fx:swapped` processes the swapped content), and pages with their own hooks
+  between the two (`htmx.onLoad(el => _hyperscript.process(el))`,
+  `_hyperscript.addAfterProcessHook(el => htmx.process(el))`, the workarounds until now) no longer
+  recurse, where upstream recurses until the stack runs out. The workarounds can be removed. The
+  first vendoring of upstream's suite left out its htmx tests (`integration/htmx.js`,
+  `ext/hs-include.js`), which is how the gap shipped; the gate now runs them and passes all 19
+  (1422/1486). `hyperfixi-hs.js` grows 0.7 KB gzipped, to 34.9 KB.
+- **`@hyperfixi/engine`: loading the engine twice no longer binds every handler twice.** Element
+  state was private to each copy of the engine, so the second copy initialised every element
+  again and one click ran its handler twice. htmx 4's boosted swaps run body scripts again, so
+  boost, then back, did it on a page that loads the engine at the end of its body. The state is
+  now `elt._hyperscript`, where upstream keeps it and a second copy finds it (two more of
+  upstream's tests pass).
+- **Examples: sortable-list's Add Task added a blank task and threw.** Its script read the input
+  with `first #new-item-input`, which is null (`first` of one element), and now reads the element
+  itself. tell-command's code sample shows its `on click`.
+
+### Deprecated
+
+- **`@hyperfixi/vite-plugin`'s `htmx` option does nothing.** It added a listener for htmx 2's
+  event names, which htmx 4 does not fire; the engine's integration covers every bundle. The
+  option is still accepted, so existing configs build.
+
+## [7.3.0] - 2026-10-21
+
+`@hyperfixi/mcp-server` lists its 14 core tools by default and keeps the other 70 in toolsets
+that `LOKASCRIPT_MCP_TOOLSETS` lists, and five of its tools that were broken work. A minor, as
+when the sampling tools went opt-in (2.11.0): every tool still answers a call by name, and the
+variable lists any of them again.
+
+### Changed
+
+- **`@hyperfixi/mcp-server` lists 14 core tools by default; the other 70 are in opt-in
+  toolsets.** A connection listed all 84: about 13k tokens of definitions in each client that
+  loads them all, and a month of sessions called 7 of them. The default list is the agent loop
+  and what it leans on (`validate_and_compile`, `get_diagnostics`, `get_code_fixes`,
+  `get_command_docs`, `get_expression_docs`, `search_patterns`), translation (`translate_code`,
+  `translate_to_english`, `get_keyword_translations`, `list_supported_languages`), proof that
+  a change kept its meaning (`score_fidelity`, `diff_behaviors`), and `detect_domain` /
+  `compile_auto`: about 2.5k tokens. Set `LOKASCRIPT_MCP_TOOLSETS` to list more: `domains`
+  (26), `lse` (13), `grail` (5), `debug` (4), `editor` (3), `analysis` (9), `profiles` (5),
+  `project` (5), comma-separated, or `all`. Only the list changes: every tool still answers a
+  call by name. A client that picks tools from the list (Claude Code, Claude Desktop) needs
+  the variable to see a tool outside the core; the README lists each toolset's tools (#1607).
+
+### Fixed
+
+- **`lse_from_hyperscript` returned `[get patient:null]` for every input**, with `ok: true` and
+  confidence 1: it read the semantic parse as the AST builder's tree. It now renders the parse,
+  and refuses (`ok: false`, the rendered LSE under `partial`) a parse that left input unread or
+  a shape whose LSE does not parse back, such as a `then` chain inside a handler (#1607).
+- **`extract_routes` and `generate_server_routes` threw on every input** ("Cannot read
+  properties of undefined"), from the day they were added: they read `.routes` from the array
+  `scanRoutes` returns. They report server-bridge's route conflicts where they promised an
+  `errors` field it never had. The import that hid this from the typecheck (an untyped ambient
+  module) is gone (#1607).
+- **`get_code_fixes` had no fixes for the codes `validate_and_compile` emits**
+  (`ENGINE_PARSE_ERROR`, `UNCONSUMED_INPUT`, …), though the server's instructions send an agent
+  there from its diagnostics; `get_diagnostics`' `parse-error` and `low-confidence` mapped to
+  keys that did not exist. Every code compilation-service emits now has fixes, and a test holds
+  that (#1607).
+- **`explain_code` listed commands by kind, not in the order they run** (toggle → wait → add
+  came out "toggles … adds … waits") and dropped their targets. It explains the parse now: each
+  step rendered back to English with what it does, a block's body and an `if`'s two branches (#1607).
+- **`get_diagnostics`' typo fix was titled `Fix typo: ${suggestion}`**, unfilled, with no edit.
+  It now reads "Fix typo: toggle" with an edit that replaces the misspelled word (#1607).
+
 ## [7.2.0] - 2026-10-20
 
 `@hyperfixi/mcp-server` moves to `@lokascript/domains` 7.1.0: learn left the domains for

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@hyperfixi/types-browser",
-  "version": "7.2.0",
+  "version": "7.4.0",
   "description": "TypeScript definitions for the hyperfixi browser globals: window.hyperfixi / window._hyperscript (the engine), LokaScriptSemantic, LokaScriptI18n",
   "type": "module",
   "types": "dist/index.d.ts",
@@ -30,7 +30,7 @@
   "author": "LokaScript Contributors",
   "license": "MIT",
   "devDependencies": {
-    "@hyperfixi/engine": "^7.2.0",
+    "@hyperfixi/engine": "^7.4.0",
     "typescript": "^5.8.3"
   },
   "publishConfig": {