@hyperfixi/server-bridge 2.11.1 → 3.0.0

package/CHANGELOG.md

@@ -7,6 +7,126 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 
 ## [Unreleased]
 
+## [3.0.0] - 2026-09-03
+
+Full notes: [GitHub Releases](https://github.com/codetalcott/hyperfixi/releases/tag/v3.0.0).
+
+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
+the exported dead code it had been carrying and collapsed the browser bundle
+lineup to two names (#1099–#1105).
+
+### ⚠ BREAKING
+
+- **`@lokascript/i18n` no longer translates** (#1001). `translate()`, `toLocale()`,
+  `toEnglish()`, `GrammarTransformer` and `createTransformer` are deleted; the
+  package is per-language vocabulary and grammar profiles. Migrate to
+  `import { translate } from '@lokascript/semantic'` (same signature; it throws
+  on unparseable input where the transformer returned nonsense). The classic-i18n
+  browser bundle, `@hyperscript-tools/i18n` and `@lokascript/types-browser` drop
+  the same members (#998, #999); the patterns corpus writer is semantic-only (#1000).
+- **The prebuilt browser bundles are two names** (#1105): `hyperfixi-hx.js`
+  (small: hybrid parser, blocks, expressions, htmx v1/v2 attributes) and
+  `hyperfixi.js` (everything); `hyperfixi-hx-v4.js` and
+  `hyperfixi-multilingual.js` stay as separate products. `hyperfixi-lite.js`,
+  `-lite-plus.js`, `-minimal.js`, `-standard.js` and their `./browser/*`
+  exports are gone — use `hyperfixi-hx.js`, `hyperfixi.js`, or the Vite
+  plugin, which picks the tier itself. `./browser/hybrid-complete` remains as
+  the plugin's internal fallback.
+- **Exported dead code deleted from `@hyperfixi/core`** — none had a
+  production caller: the six `@deprecated` `features/` families and the
+  modular bundle's `features` namespace (#1099); `Lexer`/`Tokens` (#1100 —
+  use `tokenize`); the `unified-types` `Validator`, the `types.d.ts` shim and
+  `registry/multilingual` (#1101); the `async` command (#1102 — it was
+  unreachable from parsed hyperscript; the manifest is 58 commands);
+  `ContextProviderRegistry`, the context-provider `Proxy`, the registry's
+  `context` slot and the plugin `contextProviders` field (#1104 — set
+  request-scoped values as `context.locals`).
+
+### Fixed
+
+- **A small bundle fails loudly on a command it lacks and names `hyperfixi.js`**
+  (#1103). The hybrid parser had been dropping an unrecognised word silently;
+  making it loud also exposed and fixed three silent mis-parses in the hybrid
+  bundles: unquoted `fetch /api/data` fetched `/`, `send custom:event` sent
+  `custom` to `me`, and `repeat forever` ran zero iterations.
+- **English→foreign rendering is gated** (#931–#972, #953): 3105/3105 corpus
+  renders parse on the canonical engine; the bare (handler-less) surface has its
+  own gate. `as JSON` stays part of the value (#991); a flattened loop header
+  closes (#992).
+- Plugins report their real versions (#926); `analyze_content` is unshadowed in
+  the MCP server (#927); four dependency advisories resolved; the `domain-flow`
+  → `server-bridge` route contract is pinned (#1000s).
+
+### Changed
+
+- `hyperfixi.js` and `hyperfixi-hx-v4.js` carry the 24-language render
+  vocabulary (~19 KB gzip each) so `translate` works in the browser (#931).
+- Deprecated `@lokascript/domain-*` references repoint to `@lokascript/domains`.
+
+## [2.11.1] - 2026-08-25
+
+Patch release. Fixes the release workflow itself: the build now runs **after**
+the version sync, so a published tarball carries its own version rather than
+the previous one, and `version.ts` is committed (#925). Also lands the
+agent-loop A/B benchmark with an isolated generator (#924).
+
+## [2.11.0] - 2026-08-24
+
+Full notes: [GitHub Releases](https://github.com/codetalcott/hyperfixi/releases/tag/v2.11.0).
+
+### Changed
+
+- **The domain-DSL family moved out** (#909). Twelve packages left this
+  monorepo: the ten publishable `@lokascript/domain-*` packages (bdd,
+  behaviorspec, config, flow, jsx, learn, llm, sql, todo, voice) plus the
+  private `domain-toolkit` and `mcp-multilingual-intent`. They now ship as
+  **`@lokascript/domains`**, one subpath export per domain, from the
+  [lokascript-domains](https://github.com/codetalcott/lokascript-domains)
+  repository.
+
+  All ten published names are **deprecated on npm**, each naming its
+  replacement subpath (`@lokascript/domain-sql` → "import from
+  `@lokascript/domains/sql`"). Existing installs keep working — deprecation is
+  a warning, not a removal — they simply stop receiving updates. The
+  pre-deletion tree is preserved at the `moved/domain-family` tag.
+
+  _Migration:_ replace nine dependencies with one, and change
+  `from '@lokascript/domain-x'` to `from '@lokascript/domains/x'`. The root
+  entry absorbed `domain-config` and exports `createDomainRegistry`,
+  `registerAllDomains` and `DOMAIN_PRIORITY`.
+
+### Added
+
+- **"Show in My Language"** — LSP request plus VSCode command (#921).
+- **Verified-translation badge** in the compilation service (#920).
+- **`scoreFidelity` / `@lokascript/semantic/fidelity`** (#919).
+- **Inert-shape warnings** (#918) and surfaced unconsumed-input warnings (#916)
+  in the compilation service.
+- **The agent-loop benchmark** and the silent-failure finding it produced
+  (#915), and the MCP server's agent-era roadmap (#914).
+- **Element-collection write-back** for hypermedia tables, with gallery
+  examples and four system fixes (#904).
+- **The comprehensive Playwright tier now runs in CI** (#908) alongside
+  `quick`. It had never run: 122 specs, hiding four real bugs — a detached
+  `startViewTransition`, untracked reads of unset globals, concurrent effects
+  clobbering dependency capture, and `put` stringifying DocumentFragments
+  (#905).
+
+### Fixed
+
+- **The `hyperscript-adapter` review arc** (#895–#902): whole-string
+  translation first, taking canonical validity from 2849/3105 to **3105/3105**
+  (#899); a host-parser validity gate so an invalid render falls back to the
+  author's text (#900); the dead split-statement fallback deleted after
+  measuring 0 outputs (#901); and the slim divergence set burned 6 → 1 via
+  schema marker data, repairing 39 body-dropping corpus rows (#902).
+- **`qu take.recipient`** — the R1 tail's last `take` row (#910).
+- **The release workflows** no longer reference the moved-out domain family
+  (#922).
+
 ## [2.10.0] - 2026-08-01
 
 Full notes: [GitHub Releases](https://github.com/codetalcott/hyperfixi/releases/tag/v2.10.0).

package/dist/compat/flow-route-descriptor.d.ts

@@ -0,0 +1,35 @@
+/**
+ * Compile-time compatibility pin: domain-flow's `FlowRouteDescriptor` →
+ * server-bridge's `RouteDescriptor`.
+ *
+ * `@lokascript/domains/flow` declares its route descriptor as "compatible with
+ * server-bridge's RouteDescriptor but self-contained to avoid a hard dependency
+ * on the server-bridge package", and its route extractor exists so that
+ * "each fetch/poll/stream/submit URL becomes a RouteDescriptor that can be fed
+ * into server-bridge". Those two claims live in a different repository now.
+ * The adapter below is the only place either one is written as code rather than
+ * prose, so it is what keeps them honest.
+ *
+ * WHY THIS IS ORDINARY SOURCE AND NOT A TEST: the predecessor of this pin was
+ * `domain-flow/src/__test__/route-descriptor-compat.test.ts`, and it never
+ * checked anything. That package's tsconfig excluded `**\/*.test.ts` and
+ * `**\/__test__\/**`, so `tsc` never saw the `satisfies`; vitest strips types
+ * with esbuild rather than checking them. The assertion was erased at both
+ * gates. Here the file is inside `include: ["src/**\/*.ts"]`, so
+ * `npm run typecheck` compiles it: if either shape drifts — a new required
+ * field on `RouteDescriptor`, a widened method or response-format union on
+ * `FlowRouteDescriptor` — this stops compiling.
+ *
+ * The import is `import type`, so nothing here survives to runtime and
+ * `@lokascript/domains` stays a devDependency. Deliberately NOT re-exported
+ * from `index.ts`: server-bridge does not take a dependency on the domain
+ * family, it only promises to remain assignable from it.
+ */
+import type { FlowRouteDescriptor } from '@lokascript/domains/flow';
+import type { RouteDescriptor, RouteSource } from '../types.js';
+/**
+ * The documented adaptation: supply the provenance server-bridge requires
+ * (`source`, `notes`) and drop SSE routes, which server-bridge's
+ * `responseFormat` union does not model.
+ */
+export declare function toServerBridgeRoute(flow: FlowRouteDescriptor, source: RouteSource): RouteDescriptor | null;

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@hyperfixi/server-bridge",
-  "version": "2.11.1",
+  "version": "3.0.0",
   "description": "Extract server route contracts from hyperscript/htmx HTML and generate server-side route scaffolding",
   "type": "module",
   "sideEffects": false,
@@ -29,6 +29,7 @@
     "glob": "^13.0.6"
   },
   "devDependencies": {
+    "@lokascript/domains": "^2.11.1",
     "@types/node": "^26.1.2",
     "tsup": "^8.0.0",
     "typescript": "^5.0.0",

package/src/__tests__/flow-route-descriptor.test.ts

@@ -0,0 +1,66 @@
+/**
+ * Runtime half of the domain-flow compatibility pin.
+ *
+ * The compile-time half — and the part that actually catches drift — lives in
+ * `src/compat/flow-route-descriptor.ts`, because this directory is excluded
+ * from the tsconfig and vitest strips types rather than checking them. Nothing
+ * asserted about a *type* in this file would be enforced; these cases cover the
+ * adapter's runtime behaviour only.
+ */
+
+import { describe, it, expect } from 'vitest';
+import type { FlowRouteDescriptor } from '@lokascript/domains/flow';
+import { toServerBridgeRoute } from '../compat/flow-route-descriptor.js';
+
+const source = { file: 'app.html', kind: 'fetch' as const, raw: 'fetch /api/users/{id} as json' };
+
+describe('FlowRouteDescriptor → server-bridge RouteDescriptor', () => {
+  it('adapts a fetch route by supplying the two fields flow does not carry', () => {
+    const flow: FlowRouteDescriptor = {
+      path: '/api/users/{id}',
+      method: 'GET',
+      responseFormat: 'json',
+      pathParams: ['id'],
+      handlerName: 'getUsersId',
+      sourceCommand: 'fetch',
+    };
+
+    const route = toServerBridgeRoute(flow, source);
+
+    expect(route).not.toBeNull();
+    expect(route!.path).toBe('/api/users/{id}');
+    expect(route!.method).toBe('GET');
+    expect(route!.responseFormat).toBe('json');
+    expect(route!.pathParams).toEqual(['id']);
+    expect(route!.handlerName).toBe('getUsersId');
+    expect(route!.source).toEqual(source);
+    expect(route!.notes).toEqual([]);
+  });
+
+  it('drops SSE routes — server-bridge has no sse response format', () => {
+    const flow: FlowRouteDescriptor = {
+      path: '/api/events',
+      method: 'GET',
+      responseFormat: 'sse',
+      pathParams: [],
+      handlerName: 'getEvents',
+      sourceCommand: 'stream',
+    };
+
+    expect(toServerBridgeRoute(flow, source)).toBeNull();
+  });
+
+  it('carries every non-sse response format through unchanged', () => {
+    for (const format of ['json', 'html', 'text'] as const) {
+      const flow: FlowRouteDescriptor = {
+        path: '/api/thing',
+        method: 'POST',
+        responseFormat: format,
+        pathParams: [],
+        handlerName: 'postThing',
+        sourceCommand: 'submit',
+      };
+      expect(toServerBridgeRoute(flow, source)?.responseFormat).toBe(format);
+    }
+  });
+});

package/src/compat/flow-route-descriptor.ts

@@ -0,0 +1,52 @@
+/**
+ * Compile-time compatibility pin: domain-flow's `FlowRouteDescriptor` →
+ * server-bridge's `RouteDescriptor`.
+ *
+ * `@lokascript/domains/flow` declares its route descriptor as "compatible with
+ * server-bridge's RouteDescriptor but self-contained to avoid a hard dependency
+ * on the server-bridge package", and its route extractor exists so that
+ * "each fetch/poll/stream/submit URL becomes a RouteDescriptor that can be fed
+ * into server-bridge". Those two claims live in a different repository now.
+ * The adapter below is the only place either one is written as code rather than
+ * prose, so it is what keeps them honest.
+ *
+ * WHY THIS IS ORDINARY SOURCE AND NOT A TEST: the predecessor of this pin was
+ * `domain-flow/src/__test__/route-descriptor-compat.test.ts`, and it never
+ * checked anything. That package's tsconfig excluded `**\/*.test.ts` and
+ * `**\/__test__\/**`, so `tsc` never saw the `satisfies`; vitest strips types
+ * with esbuild rather than checking them. The assertion was erased at both
+ * gates. Here the file is inside `include: ["src/**\/*.ts"]`, so
+ * `npm run typecheck` compiles it: if either shape drifts — a new required
+ * field on `RouteDescriptor`, a widened method or response-format union on
+ * `FlowRouteDescriptor` — this stops compiling.
+ *
+ * The import is `import type`, so nothing here survives to runtime and
+ * `@lokascript/domains` stays a devDependency. Deliberately NOT re-exported
+ * from `index.ts`: server-bridge does not take a dependency on the domain
+ * family, it only promises to remain assignable from it.
+ */
+
+import type { FlowRouteDescriptor } from '@lokascript/domains/flow';
+import type { RouteDescriptor, RouteSource } from '../types.js';
+
+/**
+ * The documented adaptation: supply the provenance server-bridge requires
+ * (`source`, `notes`) and drop SSE routes, which server-bridge's
+ * `responseFormat` union does not model.
+ */
+export function toServerBridgeRoute(
+  flow: FlowRouteDescriptor,
+  source: RouteSource
+): RouteDescriptor | null {
+  if (flow.responseFormat === 'sse') return null;
+
+  return {
+    path: flow.path,
+    method: flow.method,
+    responseFormat: flow.responseFormat,
+    pathParams: flow.pathParams,
+    handlerName: flow.handlerName,
+    source,
+    notes: [],
+  } satisfies RouteDescriptor;
+}