@hyperscript-tools/i18n 4.8.0 → 5.0.0

package/CHANGELOG.md

@@ -7,6 +7,46 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 
 ## [Unreleased]
 
+## [5.0.0] - 2026-10-17
+
+A renumber for everything but `@lokascript/framework`, whose classic DSL engine is removed: every
+other package is unchanged in its API, and `@lokascript/domains` 4.2.1+ accepts 5.0.
+
+### Removed (BREAKING)
+
+- **`@lokascript/framework`: the classic DSL engine** (domains rethink Phase 6; M3 (e): one
+  matcher). Every DSL reads on the core engine, which every kept domain has used since domains 4.2.0
+  (bdd's own suite and its gate read the same on it, 0 cases moved). Gone: `PatternMatcher`,
+  `patternMatcher`, `matchPattern`, `matchBest` and the `./core/pattern-matching` subpath (and
+  `PatternMatcher` from `./parsing`); the classic generator, `generatePattern`,
+  `generatePatternVariants` and `GeneratorConfig`. `createMultilingualDSL` defaults to the core;
+  `engine: 'core'` is still accepted and changes nothing, so the domains build unchanged, while
+  `engine: 'classic'` throws, naming what replaced it. Kept: the schema renderer
+  (`createDomainRenderer`, `createSchemaRenderer`, the domains' renderer kit), `PatternGenLanguageProfile`
+  and `sortRolesByWordOrder` (now in `generation/profile.ts`), and the value helpers the stock reader
+  uses (`isTypeCompatible`, `getPossessiveReference` & co., now in `core/matching`, still exported
+  from the root).
+
+### Changed
+
+- **`@hyperfixi/mcp-server`: on `@lokascript/domains` 4.2.1, without bdd's tools** (domains rethink
+  Phase 5, D6). `parse_bdd`, `compile_bdd`, `validate_bdd` and `translate_bdd` and the multi-step
+  bdd scenario handling are gone: behaviorspec reads bdd's preconditions, actions and assertions
+  (`given #button is visible`, `when user presses 'Enter'`, `expect #title text Welcome`), and the
+  server creates its registry with `createDomainRegistry({ omit: ['bdd'] })`. 98 tools defined, 93
+  listed by default (102 and 97). From domains 4.2.0 the domain tools also refuse what their DSL does
+  not read (no domain gate case accepts leftover input), and `parse_learn` & co. read and write
+  learn's commanding sentence with semantic.
+
+### Fixed
+
+- **`@hyperfixi/server-bridge` reads a fetch's method from upstream's options.** It read the method
+  only from 2.x's `via POST`, so a route written in the engine's syntax, such as
+  `fetch /api/x with {method:'POST'}`, was generated as GET. It now reads `with {method:'POST'}`,
+  `with method:'POST'` or a bare `{method:'POST'}`, with `as` before or after them (`as an html`
+  too); `via` is still read. Measured on lokascript-examples' cross-domain and flow-playground
+  pages: 3 POST routes read as GET, all POST now.
+
 ## [4.8.0] - 2026-10-16
 
 ### Added
@@ -1854,7 +1894,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/v4.8.0...HEAD
+[Unreleased]: https://github.com/codetalcott/hyperfixi/compare/v5.0.0...HEAD
+[5.0.0]: https://github.com/codetalcott/hyperfixi/compare/v4.8.0...v5.0.0
 [4.8.0]: https://github.com/codetalcott/hyperfixi/compare/v4.7.0...v4.8.0
 [4.7.0]: https://github.com/codetalcott/hyperfixi/compare/v4.6.0...v4.7.0
 [4.6.0]: https://github.com/codetalcott/hyperfixi/compare/v4.5.0...v4.6.0

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@hyperscript-tools/i18n",
-  "version": "4.8.0",
+  "version": "5.0.0",
   "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": "^4.8.0",
+    "@lokascript/semantic": "^5.0.0",
     "hyperscript.org": "^0.9.93"
   },
   "devDependencies": {