superbee 0.3.0-pre.2 → 0.3.0-pre.5

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "superbee",
-  "version": "0.3.0-pre.2",
+  "version": "0.3.0-pre.5",
   "type": "module",
   "description": "Agent-facing Superbee CLI for reading and writing local OKF knowledge bundles: context notes, docs, cross-links, and live bundle Views.",
   "keywords": [
@@ -86,6 +86,6 @@
     "darwin",
     "linux"
   ],
-  "readme": "# superbee\n\nShared, versioned, conflict-safe knowledge for AI coding agents, stored as plain markdown in\nyour repo.\n\nSuperbee is pre-1.0. Commands and formats may change between releases.\n\n## What is Superbee?\n\nAgents forget everything between sessions, overwrite each other's work, and keep what they know\ninvisible to the humans they work for. Superbee fixes all three with a **knowledge bundle**: a\nfolder of markdown documents, by convention `.superbee/` at your project root, that agents read\nand write through a small command-line tool.\n\n- **Context that persists.** Agents write context notes, decisions, plans, and research into the\n  bundle. The next session, or a different agent, picks up where the last one left off. An\n  optional `SessionStart` hook for Claude Code, Codex, and OpenCode orients every new session\n  automatically.\n- **Safe for many writers.** Each write can carry the actor that made it. A writer can name the\n  version it last read; if anyone changed the document since, the write fails with a typed\n  conflict error instead of silently overwriting their work.\n- **Visible to humans.** The bundle is plain markdown. Open it in any editor, render it on\n  GitHub, diff it in git. `superbee ui` serves it locally as cross-linked pages with backlinks and\n  a live activity feed. No bundle content leaves your machine until you run `superbee sync`, which\n  shares the bundle with teammates through the board: a copy of the bundle kept on its own git\n  branch, separate from your code.\n- **Views on demand.** Ask your agent for a dashboard, a timeline, a filtered task queue, or a\n  reading view of one dense document. It builds a self-contained HTML page, stores it in the bundle\n  as a View, and `superbee ui` hosts it in a sandboxed frame. A View reads the bundle live and can\n  change it only through a write you confirm. Views are bundle content, so they travel with `sync`.\n- **Built for agents.** Output is structured and token-lean, and errors carry a small, stable set\n  of exit codes. Agents act on responses without parsing prose or flooding their context window.\n- **Yours, and portable.** Bundles follow the Open Knowledge Format (OKF), a convention of\n  markdown with frontmatter, so they outlive the tool: hand the folder to someone else, or read it\n  with anything that speaks markdown. New bundles are written as OKF v0.2, and existing v0.1\n  bundles keep working as they are. Reading and writing the bundle works offline; only sharing\n  needs a network. The document schemas, called kinds, live inside the bundle, so it describes\n  its own structure.\n\nThe npm package is one self-contained executable with zero runtime dependencies, plus an Agent\nSkill, an instruction file your agent loads, that teaches it how to use the tool.\n\n## Install\n\nRequires Node.js 20 or newer on macOS and Linux. Native Windows is not supported by this package.\n\n```sh\nnpm install -g superbee\n```\n\nStable releases publish on npm's `latest` tag and prereleases on `next`. To try the prerelease:\n\n```sh\nnpm install -g superbee@next\n```\n\nWindows adapters and the `superbee-windows` executable live in a separate repository and are\nnot included in `superbee`. Most Windows users should run Superbee in WSL2, where npm sees a\nLinux platform and the normal installation applies. An experimental, unsupported native Windows\nbuild is available as open source, with build-from-source instructions: https://github.com/Holaxis-ai/superbee-windows-cli\n\n### Upgrading an existing Windows installation\n\nThe first release containing the Windows extraction removes native Windows support from this\npackage. Its npm `os` metadata permits only `darwin` and `linux`, so a Windows upgrade to an affected\nversion is rejected with `EBADPLATFORM`. This applies to existing prerelease users too. Forcing the\ninstallation does not restore support: the executable refuses commands on unsupported hosts\nbefore running them (the bare `--version` flag can still identify the installed build).\n\nThere is no supported Windows replacement on npm. The alternatives are WSL2 or the experimental\nbuild from source at https://github.com/Holaxis-ai/superbee-windows-cli; neither carries a\nfirst-party support promise for native Windows. An older installed version is not converted or\nremoved by this source change, and existing bundle files are not migrated by it. Review the affected release's notes before changing an existing\nWindows installation. macOS/Linux users can continue using the normal installation and setup flow.\n\nRun `superbee version --check` to compare your install with the current stable release.\n\n## First run: let your agent finish setup\n\n`npm install` gives you the CLI. The integrations (the Agent Skill, the `SessionStart` hook, and\nMCP server registration, where MCP is the Model Context Protocol) are installed by your agent,\nnot by hand. Ask it:\n\n> Run `superbee setup` and follow its instructions.\n\nSetup itself changes nothing. It inspects your configuration and returns one safe next command at\na time, and the agent runs each with your approval. Setup knows Claude Code, Codex, and OpenCode,\nplus Claude Desktop for the MCP registration only.\n\n## Everyday use\n\nYou rarely type Superbee commands yourself. You ask your agent, and the Agent Skill translates the\nrequest into CLI calls:\n\n- \"Set up a Superbee bundle for this project and track our tasks in it.\"\n- \"Write up what we decided about the auth design as a doc, and link it to the task.\"\n- \"What did the last session leave off on? Check the context notes.\"\n- \"Sync the board so my teammate's agent sees this.\"\n- \"Give me a view of the open tasks grouped by owner.\"\n\nBehind those requests the agent uses a small set of commands: `init --dir .superbee` creates the\nbundle, `new` creates a document of a declared kind, `doc write` writes a free-form one,\n`doc update` changes a document, `link add` connects two, `list` and `doc read` query them, and\n`sync` shares the board. `superbee --help` lists the commands, and `superbee <command> --help`\ngives each one's full reference.\n\nThe two commands meant for you are the ones that show you the knowledge:\n\n```sh\nsuperbee ui --open        # the whole bundle, rendered in your browser\nsuperbee doc open <id>    # one document, by an id from `superbee list`\n```\n\n## Upgrading from aslite\n\nIf you installed the earlier `@holaxis/aslite` package or its marketplace plugin: install\n`superbee` alongside it, have your agent run `superbee setup` to migrate the integrations, then\nrun `npm uninstall -g @holaxis/aslite`. Existing `.agentstate-lite/` bundles and\n`.agentstate.json` bindings keep working with no migration.\n\n## Learn more\n\nThe [repository](https://github.com/Holaxis-ai/superbee) holds the source, the\n[CLI contract](https://github.com/Holaxis-ai/superbee/blob/main/packages/superbee/AXI-CONTRACT.md),\nand the [wire protocol](https://github.com/Holaxis-ai/superbee/blob/main/docs/WIRE-PROTOCOL.md).\n\n## License\n\nApache-2.0 © 2026 Holaxis\n",
+  "readme": "# superbee\n\nShared, versioned, conflict-safe knowledge for AI coding agents, stored as plain markdown in\nyour repo.\n\nSuperbee is pre-1.0. Commands and formats may change between releases.\n\n## What is Superbee?\n\nAgents forget everything between sessions, overwrite each other's work, and keep what they know\ninvisible to the humans they work for. Superbee fixes all three with a **knowledge bundle**: a\nfolder of markdown documents, by convention `.superbee/` at your project root, that agents read\nand write through a small command-line tool.\n\n- **Context that persists.** Agents write context notes, decisions, plans, and research into the\n  bundle. The next session, or a different agent, picks up where the last one left off. An\n  optional `SessionStart` hook for Claude Code, Codex, and OpenCode orients every new session\n  automatically.\n- **Safe for many writers.** Each write can carry the actor that made it. A writer can name the\n  version it last read; if anyone changed the document since, the write fails with a typed\n  conflict error instead of silently overwriting their work.\n- **Visible to humans.** The bundle is plain markdown. Open it in any editor, render it on\n  GitHub, diff it in git. `superbee ui` serves it locally as cross-linked pages with backlinks and\n  a live activity feed. No bundle content leaves your machine until you run `superbee sync`, which\n  shares the bundle with teammates through the board: a copy of the bundle kept on its own git\n  branch, separate from your code.\n- **Views on demand.** Ask your agent for a dashboard, a timeline, a filtered task queue, or a\n  reading view of one dense document. It builds a self-contained HTML page, stores it in the bundle\n  as a View, and `superbee ui` hosts it in a sandboxed frame. A View reads the bundle live and can\n  change it only through a write you confirm. Views are bundle content, so they travel with `sync`.\n- **Built for agents.** Output is structured and token-lean, and errors carry a small, stable set\n  of exit codes. Agents act on responses without parsing prose or flooding their context window.\n- **Yours, and portable.** Bundles follow the Open Knowledge Format (OKF), a convention of\n  markdown with frontmatter, so they outlive the tool: hand the folder to someone else, or read it\n  with anything that speaks markdown. New bundles are written as OKF v0.2, and existing v0.1\n  bundles keep working as they are. Reading and writing the bundle works offline; only sharing\n  needs a network. The document schemas, called kinds, live inside the bundle, so it describes\n  its own structure.\n\nBees build comb one cell at a time. The comb holds what the colony gathers, and its shape shows\nthe next bee where to build and what belongs where. Superbee works the same way: people and\nagents record what they learn in a structure that fits their domain, and that structure guides\nwhoever works next. Each session builds on the last instead of starting over.\n\nThe npm package is one self-contained executable with zero runtime dependencies, plus an Agent\nSkill, an instruction file your agent loads, that teaches it how to use the tool.\n\n## Install\n\nRequires Node.js 20 or newer on macOS and Linux. Native Windows is not supported by this package.\n\n```sh\nnpm install -g superbee\n```\n\nStable releases publish on npm's `latest` tag and prereleases on `next`. To try the prerelease:\n\n```sh\nnpm install -g superbee@next\n```\n\nWindows adapters and the `superbee-windows` executable live in a separate repository and are\nnot included in `superbee`. Most Windows users should run Superbee in WSL2, where npm sees a\nLinux platform and the normal installation applies. An experimental, unsupported native Windows\nbuild is available as open source, with build-from-source instructions: https://github.com/Holaxis-ai/superbee-windows-cli\n\n### Upgrading an existing Windows installation\n\nThe first release containing the Windows extraction removes native Windows support from this\npackage. Its npm `os` metadata permits only `darwin` and `linux`, so a Windows upgrade to an affected\nversion is rejected with `EBADPLATFORM`. This applies to existing prerelease users too. Forcing the\ninstallation does not restore support: the executable refuses commands on unsupported hosts\nbefore running them (the bare `--version` flag can still identify the installed build).\n\nThere is no supported Windows replacement on npm. The alternatives are WSL2 or the experimental\nbuild from source at https://github.com/Holaxis-ai/superbee-windows-cli; neither carries a\nfirst-party support promise for native Windows. An older installed version is not converted or\nremoved by this source change, and existing bundle files are not migrated by it. Review the affected release's notes before changing an existing\nWindows installation. macOS/Linux users can continue using the normal installation and setup flow.\n\nRun `superbee version --check` to compare your install with the current stable release.\n\n## First run: let your agent finish setup\n\n`npm install` gives you the CLI. The integrations (the Agent Skill, the `SessionStart` hook, and\nMCP server registration, where MCP is the Model Context Protocol) are installed by your agent,\nnot by hand. Ask it:\n\n> Run `superbee setup` and follow its instructions.\n\nSetup itself changes nothing. It inspects your configuration and returns one safe next command at\na time, and the agent runs each with your approval. Setup knows Claude Code, Codex, and OpenCode,\nplus Claude Desktop for the MCP registration only.\n\n## Everyday use\n\nYou rarely type Superbee commands yourself. You ask your agent, and the Agent Skill translates the\nrequest into CLI calls:\n\n- \"Set up a Superbee bundle for this project and track our tasks in it.\"\n- \"Write up what we decided about the auth design as a doc, and link it to the task.\"\n- \"What did the last session leave off on? Check the context notes.\"\n- \"Sync the board so my teammate's agent sees this.\"\n- \"Give me a view of the open tasks grouped by owner.\"\n\nBehind those requests the agent uses a small set of commands: `init --dir .superbee` creates the\nbundle, `new` creates a document of a declared kind, `doc write` writes a free-form one,\n`doc update` changes a document, `link add` connects two, `list` and `doc read` query them, and\n`sync` shares the board. `superbee --help` lists the commands, and `superbee <command> --help`\ngives each one's full reference.\n\nThe two commands meant for you are the ones that show you the knowledge:\n\n```sh\nsuperbee ui --open        # the whole bundle, rendered in your browser\nsuperbee doc open <id>    # one document, by an id from `superbee list`\n```\n\n## Upgrading from aslite\n\nIf you installed the earlier `@holaxis/aslite` package or its marketplace plugin: install\n`superbee` alongside it, have your agent run `superbee setup` to migrate the integrations, then\nrun `npm uninstall -g @holaxis/aslite`. Existing `.agentstate-lite/` bundles and\n`.agentstate.json` bindings keep working with no migration.\n\n## Learn more\n\nThe [repository](https://github.com/Holaxis-ai/superbee) holds the source, the\n[CLI contract](https://github.com/Holaxis-ai/superbee/blob/main/packages/superbee/AXI-CONTRACT.md),\nand the [wire protocol](https://github.com/Holaxis-ai/superbee/blob/main/docs/WIRE-PROTOCOL.md).\n\n## License\n\nApache-2.0 © 2026 Holaxis\n",
   "readmeFilename": "README.md"
 }

