@delorenj/pjangler 1.2.18 → 1.2.19

package/templates/commonproject/README.md

@@ -1,13 +1,13 @@
 # CommonProject
 
-Copier template for creating new 33GOD ecosystem components with BMAD methodology, ticket-provider enforcement, and multi-agent development tooling.
+Copier template for creating new 33GOD ecosystem components with BMAD methodology, Plane ticket enforcement, and multi-agent development tooling.
 
 ## Features
 
 - **Language Support**: Python, TypeScript, Rust
 - **Event-Driven Architecture**: Optional [Bloodbank](https://github.com/delorenj/Bloodbank) integration
-- **Ticket Provider Integration**: `.project.json` records Plane or Trello board bindings
-- **Ticket Enforcement**: Git hooks enforce configured ticket-provider requirements
+- **Plane Integration**: `.project.json` for ticket management and project config
+- **Ticket Enforcement**: Git hooks enforce Plane ticket requirements
 - [TODO] **BMAD Integration**: Full BMAD methodology structure by auto running `npx bmad-method@latest install`
 - [TODO] Multiple-choice selection for different workflows: BMAD, GSD, GoogleAgentSkills, None.
 - **Containerization**: Optional Docker + Docker Compose
@@ -25,7 +25,7 @@ uv tool install copier
 # Or with pip
 pip install copier
 
-# Set up a provider key if you want automated board creation/linking
+# Set up Plane API key (for automated project creation)
 export PLANE_API_KEY="your-plane-api-key"
 OR
 [TODO] export PLANE_API_KEY=op://VaultName/Key/Field
@@ -36,14 +36,14 @@ OR
 
 ### Option 1: Automated Init (Recommended)
 
-[TODO] One command handles everything: ticket board creation/linking + Copier template:
+[TODO] One command handles everything: Plane project creation + Copier template:
 
 > TASK - Implement the following:
 > Currently, I have to run `copier copy --trust ~/code CommonProject .` globally, or `mise run init-project` while in the CommonProject source dir - but this is not ideal.
 > I would rather run `commonProject .` globally.
 
 ```bash
-# Interactive wizard - creates/links the configured ticket board automatically
+# Interactive wizard - creates Plane project automatically
 mise run init-project
 
 # Or non-interactive (uses defaults)
@@ -56,7 +56,7 @@ mise run init-project-non-interactive
 The wizard will:
 
 1. Ask for project details (name, description, type)
-2. Create or link the configured ticket board
+2. Create the Plane project automatically
 3. Run Copier with all answers pre-filled
 4. Output next steps
 
@@ -83,10 +83,9 @@ The template asks for:
 - **Project Slug**: Directory/package name (auto-generated from name)
 - **Description**: One-sentence project description
 
-### Ticket Provider Integration
+### Plane Integration
 
-- **Provider**: Plane or Trello
-- **Workspace**: Provider workspace slug when applicable (Plane default: 33god)
+- **Workspace**: Plane workspace slug (default: 33god)
 - **Project Name**
 - **Project Identifier**: 2+ character ticket prefix (e.g., HOLO, VERN)
 
@@ -111,10 +110,10 @@ The template asks for:
    git commit -m "Initial commit from template"
    ```
 
-3. **Create or Claim Ticket**
+3. **Create Plane Ticket**
 
    ```bash
-   # Create or claim a ticket in the configured provider
+   # Create ticket in Plane (or it was already created for you!)
    # Move to "In Progress"
    git checkout -b <IDENTIFIER>-123-initial-setup
    ```

package/templates/commonproject/copier.yml

@@ -3,7 +3,7 @@
 #
 # Generic base project template. Creates a project skeleton with:
 # - BMAD methodology (pre-initialized)
-# - Ticket-provider metadata (Plane or Trello)
+# - Plane project (auto-created in 33god workspace)
 # - mise environment management
 # - CLI coder configs (Claude, Codex, Gemini, etc.)
 
@@ -30,15 +30,16 @@ project_description:
   help: One-line description
   default: ""
 
-# Ticket board provider for this project. Plane boards can be created before
-# Copier runs; Trello boards are linked by id/url. The board identity is
-# persisted into .project.json so it is the single source of truth shared with
-# the hermes-agent template's agents.
+# Ticket board provider for this project. The board itself is created by
+# init-project.sh (create-plane-project.sh) BEFORE copier runs; its identity is
+# threaded back in via plane_* below and persisted into .project.json so it is
+# the single source of truth shared with the hermes-agent template's agents.
 ticket_provider:
   type: str
   help: Ticket board provider this project's board lives in
   default: plane
   choices:
+    Linear: linear
     Plane: plane
     Trello: trello
 
@@ -49,7 +50,8 @@ project_slug:
   default: "{{ project_name | lower | replace(' ', '-') | replace('_', '-') }}"
   when: false
 
-# Back-compat aliases kept for existing pjangler/CommonProject callers.
+# Board binding — supplied by init-project.sh's --data-file after the board is
+# created. Defaults keep a bare `copier copy` rendering valid (empty binding).
 plane_workspace:
   type: str
   default: "33god"
@@ -70,27 +72,6 @@ plane_base:
   default: "https://plane.delo.sh"
   when: false
 
-# Provider-agnostic board binding — supplied by pjangler's --data values after
-# the board is created or linked. Defaults keep a bare `copier copy` rendering
-# valid, and fall back to the legacy plane_* aliases above. Board URLs are
-# derived from provider/workspace/board_id and are intentionally not persisted.
-board_id:
-  type: str
-  default: "{{ plane_project_id }}"
-  when: false
-
-# Deprecated no-op accepted so older pjangler/CommonProject callers do not fail
-# when they still pass `--data board_url=...`.
-board_url:
-  type: str
-  default: ""
-  when: false
-
-ticket_workspace:
-  type: str
-  default: "{{ plane_workspace if ticket_provider == 'plane' else '' }}"
-  when: false
-
 # Drives conditional blocks in rendered files (e.g. _.python.venv in mise.toml).
 # Not asked interactively; init-project.sh can override via --data-file.
 primary_language:

package/templates/commonproject/template/.project.json.jinja

@@ -1,5 +1,8 @@
-{% set ticket_board_id = board_id | default(plane_project_id) -%}
-{% set workspace = ticket_workspace | default(plane_workspace if ticket_provider == 'plane' else '') -%}
+{% if ticket_provider == 'plane' and plane_project_id -%}
+{% set board_url = plane_base ~ '/' ~ plane_workspace ~ '/projects/' ~ plane_project_id ~ '/issues/' -%}
+{% else -%}
+{% set board_url = '' -%}
+{% endif -%}
 {
   "project_name": {{ project_name | tojson }},
   "project_description": {{ project_description | tojson }},
@@ -7,17 +10,10 @@
   "repo_path": "",
   "ticket_provider": {
     "type": {{ ticket_provider | tojson }},
-    "workspace": {{ workspace | tojson }},
+    "workspace": {{ plane_workspace | tojson }},
     "identifier": {{ project_identifier | tojson }},
-    "board_id": {{ ticket_board_id | tojson }},
-    "state": {{ ("linked" if ticket_board_id else "planned") | tojson }}
+    "board_id": {{ plane_project_id | tojson }},
+    "board_url": {{ board_url | tojson }}
   },
-  "agents": {},
-  "automation": {
-    "reconcile": {
-      "enabled": false,
-      "grace_hours": 0,
-      "auto_review": true
-    }
-  }
+  "agents": {}
 }

package/templates/hermes-agent/README.md

@@ -11,7 +11,7 @@ memory/state checkpointing.
 | What it scaffolds | A new top-level project | An agent role inside an existing project |
 | Copier target | `./my-new-project/` | `./agents/hermes/<role>/` |
 | Asks | project name + description | role + purpose + tone |
-| Post-gen artifacts | Ticket board binding, bmad init, mise tasks | Ticket board binding, Telegram bot wiring, agent-hm-* runtime repo, systemd units |
+| Post-gen artifacts | Plane project, bmad init, mise tasks | Plane project, Telegram bot wiring, agent-hm-* runtime repo, systemd units |
 
 CommonProject runs first to create the umbrella project. hermes-agent-template
 runs second (for each agent role you want) to drop agents into it.
@@ -20,8 +20,8 @@ runs second (for each agent role you want) to drop agents into it.
 
 The template provisions a single Hermes role per invocation. The `pm` role
 handles project management and triage, and also runs the continuous ticket
-sentinel out-of-band: a provider-agnostic board-reconciliation pass (Plane or
-Trello) with an autonomous adversarial review (act, do not wait). The
+sentinel out-of-band: a provider-agnostic board-reconciliation pass (Linear,
+Plane, or Trello) with an autonomous adversarial review (act, do not wait). The
 sentinel runs as the PM's **heartbeat** — a fused systemd timer tick that does
 the reconciliation pass and then a gated runtime checkpoint. (There is no
 separate `scrum-master` role; its duties folded into the PM heartbeat.)
@@ -47,7 +47,7 @@ The template will:
 5. Populate it with the runtime scaffold (config.yaml, SOUL.md, memories, consumer.py)
 6. Add it as a git submodule at `agents/hermes/pm/runtime/` (== HERMES_HOME)
 7. Prompt for a BotFather token, store it in `runtime/.env`
-8. Create or bind the configured ticket board
+8. Create a Plane project in your configured workspace
 9. Install systemd `--user` units: gateway, consumer, heartbeat timer (reconcile + checkpoint)
 10. Append the agent to `~/.hermes/agents-registry.yaml`
 
@@ -68,7 +68,7 @@ you to review it. Keys:
 | `fleet` | `fleet_env`, `registry_file` | Fleet source-of-truth + registry locations |
 | `fleet` | `oauth_file`, `codex_home` | Shared Hermes OAuth store + Codex CLI/app-server auth home |
 | `fleet` | `runtime_scaffold_dir` | Fallback scaffold (if agent-local one is missing) |
-| `fleet` | `canonical_skills_dir`, `pm_external_skill_dirs`, `symlinked_runtime_skills` | Shared runtime skills plus PM external skill libraries |
+| `fleet` | `canonical_skills_dir`, `symlinked_runtime_skills` | Skills mirrored into each profile |
 | `github` | `runtime_repo_owner` | Owner of the `agent-hm-*` runtime repos |
 | `plane` | `base`, `workspace` | Plane URL + workspace slug |
 | `bloodbank` | `nats_host`, `nats_port`, `compose_dir` | NATS endpoint + compose dir hint |
@@ -138,14 +138,14 @@ to force re-run:
 
 ```bash
 cd agents/hermes/pm
-rm .scripts/.done-42-ticket-provider
-SKIP_SYSTEMD=1 ./.scripts/42-ticket-provider.sh
+rm .scripts/.done-40-plane
+SKIP_TELEGRAM=1 SKIP_SYSTEMD=1 ./.scripts/40-plane.sh
 ```
 
 ## Retiring an agent
 
 (TODO: ship `retire.sh` in v1.1)
 
-Manual: stop systemd units, `hermes profile delete`, archive the ticket board
-if the provider supports archival, `/deletebot` in BotFather, archive the
+Manual: stop systemd units, `hermes profile delete`, archive the Plane
+project, `/deletebot` in BotFather, archive the
 `agent-hm-*` runtime repo, remove the registry entry.

package/templates/hermes-agent/config.example.toml

@@ -1,66 +1 @@
-# hermes-agent-template — distributable configuration
-#
-# This file holds every environment-specific default the provisioning scripts
-# need. Copy it to ~/.config/hermes-agent-template/config.toml (the first
-# provisioning run does this for you) and edit the values for YOUR machine.
-#
-# Resolution precedence for each value (highest wins):
-#   explicit env var  >  ~/.hermes/fleet.env  >  this file  >  built-in fallback
-#
-# Override the config location with $HERMES_TEMPLATE_CONFIG if you keep it
-# somewhere other than $XDG_CONFIG_HOME/hermes-agent-template/config.toml.
-
-[fleet]
-# Absolute path to the shared Hermes executable every agent launcher execs.
-hermes_bin = "~/.hermes/hermes-agent/.venv/bin/hermes"
-# Checkout of the hermes-agent repo. Its .venv is used to install nats-py, etc.
-hermes_repo = "~/.hermes/hermes-agent"
-# Fallback runtime scaffold dir — used only when an agent's vendored
-# ./.runtime-scaffold is missing.
-runtime_scaffold_dir = "~/code/hermes-agent-template/runtime-scaffold"
-# Shared fleet source-of-truth env file + fleet registry. ~ is expanded.
-fleet_env = "~/.hermes/fleet.env"
-registry_file = "~/.hermes/agents-registry.yaml"
-# Shared auth roots. HERMES_OAUTH_FILE is the Hermes provider OAuth store
-# (including openai-codex); CODEX_HOME is for Codex CLI/app-server auth.
-oauth_file = "~/.hermes/auth.json"
-codex_home = "~/.codex"
-# Canonical external skills dir mirrored into each agent profile.
-canonical_skills_dir = "/home/delorenj/.agents/skills"
-# PM-only external skill libraries surfaced alongside Hermes built-ins.
-pm_external_skill_dirs = [
-  "~/code/skillex/skill-sets/global/.system",
-  "~/code/skillex/packs/bmad/6.10.2",
-]
-# Voxxy plugin + service defaults for Hermes PM agents.
-voxxy_plugin_dir = "~/code/voxxy/plugins/tts/voxxy"
-vox_url = "https://vox.delo.sh"
-# Canonical PM config.yaml the provisioner seeds each runtime's config.yaml from.
-# This is the fleet-wide Hermes inference/skill config (model, toolsets, etc.)
-# every agent runtime starts from. ~ is expanded.
-# canonical_pm_config = "~/.hermes/config.yaml"
-# Skills symlinked into every agent's runtime skills root.
-symlinked_runtime_skills = [
-  "delonet-conventions",
-  "delonet-dotenv",
-  "hermes-pm-template-maintenance",
-  "hindsight",
-  "33god-projects",
-  "subagent-driven-development",
-]
-
-[github]
-# Owner of the per-agent runtime repos (creates <owner>/agent-hm-<repo>-<role>).
-runtime_repo_owner = "delorenj"
-
-[plane]
-# Plane instance base URL and workspace slug (one project per agent).
-base = "https://plane.delo.sh"
-workspace = "33god"
-
-[bloodbank]
-# NATS endpoint the consumer connects to.
-nats_host = "127.0.0.1"
-nats_port = 4222
-# Where the bloodbank docker compose lives (used only for a hint message). ~ ok.
-compose_dir = "~/code/33GOD/bloodbank"
+template/.scripts/config.example.toml

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 or binds the configured ticket board
+#   4. Creates a Plane project in 33god workspace
 #   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, ticket
-# provider defaults, NATS endpoint, skills dir, …) are NOT hardcoded — they live in
+# Environment-specific defaults (Hermes binary path, runtime repo owner, Plane
+# workspace/URL, 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,6 +59,7 @@ 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,23 +92,20 @@ 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 Ticket Board Per Repo
+## One Plane project per agent
 
-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.
+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.
 
 ## Bloodbank wiring
 
 Each consumer subscribes to two lanes:
-- `bloodbank.evt.v1.repo.<repo>.>`   — events affecting this repo
-- `bloodbank.cmd.v1.agent.<agent_id>.>` — commands targeting THIS agent specifically
+- `bloodbank.evt.v1.repo.>` — canonical repo-domain events, filtered by `data.repo`
+- `bloodbank.cmd.v1.agent.>` — canonical agent-domain commands, filtered by `data.target_agent_id`
 
 Each agent emits CloudEvents 1.0 envelopes with `actor.agent_id`,
 `producer = hermes-agent:<id>`, `source = hermes://agent/<id>`. The naming
-spec is owned by Holyfields (`~/code/33GOD/bloodbank/docs/event-naming.md`).
-
-The current generated consumer is a transitional NATS receiver and audit
-capture. The target architecture is a first-class Hermes Bloodbank gateway where
-command events enter the same turn queue as Telegram/web messages; see
-[Bloodbank Gateway](bloodbank-gateway.md).
+contract is owned by Bloodbank (`~/code/33GOD/bloodbank/docs/event-naming.md`).
+Repo and agent identifiers belong in envelope data, actor, or source fields,
+never in type or subject tokens.

package/templates/hermes-agent/docs/fleet-control-plane/README.md

@@ -24,7 +24,6 @@ The Fleet remains a set of independently useful parts:
 - [prd.md](./prd.md) - Functional and non-functional requirements.
 - [architecture.md](./architecture.md) - Technical architecture and ADRs.
 - [epics-and-stories.md](./epics-and-stories.md) - Implementation backlog with acceptance criteria.
-- [n8n-service-hub.md](./n8n-service-hub.md) - Concrete service-hub shape for n8n plus systemd fallback.
 - [implementation-readiness-report-2026-06-27.md](./implementation-readiness-report-2026-06-27.md) - Readiness assessment and launch gates.
 
 ## Adapted BMAD Note
@@ -33,3 +32,4 @@ The formal BMAD workflow expects a project-local `_bmad` runtime, PRD, and
 step-by-step user confirmations. This repo does not currently contain `_bmad`.
 These artifacts preserve the BMAD intent and structure while using the live
 architecture review and advanced elicitation decisions as input.
+

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` |
-| 42 ticket provider | Create or bind the configured ticket board, patch identifier into role.yaml | `SKIP_PLANE=1` |
+| 40 plane | Create Plane project in 33god workspace (1:1 with agent), 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 |
@@ -118,7 +118,7 @@ systemctl --user start hermes-${AGENT}-gateway.service
 | --- | --- |
 | Telegram | DM `@<repo>_<role>_bot` (once Telegram is wired) |
 | Local CLI | `./agents/hermes/<role>/hermes chat "..."` |
-| Bloodbank | Publish to subject `bloodbank.cmd.v1.agent.<agent_id>.<verb>.requested` |
+| Bloodbank | Publish to `bloodbank.cmd.v1.agent.task.assign` with `data.target_agent_id = <agent_id>` |
 
 ## Inspect fleet state
 
@@ -187,10 +187,10 @@ systemctl --user disable --now hermes-${AGENT}-heartbeat.timer
 #    that's what you want!)
 hermes profile delete ${AGENT}
 
-# 3. Archive the ticket board if the provider supports archival
+# 3. Archive Plane project (Plane UI or API)
 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_API_KEY:-${PLANE_33GOD_API_KEY}}"
+  -H "X-API-Key: ${PLANE_33GOD_API_KEY}"
 
 # 4. BotFather: /deletebot @<repo>_<role>_bot
 # 5. Archive runtime repo (GitHub UI; we don't have delete_repo scope by default)
@@ -219,7 +219,8 @@ rm -rf agents/hermes/<role>
 ### Consumer not seeing events
 - Verify NATS is up: `docker compose -f ~/code/33GOD/bloodbank/compose/docker-compose.yml ps`
 - Tail consumer: `journalctl --user -fu hermes-<agent>-consumer.service`
-- Make sure something is actually publishing to `bloodbank.evt.v1.repo.<repo>.*`
+- Make sure something is publishing canonical repo events such as
+  `bloodbank.evt.v1.repo.issue.updated` with `data.repo = <repo>`
 
 ### Heartbeat not checkpointing (runtime not pushing)
 The checkpoint runs inside the heartbeat tick (after the board-reconciliation

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 Plane or Trello. The engine lives once in this template (the
+runs on Linear, Plane, or Trello. The engine lives once in this template (the
 single source of truth) and propagates to every deployment with
 `copier update`.
 
@@ -37,6 +37,8 @@ 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).
@@ -52,7 +54,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_33GOD_API_KEY=<key>   # or PLANE_API_KEY / TRELLO_KEY + TRELLO_TOKEN
+export PLANE_API_KEY=<key>   # or LINEAR_API_KEY / TRELLO_KEY + TRELLO_TOKEN
 curl -fsSL https://raw.githubusercontent.com/delorenj/hermes-agent-template/main/install-local.sh | sh
 ```
 
@@ -64,7 +66,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 ticket board, and the Telegram step is
+> runtime repo, a Telegram bot, and a Plane project, 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
@@ -77,9 +79,9 @@ All paths are relative to the repository root.
 | Path | What it is |
 | --- | --- |
 | `copier.yml` | Questions (`role`, `ticket_provider`) and the `_tasks` provisioning chain. |
-| `template/role.yaml.jinja` | The rendered role identity/personality manifest. Repo-owned board binding and reconciliation knobs live in repo-root `.project.json`. |
+| `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/{plane,trello}.sh` | The provider adapters. |
+| `template/.scripts/providers/{linear,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). |
@@ -107,8 +109,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 (Plane is done).
-   See [Providers: verifying an
+1. Live-verify the **Trello** adapter against a real board (Linear and Plane are
+   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,8 +71,7 @@ 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 the supported ticket back ends: Plane and
-Trello.
+This is what lets one engine serve three back ends: Trello, Plane, and Linear.
 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_33GOD_API_KEY=<key>   # or PLANE_API_KEY / TRELLO_KEY + TRELLO_TOKEN
+export PLANE_API_KEY=<key>   # or LINEAR_API_KEY / 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_TRELLO_BOARD`,
-and `HAT_DRY_RUN=1` to preview without changing anything.
+`HAT_ROLES`, `HAT_PLANE_WORKSPACE`, `HAT_PLANE_PROJECT`, `HAT_LINEAR_TEAM`,
+`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=<plane|trello>
+  --data ticket_provider=<linear|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 ticket board. Don't run full
+> and `42-ticket-provider.sh` can create a Plane project. 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 or linking the ticket board. |
+| `SKIP_PLANE` | Creating a Plane project. |
 | `SKIP_BLOODBANK` | Installing the BloodBank consumer. |
 | `SKIP_SYSTEMD` | Installing `systemd` units (gateway, consumer, heartbeat timer). |
 
@@ -181,14 +181,13 @@ 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=trello
+  --data role=pm --data target_repo=<repo> --data ticket_provider=linear
 ```
 
 After provisioning, set the board binding in
-repo-root `.project.json`. For Trello, set `ticket_provider.board_id` to the
-board id; for Plane, set `ticket_provider.workspace` and `ticket_provider.board_id`.
-Make the provider key available to the heartbeat's environment: on Linux through
-a `systemd` `EnvironmentFile` (for example
+`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
 `~/.hermes/<agent_id>.env`); on macOS the `launchd` agent sources that same
 per-agent env file, so write the key there.
 
@@ -257,8 +256,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.** Plane is verified live
-   (including `transition` and `comment`). Trello is implemented against
+1. **Live-verify the Trello adapter.** Linear and Plane are verified live
+   (Plane includes `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.