@delorenj/pjangler 1.2.6 → 1.2.9

package/templates/hermes-agent/copier.yml

@@ -12,13 +12,13 @@
 #   1. Renders agents/hermes/<role>/{role.yaml, SOUL.md, hermes, .scripts/}
 #   2. Creates a per-agent runtime repo gh:delorenj/agent-hm-<repo>-<role>
 #   3. Submodules it at agents/hermes/<role>/runtime/  (this is HERMES_HOME)
-#   4. Creates a Plane project in 33god workspace
+#   4. Creates or binds the configured ticket board
 #   6. Prompts for a BotFather Telegram token, stores in runtime/.env
 #   7. Installs a Bloodbank consumer + heartbeat timer (reconcile + checkpoint)
 #   8. Appends to ~/.hermes/agents-registry.yaml
 #
-# Environment-specific defaults (Hermes binary path, runtime repo owner, Plane
-# workspace/URL, NATS endpoint, skills dir, …) are NOT hardcoded — they live in
+# Environment-specific defaults (Hermes binary path, runtime repo owner, ticket
+# provider defaults, NATS endpoint, skills dir, …) are NOT hardcoded — they live in
 # ~/.config/hermes-agent-template/config.toml, seeded from config.example.toml on
 # first run. Edit that file to retarget the template for a different machine/user.
 
@@ -59,7 +59,6 @@ ticket_provider:
   help: "Ticket system this agent's board lives in"
   default: plane
   choices:
-    "Linear": linear
     "Plane": plane
     "Trello": trello
 

package/templates/hermes-agent/docs/architecture.md

@@ -92,11 +92,11 @@ happen to share a token, the second one's startup fails fast. The N×M cost
 (N BotFather sessions per fleet) is the price we accept for zero custom
 routing code.
 
-## One Plane project per agent
+## One Ticket Board Per Repo
 
-A Plane "project" is the natural unit of work isolation. Mixing agents into a
-shared project would conflate decisions and break filters. 1:1 also makes
-archive-on-retire clean.
+The configured ticket board is the natural unit of work isolation. The PM owns
+one board per repo and routes worker agents through that shared source of truth,
+so decisions, filters, and review state stay coherent.
 
 ## Bloodbank wiring
 

package/templates/hermes-agent/docs/operations.md

@@ -29,7 +29,7 @@ invocations).
 | 10 hermes profile | `hermes profile create <repo>-<role> --clone --no-alias` + mirror skills/plugins/hooks from default + symlink canonical runtime skills (`delonet-conventions`, `delonet-dotenv`, `hermes-pm-template-maintenance`, `hindsight`, `subagent-driven-development`) from `/home/delorenj/.agents/skills`; PM roles also seed `VOX_URL` in profile `.env` | n/a |
 | 20 runtime repo | Create gh:delorenj/agent-hm-<repo>-<role> (private), push scaffold from role-local `.runtime-scaffold/`, submodule-add into ./runtime/, symlink ~/.hermes/profiles/<id> → runtime; PM roles also link the Voxxy plugin and set `tts.provider: voxxy` | `SKIP_RUNTIME_REPO=1` |
 | 30 telegram | Capture BotFather token, write to runtime/.env, enable hermes-telegram toolset | `SKIP_TELEGRAM=1` |
-| 40 plane | Create Plane project in 33god workspace (1:1 with agent), patch identifier into role.yaml | `SKIP_PLANE=1` |
+| 42 ticket provider | Create or bind the configured ticket board, patch identifier into role.yaml | `SKIP_PLANE=1` |
 | 60 bloodbank | Install consumer (renders from scaffold w/ agent values), health-check NATS, install nats-py via uv if missing | `SKIP_BLOODBANK=1` |
 | 70 systemd | Install user units: gateway, consumer, heartbeat timer (board-reconciliation sentinel pass + gated runtime checkpoint, one tick) | `SKIP_SYSTEMD=1` |
 | 80 registry | Append entry to ~/.hermes/agents-registry.yaml | n/a |
@@ -187,7 +187,7 @@ systemctl --user disable --now hermes-${AGENT}-heartbeat.timer
 #    that's what you want!)
 hermes profile delete ${AGENT}
 
-# 3. Archive Plane project (Plane UI or API)
+# 3. Archive the ticket board if the provider supports archival
 PROJECT_ID=$(python3 -c "import yaml,pathlib; print(yaml.safe_load(pathlib.Path.home().joinpath('.hermes/agents-registry.yaml').read_text())['agents']['${AGENT}']['plane']['project_id'])")
 curl -X POST "https://plane.delo.sh/api/v1/workspaces/33god/projects/${PROJECT_ID}/archive/" \
   -H "X-API-Key: ${PLANE_33GOD_API_KEY}"

package/templates/hermes-agent/docs/sentinel/README.md

@@ -26,7 +26,7 @@ that does the board-reconciliation pass and then a gated runtime checkpoint
 `.scripts/sentinel/`.
 
 It talks to the ticket board through a pluggable adapter, so the same engine
