opencode-thrum-pro 0.1.14 → 0.1.15

package/assets/skills/coordinator-interacting-with-the-owner/SKILL.md

@@ -131,7 +131,7 @@ a rule gets obeyed.** Same situation, both ways.
 ❌ *"<orchestrator> just finished reviewing <implementer>'s branch. The review found two
 minor issues: an unused import in redact.go and a missing test case for the
 empty-string path. Both were fixed and the branch is now clean. I'm going to
-merge it into thrum-agents now and then check on the next epic..."*
+merge it into the shared integration branch now and then check on the next epic..."*
 ✅ Nothing to the pane. If the agent needs an ack, `thrum reply <msg_id>
 --stdin <<'EOF'` with `merged, see <merge-target>` as the body — the pane stays
 silent.

package/assets/skills/coordinator-merging-code/SKILL.md

@@ -379,7 +379,7 @@ agreeing (`rev-parse origin/<branch>` and `ls-remote`). **Assert the branch TIP*
    agent's memory across restarts. **Never `git add -f`.**
 4. **Delete the merged branch AND drop its queue bundle — one ritual, at merge
    time**, after the push is verified. `feature/*` and `fix/*` are one-shot —
-   delete freely. **`agent/*`, `salvage/*`, `website-dev` and `release/*` are
+   delete freely. **`agent/*`, `salvage/*`, the documentation deployment branch and `release/*` are
    ongoing or archival — do NOT delete.** Then, in the same turn: `thrum queue
    done <bundle>` + `thrum queue drop <bundle>` for the bundle that tracked this
    branch, and `bd close <id>` any beads this merge closed. A merge is not
@@ -430,7 +430,7 @@ hides staleness.
 - `go test … | tail`, or `$?` read after any pipe.
 - Pushing without guarding on the merge's exit status.
 - Declaring a class closed on a count you did not re-derive.
-- Deleting `agent/*`, `salvage/*`, `website-dev` or `release/*`.
+- Deleting `agent/*`, `salvage/*`, the documentation deployment branch or `release/*`.
 - Pushing a merge without dropping the queue bundle that tracked it.
 
 ## See also

package/assets/skills/implementer-receiving-dispatch/SKILL.md

@@ -105,9 +105,9 @@ the `implementer-maintaining-memory` skill — it references the
 
 Immediately after sending the dispatch ACK, write `agent_status="working"` to
 your local identity file. This is the Pattern D self-write that makes
-`agent_status` carry signal across the fleet — the sweep script +
-coordinator-context-monitoring skill use it to flag agents that go tmux-quiet
-despite claiming `working` (STUCK-WORKING classification).
+`agent_status` carry signal across the fleet; the coordinator context monitoring
+sweep uses it to flag agents that go tmux-quiet despite claiming `working`
+(STUCK-WORKING classification).
 
 ```bash
 # Step 1: ACK the dispatch within 2 minutes

package/assets/skills/implementer-status-and-handoff/SKILL.md

@@ -67,8 +67,8 @@ Report the result as one line:
 Branch pushed: <branch-name> @ <sha> (git ls-remote origin refs/heads/<branch-name> confirms)
 ```
 
-**Never push `thrum-agents`, `main`, or `website-dev`** — the coordinator merges
-those.
+**Never push protected integration or release branches** — the coordinator
+merges those.
 
 Never report DONE with the push status silently omitted — an orchestrator
 that removes a worktree assuming "DONE implies pushed" on a project that
@@ -121,8 +121,8 @@ When reporting DONE to the coordinator, write `agent_status="idle"` to your
 local identity file. This closes the `working→idle` transition opened by the ACK
 template's `set-status working` (sibling skill
 `implementer-receiving-dispatch`). The sweep script reads this field to
-distinguish "agent finished cleanly" from "agent stuck claiming to work" — see
-`coordinator-context-monitoring` SKILL.md for the tier-ladder consumption.
+distinguish "agent finished cleanly" from "agent stuck claiming to work";
+the coordinator context monitoring sweep uses it as one signal in its tier ladder.
 
 ```bash
 # Step 1: Report DONE to coordinator

package/assets/skills/persistent-watcher-archetype/resources/roster-watch.sh

@@ -6,8 +6,8 @@
 # never-merged personal-branch scripts (`origin/agent/watcher-primary` and
 # `origin/agent/brainstorm-steward`, reconciled against a full byte-level
 # diff account of both) into one canonical, git-tracked script.
-# Neither branch is an ancestor of thrum-agents; this is the first time
-# either design lands in the shared tree.
+# Neither branch is an ancestor of the shared integration branch; this is
+# the first time either design lands in the shared tree.
 #
 # EXECUTION MODEL: single-pass / cron-driven by default (ported from
 # brainstorm-steward, the LATER of the two designs, Sep 10 vs Sep 6). Its

package/assets/skills/verify-against-plan/SKILL.md

@@ -99,7 +99,7 @@ clear error — do not proceed with partial inputs.
 4. **Authored-against drift check (informational; does not block on missing stamp).**
    Look for a stamp of this form near the top of the plan:
 
-   Literal example: `**Authored-against:** \`a1b2c3d4e5\` target: \`thrum-agents\``
+   Literal example: `**Authored-against:** \`a1b2c3d4e5\` target: \`<merge-target>\``
 
    Regex: `^\*\*Authored-against:\*\* \`([0-9a-f]+)\` target: \`([^\`]+)\``
    (sha → capture group 1, merge_target → capture group 2)

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "opencode-thrum-pro",
-  "version": "0.1.14",
+  "version": "0.1.15",
   "description": "Thrum multi-agent coordination plugin for Open Code",
   "type": "module",
   "main": "./dist/index.js",