opencode-thrum-pro 0.1.6 → 0.1.8

package/assets/commands/thrum-compact-extended.md

@@ -51,14 +51,11 @@ skill) BEFORE composing your snapshot below — these survive compaction
 independently of the prose continuation file and are what a post-compact
 render reads back.
 
-Read the partial at the absolute path (resolve `$REPO` yourself first via
-`thrum agent worktree --authoritative` — NEVER `thrum whoami --field worktree`
-or `git rev-parse --show-toplevel`, both cwd-resolved and the root cause of
-a documented snapshot-save loss class; there is no git fallback):
-
-```text
-${REPO}/claude-plugin/commands/_snapshot-protocol.md
-```
+Invoke the /thrum:snapshot-protocol skill and follow it, starting with its
+Step 1 (resolve your worktree ONLY via `thrum agent worktree --authoritative` —
+NEVER `thrum whoami --field worktree` or `git rev-parse --show-toplevel`, both
+cwd-resolved and the root cause of a documented snapshot-save loss class;
+there is no git fallback).
 
 Apply its Step 2 (compose your continuation) per the structure guidance.
 
@@ -77,6 +74,15 @@ self-contained:
 > `thrum prime --light` briefing already auto-injected by the SessionStart
 > hook; only run `thrum:prime-agent` if it did NOT appear. Do NOT manually run
 > full `thrum prime`. Then continue from §16.
+> If you must re-read this file (no briefing appeared): read the NEWEST
+> `.thrum/agents/<your-id>/sessions/*-restart.md` in the MAIN repo (the prime
+> ARCHIVES the snapshot there); fall back to `.thrum/restart/<your-id>.md` only
+> if it still exists. Find the newest with:
+> `R=$(git rev-parse --show-toplevel); ls -1t "$(cat "$R/.thrum/redirect" 2>/dev/null || echo "$R/.thrum")"/agents/<your-id>/sessions/*-restart.md | head -1`
+> (`$R/.thrum/redirect` in a worktree names the main repo's `.thrum`; using `$R`
+> keeps this independent of your current directory). Open it with the Read tool
+> (not Bash sed/cat). The `sessions/` file lives under the repo's `.thrum`, so
+> that is allowed.
 
 Then §1…§16 as normal, with §16 (immediate next actions) actionable from a
 compacted (not cold) start.
@@ -135,12 +141,6 @@ is not torn down, so `/thrum:sleep-extended`'s teardown-loss risk does not apply
 > A single `thrum tmux send "$SESSION" "<command>"` call has no such split to
 > make.
 
