@hyperfixi/server-bridge 4.8.0 → 5.1.0

package/CHANGELOG.md

@@ -7,6 +7,73 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 
 ## [Unreleased]
 
+## [5.1.0] - 2026-10-18
+
+Deprecates `@lokascript/compilation-service`'s test and component generation, which 6.0 removes;
+`@hyperfixi/mcp-server` moves to `@lokascript/domains` 5.0.0.
+
+### Changed
+
+- **`@hyperfixi/mcp-server`: on `@lokascript/domains` 5.0.0** (domains rethink Phase 6), which deletes
+  bdd and peers framework, semantic and intent `^5.0.0`. The server registers every domain (no
+  `omit`); the same seven domains and 28 domain tools as 5.0.0. framework's and server-bridge's
+  dev dependency follows (`^5.0.0`) (#1559).
+
+### Deprecated
+
+- **`@lokascript/compilation-service`: test and component generation, removed in 6.0** (#1560).
+  `generateTests`, `generateComponent`, `registerTestRenderer`, `registerComponentRenderer`, the
+  `PlaywrightRenderer`, `ReactRenderer`, `VueRenderer` and `SvelteRenderer` exports, and the react,
+  vue and svelte targets of `generate` (its `intent-element` target stays). Each call still works
+  and its response now carries an info diagnostic, `DEPRECATED`. The HTTP routes
+  `/generate-tests` and `/generate-component` and the MCP tools `generate_tests` and
+  `generate_component` go with them in 6.0; the tools' descriptions say so now. Measured on the
+  docs sites' 164 English patterns and lokascript-examples chat's five examples: 15 of 169 inputs
+  give a Playwright test that fails without the engine (103 are refused, 23 tests pass with no
+  engine loaded, 26 fail on it), and 4 of 6 React components do not typecheck (every command
+  aimed at another element: siblings with no fragment, `function ToggleDark-mode`,
+  `const [, set]`). Validation, translation, `scoreFidelity` and `diff` stay.
+
+## [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 +1921,9 @@ _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.1.0...HEAD
+[5.1.0]: https://github.com/codetalcott/hyperfixi/compare/v5.0.0...v5.1.0
+[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/dist/cli.cjs

@@ -113,7 +113,14 @@ var ATTR_PATTERNS = [
   // JSX string
 ];
 var SCRIPT_PATTERN = /<script[^>]*type=["']?text\/hyperscript["']?[^>]*>([\s\S]*?)<\/script>/gi;
-var FETCH_COMMAND = /\bfetch\s+['"]?([^\s'"]+)['"]?(?:\s+as\s+(\w+))?(?:\s+via\s+(\w+))?/gi;
+var FETCH_COMMAND = /\bfetch\s+['"]?([^\s'"]+)['"]?(?:\s+as\s+(?:an?\s+)?(\w+))?(?:\s+via\s+(\w+))?/gi;
+var OPTIONS_METHOD = /\bmethod\s*:\s*['"]?([A-Za-z]+)/i;
+var TRAILING_AS = /\bas\s+(?:an?\s+)?(\w+)/i;
+function restOfCommand(code, from) {
+  const rest = code.slice(from);
+  const end = rest.search(/\bthen\b|\bend\b|\n/);
+  return end === -1 ? rest : rest.slice(0, end);
+}
 var SEND_FORM = /\bsend\s+(?:the\s+)?form\s+to\s+['"]?([^\s'"]+)['"]?(?:\s+as\s+(\w+))?/gi;
 function extractHyperscriptRoutes(content, options) {
   const routes = [];
@@ -122,8 +129,9 @@ function extractHyperscriptRoutes(content, options) {
   for (const region of regions) {
     for (const match of region.code.matchAll(FETCH_COMMAND)) {
       const rawUrl = match[1];
-      const responseType = match[2];
-      const method = match[3];
+      const rest = restOfCommand(region.code, match.index + match[0].length);
+      const responseType = match[2] ?? rest.match(TRAILING_AS)?.[1];
+      const method = match[3] ?? rest.match(OPTIONS_METHOD)?.[1];
       addRoute(routes, seen, rawUrl, {
         file: options.file,
         line: region.line,