-runs on Linear, Plane, or Trello. The engine lives once in this template (the
+runs on Plane or Trello. The engine lives once in this template (the
 single source of truth) and propagates to every deployment with
 `copier update`.
 
@@ -37,8 +37,6 @@ The following is true as of June 1, 2026.
 - The engine, the provider abstraction, and the autonomous adversarial-review
   enforcement are built, syntax-clean, and validated offline with a mock
   provider.
-- The **Linear** adapter is verified live against a real board (a real
-  `DEL` team: `resolve`, `list_issues` returning 93 issues, and `get_issue`).
 - The **Plane** adapter is verified live against a real workspace
   (`resolve`, `list_issues`, `get_issue`, `comment`, and a
   `transition` to `completed` on a disposable issue).
@@ -54,7 +52,7 @@ For a local, single-machine install (no GitHub runtime repo, no Telegram, no
 NATS), use the one-command bootstrap. From inside the target project:
 
 ```bash
-export PLANE_API_KEY=<key>   # or LINEAR_API_KEY / TRELLO_KEY + TRELLO_TOKEN
+export PLANE_API_KEY=<key>   # or TRELLO_KEY + TRELLO_TOKEN
 curl -fsSL https://raw.githubusercontent.com/delorenj/hermes-agent-template/main/install-local.sh | sh
 ```
 
@@ -66,7 +64,7 @@ macOS). See [Development guide: local install](development.md#local-install-one-
 <!-- prettier-ignore -->
 > [!IMPORTANT]
 > Full (non-local) provisioning is outward-facing. It can create a GitHub
-> runtime repo, a Telegram bot, and a Plane project, and the Telegram step is
+> runtime repo, a Telegram bot, and a ticket board, and the Telegram step is
 > interactive. Use `install-local.sh` or the `SKIP_*` flags described in
 > [Development guide:
 > provisioning](development.md#provisioning-the-pm-manual) for local or lean
@@ -81,7 +79,7 @@ All paths are relative to the repository root.
 | `copier.yml` | Questions (`role`, `ticket_provider`) and the `_tasks` provisioning chain. |
 | `template/role.yaml.jinja` | The rendered role manifest, including the `ticket_provider` binding and the `reconcile` knobs (`grace_hours`, `auto_review`). |
 | `template/.scripts/lib/ticket-provider.sh` | The adapter dispatcher (`tp`). The engine's only seam to a ticket system. |
-| `template/.scripts/providers/{linear,plane,trello}.sh` | The provider adapters. |
+| `template/.scripts/providers/{plane,trello}.sh` | The provider adapters. |
 | `template/.scripts/42-ticket-provider.sh` | Provisioning step that resolves or creates the board. |
 | `template/.scripts/70-systemd.sh` | Provisioning step that installs the gateway, consumer, and the fused `heartbeat` timer (board-reconciliation sentinel pass + gated runtime checkpoint). |
 | `install-local.sh` | One-command local install (no cloud, macOS + Linux). |
@@ -109,8 +107,8 @@ the agent to read at run time. Keep the two in sync when behavior changes.
 
 The highest-value open work, in order:
 
-1. Live-verify the **Trello** adapter against a real board (Linear and Plane are
-   done). See [Providers: verifying an
+1. Live-verify the **Trello** adapter against a real board (Plane is done).
+   See [Providers: verifying an
    adapter](providers.md#verifying-an-adapter-against-a-live-board).
 2. Confirm `install-local.sh` on a real macOS machine. The Linux path and the
    Plane adapter are verified; the macOS `launchd` agent and `mkdir` lock get

package/templates/hermes-agent/docs/sentinel/architecture.md

@@ -71,7 +71,8 @@ function, `tp`, that dispatches to one provider implementation under
 through the `ticket_provider` question and recorded in `role.yaml` under
 `ticket_provider.name`.
 
-This is what lets one engine serve three back ends: Trello, Plane, and Linear.
+This is what lets one engine serve the supported ticket back ends: Plane and
+Trello.
 For the full contract and the per-provider details, see
 [Providers](providers.md).
 

package/templates/hermes-agent/docs/sentinel/development.md

@@ -112,7 +112,7 @@ repository root instead of driving Copier by hand. From inside the target
 project:
 
 ```bash
-export PLANE_API_KEY=<key>   # or LINEAR_API_KEY / TRELLO_KEY + TRELLO_TOKEN
+export PLANE_API_KEY=<key>   # or TRELLO_KEY + TRELLO_TOKEN
 curl -fsSL https://raw.githubusercontent.com/delorenj/hermes-agent-template/main/install-local.sh | sh
 ```
 
@@ -133,8 +133,8 @@ The script:
 7. smoke-tests the board connection through the adapter.
 
 Useful environment overrides (skip the prompts): `HAT_REPO`, `HAT_PROVIDER`,
-`HAT_ROLES`, `HAT_PLANE_WORKSPACE`, `HAT_PLANE_PROJECT`, `HAT_LINEAR_TEAM`,
-`HAT_TRELLO_BOARD`, and `HAT_DRY_RUN=1` to preview without changing anything.
+`HAT_ROLES`, `HAT_PLANE_WORKSPACE`, `HAT_PLANE_PROJECT`, `HAT_TRELLO_BOARD`,
+and `HAT_DRY_RUN=1` to preview without changing anything.
 
 This local path does not wire Telegram or email. Those are convenience layers in
 the `pjangler` provisioner, not requirements for a working agent — talk to the
@@ -151,7 +151,7 @@ cd /path/to/your-project
 copier copy gh:delorenj/hermes-agent-template ./agents/hermes/pm \
   --data role=pm \
   --data target_repo=<repo> \
-  --data ticket_provider=<linear|plane|trello>
+  --data ticket_provider=<plane|trello>
 ```
 
 The `_tasks` chain in `copier.yml` runs the numbered provisioning scripts in
@@ -162,7 +162,7 @@ order. Several of them reach outside the repository.
 > Full provisioning is outward-facing and partly interactive.
 > `20-runtime-repo.sh` creates a private GitHub repo with `gh repo create`,
 > `30-telegram.sh` prompts for a BotFather token and blocks waiting for input,
-> and `42-ticket-provider.sh` can create a Plane project. Don't run full
+> and `42-ticket-provider.sh` can create a ticket board. Don't run full
 > provisioning unattended.
 
 Use the `SKIP_*` environment flags for a local or lean install. Each numbered
@@ -172,7 +172,7 @@ script checks its flag and skips cleanly.
 | --- | --- |
 | `SKIP_TELEGRAM` | The interactive BotFather token step. |
 | `SKIP_RUNTIME_REPO` | Creating the GitHub runtime repo. |
-| `SKIP_PLANE` | Creating a Plane project. |
+| `SKIP_PLANE` | Creating or linking the ticket board. |
 | `SKIP_BLOODBANK` | Installing the BloodBank consumer. |
 | `SKIP_SYSTEMD` | Installing `systemd` units (gateway, consumer, heartbeat timer). |
 
@@ -181,13 +181,14 @@ For example, a local install that creates no cloud resources:
 ```bash
 SKIP_TELEGRAM=1 SKIP_RUNTIME_REPO=1 SKIP_PLANE=1 SKIP_BLOODBANK=1 \
   copier copy gh:delorenj/hermes-agent-template ./agents/hermes/pm \
-  --data role=pm --data target_repo=<repo> --data ticket_provider=linear
+  --data role=pm --data target_repo=<repo> --data ticket_provider=trello
 ```
 
 After provisioning, set the board binding in
-`agents/hermes/pm/role.yaml`. For Linear, set `ticket_provider.team`
-to the team key. Make the provider key available to the heartbeat's environment:
-on Linux through a `systemd` `EnvironmentFile` (for example
+`agents/hermes/pm/role.yaml`. For Trello, set `ticket_provider.board` to the
+board id; for Plane, set `ticket_provider.workspace` and `ticket_provider.project`.
+Make the provider key available to the heartbeat's environment: on Linux through
+a `systemd` `EnvironmentFile` (for example
 `~/.hermes/<agent_id>.env`); on macOS the `launchd` agent sources that same
 per-agent env file, so write the key there.
 
@@ -256,8 +257,8 @@ These cost real debugging time. Watch for them.
 
 The following work is open for the incoming agent, roughly in priority order.
 
-1. **Live-verify the Trello adapter.** Linear and Plane are verified live
-   (Plane includes `transition` and `comment`). Trello is implemented against
+1. **Live-verify the Trello adapter.** Plane is verified live
+   (including `transition` and `comment`). Trello is implemented against
    the contract but unverified. Follow [Providers: verifying an
    adapter](providers.md#verifying-an-adapter-against-a-live-board) with Trello
    credentials, and fix any endpoint or field mismatches.

package/templates/hermes-agent/docs/sentinel/providers.md

@@ -1,7 +1,7 @@
 # Provider adapters
 
 This guide is the reference for the ticket-provider abstraction: the contract
-every adapter implements, the three adapters that ship today, and a
+every adapter implements, the two adapters that ship today, and a
 step-by-step process for adding a new provider or verifying an existing one
 against a live board. Read [Architecture](architecture.md) first for how the
 adapter fits into the engine.
@@ -43,12 +43,8 @@ maps each to its back end's concrete state.
 
 ## The adapters that ship today
 
-The repository includes three adapters with different verification status.
+The repository includes two supported adapters with different verification status.
 
-- **Linear** (`providers/linear.sh`) is the reference implementation. It uses
-  the Linear GraphQL API. It's verified live against a real board. Linear's
-  `issue(id:)` field accepts both the UUID and the human identifier (for
-  example, `DEL-42`), so the engine can pass identifiers through.
 - **Plane** (`providers/plane.sh`) uses the Plane REST API with `X-API-Key`
   authentication. A Plane project maps to the board, a cycle maps to the
   milestone, and `state.group` maps to the state type. It's verified live. Note
@@ -64,21 +60,6 @@ The repository includes three adapters with different verification status.
 
 Set credentials in the environment and the board binding in `role.yaml`.
 
-<details>
-<summary>Linear</summary>
-
-- Credentials: `LINEAR_API_KEY`.
-- Binding:
-
-  ```yaml
-  ticket_provider:
-    name: linear
-    team: DEL # Linear team key
-    project: "" # optional, scopes milestone and issue queries
-  ```
-
-</details>
-
 <details>
 <summary>Plane</summary>
 
@@ -114,8 +95,9 @@ Set credentials in the environment and the board binding in `role.yaml`.
 
 To add a fourth provider, for example GitHub Issues or Jira, follow these steps.
 
-1. Create `template/.scripts/providers/<name>.sh`. Start from `linear.sh` if the
-   back end uses GraphQL, or `plane.sh` if it uses REST with a single API key.
+1. Create `template/.scripts/providers/<name>.sh`. Start from `plane.sh` if it
+   uses REST with a single API key, or `trello.sh` if it has a board/list/card
+   model.
 2. Implement every operation in [the contract](#the-contract). Return the exact
    JSON shapes shown in the table. Map your back end's states to the five
    normalized states.
@@ -127,8 +109,7 @@ To add a fourth provider, for example GitHub Issues or Jira, follow these steps.
 5. Extend `template/role.yaml.jinja` with a provider-specific binding block
    under the `{% if ticket_provider == '<name>' %}` branch.
 6. Teach `42-ticket-provider.sh` how to resolve or create the board for your
-   provider, if it differs from the existing `linear`, `plane`, and `trello`
-   cases.
+   provider, if it differs from the existing `plane` and `trello` cases.
 7. Validate and verify with the steps below.
 
 <!-- prettier-ignore -->
@@ -158,7 +139,7 @@ Before you touch a live board, confirm the adapter parses and fails cleanly.
    exit, with no Python traceback:
 
    ```bash
-   ( unset LINEAR_API_KEY; sh template/.scripts/providers/linear.sh resolve )
+   ( unset PLANE_API_KEY; sh template/.scripts/providers/plane.sh resolve )
    ```
 
 ## Verifying an adapter against a live board
@@ -169,15 +150,15 @@ never closes or modifies a ticket, so it's safe to run.
 
 ```bash
 # 1. Load the credential into the environment only (never print it).
-export LINEAR_API_KEY="$(grep -E '^(export )?LINEAR_API_KEY=' \
-  ~/.hermes/<agent>.env | head -1 | sed -E 's/^(export )?LINEAR_API_KEY=//; s/^"//; s/"$//')"
+export PLANE_API_KEY="$(grep -E '^(export )?PLANE_API_KEY=' \
+  ~/.hermes/<agent>.env | head -1 | sed -E 's/^(export )?PLANE_API_KEY=//; s/^"//; s/"$//')"
 
 # 2. Stage a role directory bound to the real board.
 T=$(mktemp -d); RD="$T/agents/hermes/pm"
 mkdir -p "$RD/.scripts/lib" "$RD/.scripts/providers"
 cp template/.scripts/lib/ticket-provider.sh "$RD/.scripts/lib/"
-cp template/.scripts/providers/linear.sh "$RD/.scripts/providers/"
-printf 'repo: demo\nrole: pm\nticket_provider:\n  name: linear\n  team: DEL\n' \
+cp template/.scripts/providers/plane.sh "$RD/.scripts/providers/"
+printf 'repo: demo\nrole: pm\nticket_provider:\n  name: plane\n  workspace: 33god\n  project: <project-uuid>\n' \
   > "$RD/role.yaml"
 
 # 3. Run the read operations.
@@ -199,5 +180,4 @@ verification.
 ## Read next
 
 - [Development guide](development.md): the full edit, validate, and propagate
-  workflow, plus the open roadmap, which includes live-verifying Plane and
-  Trello.
+  workflow, plus the open roadmap, which includes live-verifying Trello.

package/templates/hermes-agent/install-local.sh

@@ -15,10 +15,10 @@
 #
 # Environment overrides (skip the prompts):
 #   HAT_REPO=<name>            project/repo name (default: basename of CWD)
-#   HAT_PROVIDER=linear|plane|trello   (default: plane)
+#   HAT_PROVIDER=plane|trello   (default: plane)
 #   HAT_ROLES="pm"                     roles to install (default: pm)
 #   HAT_DRY_RUN=1              print actions, change nothing
-#   Provider creds: LINEAR_API_KEY | PLANE_API_KEY+PLANE_BASE | TRELLO_KEY+TRELLO_TOKEN
+#   Provider creds: PLANE_API_KEY+PLANE_BASE | TRELLO_KEY+TRELLO_TOKEN
 set -eu
 
 say()  { printf '\033[36m%s\033[0m\n' "$*"; }
@@ -100,7 +100,7 @@ TOML
 fi
 
 # --- 4. Provider credentials + board binding ---------------------------------
-ask HAT_PROVIDER "Ticket provider (linear|plane|trello)" "plane"
+ask HAT_PROVIDER "Ticket provider (plane|trello)" "plane"
 PROVIDER="$HAT_PROVIDER"
 ask HAT_REPO "Project/repo name" "$(basename "$PROJECT_DIR" | tr '[:upper:]' '[:lower:]')"
 REPO="$HAT_REPO"
@@ -109,7 +109,7 @@ PM_ENV="$HOME/.hermes/${REPO}-pm.env"
 # These get written into the pm role.yaml binding after render.
 # Pre-seed from optional env knobs so the install can run non-interactively.
 TP_WORKSPACE="${HAT_PLANE_WORKSPACE:-}"; TP_PROJECT="${HAT_PLANE_PROJECT:-}"
-TP_TEAM="${HAT_LINEAR_TEAM:-}"; TP_BOARD="${HAT_TRELLO_BOARD:-}"
+TP_BOARD="${HAT_TRELLO_BOARD:-}"
 case "$PROVIDER" in
   plane)
     ask PLANE_BASE "Plane base URL" "https://app.plane.so"
@@ -136,12 +136,6 @@ PY
     CRED_LINES="PLANE_API_KEY=$PLANE_API_KEY
 PLANE_BASE=$PLANE_BASE"
     ;;
-  linear)
-    : "${LINEAR_API_KEY:?Set LINEAR_API_KEY in your environment, then re-run}"
-    ask TP_TEAM "Linear team key (for example DEL)" ""
-    [ -n "$TP_TEAM" ] || die "team key is required"
-    CRED_LINES="LINEAR_API_KEY=$LINEAR_API_KEY"
-    ;;
   trello)
     : "${TRELLO_KEY:?Set TRELLO_KEY in your environment, then re-run}"
     : "${TRELLO_TOKEN:?Set TRELLO_TOKEN in your environment, then re-run}"
@@ -170,7 +164,7 @@ for ROLE in $ROLES; do
   DEST="$PROJECT_DIR/agents/hermes/$ROLE"
   # Scrub provider creds from copier's environment so 42-ticket-provider skips
   # board CREATION; we bind to the existing board in step 6 instead.
-  run "env -u PLANE_API_KEY -u PLANE_33GOD_API_KEY -u LINEAR_API_KEY \
+  run "env -u PLANE_API_KEY -u PLANE_33GOD_API_KEY \
         -u TRELLO_KEY -u TRELLO_TOKEN \
         copier copy '$TEMPLATE_SRC' '$DEST' --trust --defaults --overwrite \
         --data target_repo='$REPO' --data role='$ROLE' --data ticket_provider='$PROVIDER'"
@@ -180,7 +174,7 @@ done
 PM_ROLE="$PROJECT_DIR/agents/hermes/pm/role.yaml"
 if [ -f "$PM_ROLE" ] && [ "${HAT_DRY_RUN:-0}" != "1" ]; then
   say "6. binding pm to your $PROVIDER board"
-  TP_WORKSPACE="$TP_WORKSPACE" TP_PROJECT="$TP_PROJECT" TP_TEAM="$TP_TEAM" \
+  TP_WORKSPACE="$TP_WORKSPACE" TP_PROJECT="$TP_PROJECT" \
   TP_BOARD="$TP_BOARD" PROVIDER="$PROVIDER" python3 - "$PM_ROLE" <<'PY'
 import os, re, sys, pathlib
 p = pathlib.Path(sys.argv[1]); t = p.read_text()
@@ -190,7 +184,6 @@ def setleaf(text, key, val):
     return new if n else text
 t = setleaf(t, "workspace", os.environ.get("TP_WORKSPACE",""))
 t = setleaf(t, "project",   os.environ.get("TP_PROJECT",""))
-t = setleaf(t, "team",      os.environ.get("TP_TEAM",""))
 t = setleaf(t, "board",     os.environ.get("TP_BOARD",""))
 p.write_text(t)
 print("   bound:", {k:v for k,v in os.environ.items() if k.startswith("TP_") and v})

package/templates/hermes-agent/template/.scripts/42-ticket-provider.sh

@@ -46,13 +46,13 @@ PY
 }
 
 # pj_write — merge board binding (optional) + this agent into .project.json.
