superbee 0.4.1-pre.1 → 0.4.2-pre.1
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.
- package/dist/publication-bridge.mjs +17 -5
- package/dist/publication.mjs +17 -5
- package/dist/superbee.mjs +8061 -6796
- package/package.json +1 -1
- package/references/hosted-checkout.md +21 -2
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "superbee",
|
|
3
|
-
"version": "0.4.
|
|
3
|
+
"version": "0.4.2-pre.1",
|
|
4
4
|
"type": "module",
|
|
5
5
|
"description": "Agent-facing Superbee CLI for reading and writing local OKF knowledge bundles: context notes, docs, cross-links, and live bundle Views.",
|
|
6
6
|
"keywords": [
|
|
@@ -65,12 +65,31 @@ Only run it when the person asks for the move.
|
|
|
65
65
|
link, as below), creates the bundle, and converts the folder in place into a hosted checkout.
|
|
66
66
|
No file is rewritten.
|
|
67
67
|
3. A Git board is unbound from its `board` branch, but the branch stays, locally and on origin.
|
|
68
|
-
|
|
69
|
-
|
|
68
|
+
For a board shared on origin, publish commits and pushes a moved marker on the branch:
|
|
69
|
+
teammates' next `superbee sync` refuses to push and names the checkout command. Teammates on an
|
|
70
|
+
older CLI are not stopped, so suggest protecting the `board` branch until everyone updates. If
|
|
71
|
+
the receipt says the marker push was rejected or failed, show the person its `recovery`
|
|
72
|
+
commands. After the board is moved back (the marker commit reverted on origin), teammates'
|
|
73
|
+
next `superbee sync` works again. A board that is behind its upstream is refused
|
|
74
|
+
until `superbee sync` brings it current.
|
|
70
75
|
4. `--with-history` imports a Git board's earlier versions as labeled, unverified history. Use it
|
|
71
76
|
only when the person asks for history.
|
|
72
77
|
5. `TRANSIENT` with `write_outcome_unknown` means the creation may be partial: re-run the same
|
|
73
78
|
command, which finishes or confirms the same creation.
|
|
79
|
+
6. Only the person can reach the new bundle until it is shared (next section).
|
|
80
|
+
|
|
81
|
+
## Sharing a hosted bundle, and retiring one
|
|
82
|
+
|
|
83
|
+
`superbee access list <bundle>` shows the person's own access and, for a workspace admin, everyone
|
|
84
|
+
with access. When the person asks you to share a bundle with someone, run
|
|
85
|
+
`superbee access grant <bundle> <email> --level read|write` without `--yes` first, show the
|
|
86
|
+
preview, then run the `--yes` command it names. `access revoke <bundle> <email>` works the same
|
|
87
|
+
way. Only a workspace admin may change access. `person_not_member` means the person must invite
|
|
88
|
+
them from the Members page in the Superbee app first. Repeating a grant or revoke is safe.
|
|
89
|
+
|
|
90
|
+
`superbee bundle retire <bundle>` is the person's step, never yours: it needs them to type the
|
|
91
|
+
bundle id in their own terminal. If it refuses with `needs_person_at_terminal`, show the person
|
|
92
|
+
the host's statement and give them the command; do not try to work around it.
|
|
74
93
|
|
|
75
94
|
## Sign-in: relay the link, then retry
|
|
76
95
|
|