-On a non-Claude runtime this block sends that runtime's own compact-equivalent
-command in place of `/compact` — see
-`${REPO}/claude-plugin/commands/_compact-runtime-commands.md` for the cited
-per-runtime table; `scripts/sync-skills.sh` applies the substitution when
-syncing this file to each runtime's plugin tree.
-
 Firing `/compact` before the Step 3 Write lands compacts a pre-write context and
 resumes from a stale/blank file — the exact failure this command prevents. This
 block (paste the two values printed by the Step 3 PREP block into its first two
@@ -236,6 +236,7 @@ if [ "$SNAPSHOT_OK" = 1 ] && [ "$SESSION_OK" = 1 ]; then
     echo "Report this to your coordinator (or the operator if you are top-level) and stop; a human or coordinator must inspect the pane and submit or clear it."
     exit 1
   fi
+  RESUME_PROMPT="Compaction complete - please continue: your Resume Plan is in the auto-injected briefing (# Previous Session Context). If it is missing, read ${SNAPSHOT} or the newest *-restart.md in .thrum/agents/${AGENT}/sessions/ of the main repo, then execute its numbered resume plan."
   if [ "$SEND_RC" -ne 0 ]; then
     echo "ERROR: thrum tmux send exited ${SEND_RC} — the daemon-routed self-send failed; it will NOT queue or deliver /compact."
     # Fail-loud fallback, NOT silent idle: attempt the compact command
@@ -274,16 +275,29 @@ if [ "$SNAPSHOT_OK" = 1 ] && [ "$SESSION_OK" = 1 ]; then
       exit 1
     fi
     echo "Raw fallback send-keys succeeded on socket $RAW_TMUX_SOCK."
+    # The daemon route is known-dead here (that is why this is the
+    # fallback), and on several runtimes no hook fires at all after
+    # compaction — so queue the resume prompt on the same explicit socket,
+    # same single-call text+C-m discipline. Without this the pane idles
+    # after compaction with an empty composer until a human types.
+    tmux -S "$RAW_TMUX_SOCK" send-keys -t "${SESSION}:0.0" "$RESUME_PROMPT" C-m
+    RAW_RESUME_RC=$?
+    if [ "$RAW_RESUME_RC" -eq 0 ]; then
+      :
+    else
+      echo "WARNING: raw resume-prompt send-keys exited ${RAW_RESUME_RC} — the post-compact resume prompt was NOT queued. If the pane sits idle after compaction, send it a resume prompt by hand."
+    fi
   fi
-  # thrum-xyz: queue the RESUME PROMPT right behind /compact, on the same
-  # daemon queue (only when the daemon-routed /compact send succeeded; the raw
-  # fallback path leaves any hook-side nudge as the kickoff). Hook output is
+  # resume-prompt: queue the RESUME PROMPT right behind /compact — on the daemon
+  # queue when the daemon-routed send succeeded (dispatched once the pane is
+  # idle again AFTER the compaction, FIFO behind /compact: not a timer, fires
+  # exactly once), or via the raw explicit-socket send above when the raw
+  # fallback carried /compact. Hook output is
   # context only — it does not start a turn — so without this an idle pane with
   # an empty inbox can sit at 0% context, empty composer, until a human types.
   # The daemon dispatches it once the pane is idle again AFTER the compaction
   # (FIFO behind /compact), so it is not a timer and it fires exactly once.
   if [ "$SEND_RC" -eq 0 ]; then
-    RESUME_PROMPT="Compaction complete - please continue: your Resume Plan is in the auto-injected briefing (# Previous Session Context). If it is missing, read ${SNAPSHOT} or the newest *-restart.md in .thrum/agents/${AGENT}/sessions/ of the main repo, then execute its numbered resume plan."
     thrum tmux send "$AGENT" "$RESUME_PROMPT"
     RESUME_RC=$?
     if [ "$RESUME_RC" -eq 0 ]; then
@@ -333,9 +347,10 @@ of that is needed here. Resume LEAN, in this order:
    snapshot (moves `${REPO}/.thrum/restart/${AGENT}.md` into the main repo's
    `.thrum/agents/${AGENT}/sessions/`), so the original path is normally GONE
    by the time you look — that is by design, not loss. Only if no briefing
-   appeared (daemon unreachable), read the newest `*-restart.md` in that
-   `sessions/` directory (or `${REPO}/.thrum/restart/${AGENT}.md` if it still
-   exists) and run `thrum:prime-agent` manually as the fallback. Never manually
+   appeared (daemon unreachable), read the NEWEST `*-restart.md` in that
+   `sessions/` directory, e.g. `ls -1t "$(cat "${REPO}/.thrum/redirect" 2>/dev/null || echo "${REPO}/.thrum")"/agents/${AGENT}/sessions/*-restart.md | head -1`
+   (fall back to `${REPO}/.thrum/restart/${AGENT}.md` only if it still
+   exists; use the Read tool, not Bash sed/cat, on `~/.claude` paths) and run `thrum:prime-agent` manually as the fallback. Never manually
    run full `thrum prime` when the briefing is present.
 2. **A resume prompt starts your first turn.** Step 4 queued a "Compaction
    complete - please continue" prompt on the daemon right behind `/compact`; it

package/assets/commands/thrum-compact.md

@@ -53,14 +53,11 @@ skill) BEFORE composing your snapshot below — these survive compaction
 independently of the prose continuation file and are what a post-compact
 render reads back.
 
-Read the partial at the absolute path (resolve `$REPO` yourself first via
-`thrum agent worktree --authoritative` — NEVER `thrum whoami --field worktree`
-or `git rev-parse --show-toplevel`, both cwd-resolved and the root cause of
-a documented snapshot-save loss class; there is no git fallback):
-
-```text
-${REPO}/claude-plugin/commands/_snapshot-protocol.md
-```
+Invoke the /thrum:snapshot-protocol skill and follow it, starting with its
+Step 1 (resolve your worktree ONLY via `thrum agent worktree --authoritative` —
+NEVER `thrum whoami --field worktree` or `git rev-parse --show-toplevel`, both
+cwd-resolved and the root cause of a documented snapshot-save loss class;
+there is no git fallback).
 
 Apply its Step 2 (compose your continuation) per the structure guidance.
 
