superbee 0.1.6-pre.1 → 0.2.1-pre.1

package/README.md

@@ -48,9 +48,8 @@ Ubuntu, or Docker. On Windows, Superbee keeps per-user operational state under
 
 Superbee currently has two npm release channels:
 
-- `latest` is the stable channel selected by bare `superbee`. Its current release predates native
-  Windows support.
-- `next` is the prerelease channel. It contains the current native-Windows build.
+- `latest` is the stable channel selected by bare `superbee`, including native Windows support.
+- `next` is the prerelease channel for testing the current release candidate.
 
 Install the current prerelease on Windows:
 
@@ -90,9 +89,16 @@ instructions into CLI commands. For example:
 
 Behind those requests, the agent drives a small, predictable CLI: `init` creates a bundle in a
 conventional `.superbee/` folder (discovered automatically, the way git finds `.git`); `new`,
-`doc write`, `doc update`, and `link add` create and connect typed documents; `list` and
+`doc write`, `doc update`, `doc field`, and `link add` create and connect typed documents; `list` and
 `doc read` query them; `sync` shares the board with teammates.
 
+Use `superbee doc field <action> <document-id> <field-name>` to change one field.
+`set` assigns a supported non-collection field; `add` and `remove` change tags or sources;
+`edit` changes a selected source; `replace-all` replaces the complete tags or sources list.
+`edit` and `replace-all` require `--expected-version` from a document read. Source selectors
+use an exact `--id` or a unique `--resource` for an ID-less source. Supply structured values
+through a JSON or YAML `--from-file`. Verification remains `doc verify`.
+
 When you want to see the knowledge yourself, ask the agent to open it — or run the two
 human-facing commands directly:
 

package/SKILL.md

@@ -46,6 +46,11 @@ becoming a second source of truth. Add only the layer justified by current evide
 
 - Operate only on the bundle resolved from the current project or one the user explicitly selects.
   A catalog entry is available for selection; it is not ambient project context.
+- Before remote publication, ask whether the intended remote repository exists, then whether
+  `origin/board` exists. If either is unknown, stop remote mutation and diagnose access.
+- Superbee does not create the remote repository. If absence is confirmed, create it externally if authorized, or ask an authorized owner/teammate.
+- On an existing repository without `board`, establishment needs consent, repository-specific Write access,
+  and branch-create policy clearance; creation authority is irrelevant. If `origin/board` exists, join with `superbee sync`; never establish another board.
 - If no bundle resolves, determine whether this repository already shares a board and clarify the
   intended purpose, privacy, participants, and sharing boundary before creating anything.
   `superbee sync` joins an existing shared board; `superbee init --create-only --dir .superbee` is
@@ -54,6 +59,7 @@ becoming a second source of truth. Add only the layer justified by current evide
   explicit publication decision.
 - Never silently rewrite an established Kind, recipe, or its instances. Inspect dependencies and
   explain migration consequences first.
+- Writes carry an actor (`--actor`/`SUPERBEE_ACTOR`); OKF v0.2 bundles accept only `human:<id>`, `process:<id>`, or `<producer>/<version>` (e.g. `openai/codex`); a bare name is refused with the fix.
 
 ## Deliver after acceptance