-# args: set_provider(0|1) provider board_id board_url workspace identifier team
+# args: set_provider(0|1) provider board_id board_url workspace identifier
 pj_write() {
   REPO="$REPO" REPO_ROOT="$REPO_ROOT" AGENT_ID="$AGENT_ID" ROLE="$ROLE" \
   ROLE_DIR_REL="$ROLE_DIR_REL" PROJECT_DESC="${PROJECT_DESC:-}" \
   python3 - "$PROJECT_JSON" "$@" <<'PY'
 import sys, os, json, pathlib
-(path, set_provider, provider, board_id, board_url, workspace, identifier, team) = sys.argv[1:9]
+(path, set_provider, provider, board_id, board_url, workspace, identifier) = sys.argv[1:8]
 p = pathlib.Path(path)
 try:
     d = json.loads(p.read_text())
@@ -72,7 +72,6 @@ if set_provider == "1":
     if identifier: tp["identifier"] = identifier
     if board_id:   tp["board_id"] = board_id
     if board_url:  tp["board_url"] = board_url
-    if team:       tp["team"] = team
 ag = d.setdefault("agents", {})
 ag[os.environ["AGENT_ID"]] = {"role": os.environ["ROLE"], "role_dir": os.environ["ROLE_DIR_REL"]}
 p.write_text(json.dumps(d, indent=2) + "\n")
@@ -82,8 +81,8 @@ PY
 
 # Mirror the binding into role.yaml so legacy consumers keep working.
 mirror_to_role_yaml() {
-  # mirror_to_role_yaml <provider> <board_id> <board_url> <workspace> <identifier> <team>
-  local provider="$1" bid="$2" burl="$3" ws="$4" ident="$5" team="$6"
+  # mirror_to_role_yaml <provider> <board_id> <board_url> <workspace> <identifier>
+  local provider="$1" bid="$2" burl="$3" ws="$4" ident="$5"
   yaml_set ticket_provider.name "$provider" 2>/dev/null || true
   [ -n "$bid" ]  && yaml_set ticket_provider.board_id "$bid" 2>/dev/null || true
   [ -n "$burl" ] && yaml_set ticket_provider.board_url "$burl" 2>/dev/null || true
@@ -98,8 +97,8 @@ mirror_to_role_yaml() {
     trello)
       [ -n "$bid" ] && yaml_set ticket_provider.board "$bid" 2>/dev/null || true
       ;;
-    linear)
-      [ -n "$team" ] && yaml_set ticket_provider.team "$team" 2>/dev/null || true
+    *)
+      die "unsupported ticket provider: $provider (expected plane|trello)"
       ;;
   esac
 }
