@hyperfixi/server-bridge 7.5.1 → 7.6.0

package/CHANGELOG.md

@@ -7,6 +7,109 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 
 ## [Unreleased]
 
+## [7.6.0] - 2026-11-10
+
+The engine takes extensions: upstream's `tailwind` and `socket` load from a script tag or
+`register(...)`, and the Vite plugin bundles them. Spanish and Portuguese handlers agree with their
+event (`a la entrada`, `à mudança`), and German writes an event as the noun it is (`wenn Klick`).
+A minor: new features, and renders that change in es, pt and de; everything written before still
+reads.
+
+### Added
+
+- **`@hyperfixi/vite-plugin`: `extensions: ['socket', 'tailwind']`.** The generated bundle
+  imports each `@hyperfixi/engine/ext/<name>` and registers it after the modules, and the dev
+  `everything` fallback does too. Extensions are opt-in, so the scan never adds one. A project
+  that lists an extension gets an engine bundle even when the scan found nothing else (a page
+  whose only hyperscript is a `socket`).
+  - **Which module comes with `toggle` is now read from the grammar.** The plugin used to have
+    the rule "`toggleElement` comes with `toggle`" written in; it now reads which modules add
+    a reading to a command (`Grammar.fallbacks`).
+  - **`verify:reference` checks the engine's extensions as its own.** It registers each
+    `dist/ext/<name>.esm.js`, documents their keywords like the engine's, and parses their
+    examples: `socket`'s hover example is now checked, where it was skipped as "upstream's".
+
+- **`@hyperfixi/engine`: extensions that a script tag can load.** After `hyperfixi-hs.js`, a page
+  can load `ext/<name>.js`, which registers its module with the page's engine. Or, from ESM,
+  `register(...everything, tailwind)` with `@hyperfixi/engine/ext/tailwind`.
+  - **The first extension is upstream's `tailwind`** (the `twDisplay`, `twVisibility` and
+    `twOpacity` hide/show strategies), and upstream's 12 tests for it are now in the engine's
+    gate: 1,434 of 1,498.
+  - **The public object gains `register` and `extensions`, and the script-tag bundle's also gains
+    `kit`.** `register` adds modules. `extensions` lists the extension files the page has
+    loaded. `kit` holds what a module may call: the same names the library entry exports for
+    module authors. Only `hyperfixi-hs.js` carries the kit, so a bundle built from ESM (the Vite
+    plugin's) keeps only the parts of the engine it uses; it registers extensions from ESM, and an
+    extension file loaded beside it says so.
+  - **`register` skips a module it has already added.** When it does add one, it reads again
+    the elements whose scripts failed to parse, so an `async` or late-loaded extension still
+    applies.
+  - **Upstream's own `ext/tailwind.js` also runs on the engine unchanged**, through `use`.
+- **`@hyperfixi/engine/ext/socket`: upstream's `socket` feature.** `socket Chat ws://… [with
+timeout n] [on message [as JSON] …] end` defines `Chat`, a WebSocket with `raw`,
+  `dispatchEvent` (`send ping to Chat` sends the event as JSON) and an `rpc` proxy
+  (`Chat.rpc.f(…)` returns a promise for the reply).
+  - **Upstream's 16 socket tests pass:** the suite is 1,450 of 1,498, with 48 known failures.
+  - **Two differences from upstream:** the socket opens when the feature is installed, not
+    when it is parsed, so a parse alone opens nothing; and with `as JSON` a message that is
+    JSON `0`, `false` or `null` is that value, where upstream rejects it.
+  - **The kit grows to what a feature needs:** `dotOrColonPath`, `urlOrExpression`,
+    `evalStatic`, `commandList`, `makeContext`, `runList` and `assignToNamespace`. Each is
+    exported from `@hyperfixi/engine` and carried on `hyperfixi-hs.js`'s `_hyperscript.kit`.
+
+### Changed
+
+- **`@lokascript/semantic`: a Spanish or Portuguese handler's head agrees with its event, and
+  German writes an event as a noun.** Renders only; everything written before still reads.
+  - **es, pt:** `al` and `ao` hold the masculine article, and were written before every event
+    (`al entrada agregar .a`, `ao mudança de #search …`). A feminine event takes `a la` and `à`:
+    `a la entrada agregar .a`, `à mudança de #search disparar envio em #form`. The first event of
+    an `or` decides; an infinitive (`al redimensionar`) and a custom name (`al my:event`) keep the
+    masculine. Each profile lists its feminine event words (`eventHandler.feminineEventMarker`).
+    es reads `a la` as the head only before one of them, so `poner x a la` is still a put into a
+    variable named `la`. pt's `à` joins its letters and prepositions.
+  - **de:** an event's word takes its capital wherever a command names one: `wenn Klick`,
+    `wenn Änderung von #search auslösen Absenden auf #form`, `warten Änderung`. An event with no
+    German word stays code (`wenn keyup`). The event table lists each one-word name both ways, so
+    `wenn klick` and `wenn doppelklick` read as before.
+
+- **`@hyperfixi/engine`: a module can add a reading to a command without changing what the
+  command reads (`Grammar.fallbacks`).** A fallback registered for a keyword is tried, from just
+  after the keyword, only when the command's own rule fails to parse, and it counts only if it
+  reads at least as far as that rule got. `toggle <element>` (the `toggleElement` module) is now
+  one. Every `toggle` that upstream reads now goes through upstream's rule exactly (registering
+  `toggleElement` used to send every `toggle <target>` through a different expression rule).
+  An unfinished upstream `toggle` now reports upstream's error: `toggle #d as` used to say
+  `Expected 'modal'`, and now says `Expected dotOrColonPath`, as upstream does. The
+  `Grammar.toggleElement` slot is gone; a module that set it registers a fallback instead.
+  `Parser` gains `mark()` and `reset()`.
+
+### Fixed
+
+- **`@lokascript/semantic`: a translated `socket` comes back as the socket upstream reads.**
+  A socket's `on message [as JSON] …` is its own clause, closed by the socket's one `end` (or
+  by the end of the script). Semantic read it as an event handler, eventsource's shape, so:
+  - a clause closed by `end` came back with a second `end`, in every language. The engine
+    rejects that, so a translated socket failed to parse on the page;
+  - a clause with no `end` (upstream's tests write them that way) lost its body, and a
+    clause's `as JSON` was read as leftover input. `translate` refused both;
+  - a dotted name came back split: `socket MyApp.chat …` became `socket MyApp .chat …`, a
+    different socket.
+
+  `as JSON` is now written with the language's own word for `as`, as a conversion is (es
+  `como JSON`, ja `として JSON`). Text semantic wrote before, with two `end`s, still reads as
+  the one socket it was.
+
+  Where a language puts its handler word after the event (ja `messageで`, tr `message da`), a
+  socket or eventsource whose body starts with a word that looks like an event (ja
+  `messageで messageを 記録`, "on message log message") now reads. The handler word used to
+  be taken as the start of the body.
+  - **Measured by the command-shape gate, which now reads extension syntax.** Its engine
+    registers every extension the engine builds. Its harvest reads upstream's `ext/` tests,
+    and the scripts a test writes as `textContent` (how upstream's socket tests write theirs).
+    That adds 33 cases (1,168 in all), and each passes in all 24 lanes. Before this fix, 4 of
+    the 16 socket cases were refused in every language and 1 was silent in every language.
+
 ## [7.5.1] - 2026-10-23
 
 The last two silent misreads of hand-written non-English hyperscript that the 7.3.0 live test

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@hyperfixi/server-bridge",
-  "version": "7.5.1",
+  "version": "7.6.0",
   "description": "Extract server route contracts from hyperscript/htmx HTML and generate server-side route scaffolding",
   "type": "module",
   "sideEffects": false,
@@ -30,7 +30,7 @@
   },
   "devDependencies": {
     "@lokascript/domains": "^7.1.0",
-    "@types/node": "^26.6.5",
+    "@types/node": "^26.6.6",
     "tsup": "^9.0.0",
     "typescript": "^5.0.0",
     "vitest": "^5.0.5"