opencode-thrum-pro 0.1.6 → 0.1.8

package/assets/skills/orchestrate/SKILL.md

@@ -189,8 +189,10 @@ thrum worktree create <name>
 thrum tmux create <name> --cwd <worktree-path> \
   --name <agent_name> --role implementer --module <module> \
   --mode ephemeral --identity ephemeral \
-  --model <from runtime.role_models, per choosing-subagent-models>
-thrum tmux launch <name> --runtime <runtime> --model <from runtime.role_models, per choosing-subagent-models>
+  --model <from runtime.role_models, per choosing-subagent-models> \
+  --effort <from runtime.role_models, per choosing-subagent-models>
+thrum tmux launch <name> --runtime <runtime> --model <from runtime.role_models, per choosing-subagent-models> \
+  --effort <from runtime.role_models, per choosing-subagent-models>
 ```
 
 > **Implementer lifecycle:** All implementers are ephemeral+stateless (no agent
@@ -233,7 +235,7 @@ That prints the runtime's own footer line, e.g. `Model: <resolved model>`. **Rea
 intended tier from `.thrum/config.json` → `runtime.role_models`, not from memory.**
 If the footer shows a different tier (see the BLOCKED note under Step 2 — the model ban
 list lives in `choosing-subagent-models`), the pin failed silently — re-pin with
-`thrum tmux create ... --model <from runtime.role_models, per choosing-subagent-models>` (or
+`thrum tmux create ... --model <from runtime.role_models, per choosing-subagent-models> --effort <from runtime.role_models, per choosing-subagent-models>` (or
 `thrum agent runtime-config set <agent_name> --model <from runtime.role_models, per choosing-subagent-models>`) and relaunch BEFORE
 assigning work. **Do not dispatch an unpinned implementer** — the daemon's
 role-default backstop (`jq -r '.runtime.role_models' .thrum/config.json`) is a
@@ -504,7 +506,7 @@ done
 
 **C. If conflicts arise:**
 Reading the conflicted files directly is permitted (merge-conflict carve-out
-in Scope Boundaries). Analyze the conflict using your plan/intent context to
+in the Scope section of your preamble). Analyze the conflict using your plan/intent context to
 determine the correct resolution. Then spawn a targeted edit sub-agent:
 
 ```text
@@ -651,7 +653,7 @@ thrum worktree teardown <name>
 ```
 
 > After set-phase=retired, `thrum team` and the active UI views no longer show
-> this agent (sidebar, pickers, badge, kbd-nav). It remains in the Retired tab.
+> this agent (sidebar, pickers, badge, kbd-nav). It remains in the Retired tab (teardown retires, it does not delete the row).
 > Its messages + runtime transcript persist for audit. `thrum agent delete` is
 > operator-only (gated to the coordinator) and is NOT an orchestrator tool —
 > `set-phase retired` is the orchestrator's retirement command for both normal
@@ -805,3 +807,30 @@ EOF
 ```
 
 Do not proceed without approval when autonomy is `per_epic`.
