@opum-ai/lore 0.1.0 → 0.1.1

package/README.md

@@ -19,18 +19,21 @@ semantic exit codes, machine-readable `--json`).
 
 - Built on **Bun + TypeScript** with an exact-pinned **Commander** parser fed by
   Lore's capability manifest; Lore still owns output, errors, and process lifecycle.
-- Prepared for npm distribution as **`@opum-ai/lore@0.1.0`** (bin `lore`);
-  registry publication is not claimed until the release-truth evidence lands.
+- Published on npm as **`@opum-ai/lore@0.1.0`** (bin `lore`) with five
+  exact-pinned platform packages.
+- The next release matrix adds a sixth native package for **Windows ARM64**;
+  `0.1.0` itself remains the immutable five-platform release described below.
 - The agent bridge is a generated **`.claude/skills/lore/SKILL.md`** plus a tiny
   CLAUDE.md nudge and `lore instructions`. An **MCP server is secondary and
   deferred to v2**.
 
-> **Status: prepared 0.1.0 release candidate.** The six manifests and exact
-> optional-dependency pins are set to `0.1.0`, but the repository has no
-> release tag or artifact and `@opum-ai/lore` is absent from npm. The upstream
-> Backlog.md dependency gate is complete
-> (LCLI-253), but the repository-owner publication-control gate remains open
-> (LCLI-278). See [Lore CLI release truth](docs/reference/lore-cli-release-truth.md).
+> **Status: 0.1.0 released.** Tag `v0.1.0`, the qualified workflow artifacts,
+> all six public `@opum-ai/lore*` npm packages, a clean registry install, and
+> the private repository's GitHub Release agree on `0.1.0`. Trusted Publishing
+> is configured for every package. LCLI-278 still blocks future automated
+> `publish: true` dispatches; it does not invalidate the explicitly authorized
+> interactive `0.1.0` bootstrap. See
+> [Lore CLI release truth](docs/reference/lore-cli-release-truth.md).
 
 ---
 
@@ -71,44 +74,52 @@ Full details: [Backlog CLI contract](docs/reference/backlog-cli-contract.md) and
 
 ## Install
 
-`@opum-ai/lore` is not published. Until the release-truth evidence is
-complete, use a trusted source checkout and its pinned toolchain; do not expect
-these planned registry commands to work.
-
-After a verified release, the intended package and bin are
-`@opum-ai/lore` and `lore`:
+The package and bin are `@opum-ai/lore` and `lore`:
 
 ```bash
 # Node / npm
-npx @opum-ai/lore --help
+npx @opum-ai/lore@0.1.0 --help
 
 # Bun
-bunx @opum-ai/lore --help
+bunx @opum-ai/lore@0.1.0 --help
+
+# Global npm install
+npm install -g @opum-ai/lore@0.1.0
 ```
 
+`0.1.0` declared LadybugDB as a runtime dependency, so npm versions with
+install-script approval may require
+`npm install -g --allow-scripts=@ladybugdb/core @opum-ai/lore@0.1.0`. The next
+release removes that exception: the launcher installs only the matching
+script-free platform package, while qualified macOS/Linux executables embed
+LadybugDB's native addon at build time. Windows continues to use the reference
+backend and installs no LadybugDB package.
+
 Or add it to a project:
 
 ```bash
-bun add -d @opum-ai/lore   # or: npm i -D @opum-ai/lore
+bun add -d @opum-ai/lore@0.1.0   # or: npm i -D @opum-ai/lore@0.1.0
 ```
 
-The planned npm package is a dual artifact: a Node `.cjs` launcher plus a
+The npm package is a dual artifact: a Node `.cjs` launcher plus a
 per-platform compiled binary delivered as `optionalDependencies` (built with
-`bun build --compile`, `-baseline` x64 targets). You also need a
+`bun build --compile`, `-baseline` x64 targets). Starting with the next release,
+all JavaScript libraries are build-only and are not installed transitively with
+the launcher. You also need a
 `--json`-capable Backlog.md (>=1.49.0) on `PATH` — e.g. `npm install -g
 backlog.md`; see the [runbook](docs/runbooks/backlog-json-patch.md).
 
-### Private-repository CI before npm publication
+### Private-repository CI
 
 Repositories inside the `opum-ai` organization can run strict Lore gates
-without a cross-repository PAT or a public npm release:
+from the private source repository through the immutable composite action:
 
 ```yaml
 - uses: actions/checkout@v6
 - uses: opum-ai/lore-cli/.github/actions/strict-check@<full-commit-sha>
 ```
 
-The private composite action installs Bun 1.2.23 and this action revision's
+The private composite action installs Bun 1.3.14 and this action revision's
 frozen dependencies, installs the published JSON-capable `backlog.md` version
 pinned by the Docker E2E harness, then runs `lore validate --strict` and `lore
 check --strict` against the caller workspace. Consumer workflows must replace

package/bin/lore.cjs

@@ -11,11 +11,10 @@
  * `os`/`cpu` fields so only the matching one lands in `node_modules`) and exec it,
  * forwarding argv/stdio/exit code verbatim.
  *