@@ -111,7 +110,6 @@ SOT_BOARD_ID="$(pj ticket_provider.board_id)"
 SOT_URL="$(pj ticket_provider.board_url)"
 SOT_WS="$(pj ticket_provider.workspace)"
 SOT_IDENT="$(pj ticket_provider.identifier)"
-SOT_TEAM="$(pj ticket_provider.team)"
 
 # role.yaml provider comes from copier --data (the operator's pjangler choice).
 ROLE_PROVIDER="$(yaml_get ticket_provider.name)"
@@ -122,9 +120,10 @@ if [ -n "$SOT_BOARD_ID" ]; then
   if [ -n "$ROLE_PROVIDER" ] && [ "$ROLE_PROVIDER" != "$PROVIDER" ]; then
     warn "[42] requested provider '$ROLE_PROVIDER' but repo board is '$PROVIDER' (.project.json wins); binding to existing board"
   fi
+  case "$PROVIDER" in plane|trello) ;; *) die "unsupported ticket provider in .project.json: $PROVIDER (expected plane|trello)" ;; esac
   log "[42] binding $AGENT_ID to existing repo board (provider=$PROVIDER, id=$SOT_BOARD_ID)"
-  mirror_to_role_yaml "$PROVIDER" "$SOT_BOARD_ID" "$SOT_URL" "$SOT_WS" "$SOT_IDENT" "$SOT_TEAM"
-  pj_write 0 "$PROVIDER" "" "" "" "" ""   # register agent only; board already recorded
+  mirror_to_role_yaml "$PROVIDER" "$SOT_BOARD_ID" "$SOT_URL" "$SOT_WS" "$SOT_IDENT"
+  pj_write 0 "$PROVIDER" "" "" "" ""   # register agent only; board already recorded
   mark_done 42-ticket-provider
   exit 0
 fi