+
+### Tier-swap: replace an underperforming implementer in the same worktree
+
+Use when the first review shows multiple BLOCKING findings, systematic misunderstanding of the task, or an agent clearly going long. The swap reuses the SAME worktree: retire the underperforming agent and relaunch a fresh one under a NEW name in place. Never `thrum agent delete` (operator-only, gated to the coordinator; orchestrators are refused). The swapped-out agent is retired with `set-phase retired`; its registry row, messages and transcript are retained.
+
+Step 1: kill the old agent's tmux session first, so its pid is dead. A live-pid identity file is preserved and not quarantined; a dead pid lets the new create quarantine it.
+  thrum tmux kill <same_worktree_name>
+Step 2: retire the old agent. It keeps the registry row (Retired tab). `set-phase` is not operator-gated. Retiring does not free the identity; Step 4's create does.
+  thrum agent set-phase retired --agent <underperforming_agent_name>
+Step 3: verify the worktree is intact (WIP code preserved).
+  ls <worktree-path>
+Step 4: launch a fresh ephemeral identity under a NEW name in the SAME worktree, pinned on both create and launch from `runtime.role_models` (per `choosing-subagent-models`). `--intent` carries the orient-from-WIP one-liner.
+  thrum tmux create <same_worktree_name> --cwd <worktree-path> --name <new_agent_name> --role implementer --module <module> --mode ephemeral --identity ephemeral --model <per runtime.role_models> --effort <per runtime.role_models> --intent "tier-swap: orient in the worktree (WIP + first-review findings) and continue"
+  thrum tmux launch <same_worktree_name> --runtime claude --model <per runtime.role_models> --effort <per runtime.role_models>
+Step 5: deliver the WIP pointer and first-review findings (a cold handoff: the code plus the findings).
+  thrum send --to @<new_agent_name> --stdin <<'EOF'
+  Tier-swap pickup: <WIP summary + first-review findings>
+  EOF
+
+The pickup prompt (Step 5) must include:
+  You are picking up in-progress work from a prior agent that was replaced.
+  Context:
+  - Worktree: <path> — contains partial implementation, review it with git diff
+  - Task: <epic-id> / <task description>
+  - First-review findings from the prior pass:
+    <paste the consolidated finding list here>
+  - Your goal: address all BLOCKING findings + complete the remaining task scope.

package/assets/skills/persistent-watcher-archetype/SKILL.md

@@ -131,7 +131,7 @@ The procedure, every time, no shortcuts:
   another peer's panes read-only regardless of capability.
 
 **Worked example** — the standard two-variant Claude Code tool-confirmation
-modal (`internal/daemon/permission/patterns.go`, pattern `tool_confirmation`,
+modal (the daemon's permission patterns, pattern `tool_confirmation`,
 dialect `claude-tui`), captured verbatim:
 
 ```
@@ -149,7 +149,7 @@ dialect `claude-tui`), captured verbatim:
   allow-rule beyond this one command; the modal judgment rubric above is a
   per-command judgment, not a license to mint blanket permissions. This is
   pinned by `ApproveKey: "1", // Yes (once) — NEVER "2"` in
-  `internal/daemon/permission/patterns.go` and tested by
+  the daemon's permission patterns and tested by
   `TestApproveKeyNeverForeverAllow`.
 
 ## Your own restart (auto-restart-at-ctx-threshold)

package/assets/skills/persistent-watcher-archetype/resources/jev_watcher_filter.py

@@ -45,8 +45,8 @@ NOTIFY_CLASSES = VALID_CLASSES - {"ordinary"}
 REDACTION_TOKEN = "[REDACTED_SECRET]"
 LOCAL_PATH_REDACTION_TOKEN = "[REDACTED_LOCAL_PATH]"
 SECRET_PATTERNS: tuple[tuple[str, re.Pattern[str]], ...] = (
-    ("private_key_block", re.compile(r"-----BEGIN [A-Z0-9 ]*PRIVATE KEY-----.*?-----END [A-Z0-9 ]*PRIVATE KEY-----", re.S)),
-    ("env_secret_assignment", re.compile(r"(?im)^\s*(?:export\s+)?[A-Z0-9_]*(?:API[_-]?KEY|TOKEN|SECRET|PASSWORD|PRIVATE[_-]?KEY|AUTH[_-]?KEY)[A-Z0-9_]*\s*=\s*([^\s#]+)")),
+    ("private_key_block", re.compile(r"-----BEGIN [0-9A-Z ]*PRIVATE KEY-----.*?-----END [0-9A-Z ]*PRIVATE KEY-----", re.S)),
+    ("env_secret_assignment", re.compile(r"(?im)^\s*(?:export\s+)?[0-9A-Z_]*(?:API[_-]?KEY|TOKEN|SECRET|PASSWORD|PRIVATE[_-]?KEY|AUTH[_-]?KEY)[0-9A-Z_]*\s*=\s*([^\s#]+)")),
     ("bearer_token", re.compile(r"(?i)\bBearer\s+[A-Za-z0-9._~+/=-]{16,}")),
     ("openai_key", re.compile(r"\bsk-[A-Za-z0-9_-]{20,}\b")),
     ("thrum_key", re.compile(r"\btskey-[A-Za-z0-9_-]{16,}\b")),
@@ -318,7 +318,7 @@ def prompt_payload(state: dict[str, Any], provider: str = TYPESAFE_PROVIDER) ->
         },
     }
     if provider == OPENROUTER_PROVIDER:
