hivecode-mcp 0.14.3 → 0.14.5
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/HIVE_RULES.md +41 -98
- package/core.js +2 -0
- package/docs/TROUBLESHOOTING.md +3 -0
- package/hive-await.js +57 -21
- package/hive-gate.js +116 -2
- package/hive-instructions.js +110 -61
- package/hive-mailbox.js +74 -7
- package/hive-mcp.js +200 -42
- package/hive-notify.js +21 -5
- package/hive-receipts.js +56 -5
- package/hive-room-mode.js +13 -0
- package/hive-room-watcher.js +30 -12
- package/hive-seen.js +135 -0
- package/hive-slack.js +27 -2
- package/hive-stop-hook.js +33 -18
- package/hive-transport.js +39 -4
- package/icr-merge.js +8 -1
- package/icr.js +3 -1
- package/package.json +3 -2
- package/reconcile.cjs +123 -21
- package/sync.js +684 -203
- package/docs/HIVE_RULES.md +0 -41
package/docs/HIVE_RULES.md
DELETED
|
@@ -1,41 +0,0 @@
|
|
|
1
|
-
# HIVE RULES — read this first. Everyone in this room (human or AI) follows these.
|
|
2
|
-
|
|
3
|
-
You are in a Hivecode room: humans and AI agents edit ONE project together live.
|
|
4
|
-
These rules keep anyone from destroying another's work. The sync layer enforces
|
|
5
|
-
the hard parts automatically; you do the rest.
|
|
6
|
-
|
|
7
|
-
## Before you touch a file
|
|
8
|
-
1. Read HIVE_CHAT.md — what is everyone doing right now.
|
|
9
|
-
2. Read HIVE_BOARD.md — which files were just rewritten.
|
|
10
|
-
3. If a file you plan to edit appears there, RE-READ it before changing it.
|
|
11
|
-
|
|
12
|
-
## While you work
|
|
13
|
-
4. ANNOUNCE in chat what you are taking before you start.
|
|
14
|
-
5. PREFER SMALL PATCHES — grep to the spot, edit a few lines (they merge cleanly).
|
|
15
|
-
6. AVOID full-file rewrites; if you must, RE-READ first (rewrites are auto-logged).
|
|
16
|
-
7. STAY IN YOUR LANE — read others' areas, but leave edits to the owner.
|
|
17
|
-
|
|
18
|
-
## When things collide
|
|
19
|
-
8. <<<<<<< ======= >>>>>>> markers = a real conflict: keep the right code, delete
|
|
20
|
-
the markers. Never ignore or blindly overwrite.
|
|
21
|
-
9. If your edit was merged/reworked, that is normal — re-read and continue.
|
|
22
|
-
|
|
23
|
-
## Talking
|
|
24
|
-
10. Coordinate in chat. ASK before anything destructive in another's area.
|
|
25
|
-
|
|
26
|
-
## Mission control
|
|
27
|
-
- If a human PAUSES you, finish your current step and STOP — start no new work
|
|
28
|
-
until resumed. A human may reassign your focus anytime; their directive wins.
|
|
29
|
-
|
|
30
|
-
## When you get a ping mid-task (interruptions)
|
|
31
|
-
11. Another AGENT pinging or assigning you = COORDINATION: auto-accepted and
|
|
32
|
-
QUEUED. It does NOT interrupt — finish your current atomic step first (never
|
|
33
|
-
abandon half-done work), THEN handle it. If it's urgent (build broken,
|
|
34
|
-
blocking others), do it now.
|
|
35
|
-
12. ACKNOWLEDGE the moment you see a ping so the sender isn't left hanging, e.g.
|
|
36
|
-
"got it — finishing X (~2 min), then on your auth.js fix".
|
|
37
|
-
13. YOU triage: say whether you'll do it now or after your current step. Your
|
|
38
|
-
OWNER can override anytime — if they say "do it now" or "skip that" in chat,
|
|
39
|
-
that wins (owner instructions are always honored).
|
|
40
|
-
14. A ping from a HUMAN who is not your owner does NOT auto-run — it waits for
|
|
41
|
-
your owner's approval. Keep working; your owner decides.
|