@@ -143,45 +142,23 @@ NAME="$(printf '%s' "$REPO" | tr '_-' '  ' | python3 -c 'import sys; print(" ".j
 DESC="Ticket board for $REPO"
 
 case "$PROVIDER" in
-  linear)
-    if [[ -z "${LINEAR_API_KEY:-}" ]]; then
-      warn "[42] LINEAR_API_KEY not set; set role.yaml/.project.json ticket_provider.team and re-run ./.scripts/42-ticket-provider.sh"
-      pj_write 1 linear "" "" "" "$IDENT" "$SOT_TEAM"
-      mark_done 42-ticket-provider; exit 0
-    fi
-    OUT="$(tp resolve 2>/dev/null || true)"
-    BID="$(printf '%s' "$OUT" | python3 -c 'import sys,json
-try: print(json.load(sys.stdin).get("board_id",""))
-except Exception: print("")')"
-    BURL="$(printf '%s' "$OUT" | python3 -c 'import sys,json
-try: print(json.load(sys.stdin).get("board_url",""))
-except Exception: print("")')"
-    if [ -n "$BID" ]; then
-      mirror_to_role_yaml linear "$BID" "$BURL" "" "$IDENT" "$SOT_TEAM"
-      pj_write 1 linear "$BID" "$BURL" "" "$IDENT" "$SOT_TEAM"
-    else
-      warn "[42] linear resolve returned no board; set ticket_provider.team and re-run"
-      pj_write 1 linear "" "" "" "$IDENT" "$SOT_TEAM"
-    fi
-    ;;
-
   plane|trello)
     KEYVAR=PLANE_API_KEY; [ "$PROVIDER" = trello ] && KEYVAR=TRELLO_KEY
     if [[ -z "${!KEYVAR:-}" ]]; then
       warn "[42] $KEYVAR not set; skipping board creation. Set creds and re-run ./.scripts/42-ticket-provider.sh"