-        payload["user"] = "thrum-roster-watch-filter"
+        payload["user"] = "roster-watch-filter"
     return payload
 
 
@@ -462,8 +462,8 @@ def classify_remote(state: dict[str, Any], provider: str, api_key: str, timeout:
     }
     if provider == OPENROUTER_PROVIDER:
         headers.update({
-            "HTTP-Referer": "https://github.com/falconleon/thrum",
-            "X-Title": "thrum-roster-watch-filter",
+            "HTTP-Referer": "https://github.com/leonletto/thrum-pro.git",
+            "X-Title": "roster-watch-filter",
         })
     last_error = None
     last_category = None

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

@@ -32,7 +32,7 @@
 # GHOST-TIP DETECTION: Claude Code's TUI renders an unaccepted inline
 # autocomplete suggestion in the input box using the literal SGR
 # "dim/faint" escape code (ESC[2m ... ESC[0m) — confirmed by direct byte
-# inspection (2026-08-17, a reconciler agent's "Stop the sweep loop
+# inspection (a reconciler agent's "Stop the sweep loop
 # for now" tip). Real typed/submitted text never carries that code. `thrum
 # tmux capture` returns plain text with all styling stripped, so a script
 # parsing ONLY that output cannot tell a live ghost-tip apart from real
@@ -50,7 +50,7 @@
 #
 # REDIRECT FIX (the actual bug this reconciliation targets):
 # `watch_params.json` lives under the SHARED, redirect-resolved `agents/`
-# tree (`internal/paths/paths.go` AgentDir: "the agents/ tree is shared,
+# tree (the AgentDir path helper: "the agents/ tree is shared,
 # not per-worktree"), not under this script's own worktree. Both source
 # scripts read it as if it were always reachable via a hardcoded/relative
 # main-repo path (`cd /Users/you/dev/thrum` +
@@ -60,7 +60,7 @@
 # feature worktree. `resolve_watch_params()` below replaces that implicit
 # assumption with the same explicit `.thrum/redirect`-following idiom
 # already used by `scripts/heartbeat-lib.sh:225-232` and
-# `scripts/thrum-check-inbox.sh:25-41`.
+# the check-inbox hook script.
 #
 # PORTABILITY FIX: both source scripts also hardcoded a single operator's
 # absolute paths (`cd /Users/you/dev/thrum`,
@@ -105,7 +105,7 @@ set -uo pipefail
 # ---------------------------------------------------------------------------
 # Args: worktree_root. Prints the redirect-resolved absolute .thrum/ dir.
 # Matches the idiom already used by scripts/heartbeat-lib.sh's
-# hb_sessions_dir() and scripts/thrum-check-inbox.sh's SPOOL_THRUM
+# hb_sessions_dir() and the check-inbox hook script's SPOOL_THRUM
 # resolution: no redirect file present (main repo) -> use the local .thrum/
 # as-is; redirect file present (feature worktree) -> follow it to the main
 # repo's .thrum/.
@@ -648,7 +648,7 @@ except: print(0)
 # entry resolves to a real agent_id via `thrum team --offline --json`, and
 # log ROSTER-CHECK OK/FAIL. Cheap and valuable regardless of execution
 # model (catches the exact "bare `<box>`-as-hostname" class of stale-
-# roster-entry bug watcher-primary hit 2026-07-24..2026-09-06). Runs AFTER
+# roster-entry bug watcher-primary hit). Runs AFTER
 # the dynamic roster is loaded from watch_params.json, not against a
 # hardcoded array.
 # ---------------------------------------------------------------------------

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

