@hydranium/langium 1.0.0-next.224 → 1.0.0-next.226

package/README.md

@@ -11,12 +11,14 @@ project stays in lockstep with the version the framework was built against.
 ## Why this package exists
 
 Langium is pinned to **one exact version** here, to guarantee a **single physical copy** across the
-workspace. Re-export is transparent — given one physical install, importing `AstNode` or `URI` from
-`@hydranium/langium` and from `langium` yields the same class object and the same declaration. That
-transparency is exactly what a split install destroys: two copies of Langium mean two `AstNode`
-declarations and two `URI` classes, so `instanceof` and every nominal identity check across them
-silently start returning `false`. Without the pin, single-copy is only a semver-dedup coincidence,
-one minor bump away from breaking.
+workspace. Re-export is transparent — given one physical install, importing `AstUtils` or
+`OperationCancelled` from `@hydranium/langium` and from `langium` yields the same object and the
+same declaration. That transparency is exactly what a split install destroys: two copies of Langium
+mean two sets of declarations, which TypeScript refuses to mix, and two sets of module-level values,
+so one that Langium compares by identity, such as its cancellation signal, is not recognised by the
+other copy. The framework refuses to start a server whose AST reflection is built on a copy other
+than its own. Without the pin, single-copy is only a semver-dedup coincidence, one minor bump away
+from breaking.
 
 For an **adopter**, the reason to route imports here is not runtime identity (that already holds) —
 it is **version coupling**. Langium sits in a chain with `vscode-languageserver`,
@@ -24,7 +26,7 @@ it is **version coupling**. Langium sits in a chain with `vscode-languageserver`
 adopter importing `langium` directly owns that pin itself and can drift out of lockstep with the
 framework it composes; importing it from here means the framework owns it.
 
-The chokepoint is **lint-enforced**, not merely conventional: an ESLint
+The chokepoint is **lint-enforced**, not merely conventional: an oxlint
 `no-restricted-imports` rule over `packages/**` and `examples/**` rejects direct imports of
 `langium`, `langium/lsp`, `langium/node`, `langium/test` and `vscode-uri` (whose `URI` Langium
 re-exports and owns the version of). This package itself is exempt, as is any `generated` directory —
@@ -77,9 +79,10 @@ only the stock surface.
 
 ## Status
 
-Alpha — pre-v0, published nightly as `1.0.0-next` prereleases. The API is Langium's and is stable
-to the extent Langium's is; what is not yet settled is the augmentation set and the pinned version.
-See the [repository README](../../README.md) for the current status and known limitations.
+Alpha — pre-v0, published as a `1.0.0-next` prerelease on every merge to `main`. The API is
+Langium's and is stable to the extent Langium's is; what is not yet settled is the augmentation set
+and the pinned version. See the [repository README](../../README.md) for the current status and
+known limitations.
 
 ## License
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@hydranium/langium",
-  "version": "1.0.0-next.224",
+  "version": "1.0.0-next.226",
   "description": "Augmented re-export of the Langium API for the hydranium framework: the single chokepoint where hydranium pins the Langium version and layers its type/namespace augmentations. ~99% passthrough today.",
   "keywords": [
     "hydranium",