@hyperscript-tools/i18n 3.0.0 → 3.1.1

package/CHANGELOG.md

@@ -7,6 +7,206 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 
 ## [Unreleased]
 
+## [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
+
+- **`hyperscript.use(frontEnd)`** — register the multilingual front-end
+  `compile()` consults for a non-English program (and `toLSE`/`fromLSE` for
+  a semantic node and a renderer). The contract is `FrontEnd` in
+  `@hyperfixi/core` (`parseToAST`, optional `parse`/`render`);
+  `@lokascript/semantic` satisfies it through
+  `createBridgeFrontEnd(new SemanticGrammarBridge())` from
+  `@hyperfixi/core/multilingual`. The full browser bundle registers it at
+  boot. The library entry registers nothing and, through 3.x, builds the same
+  bridge lazily on the first non-English compile — so nothing changes for a
+  consumer with `@lokascript/semantic` installed. **4.0 will remove that
+  default:** a non-English `compile()` with no front-end registered will
+  return the same result the core-parser-only path returns today, and
+  `@lokascript/semantic` becomes an optional peer. Engine-migration plan
+  Arc 1, steps 2 and 3.
+
+### Fixed
+
+- **Language server: valid non-English code no longer gets a `parse-error`.**
+  In `lokascript`/`hyperscript-i18n` mode the server ran core's English
+  parser on every region regardless of what the semantic front-end said, so
+  `al hacer clic alternar .activo` (accepted at 0.89 confidence) was published
+  as `Unexpected token: hacer`. Core's errors are now suppressed for a region
+  the front-end accepted in a non-English language. The integration suite
+  that claimed to cover this had been discarding every notification; it now
+  records `publishDiagnostics` and asserts on it.
+
+- **Language server: settings actually reach the server.** Neither VS Code
+  extension set `synchronize.configurationSection`, so the client pushed
+  `settings: null` and every `mode`/`language`/`maxDiagnostics` value was
+  ignored; `initializationOptions` was ignored too. The server now reads
+  `initializationOptions`, a pushed `lokascript`/`hyperscript` section, or
+  pulls `workspace/configuration` when the push is empty — and merges partial
+  objects over the defaults instead of replacing them (a bare
+  `{ maxDiagnostics }` used to leave `language` undefined and error on every
+  document). Both extensions push their section, and the LokaScript one now
+  contributes `lokascript.mode`.
+
+- **Both VS Code extension server bundles build and run.** The standalone
+  hyperscript extension's `bundle:server` had failed since #1016 (no shim for
+  `@hyperfixi/core/multilingual`); the LokaScript extension externalized
+  `@hyperfixi/core` without shipping it, so every install ran with core
+  absent ("diagnostics and hover degraded"). Core is bundled in now, and CI
+  runs both bundle scripts.
+
+- **`@lokascript/language-server` declares what it imports.**
+  `@lokascript/semantic` was an optional peer but a static import (the
+  server crashed at startup without it); `@lokascript/framework` was
+  undeclared and got inlined together with `@lokascript/intent` (261 KB) —
+  and without `--clean`, `dist/` shipped every previous build's chunk (three
+  dead ones, 63% of the tarball). Both are regular dependencies now, the
+  build cleans, the 20-byte `--dts` output is gone, and `npm test` rebuilds
+  the server it spawns.
+
+- **Hyperscript-compat mode stops flagging portable code.** `as Int`, `Float`,
+  `JSON`, `Date`, `Set`, `Map` are upstream conversions (the extension list
+  is now `Math`/`Values`, the ones core registers and upstream lacks);
+  `my.x`/`your.x` evaluate upstream (only `its.` is flagged); and the
+  extension-command scan no longer fires inside `y.replace(`, `arr.push(`,
+  string literals, `:process`, `--` comments, or the upstream trailing
+  `… unless …` modifier.
+
+- **Language-server false positives and misses.** A `.hs` file containing a
+  query literal like `<li/>` was classified as HTML and lost every feature;
+  possessives after `)`/`]`/`>` and apostrophes in `--` comments raised
+  `unmatched-quote`; the outline reported the `on` in `toggle .x on me` as a
+  handler and `.init` as an init block; `install Foo(args)` produced
+  overlapping rename edits VS Code rejects; `on draggable:start` became a
+  variable named `:start`; and keyword boundaries were ASCII `\b`, so
+  definitions and symbols were silently absent in the ten non-Latin
+  languages. Completion-context and document-symbol logic moved out of the
+  entry script into `completion-context.ts` / `document-symbols.ts` so the
+  unit suite tests the shipped code rather than the hand-copied twins it
+  used to carry.
+
+- **MCP `get_diagnostics`, `get_completions` and `get_document_symbols` read
+  the AST.** The bridge guarded those paths on helper names core never
+  exported, so all three had only ever taken their token-based fallback.
+  They now read the interchange: the core parser's own errors become
+  diagnostics, completions inside a command offer that command's argument
+  shapes, symbols carry their commands as children, and a document with
+  several `end`-terminated handlers keeps all of them.
+
+- **`hyperscript.process()` honours the event grammar.** The API-side DOM
+  processor carried its own listener installer for `on …` attributes and
+  silently dropped what the runtime's installer handles: `on
+click[event.shiftKey]` fired on a plain click, `on mouseenter or click` never
+  fired on mouseenter, `on click from document` never fired. Every browser
+  bundle already went through the runtime; `process()` now does too, and
+  `config.logAll` moved into the runtime so both paths log. Pinned by
+  `api/dom-processor.test.ts`, which runs each case on both paths.
+
+- **The browser bundles' attribute processor now runs the element lifecycle,
+  and its lazy stub only takes the shapes it can run faithfully.** Measured
+  side by side with `hyperscript.process()`: the bundle path never dispatched
+  `hyperscript:before:init` / `hyperscript:after:init` and never set
+  `data-hyperscript-powered` — both lived only in the API processor, so a
+  morph engine reading the marker saw nothing on a bundle-processed page, and
+  canceling `before:init` was impossible there. It also compiled every
+  attribute as English; it now detects the element's language (`data-lang`,
+  closest `lang`, the document's) the way `process()` always did. And the
+  `lazyParsing` stub read only the event NAME from the header, so for the
+  first event it ignored a filter (`on click[event.shiftKey]` fired on a
+  plain click), listened for the first name of an `or` list only, and never
+  saw `from <target>` at all; a header with a filter, `(args)`, `or`, `from`,
+  `elsewhere`, `queue`, `debounced`, `throttled` or `in` is now processed
+  eagerly. `dom/processor-parity.test.ts` runs every row on all three paths
+  (API, eager, lazy) and is the gate the DOM-processor collapse landed under.
+
+- **`hyperscript.process()` and the browser bundles share one DOM
+  processor.** `process()` and `cleanup()` now run on the attribute
+  processor every bundle uses, which receives its compiler and runtime from
+  the API by injection instead of importing it (the `dom -> api` layering
+  edge is gone). What changes for `process()` callers, all of it upstream
+  parity: an element is initialized once however many times it is passed or
+  scanned (it used to re-install on every call); `<script
+type="text/hyperscript">` tags inside the tree are processed, with or
+  without `for=`, before the elements that may `install` what they define;
+  each element gets a non-bubbling `load` event once its program has run,
+  and an unparseable attribute is reported through `console.error`, the
+  `hyperfixi:compile-error` event and `config.onCompileError` (it was logged
+  at debug level only). And `cleanup(container)` now un-marks every processed
+  descendant — it stripped the root's `data-hyperscript-powered` only — and
+  drops a lazy stub still waiting on an element, so cleanup-then-process
+  re-initializes the tree once. A second scan in `lazyParsing` mode no longer
+  registers a second stub.
+  The API-side processor module is deleted; the multilingual bundle's own
+  copy of the language walk now calls the shared one, narrowed to the
+  languages that bundle ships; and a subtree the `MutationObserver` picks up
+  takes the same entry as `process()`.
+
+- **`set *<css-property>` writes inline style in every spelling upstream
+  accepts.** `set *opacity to 0.5`, `set *opacity of me to 0.5` and
+  `set *background-color of me to "red"` were silent no-ops and
+  `set the *opacity of me to 0.5` threw; only the possessive `set my *opacity`
+  worked. The tokenizer classes `*opacity` as a selector (for `measure`), and
+  `set`'s parser now re-types it into the identifier property the runtime's
+  style rungs already handle, so one path serves all of them — bare, `of
+<target>`, `the … of <target>`, `<target>'s`. Ten rows pinned against
+  `_hyperscript` 0.9.93.
+
+- **`require('@hyperfixi/core')` returned `{}`, and the subpath `require`s
+  threw — since `"type": "module"`, on 3.0.0 too.** Every `exports.*.require`
+  and `main` pointed at a `.js` file built as CommonJS, which Node reads as
+  ESM under that flag. The CJS outputs are `.cjs` now (main entry, the 21
+  subpaths, the parser modules); the `import` conditions are unchanged. The
+  bare-Node check in CI now `require()`s the entries as well as importing
+  them, which is the check that would have caught this. Found by the
+  end-to-end probe that landed Arc 1's build half.
+
+### Changed
+
+- **`@hyperfixi/core`'s library entry no longer bundles the multilingual
+  front-end.** `dist/index.mjs`/`index.js` had `@lokascript/semantic`,
+  `@lokascript/intent` and `@lokascript/framework` inlined whole (3.33 MB, zero
+  dynamic imports left); they are external now (1.04 MB) and load on the first
+  non-English `compileAsync`, the way the source always said they would. No
+  API change: semantic and intent stay `dependencies`, framework stays an
+  optional peer — and is now genuinely one. A consumer that imported both core
+  and semantic no longer holds two copies of semantic. `dist/index.min.js`
+  (UMD, not in `exports`) stays self-contained. Gated by
+  `scripts/check-node-import.mjs` on the sourcemap. Engine-migration plan Arc 1
+  step 2, build half.
+
+- **`@lokascript/semantic` drops its `asyncSchema`.** Core deleted the `async`
+  command in 3.0.0 (#1102); the semantic front-end never emitted the action
+  anyway — its `stripAsyncModifier` pass removes the keyword (in all 24
+  languages) and parses the following command, so `async fetch /api as json`
+  is a `fetch`. The schema, its registration, the `'async'` `ActionType`
+  member and the AST-builder mapper row are gone. Kept on purpose: every
+  profile's `keywords.async` (the stripper matches on it) and the
+  `'then' | 'and' | 'async'` chain type (a different concept). The IR-level
+  `async all/race` node lives in `@lokascript/intent` and is untouched.
+
 ## [3.0.0] - 2026-09-03
 
 Full notes: [GitHub Releases](https://github.com/codetalcott/hyperfixi/releases/tag/v3.0.0).
@@ -14,9 +214,11 @@ Full notes: [GitHub Releases](https://github.com/codetalcott/hyperfixi/releases/
 One major, two themes. `@lokascript/i18n`'s grammar transformer is gone,
 because `@lokascript/semantic` overtook it on every row of the translation
 corpus (#973–#1001). And the engine-migration plan
-(`docs-internal/ENGINE_MIGRATION_PLAN.md`) is complete: its last arc deleted
+(`docs-internal/ENGINE_MIGRATION_PLAN.md`) closed its last arc, which deleted
 the exported dead code it had been carrying and collapsed the browser bundle
-lineup to two names (#1099–#1105).
+lineup to two names (#1099–#1105). One arc is still open: Arc 1's steps 2
+and 3 — `@hyperfixi/core`'s library entry still bundles the semantic
+front-end (recorded in the plan's History, 2026-09-03).
 
 ### ⚠ BREAKING
 
@@ -514,7 +716,8 @@ _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/v2.10.0...HEAD
+[Unreleased]: https://github.com/codetalcott/hyperfixi/compare/v3.1.0...HEAD
+[3.1.0]: https://github.com/codetalcott/hyperfixi/compare/v3.0.0...v3.1.0
 [2.10.0]: https://github.com/codetalcott/hyperfixi/compare/v2.9.0...v2.10.0
 [2.9.0]: https://github.com/codetalcott/hyperfixi/compare/v2.8.0...v2.9.0
 [2.8.0]: https://github.com/codetalcott/hyperfixi/compare/v2.5.1...v2.8.0

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@hyperscript-tools/i18n",
-  "version": "3.0.0",
+  "version": "3.1.1",
   "description": "Build-time translation for hyperscript code samples — generate per-language HTML from a canonical English source",
   "type": "module",
   "main": "dist/index.js",
@@ -48,7 +48,7 @@
   "author": "HyperFixi Contributors",
   "license": "MIT",
   "dependencies": {
-    "@lokascript/semantic": "^3.0.0",
+    "@lokascript/semantic": "^3.1.1",
     "hyperscript.org": "^0.9.93"
   },
   "devDependencies": {