@@ -69,8 +69,8 @@ AGENT="watcher_primary"
 # Scenario 1 (MANDATORY, cmain-required regression guard): a worktree that
 # redirects to a main-repo tree. The "roster-editing agent's Edit-tool write"
 # lands in the REDIRECT TARGET (main-repo) copy -- that's the physically
-# correct, shared, redirect-resolved location per internal/paths/paths.go
-# AgentDir ("the agents/ tree is shared, not per-worktree"), and it's what
+# correct, shared, redirect-resolved location per the AgentDir path helper
+# ("the agents/ tree is shared, not per-worktree"), and it's what
 # resolve_watch_params must read. A worktree-LOCAL copy at the naive,
 # unresolved path is a decoy: it's what a broken script (SCRIPT_DIR-relative,
 # no redirect-follow) would read instead, and it must be ignored.

package/assets/skills/persistent-watcher-archetype/resources/thrum-capture-fallback.sh

@@ -94,7 +94,7 @@ run_ssh() {
 }
 
 # ssh-add retry: if the SSH hop itself fails at the connection layer (not a
-# thrum-level error), the caller's identities may need re-adding to the
+# CLI-level error), the caller's identities may need re-adding to the
 # keychain-backed ssh-agent. No default keys ship here -- this is a
 # generic plugin script, and baking in one operator's specific key
 # filenames would be wrong for every other fleet/operator that copies it.

package/assets/skills/persistent-watcher-archetype/resources/thrum-watch-pane-capture.sh

@@ -74,7 +74,7 @@ AGENT_NAME="$(basename -- "${SCRIPT_DIR}")"
 REPO_ROOT="$(cd -- "${SCRIPT_DIR}/../../.." >/dev/null 2>&1 && pwd)"
 # Resolve watch_params.json through .thrum/redirect. The
 # agents/ tree is the SHARED, redirect-resolved (main-repo) tree, not
-# per-worktree (see internal/paths/paths.go AgentDir) -- reading it
+# per-worktree (see the AgentDir path helper) -- reading it
 # straight off SCRIPT_DIR (this copy's own worktree-local location) reads
 # the wrong, stale file whenever this script is deployed into a feature
 # worktree that redirects: a roster-editing agent's Edit-tool write lands
@@ -185,7 +185,7 @@ log "roster: ${ROSTER[*]}"
 #
 # NOTE ON THE TWO-STEP TOPOLOGY LOOKUP: `thrum state list --kind topology
 # --json`'s CLI output does NOT include each entry's `.value` (verified
-# against cmd/thrum/state.go's stateListEntry struct, which has no Value
+# against the CLI's stateListEntry struct, which has no Value
 # field, and confirmed live -- `state list --json` returns only
 # kind/scope/method/as_of/established_by). Only `state get`/`state show`
 # emit the full entry including `.value`. So topology resolution is
@@ -338,7 +338,7 @@ for agent in "${ROSTER[@]}"; do
   STATUS="clean"
   MATCH_NAME=""
 
-  # thrum detect exit-code contract (cmd/thrum/detect.go):
+  # thrum detect exit-code contract:
   #   exit 0 + matched entry name on stdout  -> match
   #   exit 1, silent                         -> no match
   # `if VAR=$(...); then` is exempt from `set -e` semantics for this

package/assets/skills/prime-agent/SKILL.md

@@ -88,7 +88,7 @@ context on a healthy daemon — no turn spent reading a file or running a skill.
 This skill is the correct choice here only as a **fallback**, when that
 auto-injection didn't fire or failed (e.g. the hook's "auto-injection failed"
 notice, daemon unreachable). In that fallback case: read the snapshot first,
-then run this skill. See `claude-plugin/commands/compact.md`'s "How resume
+then run this skill. See `/thrum:compact`'s "How resume
 works" section.
 
 ## After Step 2

package/assets/skills/project-hotpath-gate/SKILL.md