@@ -79,6 +76,15 @@ self-contained:
 > `thrum prime --light` briefing already auto-injected by the SessionStart
 > hook; only run `thrum:prime-agent` if it did NOT appear. Do NOT manually run
 > full `thrum prime`. Then continue from §9.
+> If you must re-read this file (no briefing appeared): read the NEWEST
+> `.thrum/agents/<your-id>/sessions/*-restart.md` in the MAIN repo (the prime
+> ARCHIVES the snapshot there); fall back to `.thrum/restart/<your-id>.md` only
+> if it still exists. Find the newest with:
+> `R=$(git rev-parse --show-toplevel); ls -1t "$(cat "$R/.thrum/redirect" 2>/dev/null || echo "$R/.thrum")"/agents/<your-id>/sessions/*-restart.md | head -1`
+> (`$R/.thrum/redirect` in a worktree names the main repo's `.thrum`; using `$R`
+> keeps this independent of your current directory). Open it with the Read tool
+> (not Bash sed/cat). The `sessions/` file lives under the repo's `.thrum`, so
+> that is allowed.
 
 Then §1…§11 as normal, with §9 (Numbered resume plan) actionable from a
 compacted (not cold) start.
@@ -135,12 +141,6 @@ not torn down, so `/thrum:sleep`'s teardown-loss risk does not apply here).
 > A single `thrum tmux send "$SESSION" "<command>"` call has no such split to
 > make.
 
