@opum-ai/lore 0.1.1 → 0.3.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (2) hide show
  1. package/README.md +19 -23
  2. package/package.json +7 -7
package/README.md CHANGED
@@ -5,7 +5,7 @@
5
5
 
6
6
  `lore` makes your repository's `docs/` tree a first-class, agent-readable
7
7
  [Open Knowledge Format](https://github.com/GoogleCloudPlatform/knowledge-catalog/tree/main/okf)
8
- (OKF v0.1) bundle, couples that bundle to [Backlog.md](https://github.com/MrLesk/Backlog.md)
8
+ bundle, couples that bundle to [Backlog.md](https://github.com/MrLesk/Backlog.md)
9
9
  tasks, and exposes it through a deterministic, non-interactive CLI. The
10
10
  repository is the single source of truth — the bundle is plain markdown with
11
11
  YAML frontmatter that renders on GitHub, in Obsidian, and under
@@ -19,20 +19,18 @@ semantic exit codes, machine-readable `--json`).
19
19
 
20
20
  - Built on **Bun + TypeScript** with an exact-pinned **Commander** parser fed by
21
21
  Lore's capability manifest; Lore still owns output, errors, and process lifecycle.
22
- - Published on npm as **`@opum-ai/lore@0.1.0`** (bin `lore`) with five
23
- exact-pinned platform packages.
24
- - The next release matrix adds a sixth native package for **Windows ARM64**;
25
- `0.1.0` itself remains the immutable five-platform release described below.
22
+ - Published on npm as **`@opum-ai/lore@0.2.0`** (bin `lore`) with six
23
+ exact-pinned platform packages, including Windows ARM64.
26
24
  - The agent bridge is a generated **`.claude/skills/lore/SKILL.md`** plus a tiny
27
25
  CLAUDE.md nudge and `lore instructions`. An **MCP server is secondary and
28
26
  deferred to v2**.
29
27
 
30
- > **Status: 0.1.0 released.** Tag `v0.1.0`, the qualified workflow artifacts,
31
- > all six public `@opum-ai/lore*` npm packages, a clean registry install, and
32
- > the private repository's GitHub Release agree on `0.1.0`. Trusted Publishing
28
+ > **Status: 0.2.0 released.** Tag `v0.2.0`, the qualified workflow artifacts,
29
+ > all seven public `@opum-ai/lore*` npm packages, a clean registry install, and
30
+ > the private repository's GitHub Release agree on `0.2.0`. Trusted Publishing
33
31
  > is configured for every package. LCLI-278 still blocks future automated
34
32
  > `publish: true` dispatches; it does not invalidate the explicitly authorized
35
- > interactive `0.1.0` bootstrap. See
33
+ > interactive publication. See
36
34
  > [Lore CLI release truth](docs/reference/lore-cli-release-truth.md).
37
35
 
38
36
  ---
@@ -78,34 +76,32 @@ The package and bin are `@opum-ai/lore` and `lore`:
78
76
 
79
77
  ```bash
80
78
  # Node / npm
81
- npx @opum-ai/lore@0.1.0 --help
79
+ npx @opum-ai/lore --help
82
80
 
83
81
  # Bun
84
- bunx @opum-ai/lore@0.1.0 --help
82
+ bunx @opum-ai/lore --help
85
83
 
86
84
  # Global npm install
87
- npm install -g @opum-ai/lore@0.1.0
85
+ npm install -g @opum-ai/lore
88
86
  ```
89
87
 
90
- `0.1.0` declared LadybugDB as a runtime dependency, so npm versions with
91
- install-script approval may require
92
- `npm install -g --allow-scripts=@ladybugdb/core @opum-ai/lore@0.1.0`. The next
93
- release removes that exception: the launcher installs only the matching
94
- script-free platform package, while qualified macOS/Linux executables embed
95
- LadybugDB's native addon at build time. Windows continues to use the reference
96
- backend and installs no LadybugDB package.
88
+ Starting with `0.2.0`, the launcher installs only the matching script-free
89
+ platform package, so a current install does not require an install-script
90
+ approval exception. Qualified macOS/Linux executables embed LadybugDB's native
91
+ addon at build time. Windows continues to use the reference backend and
92
+ installs no LadybugDB package.
97
93
 
98
94
  Or add it to a project:
99
95
 
100
96
  ```bash
101
- bun add -d @opum-ai/lore@0.1.0 # or: npm i -D @opum-ai/lore@0.1.0
97
+ bun add -d @opum-ai/lore # or: npm i -D @opum-ai/lore
102
98
  ```
103
99
 
104
100
  The npm package is a dual artifact: a Node `.cjs` launcher plus a
105
101
  per-platform compiled binary delivered as `optionalDependencies` (built with
106
- `bun build --compile`, `-baseline` x64 targets). Starting with the next release,
107
- all JavaScript libraries are build-only and are not installed transitively with
108
- the launcher. You also need a
102
+ `bun build --compile`, `-baseline` x64 targets). In `0.2.0`, all JavaScript
103
+ libraries became build-only and are not installed transitively with the
104
+ launcher. You also need a
109
105
  `--json`-capable Backlog.md (>=1.49.0) on `PATH` — e.g. `npm install -g
110
106
  backlog.md`; see the [runbook](docs/runbooks/backlog-json-patch.md).
111
107
 
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@opum-ai/lore",
3
- "version": "0.1.1",
3
+ "version": "0.3.0",
4
4
  "description": "Thin, OKF-native documentation CLI that couples repo-resident docs to Backlog.md and serves them to agents and humans.",
5
5
  "publishConfig": {
6
6
  "access": "public"
@@ -25,12 +25,12 @@
25
25
  "LICENSE"
26
26
  ],
27
27
  "optionalDependencies": {
28
- "@opum-ai/lore-darwin-arm64": "0.1.1",
29
- "@opum-ai/lore-darwin-x64": "0.1.1",
30
- "@opum-ai/lore-linux-arm64": "0.1.1",
31
- "@opum-ai/lore-linux-x64": "0.1.1",
32
- "@opum-ai/lore-win32-arm64": "0.1.1",
33
- "@opum-ai/lore-win32-x64": "0.1.1"
28
+ "@opum-ai/lore-darwin-arm64": "0.3.0",
29
+ "@opum-ai/lore-darwin-x64": "0.3.0",
30
+ "@opum-ai/lore-linux-arm64": "0.3.0",
31
+ "@opum-ai/lore-linux-x64": "0.3.0",
32
+ "@opum-ai/lore-win32-arm64": "0.3.0",
33
+ "@opum-ai/lore-win32-x64": "0.3.0"
34
34
  },
35
35
  "scripts": {
36
36
  "lore": "bun run src/cli.ts",