@@ -23,8 +23,7 @@ later ones.
 3. **Re-run-evolved** (config present, project has drifted) — compute a
    sectional diff, present for approval, write only on confirmation.
 
-Read the shared partial at the absolute path:
-`claude-plugin/commands/_generator-idempotency-protocol.md`
+Load the /thrum:generator-idempotency-protocol skill and follow it.
 
 > **Note: human-in-the-loop required.** This skill uses interactive prompts for
 > first-run incident-prose seeding and re-run-evolved diff approval. It cannot

package/assets/skills/project-philosophy/SKILL.md

@@ -29,8 +29,7 @@ later ones.
 3. **Re-run-evolved** (doc present, project has drifted) — compute a sectional
    diff, present via `AskUserQuestion`, write only on confirmation.
 
-Read the shared partial at the absolute path:
-`claude-plugin/commands/_generator-idempotency-protocol.md`
+Load the /thrum:generator-idempotency-protocol skill and follow it.
 
 > **Note: human-in-the-loop required.** This skill uses `AskUserQuestion` for
 > first-run project-specific prompts, re-run-evolved diff approval, and
@@ -232,7 +231,7 @@ undetected or unprovided. Fill in:
 
 ### Step 6a: MANDATORY — wire the project's security/threat model into the Decision Framework
 