-      pj_write 1 "$PROVIDER" "" "" "${SOT_WS:-$PLANE_WORKSPACE}" "$IDENT" ""
+      pj_write 1 "$PROVIDER" "" "" "${SOT_WS:-${PLANE_WORKSPACE:-}}" "$IDENT"
       mark_done 42-ticket-provider; exit 0
     fi
     OUT="$(tp create_board "$NAME" "$IDENT" "$DESC")" || die "create_board failed for $PROVIDER"
     BID="$(printf '%s' "$OUT" | python3 -c 'import sys,json; print(json.load(sys.stdin).get("board_id",""))')"
     BURL="$(printf '%s' "$OUT" | python3 -c 'import sys,json; print(json.load(sys.stdin).get("board_url",""))')"
-    WS="${SOT_WS:-$PLANE_WORKSPACE}"
+    WS="${SOT_WS:-${PLANE_WORKSPACE:-}}"
     [ "$PROVIDER" = trello ] && WS=""
-    mirror_to_role_yaml "$PROVIDER" "$BID" "$BURL" "$WS" "$IDENT" ""
-    pj_write 1 "$PROVIDER" "$BID" "$BURL" "$WS" "$IDENT" ""
+    mirror_to_role_yaml "$PROVIDER" "$BID" "$BURL" "$WS" "$IDENT"
+    pj_write 1 "$PROVIDER" "$BID" "$BURL" "$WS" "$IDENT"
     ;;
 