- * NOT YET the active `bin` target: `package.json`'s `bin.lore` still points at
- * `src/cli.ts` (the pre-publish install path — git dependency, `npm`/`bun link`), because
- * this file only works once the five platform packages it resolves are actually published.
- * Flipping `bin.lore` to this file is the first step of cutting a real release, not a
- * standing state — see docs/runbooks/release-publishing.md.
+ * This is the active `bin` target since the `0.1.0` release. It resolves only
+ * published platform packages, so source contributors should use `bun run lore`
+ * when exercising an unpublished platform addition; see
+ * docs/runbooks/release-publishing.md.
  *
  * Kept deliberately tiny and dependency-free plain CommonJS (`.cjs`, so it runs as
  * CJS regardless of the package's own `"type": "module"`) — per ADR-0001, "the
@@ -24,7 +23,7 @@
  * never imports `src/`.
  */
 
-const { spawnSync } = require("node:child_process");
+const { spawn, spawnSync } = require("node:child_process");
 const os = require("node:os");
 const path = require("node:path");
 
@@ -77,6 +76,30 @@ function exitCodeForSignal(signal) {
   return signalNumber === undefined ? 1 : 128 + signalNumber;
 }
 
+/**
+ * Windows Bun executables can lose output when they inherit a redirected file
+ * handle through Node. Give the executable real Node-owned pipes instead, then
+ * stream those pipes to the launcher's own stdout/stderr. This preserves live
+ * output without imposing spawnSync's maxBuffer limit.
+ */
+function spawnWindowsBinary(binaryPath) {
+  const child = spawn(binaryPath, process.argv.slice(2), {
+    stdio: ["inherit", "pipe", "pipe"],
+  });
+  child.stdout.pipe(process.stdout);
+  child.stderr.pipe(process.stderr);
+
+  let spawnFailed = false;
+  child.once("error", (err) => {
+    spawnFailed = true;
+    process.stderr.write(`lore: failed to run the compiled binary at ${binaryPath}: ${err.message}\n`);
+    process.exitCode = 1;
+  });
+  child.once("close", (status, signal) => {
+    if (!spawnFailed) process.exitCode = status === null ? exitCodeForSignal(signal) : status;
+  });
+}
+
 function main() {
   let binaryPath;
   try {
@@ -92,12 +115,17 @@ function main() {
       `lore: no compiled binary found for this platform (${process.platform}-${process.arch}).\n` +
         `Expected the optional dependency "${platformPackageName()}" to be installed alongside\n` +
         `@opum-ai/lore, but it is missing. If your platform/architecture is one lore\n` +
-        `ships (macOS x64/arm64, Linux x64/arm64, Windows x64), try reinstalling with npm;\n` +
+        `ships (macOS x64/arm64, Linux x64/arm64, Windows x64/arm64), try reinstalling with npm;\n` +
         `otherwise this platform is not yet supported.\n`,
     );
     process.exit(1);
   }
 
+  if (process.platform === "win32") {
+    spawnWindowsBinary(binaryPath);
+    return;
+  }
+
   const result = spawnSync(binaryPath, process.argv.slice(2), { stdio: "inherit" });
   if (result.error) {
     process.stderr.write(`lore: failed to run the compiled binary at ${binaryPath}: ${result.error.message}\n`);

package/package.json

@@ -1,12 +1,11 @@
 {
   "name": "@opum-ai/lore",
-  "version": "0.1.0",
+  "version": "0.1.1",
   "description": "Thin, OKF-native documentation CLI that couples repo-resident docs to Backlog.md and serves them to agents and humans.",
   "publishConfig": {
     "access": "public"
   },
   "type": "module",
-  "module": "src/cli.ts",
   "bin": {
     "lore": "bin/lore.cjs"
   },
@@ -16,26 +15,26 @@
     "type": "git",
     "url": "git+https://github.com/opum-ai/lore-cli.git"
   },
-  "packageManager": "bun@1.2.23",
+  "packageManager": "bun@1.3.14",
   "engines": {
-    "bun": ">=1.2.23"
+    "bun": ">=1.3.14"
   },
   "files": [
-    "src",
     "bin",
     "README.md",
     "LICENSE"
   ],
   "optionalDependencies": {
-    "@opum-ai/lore-darwin-arm64": "0.1.0",
-    "@opum-ai/lore-darwin-x64": "0.1.0",
-    "@opum-ai/lore-linux-arm64": "0.1.0",
-    "@opum-ai/lore-linux-x64": "0.1.0",
-    "@opum-ai/lore-win32-x64": "0.1.0"
+    "@opum-ai/lore-darwin-arm64": "0.1.1",
+    "@opum-ai/lore-darwin-x64": "0.1.1",
+    "@opum-ai/lore-linux-arm64": "0.1.1",
+    "@opum-ai/lore-linux-x64": "0.1.1",
+    "@opum-ai/lore-win32-arm64": "0.1.1",
+    "@opum-ai/lore-win32-x64": "0.1.1"
   },
   "scripts": {
     "lore": "bun run src/cli.ts",
-    "build": "bun build --compile src/cli.ts --outfile dist/lore",
+    "build": "bun build --compile src/compiled.ts --outfile dist/lore",
     "typecheck": "tsc --noEmit",
     "format": "biome format --write .",
     "lint": "biome check .",
@@ -45,23 +44,24 @@
     "test:coverage": "bun test --coverage"
   },
   "devDependencies": {
+    "@ladybugdb/core": "0.19.0",
     "@biomejs/biome": "2.4.12",
     "@playwright/test": "1.62.1",
-    "@types/bun": "^1.2.23",
+    "@types/bun": "^1.3.14",
     "@types/mdast": "4.0.4",
-    "typescript": "^5"
-  },
-  "dependencies": {
-    "@ladybugdb/core": "0.19.0",
     "commander": "15.0.0",
     "github-slugger": "2.0.0",
     "ipaddr.js": "2.4.0",
     "js-yaml": "5.2.2",
     "mdast-util-from-markdown": "2.0.3",
     "string-width": "8.2.2",
+    "typescript": "^5",
     "zod": "4.4.3"
   },
   "trustedDependencies": [
     "@ladybugdb/core"
-  ]
+  ],
+  "patchedDependencies": {
+    "@ladybugdb/core@0.19.0": "patches/@ladybugdb%2Fcore@0.19.0.patch"
+  }
 }