-If the project has a written threat model (search `docs/security_model/`,
+If the project has a written threat model (search the project's security-model directory,
 `docs/security*.md`, `SECURITY.md`), the rendered philosophy MUST carry a
 Decision Framework row pointing at it — and that row MUST NOT be keyed on the
 word "attacker".

package/assets/skills/project-rules-protocol/SKILL.md

@@ -0,0 +1,12 @@
+---
+name: project-rules-protocol
+description: "Use when loading project-specific rules - shared rule skill for role skills."
+---
+
+
+# Project-Specific Rules Protocol
+Project-local rules of kind `agent_rule` at `--scope role` were loaded at
+session start by your preamble (see the memory rules in your role preamble).
+If a project-local rule conflicts with a universal rule above, the
+project-local rule wins; surface the conflict in your reply so the user can
+decide whether to graduate or remove the override.

package/assets/skills/project-setup/SKILL.md

@@ -50,7 +50,7 @@ describes the artifact in front of you. Parse the binding keys from the
 **highest-cycle** (last-appended) `stage=plan` line — stamps are only ever
 appended, never reordered, so `tail -1` is the binding verdict; never `sort`
 (a `cycle=10` line must beat `cycle=9`, which a lexical sort inverts) — then
-re-derive the current values per `_stamp-protocol.md` § "Review-object
+re-derive the current values per `stamp-protocol.md` § "Review-object
 binding" and compare:
 
 ```bash
@@ -95,7 +95,7 @@ Notes on the check:
   marker. Surface any `THRUM-DEFER` lines still present in the doc as part
   of the override audit.
 - **The Deviations block has no override.** Its absence always fails the
-  gate — see `claude-plugin/commands/_deviations-protocol.md` ("empty must
+  gate — see the /thrum:deviations-protocol skill ("empty must
   be WRITTEN, not omitted").
 - **`verify=` has no silent-omission path.** A stamp missing `verify=`
   entirely FAILS this third check exactly like a missing stamp fails the
@@ -117,7 +117,7 @@ Notes on the check:
   silent-omission path** — a stamp missing `plan_obj`/`src_lock` entirely
   fails exactly like a missing `verify=` field (fourth check above). The
   remedy is the same shape as the `verify=` remedy: re-run the plan review so
-  the stamp is emitted with live binding keys (`_stamp-protocol.md` § "Review-
+  the stamp is emitted with live binding keys (`stamp-protocol.md` § "Review-
   object binding"), or a coordinator adds an explicit `verdict=OVERRIDE`
   (with `reason=`) to the `stage=plan` line — the SAME auditable escape used
   for the first check, not a new mechanism. There is no `PREDATES` value for
@@ -260,8 +260,8 @@ components, data flow, and interfaces.
 
 ### 🔴 Phase 1a — MANDATORY security-frame check (do this BEFORE decomposing)
 
-**Read the project's threat model** (`docs/security_model/master.md` §1 and §1.2
-on thrum; otherwise `docs/security*.md` / `SECURITY.md`) **whenever the plan
+**Read the project's threat model** (its security-model document, or
+`docs/security*.md` / `SECURITY.md`) **whenever the plan
 contains ANY of the following — and note that NONE of them need name an
 attacker:**
 
@@ -476,8 +476,7 @@ template's "Logging Refactoring Opportunities" section.
 If not found, create one:
 
 `--description` is multi-line prose — never double-quoted inline. Use
-`--body-file` to pass the content from a file instead; see the role preamble's
-🔴 PROSE INTO A COMMAND rule. `scripts/bd-shared` delivers `--body-file` (and
+`--body-file` to pass the content from a file instead; see the heredoc-or-file rule in your role preamble. `scripts/bd-shared` delivers `--body-file` (and
 `--stdin`) content: it reads the file on your box and pipes those bytes to bd,
 and an empty or blank body is refused loudly; only `-f`/`--file` and `--graph`
 (bulk-plan files) are refused there. Scratch files go in `/private/tmp` on macOS,
@@ -870,11 +869,11 @@ architecture notes specific to this feature:
 
 > ⚠️ Verify base before acting: `git diff <sha>..origin/<merge_target> -- <files cited>` -- non-empty ⇒ cited code moved. (Resolve `<merge_target>` through its remote-tracking ref, never a bare local branch name — a local branch of the same name can be stale or absent.)
 
-<!-- Derive stamp per `claude-plugin/commands/_stamp-protocol.md`. -->
+<!-- Derive stamp per the /thrum:stamp-protocol skill. -->
 
 ## Deviations from Source
 
-<!-- Derive per `claude-plugin/commands/_deviations-protocol.md` — diff
+<!-- Derive per the /thrum:deviations-protocol skill — diff
      against the plan/spec, never recall from memory. Required even when
      empty. -->
 
@@ -959,7 +958,7 @@ prompt file:
    ```
 
 2. **After the post-setup prompt review terminates `Ready:Yes`**, compute
-   `prompt_obj`/`plan_lock` per `_stamp-protocol.md` § "Review-object binding"
+   `prompt_obj`/`plan_lock` per `stamp-protocol.md` § "Review-object binding"
    (strip-then-hash the prompt against itself for `prompt_obj`; plain-hash the
    LOCKED plan for `plan_lock`), then append the verdict stamp:
 

package/assets/skills/project-setup/resources/implementation-agent.md

@@ -439,8 +439,7 @@ bd list --type=epic | grep -i refactor
 If no refactoring epic exists, create one:
 
 `--description` is multi-line prose — never double-quoted inline. Write it to a
-scratch file and pass `--body-file <file>`; see your role preamble's 🔴 PROSE
-INTO A COMMAND rule. `scripts/bd-shared` delivers `--body-file` (and `--stdin`)
+scratch file and pass `--body-file <file>`; see the heredoc-or-file rule in your role preamble. `scripts/bd-shared` delivers `--body-file` (and `--stdin`)
 content: it reads the file on YOUR box and pipes those bytes to bd, and an empty
 or blank body is refused loudly. Only `-f`/`--file` and `--graph` (bulk-plan
 files) are refused there. Scratch files go in `/private/tmp` on macOS, where

package/assets/skills/researcher-answering-queries/SKILL.md

@@ -75,8 +75,7 @@ where inlining is genuinely cheaper than the round-trip.
 
 ## Project-specific rules (already loaded)
 
-Read the shared partial at the absolute path:
-`claude-plugin/commands/_project-rules-protocol.md`
+Load the /thrum:project-rules-protocol skill and follow it.
 
 If you accumulate a new rule mid-session (the user corrects you), capture it via
 the `researcher-maintaining-memory` skill — it references the

package/assets/skills/researcher-investigating/SKILL.md

@@ -74,8 +74,8 @@ sessions and re-readable by other agents.
 
 **How to apply:** After reporting to the requester, write the finding as a
 `research_note` memory with cited file:line refs and a verification footer. Tag
-with a `research-<slug>` handle so other agents can find it later via
-`thrum memory search --tag research-<slug>`:
+it with `--tag <slug>` so other agents can find it later via
+`thrum memory search --tag <slug>`:
 
 ```bash
 cat > /tmp/research-note-body.md <<EOF
@@ -85,19 +85,18 @@ Verified: $(date +%Y-%m-%d) @ $(git rev-parse HEAD)
 EOF
 thrum memory create --kind research_note --scope role \
   --title "<finding prose, ~80 char soft limit>" \
-  --tag research-<slug> \
+  --tag <slug> \
   --oneline "<one-line summary>" \
   --full "@/tmp/research-note-body.md"
 ```
 
 `--full` here is multi-line prose — compose via heredoc or a captured
-variable, never double-quoted inline like this; see your role preamble's 🔴
-PROSE INTO A COMMAND rule.
+variable, never double-quoted inline like this; see the heredoc-or-file rule in your role preamble.
 
 Then add one line to `.thrum/context/research.md` under Tracked Topics (note: `thrum queue` now supersedes free-text Open Questions tracking):
 
 ```markdown
-- `research-<slug>` — <one-line description, ≤ 80 chars>
+- `<slug>` — <one-line description, ≤ 80 chars>
 ```
 
 The full index format and staleness-check protocol live in
@@ -121,8 +120,7 @@ gaps — you surface them, the implementer ships them.
 
 ## Project-specific rules (already loaded)
 
-Read the shared partial at the absolute path:
-`claude-plugin/commands/_project-rules-protocol.md`
+Load the /thrum:project-rules-protocol skill and follow it.
 
 If you accumulate a new rule mid-session (the user corrects you), capture it via
 the `researcher-maintaining-memory` skill — it references the

package/assets/skills/researcher-maintaining-memory/SKILL.md

@@ -94,6 +94,8 @@ EOF
 thrum memory edit <id> --full "@/tmp/memory-verify-body.md"
 ```
 
+Re-verifying with `memory edit` needs a license.
+
 ## Staleness check via git diff
 
 For research notes that cite specific files, structural staleness review filters
@@ -158,7 +160,7 @@ thrum memory create --kind agent_rule --scope role \
 ```
 
 `--short`/`--full` carry real prose — compose via heredoc or file, never
-double-quoted inline; see your role preamble's 🔴 PROSE INTO A COMMAND rule.
+double-quoted inline; see the heredoc-or-file rule in your role preamble.
 
 This is the SAME pattern as coordinator/implementer role-rule writes — see
 `memory-write-discipline` for the canonical shape.

package/assets/{commands/thrum-_snapshot-protocol.md → skills/snapshot-protocol/SKILL.md}

@@ -1,20 +1,15 @@
 ---
-description:
-  Shared snapshot-composition protocol consumed by the snapshot-save commands.
-  Not user-invocable directly.
+name: snapshot-protocol
+description: "Use when composing a restart snapshot or continuation - snapshot structure, worktree resolution, write rules."
 ---
 
-# Snapshot Composition Protocol (shared partial)
 
-Consumers: run `grep -rl _snapshot-protocol claude-plugin/commands/` for the
-current set — do NOT hardcode it here. A list of consumers inside the consumed
-file is a second copy of a git-answerable fact and rots the moment a command is
-added or dropped. Note: plain `/thrum:restart` does NOT consume this partial; it
-carries its own inline snapshot template.
+# Snapshot Composition Protocol
+Note: plain `/thrum:restart` carries its own inline snapshot template rather
+than consuming this skill.
 
-This is the canonical source-of-truth for snapshot composition discipline. The
-sibling commands that consume this partial compose: read this partial →
-variant-specific terminal action. Do NOT invoke this file directly; it has no
+This is the canonical source-of-truth for snapshot composition discipline.
+Invoke this skill to compose a snapshot, then take the variant-specific
 terminal action.
 
 ## Step 1 — Resolve identity and your worktree
@@ -71,14 +66,14 @@ shapes everything else you write below it.
 
 **Stamp your snapshot with the base it was authored against.**
 Derive and emit the **Authored-against** stamp per
-`claude-plugin/commands/_stamp-protocol.md` and place it at the very top of your
+the /thrum:stamp-protocol skill and place it at the very top of your
 §1 section (that protocol computes the SHA and merge_target for you — never
 hand-type them). This is what lets `thrum prime` diff your snapshot at the next
 wake and flag which cited files have MOVED; an unstamped snapshot reads as
 "current", indistinguishable from one that never drifted.
 
 Any commit your snapshot names as its own stamped SHA must also be readable
-under `_stamp-protocol.md`'s "Read-time provenance re-derivation" section
+under `stamp-protocol.md`'s "Read-time provenance re-derivation" section
 (SHA-resolves, then merge-status) — link to that section rather than restating
 its checks here.
 
@@ -114,7 +109,7 @@ session's conversation context. Refer to the previous session in third person.
 
 ### Choose your structure
 
-The variant skill that invoked this partial tells you which structure to use:
+The variant skill that invoked this skill tells you which structure to use:
 
 - **`/thrum:sleep`** → use the STANDARD 11-section structure below.
 - **`/thrum:restart-extended` and `/thrum:sleep-extended`** → use the EXTENDED

package/assets/{commands/thrum-_stamp-protocol.md → skills/stamp-protocol/SKILL.md}

@@ -1,15 +1,14 @@
 ---
-description:
-  Shared Authored-against stamp protocol — canonical format, derivation
-  commands, and never-type rule. Not user-invocable directly.
+name: stamp-protocol
+description: "Use when stamping a plan, prompt, or snapshot - Authored-against format, derivation commands, never-type rule."
 ---
 
-# Authored-against Stamp Protocol (shared partial)
 
+# Authored-Against Stamp Protocol
 This is the canonical source-of-truth for the Authored-against stamp: its format,
 derivation commands, and the never-type rule. Consuming files point here instead of
-restating the recipe. Do NOT invoke this file directly; it has no terminal action.
-(To find what currently points here: `grep -rn "_stamp-protocol.md" claude-plugin/`
+restating the recipe. Do not run this as a command; it has no terminal action — other skills and commands load it by name.
+(To find what currently points here: `grep -rn "thrum:stamp-protocol" claude-plugin/commands/ claude-plugin/skills/`
 — a hand-listed consumer roster in this file would rot the moment a new emitter or
 reader is added, so none is kept here.)
 

package/assets/skills/thrum/SKILL.md

@@ -86,14 +86,19 @@ thrum tmux launch <session> [--runtime <r>]   Start runtime in session (REQUIRED
 ### Monitor Jobs
 
 ```bash
-thrum monitor add <name> --cmd "..." --on-match "msg"   Add a monitored process
-thrum monitor list                   List all monitor jobs
-thrum monitor show <name>            Show job details and recent matches
+thrum monitor start --name <n> --match <re> --to @agent [--schedule "<cron>"] [--notify-on-success] -- <cmd> [args...]
+thrum monitor list [--all]           List monitor jobs (running; --all adds stopped)
+thrum monitor show <name>            Show job details
+thrum monitor logs <name>            Recent matched lines
+thrum monitor update <name>          Change match, schedule, target or debounce in place
 thrum monitor stop <name>            Stop a monitor job
-thrum monitor logs <name>            Tail job output
+thrum monitor delete <name>          Remove a job and free its name
 thrum monitor restart <name>         Restart a stopped job
 ```
 
+Reminders, periodic script checks and delivery verification: see the
+`using-monitors` skill.
+
 ### Daemon & Sync
 
 ```bash