package/references/hosted-checkout.md

@@ -4,6 +4,54 @@ Read this when you work in a folder made by `superbee checkout`, or when `superb
 conflict there. The hosted bundle is the authority. The folder is a working copy. `superbee sync`
 applies changes directly under the signed-in person's own access, and nobody has to approve them.
 
+## Finding a bundle to check out
+
+`superbee catalog list --hosted` lists the hosted bundles the signed-in person can reach on the
+host of their last sign-in (or `--host <url>`), across all their workspaces. Each row has the
+`bundle_id` that `superbee checkout <bundle-id>` takes, its `name` and `lifecycle`, the `folder` of
+an existing checkout here (null when there is none), and `ambiguous: true` when two of their
+workspaces hold the same id, which checkout refuses. If a bundle already has a `folder`, work there
+with `--dir` instead of checking it out again. The list is read live and never cached.
+
+## The folder marker, and adopting a moved or copied checkout
+
+A checkout folder carries a read-only `.superbee/checkout.json` naming its host and bundle. It is a
+note for you and the person, never an authority: nothing reads it to decide where a command goes.
+The checkout is bound by private state, keyed by the folder's path.
+
+When `status`, `home`, `bundle locate` or `session-start` report `copy_of_checkout` (and `home:
+local`), the folder was moved, copied or restored, and it is not bound here. It behaves as a plain
+local bundle, and `sync` refuses it (`unbound_copy`). Tell the person, then:
+
+- `superbee checkout --adopt <folder>` binds a folder moved on the same disk back to its own
+  checkout, with no network. Unsent edits and conflicts carry over.
+- For a copy or a restore, the same command only previews. Adopting it needs `--host <url>`, and
+  the person should confirm the host: never take the marker's host on its own. Adopt adds the
+  documents the folder lacks and never overwrites a file. A file that differs from the host's
+  version becomes a conflict (below), and a document only in the folder is sent as new by the next
+  sync, so check its `local_only` list with the person first.
+
+## Moving a local bundle or Git board to hosted
+
+`superbee publish --to hosted` moves a bundle to hosted Superbee in the person's own workspace.
+Only run it when the person asks for the move.
+
+1. Run it without `--yes` first. It makes no request. It lists what travels (documents, reserved
+   files, other files), what stays (dot-files, links), anything that blocks the move, and the
+   bundle id and host it will use. Show the person the preview. A document that does not satisfy
+   its Kind, or a Kind convention with a problem, blocks the move, because the host would refuse
+   writes to it. Fix them before publishing.
+2. When they agree, run the `--yes` command the preview names. It signs in if needed (relay the
+   link, as below), creates the bundle, and converts the folder in place into a hosted checkout.
+   No file is rewritten.
+3. A Git board is unbound from its `board` branch, but the branch stays, locally and on origin.
+   Tell the person their teammates keep using the Git board until they check out the hosted bundle
+   instead. A board that is behind its upstream is refused until `superbee sync` brings it current.
+4. `--with-history` imports a Git board's earlier versions as labeled, unverified history. Use it
+   only when the person asks for history.
+5. `TRANSIENT` with `write_outcome_unknown` means the creation may be partial: re-run the same
+   command, which finishes or confirms the same creation.
+
 ## Sign-in: relay the link, then retry
 
 Hosted commands start sign-in by themselves. When a command returns `AUTH_REQUIRED` (exit 4):
@@ -108,9 +156,16 @@ Superbee app, by the person.
 ## Refusals that belong to the person
 
 Some commands are refused in a hosted checkout with "do this in the Superbee app". Examples:
-editing Kinds or recipes, artifacts, and `doc verify`. Tell the person what to do in the app. Do
-not work around a refusal by editing files, using another command, or copying the bundle
-somewhere else.
+artifacts and `doc verify`. Tell the person what to do in the app. Editing Kinds or recipes is
+refused too, and the app cannot do it either: a hosted bundle's Kinds cannot be changed from a
+checkout. Kinds are designed in a local or Git bundle before it is published. Do not work around a
+refusal by editing files, using another command, or copying the bundle somewhere else. Taking a
+bundle out of hosted is `superbee export` (below), and only when the person asks for it.
+
+`checkout` adds the folder to the workspace catalog, where `catalog list` shows it with
+`home: hosted`. The local MCP app (`superbee mcp`) can read it by that label, but refuses every
+write there with the same "do this in the Superbee app": Views and documents written through it
+could not sync.
 
 `sync_busy` means another command is working, or is just taking or releasing the lock: wait,
 then retry, and never remove that lock. Only `lock_orphaned` means the lock's holder is gone:
@@ -119,12 +174,45 @@ confirm that no superbee command is still running, then remove the lock named in
 ## Session hooks (opt-in)
 
 - `superbee hook install` installs the SessionStart hook. In a hosted checkout, it pulls from the
-  host at the start of each session.
+  host at the start of each session. Its `workspaces` block lists the other catalog bundles with
+  their `home` (local, git or hosted) and `freshness` (when each was last pulled or fetched). It
+  pulls none of them: to work in one, get its path with `superbee catalog resolve <label> --field
+  path` and pass `--dir`, and sync a stale one only when the work needs it.
 - `superbee hook install --turn-end-sync` also installs a Stop hook for Claude Code and Codex. It
   syncs the checkout when each turn ends, and skips the network when nothing changed and the last
   pull is recent. If that sync finds a conflict, a held file or a sign-in link, the hook hands it
   back to you before the turn ends: handle it as above. It reports each condition once; the same
   unresolved condition is not reported on later turns, so check `superbee sync` yourself.
+- A Git board is never synced by the Stop hook unless the person also asks for it:
+  `superbee hook install --turn-end-sync --git-boards`. Then the shared board the session is in
+  syncs at turn end under the same rules, and a conflict comes back once, in Git's form: the
+  teammate's version is kept and yours is saved to the export file the reason names.
 - Offer the Stop hook, but install it only when the person agrees.
   `superbee hook uninstall --turn-end-sync` removes it, and `SUPERBEE_NO_TURN_SYNC=<any value>`
   turns it off for a shell.
+- Each write names the agent the sync runs under, and the host records it with the write as
+  unverified attribution, never authority: `claude-code` under Claude Code (`CLAUDECODE=1`), or
+  `SUPERBEE_VIA=<token>` (1 to 32 of `a-z 0-9 . _ -`, not starting with `superbee`).
+  `SUPERBEE_NO_VIA=<any value>` names none. Another agent started from a Claude Code shell (a
+  Codex in a tmux pane, for example) inherits `CLAUDECODE=1` and is named `claude-code` unless
+  `SUPERBEE_VIA` is set. A token the host would refuse is not sent, and the receipt says so
+  (`via_ignored`).
+
+## Export: taking a bundle out of hosted
+
+Run `superbee export` only when the person asks for a copy outside hosted, or to stop using a
+checkout. It never changes the hosted bundle, and it carries the current revision only, never
+history.
+
+- `superbee export <bundle-id> --to <folder>` (or `--dir <checkout> --to <folder>`) writes every
+  document, reserved file and blob into a new or empty folder, which becomes an ordinary local
+  bundle. The archive is verified against the host's digests first, and the folder appears
+  complete or not at all. `export_incomplete` (TRANSIENT) means the host stopped the export:
+  retry the same command.
+- `superbee export --dir <checkout> --in-place` turns the checkout into a local bundle: it adds
+  the files the checkout lacks, never overwrites one (`kept_local` lists files that differ from
+  the host's), and forgets the binding. It refuses `unsent_changes`: run `superbee sync` first. Pass
+  `--keep-unsent` only when the person agrees that those changes stay in this folder and never
+  reach the host. If it stops part way, re-run the same command: it finishes without the network.
+- `--git` makes the result a Git board on branch `board`. To share it, the person adds a remote
+  (`git remote add origin <url>`), then `superbee sync --establish`.