-  *) die "unknown ticket provider: $PROVIDER (expected linear|plane|trello)" ;;
+  *) die "unknown ticket provider: $PROVIDER (expected plane|trello)" ;;
 esac
 
 mark_done 42-ticket-provider

package/templates/hermes-agent/template/.scripts/70-systemd.sh

@@ -33,6 +33,7 @@ Environment=HERMES_HOME=$RUNTIME
 Environment=HERMES_OAUTH_FILE=$HERMES_OAUTH_FILE
 Environment=CODEX_HOME=$CODEX_HOME
 Environment=HERMES_KANBAN_DISPATCH_IN_GATEWAY=0
+Environment=HERMES_KANBAN_SLASH_ENABLED=0
 EnvironmentFile=-$RUNTIME/.env
 ExecStart=$HERMES_BIN gateway run --replace
 Restart=on-failure

package/templates/hermes-agent/template/.scripts/lib/ticket-provider.sh

@@ -1,6 +1,6 @@
 # shellcheck shell=bash
 # Ticket-provider adapter dispatcher — the single seam between the heartbeat
-# sentinel engine and a concrete ticket system (Linear | Plane | Trello).
+# sentinel engine and a concrete ticket system (Plane | Trello).
 #
 # The engine NEVER calls a provider directly. It calls `tp <op> [args...]`,
 # which dispatches to providers/<provider>.sh. Swapping providers is a one-line
@@ -64,7 +64,7 @@ PY
 )"
     [ -n "$name" ] && { printf '%s\n' "$name"; return 0; }
   fi
-  printf 'linear\n'
+  printf 'plane\n'
 }
 
 # Directory holding provider implementations (sibling of this lib).
@@ -81,6 +81,10 @@ tp() {
 
   local name impl
   name="$(tp_provider_name)"
+  case "$name" in
+    plane|trello) ;;
+    *) echo "tp: unsupported ticket provider '$name' (expected plane|trello)" >&2; return 2 ;;
+  esac
   impl="$(tp_providers_dir)/${name}.sh"
 
   if [ ! -f "$impl" ]; then

package/templates/hermes-agent/template/.scripts/sentinel/docs/autonomous-delegated-review.md

