okf-parser 0.45.4__tar.gz → 0.45.5__tar.gz

{okf_parser-0.45.4 → okf_parser-0.45.5}/Cargo.lock

@@ -447,7 +447,7 @@ dependencies = [
 
 [[package]]
 name = "okf-core"
-version = "0.45.4"
+version = "0.45.5"
 dependencies = [
  "clap",
  "okf-engine",
@@ -457,7 +457,7 @@ dependencies = [
 
 [[package]]
 name = "okf-engine"
-version = "0.45.4"
+version = "0.45.5"
 dependencies = [
  "chrono",
  "ignore",

{okf_parser-0.45.4 → okf_parser-0.45.5}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: okf-parser
-Version: 0.45.4
+Version: 0.45.5
 Requires-Dist: cyclopts>=4.22,<5
 Requires-Dist: duckdb>=1.4,<2
 Requires-Dist: fastmcp>=3.4,<4
@@ -231,7 +231,7 @@ Add the repository as a CI check:
 ```yaml
 steps:
   - uses: actions/checkout@v7
-  - uses: franklinbaldo/okf-parser@v0.45.4
+  - uses: franklinbaldo/okf-parser@v0.45.5
     with:
       path: knowledge
 ```

{okf_parser-0.45.4 → okf_parser-0.45.5}/README.md

@@ -209,7 +209,7 @@ Add the repository as a CI check:
 ```yaml
 steps:
   - uses: actions/checkout@v7
-  - uses: franklinbaldo/okf-parser@v0.45.4
+  - uses: franklinbaldo/okf-parser@v0.45.5
     with:
       path: knowledge
 ```

okf_parser-0.45.5/changelog/0.45.5/scoped-npm-packages.md

@@ -0,0 +1,9 @@
+---
+type: Release Note
+title: publish the npm packages under the @franklinbaldo scope
+---
+
+- Rename all three npm packages to `@franklinbaldo/okf-parser`, `@franklinbaldo/okf-parser-duckdb` and `@franklinbaldo/okf-parser-native-linux-x64`. npm refuses the unscoped name `okf-parser` because its similarity filter considers it too close to the existing `oxc-parser`; the refusal happens on upload, so name availability alone never proved the name was publishable.
+- Keep the PyPI distribution unscoped as `okf-parser`. The Python and npm names are now deliberately different, because only npm imposes the similarity constraint.
+- Update the source contract to expect the scoped names and the tarball file names `npm pack` derives from them, where the scope is flattened into the leading `franklinbaldo-` segment.
+- Resolve the optional native package through its scoped name, so a Linux x64 consumer still finds the packaged engine.

{okf_parser-0.45.4 → okf_parser-0.45.5}/docs/native-engine.md

@@ -15,7 +15,7 @@ bundle = load_bundle(root)
 ```
 
 ```ts
-import { loadBundle } from "okf-parser";
+import { loadBundle } from "@franklinbaldo/okf-parser";
 
 const bundle = await loadBundle(root);
 ```
@@ -42,7 +42,7 @@ A source installation builds that same executable as part of building the `okf-p
 
 ## npm packaging
 
-`okf-parser` declares platform packages as optional dependencies. The first supported target is `okf-parser-native-linux-x64`, which contains the release-matched executable under `bin/okf-core`. The TypeScript resolver discovers that package directly from `node_modules` before consulting environment overrides.
+`@franklinbaldo/okf-parser` declares platform packages as optional dependencies. The first supported target is `@franklinbaldo/okf-parser-native-linux-x64`, which contains the release-matched executable under `bin/okf-core`. The TypeScript resolver discovers that package directly from `node_modules` before consulting environment overrides.
 
 Installing with `--omit=optional`, or running on a platform for which no native companion is published, keeps the same `loadBundle()` API and uses the portable TypeScript implementation.
 

{okf_parser-0.45.4 → okf_parser-0.45.5}/docs/releasing.md

@@ -9,9 +9,11 @@ description: Build, verify and publish synchronized Python and TypeScript releas
 The repository publishes one synchronized protocol version across one Python project and three npm packages:
 
 - Python `okf-parser` on PyPI;
-- TypeScript `okf-parser` on npm;
-- TypeScript `okf-parser-duckdb` on npm;
-- platform npm companion `okf-parser-native-linux-x64` on npm.
+- TypeScript `@franklinbaldo/okf-parser` on npm;
+- TypeScript `@franklinbaldo/okf-parser-duckdb` on npm;
+- platform npm companion `@franklinbaldo/okf-parser-native-linux-x64` on npm.
+
+The npm packages are scoped and the PyPI distribution is not. npm refuses the unscoped name `okf-parser`, whose similarity filter considers it too close to the existing `oxc-parser`, and that refusal only happens on upload. The scope is therefore a constraint npm imposes, not a naming preference.
 
 There is no `okf-parser-native` PyPI project. The Rust engine is an implementation detail of the `okf-parser` Python distribution and is embedded directly in its single `okf-parser` executable.
 
@@ -27,10 +29,10 @@ release/
 │   ├── okf_parser-X.Y.Z-<platform>.whl
 │   └── okf_parser-X.Y.Z.tar.gz
 ├── npm/
-│   ├── okf-parser-X.Y.Z.tgz
-│   └── okf-parser-duckdb-X.Y.Z.tgz
+│   ├── franklinbaldo-okf-parser-X.Y.Z.tgz
+│   └── franklinbaldo-okf-parser-duckdb-X.Y.Z.tgz
 ├── native-npm/
-│   └── okf-parser-native-linux-x64-X.Y.Z.tgz
+│   └── franklinbaldo-okf-parser-native-linux-x64-X.Y.Z.tgz
 ├── manifest.json
 ├── registry-state.json
 └── SHA256SUMS
@@ -52,7 +54,7 @@ Before building, `scripts/release_contract.py verify-source` requires all of the
 - the Rust crate version;
 - versions in the npm manifests;
 - `PROTOCOL_VERSION` in `typescript/src/version.ts`;
-- the `okf-parser` peer range in the DuckDB adapter;
+- the `@franklinbaldo/okf-parser` peer range in the DuckDB adapter;
 - at least one release-note fragment in `changelog/X.Y.Z/`;
 - an optional stable tag, exactly `vX.Y.Z`.
 

okf_parser-0.45.5/native-npm-linux-x64/README.md

@@ -0,0 +1,15 @@
+---
+type: Documentation
+title: okf-parser native Linux x64 package
+description: Platform companion that ships the release-matched okf-core executable for npm consumers
+---
+
+# @franklinbaldo/okf-parser-native-linux-x64
+
+Platform companion for `@franklinbaldo/okf-parser` on Linux x64.
+
+This package contains the release-matched `okf-core` executable. It is installed as an optional dependency of `@franklinbaldo/okf-parser`; applications should not depend on it directly or hard-code its path. `loadBundle()` discovers it automatically and falls back to the portable TypeScript engine when no compatible native package is installed.
+
+The companion version always matches the `@franklinbaldo/okf-parser` release that consumes it, so the resolver never needs to negotiate protocol compatibility at runtime.
+
+The executable is built during the release workflow. Rust is never compiled during application installation or startup.

{okf_parser-0.45.4 → okf_parser-0.45.5}/native-npm-linux-x64/package.json

@@ -1,6 +1,6 @@
 {
-  "name": "okf-parser-native-linux-x64",
-  "version": "0.45.4",
+  "name": "@franklinbaldo/okf-parser-native-linux-x64",
+  "version": "0.45.5",
   "description": "Linux x64 native okf-core engine for okf-parser",
   "license": "MIT",
   "os": ["linux"],

{okf_parser-0.45.4 → okf_parser-0.45.5}/okf-engine/Cargo.toml

@@ -1,6 +1,6 @@
 [package]
 name = "okf-engine"
-version = "0.45.4"
+version = "0.45.5"
 edition = "2024"
 license = "MIT"
 description = "DuckDB-independent OKF semantic ingestion engine"

{okf_parser-0.45.4 → okf_parser-0.45.5}/pyproject.toml

@@ -1,6 +1,6 @@
 [project]
 name = "okf-parser"
-version = "0.45.4"
+version = "0.45.5"
 description = "Relational inspection and validation for Open Knowledge Format bundles"
 readme = "README.md"
 requires-python = ">=3.12"

{okf_parser-0.45.4 → okf_parser-0.45.5}/rfcs/0003-resumable-multi-registry-release.md

@@ -13,8 +13,8 @@ Add one tag-driven GitHub Actions release pipeline for the three synchronized
 artifacts produced by this repository:
 
 - the Python `okf-parser` distribution on PyPI;
-- the TypeScript `okf-parser` package on npm;
-- the optional `okf-parser-duckdb` package on npm.
+- the TypeScript `@franklinbaldo/okf-parser` package on npm;
+- the optional `@franklinbaldo/okf-parser-duckdb` package on npm.
 
 The workflow builds all artifacts once from one tagged commit, verifies them as
 installed consumer artifacts, records checksums and provenance, and then
@@ -40,7 +40,7 @@ is still manual and therefore weaker than the code path it distributes.
 Three facts make a naive `npm publish && twine upload` workflow unsafe:
 
 1. the artifacts live in two independent registries;
-2. `okf-parser-duckdb` has a peer dependency on the main npm package and must
+2. `@franklinbaldo/okf-parser-duckdb` has a peer dependency on the main npm package and must
    not become visible first;
 3. a network or registry failure can occur after one immutable upload succeeds.
 
@@ -214,7 +214,7 @@ release/
 │   └── okf_parser-X.Y.Z.tar.gz
 ├── npm/
 │   ├── okf-parser-X.Y.Z.tgz
-│   └── okf-parser-duckdb-X.Y.Z.tgz
+│   └── franklinbaldo-okf-parser-duckdb-X.Y.Z.tgz
 └── manifest.json
 ```
 
@@ -296,8 +296,8 @@ automatic recovery action.
 The safe dependency order is:
 
 1. Python `okf-parser` to PyPI;
-2. npm `okf-parser`;
-3. npm `okf-parser-duckdb`.
+2. npm `@franklinbaldo/okf-parser`;
+3. npm `@franklinbaldo/okf-parser-duckdb`.
 
 PyPI and the main npm package do not depend on one another and may technically be
 published in parallel. This RFC chooses a linear sequence because it produces a
@@ -366,11 +366,32 @@ workflow:
 4. publish version `X.Y.Z` interactively from a maintainer workstation using
    npm account MFA;
 5. configure `release.yml` as the trusted publisher for the new package;
-6. repeat for `okf-parser-duckdb` only after `okf-parser` exists;
+6. repeat for `@franklinbaldo/okf-parser-duckdb` only after `@franklinbaldo/okf-parser` exists;
 7. remove any temporary automation credential if one was created;
 8. re-run the tag workflow, which verifies the existing digest and completes
    the other registries/finalization idempotently.
 
+## Amendment: the npm names are scoped
+
+This section originally assumed unscoped npm names matching the PyPI
+distribution. That assumption did not survive contact with the registry.
+
+npm refused `okf-parser` with `403 Package name too similar to existing package
+oxc-parser`. The refusal is produced by npm's similarity filter at upload time,
+so the availability check in step 3 above -- which only proves that nobody has
+registered the exact name -- can never predict it. All three packages are
+therefore published under the `@franklinbaldo` scope, while the PyPI
+distribution stays unscoped as `okf-parser`.
+
+Scoping does not remove the bootstrap requirement: npm still refuses to
+configure a trusted publisher for a package that does not exist, whether or not
+it is scoped. It does remove the risk of a second similarity refusal, because
+scoped names are not subject to that filter.
+
+Two further details in this RFC are stale: the publication workflow is
+`publish.yml`, not `release.yml`, and there are three npm packages rather than
+two, since the platform companion did not exist when this RFC was written.
+
 The first public release version is chosen only after package-name availability
 is confirmed. If either name has been claimed, package renaming requires a
 separate reviewed change; the release workflow must not improvise a registry

{okf_parser-0.45.4 → okf_parser-0.45.5}/rust-core/Cargo.toml

@@ -1,6 +1,6 @@
 [package]
 name = "okf-core"
-version = "0.45.4"
+version = "0.45.5"
 edition = "2024"
 license = "MIT"
 description = "Native OKF CLI and compatibility adapters"
@@ -11,6 +11,6 @@ path = "src/main.rs"
 
 [dependencies]
 clap = { version = "4", features = ["derive"] }
-okf-engine = { path = "../okf-engine", version = "0.45.4" }
+okf-engine = { path = "../okf-engine", version = "0.45.5" }
 serde = { version = "1", features = ["derive"] }
 serde_json = "1"

{okf_parser-0.45.4 → okf_parser-0.45.5}/scripts/registry_state.py

@@ -357,15 +357,22 @@ def inspect_registry_state(
     if timeout <= 0:
         _fail("registry timeout must be positive")
     version, artifacts = _artifact_index(manifest)
+
+    # The published name is read from the manifest rather than repeated here, so
+    # a rename in the source contract cannot leave the preflight probing a name
+    # that is no longer the one being published.
+    def _npm_package(kind: str) -> str:
+        return _string(artifacts[kind], "package", "manifest artifact")
+
     entries = [
         _pypi_state(version, artifacts, fetch, timeout),
-        _npm_state("okf-parser", artifacts["npm-parser"], fetch, timeout),
-        _npm_state("okf-parser-duckdb", artifacts["npm-duckdb"], fetch, timeout),
+        _npm_state(_npm_package("npm-parser"), artifacts["npm-parser"], fetch, timeout),
+        _npm_state(_npm_package("npm-duckdb"), artifacts["npm-duckdb"], fetch, timeout),
     ]
     if "npm-native" in artifacts:
         entries.append(
             _npm_state(
-                "okf-parser-native-linux-x64",
+                _npm_package("npm-native"),
                 artifacts["npm-native"],
                 fetch,
                 timeout,

{okf_parser-0.45.4 → okf_parser-0.45.5}/scripts/release_contract.py

@@ -282,16 +282,19 @@ def _verify_npm_manifest(path: Path, package: str, version: str) -> dict[str, ob
 
 def _verify_npm_contract(root: Path, version: str) -> None:
     parser_path = root / "typescript" / "package.json"
-    parser = _verify_npm_manifest(parser_path, "okf-parser", version)
+    parser = _verify_npm_manifest(parser_path, "@franklinbaldo/okf-parser", version)
     optional = _mapping(parser.get("optionalDependencies"), "optionalDependencies")
-    if _string(optional, "okf-parser-native-linux-x64", "optionalDependencies") != version:
+    if (
+        _string(optional, "@franklinbaldo/okf-parser-native-linux-x64", "optionalDependencies")
+        != version
+    ):
         _fail(f"native optional dependency must be {version}")
     native_path = root / "native-npm-linux-x64" / "package.json"
-    _verify_npm_manifest(native_path, "okf-parser-native-linux-x64", version)
+    _verify_npm_manifest(native_path, "@franklinbaldo/okf-parser-native-linux-x64", version)
     adapter_path = root / "typescript-duckdb" / "package.json"
-    adapter = _verify_npm_manifest(adapter_path, "okf-parser-duckdb", version)
+    adapter = _verify_npm_manifest(adapter_path, "@franklinbaldo/okf-parser-duckdb", version)
     peers = _mapping(adapter.get("peerDependencies"), "peerDependencies")
-    if _string(peers, "okf-parser", "peerDependencies") != f"^{version}":
+    if _string(peers, "@franklinbaldo/okf-parser", "peerDependencies") != f"^{version}":
         _fail(f"adapter peer dependency must be ^{version}")
 
 
@@ -399,21 +402,21 @@ def _expected(version: str) -> tuple[ExpectedArtifact, ...]:
         ),
         ExpectedArtifact(
             "npm-parser",
-            "okf-parser",
+            "@franklinbaldo/okf-parser",
             "npm",
-            filename=f"okf-parser-{version}.tgz",
+            filename=f"franklinbaldo-okf-parser-{version}.tgz",
         ),
         ExpectedArtifact(
             "npm-duckdb",
-            "okf-parser-duckdb",
+            "@franklinbaldo/okf-parser-duckdb",
             "npm",
-            filename=f"okf-parser-duckdb-{version}.tgz",
+            filename=f"franklinbaldo-okf-parser-duckdb-{version}.tgz",
         ),
         ExpectedArtifact(
             "npm-native",
-            "okf-parser-native-linux-x64",
+            "@franklinbaldo/okf-parser-native-linux-x64",
             "native-npm",
-            filename=f"okf-parser-native-linux-x64-{version}.tgz",
+            filename=f"franklinbaldo-okf-parser-native-linux-x64-{version}.tgz",
         ),
     )
 

{okf_parser-0.45.4 → okf_parser-0.45.5}/tests/test_release_contract.py

@@ -45,23 +45,23 @@ def _write_source(root: Path, *, protocol_version: str = VERSION) -> None:
     (root / "typescript" / "package.json").write_text(
         json.dumps(
             {
-                "name": "okf-parser",
+                "name": "@franklinbaldo/okf-parser",
                 "version": VERSION,
-                "optionalDependencies": {"okf-parser-native-linux-x64": VERSION},
+                "optionalDependencies": {"@franklinbaldo/okf-parser-native-linux-x64": VERSION},
             }
         ),
         encoding="utf-8",
     )
     (root / "native-npm-linux-x64" / "package.json").write_text(
-        json.dumps({"name": "okf-parser-native-linux-x64", "version": VERSION}),
+        json.dumps({"name": "@franklinbaldo/okf-parser-native-linux-x64", "version": VERSION}),
         encoding="utf-8",
     )
     (root / "typescript-duckdb" / "package.json").write_text(
         json.dumps(
             {
-                "name": "okf-parser-duckdb",
+                "name": "@franklinbaldo/okf-parser-duckdb",
                 "version": VERSION,
-                "peerDependencies": {"okf-parser": f"^{VERSION}"},
+                "peerDependencies": {"@franklinbaldo/okf-parser": f"^{VERSION}"},
             }
         ),
         encoding="utf-8",
@@ -155,18 +155,25 @@ def _write_artifacts(release: Path, extra: dict[str, tuple[str, ...]] | None = N
         for member in SDIST_MEMBERS + additions.get("python-sdist", ()):
             _tar_member(archive, f"{root}/{member}", b"content\n")
     with tarfile.open(
-        native_dir / f"okf-parser-native-linux-x64-{VERSION}.tgz", mode="w:gz"
+        native_dir / f"franklinbaldo-okf-parser-native-linux-x64-{VERSION}.tgz", mode="w:gz"
     ) as archive:
         _tar_member(
             archive,
             "package/package.json",
-            json.dumps({"name": "okf-parser-native-linux-x64", "version": VERSION}).encode(),
+            json.dumps(
+                {"name": "@franklinbaldo/okf-parser-native-linux-x64", "version": VERSION}
+            ).encode(),
         )
         for member in NPM_NATIVE_MEMBERS + additions.get("npm-native", ()):
             _tar_member(archive, f"package/{member}", b"content\n")
-    kinds = {"okf-parser": "npm-parser", "okf-parser-duckdb": "npm-duckdb"}
-    for package, kind in kinds.items():
-        with tarfile.open(npm_dir / f"{package}-{VERSION}.tgz", mode="w:gz") as archive:
+    # `npm pack` flattens a scope into the leading file-name segment, so the
+    # published name and the tarball name differ for every scoped package.
+    kinds = {
+        "@franklinbaldo/okf-parser": ("npm-parser", "franklinbaldo-okf-parser"),
+        "@franklinbaldo/okf-parser-duckdb": ("npm-duckdb", "franklinbaldo-okf-parser-duckdb"),
+    }
+    for package, (kind, stem) in kinds.items():
+        with tarfile.open(npm_dir / f"{stem}-{VERSION}.tgz", mode="w:gz") as archive:
             _tar_member(
                 archive,
                 "package/package.json",
@@ -201,7 +208,7 @@ def test_verify_source_rejects_stale_native_optional_dependency(tmp_path: Path)
     _write_source(tmp_path)
     parser_path = tmp_path / "typescript" / "package.json"
     parser = json.loads(parser_path.read_text(encoding="utf-8"))
-    parser["optionalDependencies"]["okf-parser-native-linux-x64"] = "1.2.2"
+    parser["optionalDependencies"]["@franklinbaldo/okf-parser-native-linux-x64"] = "1.2.2"
     parser_path.write_text(json.dumps(parser), encoding="utf-8")
     with pytest.raises(ContractError, match="native optional dependency"):
         verify_source(tmp_path)
@@ -320,7 +327,7 @@ def test_verify_contents_rejects_members_outside_package_root(tmp_path: Path) ->
     _write_source(tmp_path)
     release = tmp_path / "release"
     _write_artifacts(release)
-    tarball = release / "npm" / f"okf-parser-{VERSION}.tgz"
+    tarball = release / "npm" / f"franklinbaldo-okf-parser-{VERSION}.tgz"
     with tarfile.open(tarball, mode="r:gz") as archive:
         members = [(member.name, _tar_bytes(archive, member)) for member in archive.getmembers()]
     with tarfile.open(tarball, mode="w:gz") as archive:

{okf_parser-0.45.4 → okf_parser-0.45.5}/typescript/README.md

@@ -11,12 +11,12 @@ the same observable contract as the Python package while using an idiomatic
 immutable TypeScript core.
 
 ```bash
-npm install okf-parser
+npm install @franklinbaldo/okf-parser
 npx okf-parser-ts check ./knowledge
 ```
 
 ```ts
-import { checkBundle, exportZod, parseDocumentContent } from "okf-parser";
+import { checkBundle, exportZod, parseDocumentContent } from "@franklinbaldo/okf-parser";
 
 const parsed = parseDocumentContent(`---\ntype: Reference\ncount: 0012\n---\n`);
 const report = await checkBundle("./knowledge");
@@ -49,15 +49,15 @@ to errors. The slug derivation is shared with the Python package through
 Formatting is read-only unless `--write` is explicit:
 
 ```bash
-npx --package okf-parser okf-parser-ts format ./knowledge
-npx --package okf-parser okf-parser-ts format ./knowledge --write
+npx --package @franklinbaldo/okf-parser okf-parser-ts format ./knowledge
+npx --package @franklinbaldo/okf-parser okf-parser-ts format ./knowledge --write
 ```
 
 The library exposes both the pure one-document formatter and the filesystem
 operation:
 
 ```ts
-import { formatMarkdown, formatPath } from "okf-parser";
+import { formatMarkdown, formatPath } from "@franklinbaldo/okf-parser";
 
 const canonical = formatMarkdown("# Heading\n\n-   item\n");
 const report = await formatPath("./knowledge", { write: true });
@@ -74,7 +74,7 @@ formatted before the first write.
 The package includes a read-only stdio MCP server:
 
 ```bash
-npx --package okf-parser okf-parser-ts-mcp
+npx --package @franklinbaldo/okf-parser okf-parser-ts-mcp
 ```
 
 A typical host configuration is:
@@ -109,11 +109,11 @@ DuckDB support is published separately so native database bindings are never
 installed for parser-only consumers:
 
 ```bash
-npm install okf-parser okf-parser-duckdb
+npm install @franklinbaldo/okf-parser okf-parser-duckdb
 ```
 
 ```ts
-import { exportDuckDb } from "okf-parser-duckdb";
+import { exportDuckDb } from "@franklinbaldo/okf-parser-duckdb";
 
 await exportDuckDb("./knowledge", { database: "knowledge.duckdb" });
 ```

{okf_parser-0.45.4 → okf_parser-0.45.5}/typescript/package-lock.json

@@ -1,12 +1,12 @@
 {
-  "name": "okf-parser",
-  "version": "0.44.0",
+  "name": "@franklinbaldo/okf-parser",
+  "version": "0.45.5",
   "lockfileVersion": 3,
   "requires": true,
   "packages": {
     "": {
-      "name": "okf-parser",
-      "version": "0.44.0",
+      "name": "@franklinbaldo/okf-parser",
+      "version": "0.45.5",
       "license": "MIT",
       "dependencies": {
         "@modelcontextprotocol/sdk": "^1.30.0",
@@ -35,12 +35,12 @@
         "node": ">=22"
       },
       "optionalDependencies": {
-        "okf-parser-native-linux-x64": "0.44.0"
+        "@franklinbaldo/okf-parser-native-linux-x64": "file:../native-npm-linux-x64"
       }
     },
     "../native-npm-linux-x64": {
-      "name": "okf-parser-native-linux-x64",
-      "version": "0.44.0",
+      "name": "@franklinbaldo/okf-parser-native-linux-x64",
+      "version": "0.45.5",
       "cpu": [
         "x64"
       ],
@@ -495,6 +495,10 @@
         "node": ">=18"
       }
     },
+    "node_modules/@franklinbaldo/okf-parser-native-linux-x64": {
+      "resolved": "../native-npm-linux-x64",
+      "link": true
+    },
     "node_modules/@hono/node-server": {
       "version": "2.0.12",
       "resolved": "https://registry.npmjs.org/@hono/node-server/-/node-server-2.0.12.tgz",
@@ -2990,10 +2994,6 @@
         "url": "https://github.com/sponsors/ljharb"
       }
     },
-    "node_modules/okf-parser-native-linux-x64": {
-      "resolved": "../native-npm-linux-x64",
-      "link": true
-    },
     "node_modules/on-finished": {
       "version": "2.4.1",
       "resolved": "https://registry.npmjs.org/on-finished/-/on-finished-2.4.1.tgz",

{okf_parser-0.45.4 → okf_parser-0.45.5}/typescript/package.json

@@ -1,6 +1,6 @@
 {
-  "name": "okf-parser",
-  "version": "0.45.4",
+  "name": "@franklinbaldo/okf-parser",
+  "version": "0.45.5",
   "description": "Native TypeScript parser, validator, formatter, graph inspector, schema exporter, and MCP server for Open Knowledge Format bundles",
   "type": "module",
   "license": "MIT",
@@ -15,7 +15,7 @@
   "bin": {"okf-parser-ts": "./dist/cli.js", "okf-parser-ts-mcp": "./dist/mcp-cli.js"},
   "scripts": {"build": "tsc -p tsconfig.build.json", "check": "tsc -p tsconfig.json --noEmit", "test": "vitest run", "test:watch": "vitest", "prepack": "npm run build"},
   "dependencies": {"@modelcontextprotocol/sdk": "^1.30.0", "markdown-it": "^14.1.0", "mdast-util-frontmatter": "^2.0.1", "mdast-util-from-markdown": "^2.0.3", "mdast-util-gfm": "^3.0.0", "mdast-util-to-markdown": "^2.1.2", "micromark-extension-frontmatter": "^2.0.0", "micromark-extension-gfm": "^3.0.0", "yaml": "^2.8.1", "zod": "^4.0.0"},
-  "optionalDependencies": {"okf-parser-native-linux-x64": "0.45.4"},
+  "optionalDependencies": {"@franklinbaldo/okf-parser-native-linux-x64": "0.45.5"},
   "devDependencies": {"@types/markdown-it": "^14.1.2", "@types/node": "^24.0.0", "@types/unist": "^3.0.3", "typescript": "^5.9.0", "vitest": "^3.2.4"},
   "keywords": ["okf", "open-knowledge-format", "markdown", "formatter", "knowledge-graph", "json-schema", "zod", "mcp", "model-context-protocol", "typescript"],
   "repository": {"type": "git", "url": "git+https://github.com/franklinbaldo/okf-parser.git", "directory": "typescript"}

{okf_parser-0.45.4 → okf_parser-0.45.5}/typescript/src/rust-core.ts

@@ -23,7 +23,7 @@ function binaryName(): string {
 
 function nativePackageName(): string | undefined {
   if (process.platform === "linux" && process.arch === "x64") {
-    return "okf-parser-native-linux-x64";
+    return "@franklinbaldo/okf-parser-native-linux-x64";
   }
   return undefined;
 }

okf_parser-0.45.5/typescript/src/version.ts

@@ -0,0 +1 @@
+export const PROTOCOL_VERSION = "0.45.5";

{okf_parser-0.45.4 → okf_parser-0.45.5}/typescript-duckdb/README.md

@@ -4,19 +4,19 @@ title: okf-parser DuckDB adapter
 description: Optional native DuckDB materialization for the TypeScript parser
 ---
 
-# okf-parser-duckdb
+# @franklinbaldo/okf-parser-duckdb
 
-Optional DuckDB materialization adapter for the TypeScript `okf-parser` package.
+Optional DuckDB materialization adapter for the TypeScript `@franklinbaldo/okf-parser` package.
 It uses the official promise-native `@duckdb/node-api` client and remains a
 separate package so native database bindings never burden parser-only users.
 
 ```bash
-npm install okf-parser okf-parser-duckdb
+npm install @franklinbaldo/okf-parser @franklinbaldo/okf-parser-duckdb
 ```
 
 ```ts
 import { DuckDBConnection } from "@duckdb/node-api";
-import { attachOkf } from "okf-parser-duckdb";
+import { attachOkf } from "@franklinbaldo/okf-parser-duckdb";
 
 const connection = await DuckDBConnection.create();
 const report = await attachOkf(connection, "./knowledge");
@@ -25,7 +25,7 @@ const report = await attachOkf(connection, "./knowledge");
 To create or update a persistent database file:
 
 ```ts
-import { exportDuckDb } from "okf-parser-duckdb";
+import { exportDuckDb } from "@franklinbaldo/okf-parser-duckdb";
 
 const report = await exportDuckDb("./knowledge", {
   database: "knowledge.duckdb",
@@ -36,7 +36,7 @@ const report = await exportDuckDb("./knowledge", {
 Or use the CLI:
 
 ```bash
-npx --package okf-parser-duckdb okf-parser-ts-duckdb ./knowledge \
+npx --package @franklinbaldo/okf-parser-duckdb okf-parser-ts-duckdb ./knowledge \
   --database knowledge.duckdb
 ```