@opum-ai/lore 0.6.0 → 0.6.1

package/LICENSE

@@ -1,6 +1,6 @@
 MIT License
 
-Copyright (c) 2026 Jeremy Newhouse
+Copyright (c) 2026 Opum AI
 
 Permission is hereby granted, free of charge, to any person obtaining a copy
 of this software and associated documentation files (the "Software"), to deal

package/README.md

@@ -1,15 +1,26 @@
 # lore
 
 > A thin, OKF-native documentation CLI that couples repo-resident docs to
-> Backlog.md and serves them to coding agents and humans — CLI-first.
+> Backlog.md, Quest, or Jira tasks and serves them to coding agents and
+> humans — CLI-first.
 
 `lore` makes your repository's `docs/` tree a first-class, agent-readable
 [Open Knowledge Format](https://github.com/GoogleCloudPlatform/knowledge-catalog/tree/main/okf)
-bundle, couples that bundle to [Backlog.md](https://github.com/MrLesk/Backlog.md)
-tasks, and exposes it through a deterministic, non-interactive CLI. The
-repository is the single source of truth — the bundle is plain markdown with
-YAML frontmatter that renders on GitHub, in Obsidian, and under
-MkDocs/Docusaurus, with or without `lore` installed.
+bundle, couples that bundle to task-tracker records, and exposes it through a
+deterministic, non-interactive CLI. The repository is the single source of
+truth — the bundle is plain markdown with YAML frontmatter that renders on
+GitHub, in Obsidian, and under MkDocs/Docusaurus, with or without `lore`
+installed.
+
+**Tracker backend is a choice, not a dependency.** `lore init --tracker
+<quest|backlog|jira|none>` selects it; `quest` and `jira` are just as
+first-class as the original `backlog` integration below, each with its own
+adapter and coupling contract. `lore init`'s interactive wizard checks
+whichever binary is on `PATH` and offers to migrate an existing Backlog.md
+project into Quest (`--migrate-backlog`) when both are present. The rest of
+this README documents the original, most-detailed integration —
+[Backlog.md](https://github.com/MrLesk/Backlog.md) — as a worked example of
+the coupling contract; see `lore init --help` for the Quest and Jira flags.
 
 `lore` is **thin** and **zero-config** by design. It does not reimplement
 Backlog.md, Confluence, or the documentation consumers it scaffolds for. Its
@@ -19,15 +30,15 @@ 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.
-- Published on npm as **`@opum-ai/lore@0.5.0`** (bin `lore`) with six
+- Published on npm as **`@opum-ai/lore@0.6.0`** (bin `lore`) with six
   exact-pinned platform packages, including Windows ARM64.
 - 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: 0.5.0 released.** Tag `v0.5.0`, the qualified workflow artifacts,
+> **Status: 0.6.0 released.** Tag `v0.6.0`, the qualified workflow artifacts,
 > all seven public `@opum-ai/lore*` npm packages, and a clean registry install
-> agree on `0.5.0`. Trusted Publishing is configured for every package; the
+> agree on `0.6.0`. Trusted Publishing is configured for every package; the
 > owner lifted the `publish: true` prohibition on 2026-08-29 (LCLI-278), so a
 > release is a single `gh workflow run release.yml --ref v<version> -f
 > publish=true` dispatch. See
@@ -35,7 +46,12 @@ semantic exit codes, machine-readable `--json`).
 
 ---
 
-## The headline: lore reads Backlog.md via JSON
+## The Backlog.md integration: lore reads it via JSON
+
+The section below documents `lore`'s original tracker integration in full
+technical detail as a worked example; `--tracker quest` and `--tracker jira`
+have their own contracts, summarized above and covered in
+[docs/reference/](docs/reference/).
 
 `lore` couples docs to tasks by reading Backlog.md's **JSON** output — not by
 scraping text and not by importing Backlog.md internals or hand-editing its task
@@ -307,10 +323,10 @@ The full design lives in this repo's OKF bundle under [`docs/`](docs/index.md):
 
 ## Contributing
 
-This is a private repo (`main` + `dev`; `dev` is the default branch). See
+This repository is public (`main` + `dev`; `dev` is the default branch). See
 [CONTRIBUTING](CONTRIBUTING.md), the [Code of Conduct](CODE_OF_CONDUCT.md), and
 [SECURITY](SECURITY.md).
 
 ## License
 
-[MIT](LICENSE) © 2026 Jeremy Newhouse.
+[MIT](LICENSE) © 2026 Opum AI.

package/package.json

@@ -1,11 +1,26 @@
 {
   "name": "@opum-ai/lore",
-  "version": "0.6.0",
-  "author": "Jeremy Newhouse",
+  "version": "0.6.1",
+  "author": "Opum AI",
   "repository": {
     "type": "git",
     "url": "git+https://github.com/opum-ai/lore-cli.git"
   },
+  "homepage": "https://loregraph.dev",
+  "bugs": {
+    "url": "https://github.com/opum-ai/lore-cli/issues"
+  },
+  "keywords": [
+    "cli",
+    "documentation",
+    "docs",
+    "okf",
+    "backlog",
+    "quest",
+    "jira",
+    "ai-agents",
+    "claude-code"
+  ],
   "devDependencies": {
     "@ladybugdb/core": "0.19.0",
     "@biomejs/biome": "2.4.12",
@@ -23,17 +38,17 @@
     "zod": "4.4.3"
   },
   "optionalDependencies": {
-    "@opum-ai/lore-darwin-arm64": "0.6.0",
-    "@opum-ai/lore-darwin-x64": "0.6.0",
-    "@opum-ai/lore-linux-arm64": "0.6.0",
-    "@opum-ai/lore-linux-x64": "0.6.0",
-    "@opum-ai/lore-win32-arm64": "0.6.0",
-    "@opum-ai/lore-win32-x64": "0.6.0"
+    "@opum-ai/lore-darwin-arm64": "0.6.1",
+    "@opum-ai/lore-darwin-x64": "0.6.1",
+    "@opum-ai/lore-linux-arm64": "0.6.1",
+    "@opum-ai/lore-linux-x64": "0.6.1",
+    "@opum-ai/lore-win32-arm64": "0.6.1",
+    "@opum-ai/lore-win32-x64": "0.6.1"
   },
   "bin": {
     "lore": "bin/lore.cjs"
   },
-  "description": "Thin, OKF-native documentation CLI that couples repo-resident docs to Backlog.md and serves them to agents and humans.",
+  "description": "Thin, OKF-native documentation CLI that couples repo-resident docs to Backlog.md, Quest, or Jira tasks and serves them to agents and humans.",
   "engines": {
     "bun": ">=1.3.14"
   },