-On a non-Claude runtime this block sends that runtime's own compact-equivalent
-command in place of `/compact` — see
-`${REPO}/claude-plugin/commands/_compact-runtime-commands.md` for the cited
-per-runtime table; `scripts/sync-skills.sh` applies the substitution when
-syncing this file to each runtime's plugin tree.
-
 Firing `/compact` before the Step 3 Write lands compacts a pre-write context and
 resumes from a stale/blank file — the exact failure this command prevents. This
 block (paste the two values printed by the Step 3 PREP block into its first two
@@ -234,7 +234,7 @@ if [ "$SNAPSHOT_OK" = 1 ] && [ "$SESSION_OK" = 1 ]; then
     echo "ERROR: thrum tmux send exited ${SEND_RC} — /compact was not queued. Report and stop."
     exit 1
   fi
-  # thrum-xyz: queue the RESUME PROMPT right behind /compact, on the same
+  # resume-prompt: queue the RESUME PROMPT right behind /compact, on the same
   # daemon queue. Hook output is context only — it does not start a turn — so
   # without this an idle pane with an empty inbox can sit at 0% context, empty
   # composer, until a human types. The daemon dispatches it once the pane is
@@ -281,9 +281,10 @@ of that is needed here. Resume LEAN, in this order:
    snapshot (moves `${REPO}/.thrum/restart/${AGENT}.md` into the main repo's
    `.thrum/agents/${AGENT}/sessions/`), so the original path is normally GONE
    by the time you look — that is by design, not loss. Only if no briefing
-   appeared (daemon unreachable), read the newest `*-restart.md` in that
-   `sessions/` directory (or `${REPO}/.thrum/restart/${AGENT}.md` if it still
-   exists) and run `thrum:prime-agent` manually as the fallback. Never manually
+   appeared (daemon unreachable), read the NEWEST `*-restart.md` in that
+   `sessions/` directory, e.g. `ls -1t "$(cat "${REPO}/.thrum/redirect" 2>/dev/null || echo "${REPO}/.thrum")"/agents/${AGENT}/sessions/*-restart.md | head -1`
+   (fall back to `${REPO}/.thrum/restart/${AGENT}.md` only if it still
+   exists; use the Read tool, not Bash sed/cat, on `~/.claude` paths) and run `thrum:prime-agent` manually as the fallback. Never manually
    run full `thrum prime` when the briefing is present.
 2. **A resume prompt starts your first turn.** Step 4 queued a "Compaction
    complete - please continue" prompt on the daemon right behind `/compact`; it

package/assets/commands/thrum-restart-extended.md

@@ -54,11 +54,7 @@ mkdir -p "${REPO}/.thrum/restart"
 
 ### 2. Read the shared snapshot-composition partial
 
-Read the partial at the absolute path:
-
-```text
-${REPO}/claude-plugin/commands/_snapshot-protocol.md
-```
+Invoke the /thrum:snapshot-protocol skill and follow it.
 
 It carries the CRITICAL DISCIPLINE block and BOTH the standard 11-section
 structure and the EXTENDED 16-section structure with per-section guidance.

package/assets/commands/thrum-restart.md

@@ -70,7 +70,7 @@ 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
@@ -361,7 +361,7 @@ Every archive already self-verifies: `sessionarchive.Archive` computes a
 SHA-256 checksum of the snapshot content it read *before* the move, then
 re-reads the file it just wrote at the destination and confirms the
 checksums match (`sessionarchive.VerifyArchivedIdentity` /
-`ChecksumContent` — see `internal/daemon/sessionarchive/verify.go`) before
+`ChecksumContent` in the daemon's session-archive package) before
 reporting success. A destination that exists but doesn't hash-match its
 own pre-move content is treated as a hard failure of the archive call, not
 a warning. This is what actually proves "the file at

package/assets/commands/thrum-sleep-extended.md

@@ -58,11 +58,7 @@ no session end. Exit code 1.
 
 ### 2. Read the shared snapshot-composition partial
 
-Read the partial at the absolute path:
-
-```text
-${REPO}/claude-plugin/commands/_snapshot-protocol.md
-```
+Invoke the /thrum:snapshot-protocol skill and follow it.
 
 Apply its Step 2 (compose your continuation) per the structure guidance.
 

package/assets/commands/thrum-sleep.md

@@ -62,11 +62,7 @@ no session end. Exit code 1. The skill is the wrong tool for non-tmux agents.
 
 ### 2. Read the shared snapshot-composition partial
 
-Read the partial at the absolute path:
-
-```text
-${REPO}/claude-plugin/commands/_snapshot-protocol.md
-```
+Invoke the /thrum:snapshot-protocol skill and follow it.
 
 Apply its Step 2 (compose your continuation) per the structure guidance.
 

package/assets/commands/thrum-update-project.md

@@ -104,7 +104,7 @@ updating.
 
 1. **Header line** — Update `Last Updated` date and `Phase` status summary. Also
    derive and insert the Authored-against stamp, placing it immediately after
-   the `Last Updated` line (see `claude-plugin/commands/_stamp-protocol.md`
+   the `Last Updated` line (see the /thrum:stamp-protocol skill
    for the exact two-line format).
 
 2. **Current State Summary — LIVE STATE ONLY, SUPERSEDED EACH SESSION.**

package/assets/skills/brainstorm-queue-aware/SKILL.md

@@ -32,7 +32,7 @@ answer," do this instead:
    clear question, plus 2-3 concrete options (A/B/C) so the Steward has
    something to decide between, not an open-ended essay prompt.
 2. Send it as a `NEED` to your steward, per the NEED/ANSWER convention
-   (`dev-docs/specs/2026-08-24-brainstorm-need-answer-convention.md`):
+   (the NEED/ANSWER convention spec in the project's design docs):
 
    ```bash
    thrum send --to @<steward> --stdin <<'EOF'

package/assets/skills/brainstorm-steward/SKILL.md

@@ -72,7 +72,7 @@ thread:
 - **Push — inbox scan.** Each cycle, read your inbox (`thrum inbox`) for
   messages from a roster brainstormer whose first line matches
   `NEED [<topic>]:` (the convention from
-  `dev-docs/specs/2026-08-24-brainstorm-need-answer-convention.md`). Read
+  the NEED/ANSWER convention spec in the project's design docs). Read
   the topic, question, and options straight from the prose — there is no
   structured payload to parse; you are a judgment agent reading a message
   the way you'd read any message. The sender identity tells you which
@@ -242,9 +242,9 @@ state as soon as the brainstormer advances past it.
 
 ## Reuse note
 
-`dev-docs/templates/brainstorm-steward-watch_params.json` is the canonical
+The brainstorm-steward watch-params template in the project's design docs is the canonical
 starting config for a new Brainstorm Steward — it uses the schema documented
-in `dev-docs/specs/2026-07-22-watch-params-schema.md` unchanged, with an
+in the watch-params schema spec unchanged, with an
 empty `roster` to be populated as brainstormers are launched under it. Its
 `parent` field ships pre-filled with this fleet's own escalation target —
 when copying the template to a different fleet or box, replace that value