@hyperscript-tools/language-server 3.1.0 → 3.2.0

package/CHANGELOG.md

@@ -7,6 +7,174 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 
 ## [Unreleased]
 
+## [3.2.0] - 2026-09-30
+
+A correctness release for multilingual hyperscript. The semantic parser behind
+`translate()`, `@lokascript/hyperscript-adapter`, MCP `translate_code` and hyperfixi's
+non-English path now keeps whole programs that it used to shorten or drop: values,
+conditions, loops and handler heads. Every value shape in a generated matrix of 4,205
+(executed in 24 languages, directly and through the adapter, against upstream
+\_hyperscript) now matches upstream, apart from two documented differences. Core
+matches upstream \_hyperscript on more forms.
+
+### Added
+
+- **Counted loops are written in each language's own words**: es `repetir 3 veces`,
+  fr `répéter 3 fois`, ja `3 回 を 繰り返し`, hi `3 बार को दोहराएं`, where translations
+  wrote English `times` in 18 languages and English `repeat` in the SOV six. English
+  `times`/`repeat` and each language's other count words (es `vez`, ru `раза`, …) still
+  read. 18 i18n dictionaries gain a `temporal.times` word.
+- **Variable names that are words of the target language.** A variable spelled like a
+  structure word (es `si`, pl `w`, tr `al`) is written in parentheses, `(si)`, where the
+  plain translation would be misread, and read back as the variable. The language server
+  warns (`name-collision`, with a rename quick fix), MCP `validate_hyperscript` reports
+  `NAME_COLLISION`, and `translate_code` warns when a variable reads as a value word in
+  the target (tl `ako` is `me`). `@lokascript/semantic` exports `nameCollision`,
+  `findNameCollisions` and `findTranslationCollisions`.
+- Event-handler modifiers (`once`, `debounced at`, `throttled at`, `from`) render in every
+  language and are scored by the fidelity signals.
+- `of`-paths and pseudo-commands (`reset() the closest <form/>`) survive translation.
+- `@lokascript/hyperscript-adapter`'s host gate also rejects a translation that reads a
+  reference as a handler's event (`on click on me toggle .active`, an empty click handler
+  plus a handler for an event named `me`), falling back to the author's text with a
+  warning; such a translation used to parse cleanly and do nothing.
+- **Localized htmx attributes: all 23 non-English languages now cover
+  every attribute the _Hypermedia Systems_ book's code listings use** —
+  `hx-vals`, `hx-select`, `hx-swap-oob` and `hx-sync` join the Contact.app
+  twelve (`hx-値`, `hx-valores`, `hx-값`, `hx-werte`, `hx-選択`, `hx-selección`,
+  `hx-seçim`, `hx-auswahl`, `hx-sélection`, `hx-选择`, …). tr/de/fr/zh are new
+  in the table: the Contact.app seven they lacked (`hx-sil`, `hx-löschen`,
+  `hx-supprimer`, `hx-删除`, …) plus audited trigger/swap primaries following
+  loka-js (`hx-tetikleyici`, `hx-auslöser`, `hx-déclencheur`, `hx-替换`; the
+  profile words `hx-tetikle`, `hx-auslösen`, `hx-déclencher`, `hx-交换` still
+  resolve). de gains a lowercase `hx-ziel`: the profile's `hx-Ziel` could never
+  match a parsed attribute, since HTML lowercases attribute names. The other
+  15 languages (ar, bn, he, hi, id, it, ms, pl, qu, ru, sw, th, tl, uk, vi)
+  are unreviewed drafts, every entry flagged `lowConfidence`; they also gain
+  the trigger heads their dictionaries left in English (ms and tl all six,
+  vi/he/ar some). id gains `hx-sasaran` for a target that was the English
+  identity; tl keeps `hx-target` on purpose. `hx-ext` is left in English on
+  purpose: htmx 4 removed it. The vocab table gains an `events` block for
+  trigger heads the i18n dictionaries do not name; ja, es, pt and ko author
+  the DOM `search` event (`検索`, `buscar`, `검색`), which the book's and
+  Contact.app's search box fires. htmx's own trigger words (`revealed`,
+  `every`) stay English, like the `delay:` / `from:` modifiers.
+- Adapter-only vocab keys now resolve from the authored table alone, never
+  from a semantic profile: 22 profiles carry a `select` keyword that means
+  mark/highlight text (de `markieren`, tr `vurgula`), and it would otherwise
+  have shipped as `hx-select` in 22 unreviewed languages.
+
+- **Localized htmx attributes: ja, es, pt and ko now cover every attribute the
+  _Hypermedia Systems_ Contact.app uses** — `hx-post`, `hx-delete`,
+  `hx-confirm`, `hx-push-url`, `hx-boost`, `hx-indicator` and `hx-include` join
+  the existing five (e.g. `hx-削除`, `hx-eliminar`, `hx-excluir`, `hx-삭제`).
+  `hx-indicator` / `hx-include` localize under `@hyperfixi/htmx-adapter` (stock
+  htmx implements them; the embedded layer does not).
+- **Vocab aliases.** Several localized names may map to one attribute or event;
+  the first is the form to teach, later ones keep already-authored pages
+  working. Core's embedded orchestrator now reads whichever form an element
+  carries (it previously kept a single name per attribute).
+
+### Changed
+
+- **Rendered vocabulary** (owner decisions): `null` is written `null` in ar, hi, id, qu,
+  sw, th and tr, where it shared the word for `empty`; hi writes `no` as `कोई नहीं`; qu
+  writes `and` as `hinallataq`; tl and tr write `includes` with `contains`' word (both
+  engines read the two as one operator).
+- `@lokascript/semantic` exports its real `VERSION` (it was `0.1.0` since the first
+  release); browser bundles report `<version>-<bundle>`.
+- MCP `translate_hyperscript` is described accurately: it uses the same semantic engine as
+  `translate_code`, without the verification.
+- **Audited primaries for `hx-trigger` / `hx-swap`** in ja (`hx-トリガー`,
+  `hx-置換`), es (`hx-disparador`, `hx-intercambio`), pt (`hx-gatilho`,
+  `hx-troca`) and ko (`hx-교체`), following loka-js's terminology reviews. The
+  names that shipped before (`hx-引き金`, `hx-disparar`, …) still resolve.
+- The vocab modules are regenerated against the current i18n dictionaries.
+  **No working name was removed** — 141 retired event names and three attribute
+  names are kept as aliases. One name changed meaning with its dictionary: sw
+  `panya_juu` is now `mouseup` (was `mouseover`).
+
+### Fixed
+
+- **Translations that lost code** (semantic parse and render, in every language):
+  - `get` of a literal (`get "hello"`, `get 3`, `get true`) dropped the whole command; an
+    object literal after `get` was cut to `get {`.
+  - Loops keep their extent and body; `repeat until` stops; a loop keeps its index
+    variable, the tail after an `if` inside it, and the command after an empty loop its own
+    `end` closes; a count may be any value (a variable, `$n`, `it`, a possessive), where
+    some translations read `forever`, a silent infinite loop.
+  - Handler heads keep `or` events, filters and event parameters; a translated
+    `wait for <event>` waits instead of throwing; behaviors keep their handlers and init
+    blocks; an else-if chain shares one `end`.
+  - Values keep their comparison phrases (`is equal to`, `includes`, `is an Element`, …),
+    `and`/`or`/`not`, `mod`, possessive and `of` chains, object and array literals, every
+    conversion core supports (`as Int`, `as Fixed:2`, piped conversions), unary minus and
+    property paths; `true`/`false`/`null` keep their meaning.
+  - Commands keep `put … into <variable>`, `tell … to show`, fetch's `do not throw` and
+    response type, event-source/socket URLs, show/hide `with` strategies, `go`/`scroll`
+    positions, `${…}` URLs, core's `has`, and a class query's `in` scope.
+- **`@hyperfixi/core` follows upstream \_hyperscript**:
+  - `X of Y` binds as property access, and the X of a null target is null.
+  - `increment` reads its amount and counter as upstream does, and writing an object's
+    property through `'s`/`of` works.
+  - A loop's count reads as upstream's `index < times` does: `"6.5"` loops 7 times and
+    `"6abc"` none, in the full runtime and in the hybrid bundles (`hyperfixi-hx.js`,
+    plugin bundles), which read `parseInt`.
+  - Blocks close at the end of input; `morph … to`; `render … with name: value`; `beep!`
+    as an expression; `transition`'s owners, several properties, `from` and `using`; three
+    handler forms from _Hypermedia Systems_; four upstream-valid forms that compiled and
+    then failed at run time; `.item in #list` keeps its scope; `on click once` fires on
+    the first click.
+- htmx: camelCase event names survive an attribute name.
+- MCP: the validators report what the parsers actually did.
+- The AOT compiler (experimental): loops were compiled to `while (true)`; targets,
+  property access, scoped queries, `empty` and variable scope now compile to what they
+  mean.
+- `@lokascript/hyperscript-adapter` and `@hyperscript-tools/multilingual` READMEs: the
+  Japanese quickstart example was a dead button, and the multi-language example loaded
+  only the Spanish bundle; the examples are now native and run in a test. Bundle sizes are
+  measured.
+- Bare CDN URLs now serve a browser bundle: `unpkg.com/@lokascript/hyperscript-adapter@3` (and
+  jsDelivr) served `dist/index.cjs`, which throws in a `<script>` tag. The adapter,
+  `@hyperscript-tools/multilingual`, `@lokascript/semantic`, `@hyperfixi/core` and
+  `@lokascript/htmx-adapter` declare `unpkg`/`jsdelivr` entries.
+- `hyperfixi-multilingual.js`'s error names the semantic bundle that exists (the full
+  `browser.global.js`, the only one that defines `LokaScriptSemantic`).
+- READMEs: `@lokascript/i18n` no longer claims to translate (and its `/lsp` export and CLI,
+  which do not exist, are gone); `@lokascript/semantic`, `@hyperfixi/vite-plugin` and
+  `@hyperfixi/core` have correct package names, API calls, language lists (24) and measured
+  bundle sizes.
+- Dependencies: the js-yaml and smol-toml advisories; Vite 8, vitest 5 and happy-dom 20.14.
+- **Vietnamese `hx-get` / `hx-target` / `hx-swap` / `hx-trigger` / `sse-swap`
+  never worked**: the names were emitted with spaces (`hx-lấy giá trị`), which
+  HTML reads as three attributes. They are now hyphen-joined
+  (`hx-lấy-giá-trị`), like vi's existing `hx-trực-tiếp`.
+- 29 multi-word event names (ar, vi) were removed from the vocab modules: an
+  event is a single token of an `hx-trigger` value, so they could never match.
+
+## [3.1.1] - 2026-09-04
+
+### Fixed
+
+- **`@hyperfixi/mcp-server` no longer installs two copies of the contract
+  packages.** 3.1.0 pinned `@lokascript/domains ^2.11.1`, whose framework /
+  semantic / intent were hard 2.x dependencies — a clean install got 3.1.0 at
+  the top level and 2.11.1 nested under domains, and every `DomainRegistry` /
+  schema singleton forked across that boundary. mcp-server, framework and
+  server-bridge now range on `@lokascript/domains ^3.0.0`, which peers on
+  framework 3.x instead.
+
+### Added
+
+- **`scripts/check-domains-peer-major.cjs`** — the cross-repo guard for that
+  class: the domains version the lockfile pins must PEER (not depend) on
+  framework / semantic / intent at a range the version this repo publishes
+  satisfies. Runs in `lint-typecheck`, first thing in `publish.yml` after the
+  version bump, and from the pre-commit hook. `examples/release-smoke/run.mjs`
+  additionally asserts one installed copy of each contract package, and
+  Dependabot now gives `@lokascript/domains` its own PR group so a domains
+  release is visible on its own instead of riding the weekly tooling PR.
+
 ## [3.1.0] - 2026-09-04
 
 ### Added

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@hyperscript-tools/language-server",
-  "version": "3.1.0",
+  "version": "3.2.0",
   "description": "Language Server Protocol implementation for original _hyperscript — completions, diagnostics, hover docs",
   "type": "module",
   "main": "dist/server.js",
@@ -25,14 +25,14 @@
   "author": "HyperFixi Contributors",
   "license": "MIT",
   "dependencies": {
-    "@lokascript/language-server": "^3.1.0"
+    "@lokascript/language-server": "^3.2.0"
   },
   "devDependencies": {
-    "@types/node": "^26.1.2",
+    "@types/node": "^26.6.3",
     "tsup": "^8.0.0",
-    "tsx": "^4.23.1",
+    "tsx": "^4.23.15",
     "typescript": "^5.0.0",
-    "vitest": "^4.1.5"
+    "vitest": "^5.0.2"
   },
   "files": [
     "dist",