@@ -13,7 +13,7 @@ actively tries to break the work, surface unmet acceptance criteria, hidden
 regressions, and drift. On a clean adversarial verdict the loop treats the
 ticket as done and moves on — through the ticket-provider adapter
 (`tp transition <id> <state>`) — and emits a BloodBank decision event carrying
-the full report. This works identically on Linear, Plane, or Trello.
+the full report. This works identically on Plane or Trello.
 
 The operator's verification is **deferred** to end-of-product QA over the review
 lane, backed by a queryable decision trail. A downstream regression rollback is
@@ -144,7 +144,7 @@ Write `<ISSUE>.review.md`; the script validates it:
 ```markdown
 # Autonomous Review Report: <ISSUE>
 ## Issue
-- Linear/Plane/Trello issue: <ISSUE>
+- Provider issue: <ISSUE>
 - Review lane reason:
 ## Reviewer
 - Reviewer agent: <independent-agent-id>

package/templates/hermes-agent/template/.scripts/sentinel/docs/continuous-ticket-orchestration.md

@@ -19,7 +19,7 @@ approve merges.
 All board access goes through the adapter (`tp`, from
 `.scripts/lib/ticket-provider.sh`) and reasons in normalized states:
 `backlog | unstarted | started | in_review | completed`. Never call the provider
-directly — the engine is identical across Linear, Plane, and Trello.
+directly — the engine is identical across Plane and Trello.
 
 ## Work-state feed
 

package/templates/hermes-agent/template/.scripts/sentinel.prompt.md.jinja

@@ -6,13 +6,11 @@ A cheap systemd heartbeat already decided this full pass is needed.
 Working repo: the git root containing this role at `agents/hermes/{{ role }}/`.
 Ticket provider: **{{ ticket_provider }}** (reached only through the adapter — see below).
 
-{% if ticket_provider == "plane" -%}
-**Plane is the authoritative repo ticket board/SOT for this PM.** Hermes local
-Kanban must NOT be an active durable task lifecycle surface. Local Kanban may
-only run as an explicitly configured ephemeral child execution queue and must
-never close/move authoritative repo tickets.
+The configured ticket provider is the authoritative repo ticket board/SOT for
+this PM. Hermes local Kanban must NOT be an active durable task lifecycle
+surface. Local Kanban may only run as an explicitly configured ephemeral child
+execution queue and must never close/move authoritative repo tickets.
 
-{% endif -%}
 You are the **{{ target_repo }} PM**, running your continuous board-reconciliation
 pass. Act autonomously, but stay inside the project contracts. Read
 `agents/hermes/{{ role }}/SOUL.md` and the engine docs under
@@ -34,7 +32,7 @@ tp transition <id> <normalized-state>  # backlog|unstarted|started|in_review|com
 ```
 
 Reason in **normalized states**, not provider terms. This pass works identically
-on Linear, Plane, or Trello.
+on Plane or Trello.
 
 ## Pass
 

package/templates/hermes-agent/template/SOUL.md.jinja

@@ -55,17 +55,18 @@ read it before publishing a type you haven't published before.
 {% if role == "pm" -%}
 You are the **project manager**. You triage incoming requests from Telegram /
 Bloodbank command lanes, decompose them into discrete tasks on the
-**Plane board only**, and route work to other agents in the fleet (e.g. the dev role
+configured ticket board, and route work to other agents in the fleet (e.g. the dev role
 on `bloodbank.cmd.v1.agent.{{ target_repo }}-dev.task.assign`). You do not
 write application code. You do not approve merges.
 
-**Plane is the authoritative repo ticket board/SOT for this PM.** Hermes local
-Kanban must NOT be an active durable task lifecycle surface. The kanban toolset
-is removed from the PM's cli surface. Local Kanban may only run as an explicitly-configured
-ephemeral child execution queue and must never close/move authoritative repo tickets.
+The configured ticket provider (`{{ ticket_provider }}`) is the authoritative
+repo ticket board/SOT for this PM. Hermes local Kanban must NOT be an active
+durable task lifecycle surface. The kanban toolset is removed from the PM's cli
+surface. Local Kanban may only run as an explicitly configured ephemeral child
+execution queue and must never close/move authoritative repo tickets.
 
 Default execution workflow for implementation delivery: use
-`subagent-driven-development` in Plane-ticket-orchestrated implementation mode
+`subagent-driven-development` in provider-ticket-orchestrated implementation mode
 (WIP=1, spec review gate, quality review gate).
 
 Decision events you commonly emit:
@@ -111,7 +112,7 @@ declared` event so the fleet knows what to route to you.
 - **Hostnames**: Use `*.delo.sh` for external/cross-machine access (resolved
   via Cloudflare Tunnel), `localhost` for same-host, Docker network service
   names for container-to-container, Tailscale for private machine-to-machine.
-- **Plane**: Always include a Plane ticket reference in commit messages.
+- **Ticketing**: Always include the configured provider's ticket reference in commit messages.
 
 ## Memory hygiene