cohorte 2.1.0 → 2.3.0

package/core/runtimes/cursor.json

@@ -0,0 +1,75 @@
+{
+  "id": "cursor",
+  "label": "Cursor",
+  "docs": "https://cursor.com/docs/cli/overview",
+  "detect": [
+    "~/.cursor"
+  ],
+  "notes": [
+    "Cursor commands are plain markdown with NO placeholder substitution: whatever the human",
+    "types after the command name is appended to the prompt. The adapter therefore explains the",
+    "argument placeholder in the preamble rather than rewriting it to a token.",
+    "Subagents are markdown + frontmatter, and `readonly: true` is a real tool restriction \u2014",
+    "the review agent gets it. Cursor also reads .claude/agents and .codex/agents.",
+    "Hooks use Cursor's own envelope ({\"permission\": \u2026}), not Claude's.",
+    "Model pins are NOT carried across: the profile names Anthropic aliases (sonnet/haiku), which are meaningless here and would either error or be silently ignored. Agents and commands inherit this runtime's own model selection instead."
+  ],
+  "scopes": {
+    "global": {
+      "root": "~/.cursor",
+      "core": "~/.cohorte/cursor",
+      "commands": "~/.cursor/commands",
+      "agents": "~/.cursor/agents",
+      "hooks": "~/.cohorte/cursor/hooks",
+      "hooks_config": "~/.cursor/hooks.json",
+      "workflows": null,
+      "settings": null
+    },
+    "project": {
+      "root": ".cursor",
+      "core": ".cohorte/cursor",
+      "commands": ".cursor/commands",
+      "agents": ".cursor/agents",
+      "hooks": ".cohorte/cursor/hooks",
+      "hooks_config": ".cursor/hooks.json",
+      "workflows": null,
+      "settings": null
+    }
+  },
+  "exclude_commands": [],
+  "command": {
+    "format": "md",
+    "ext": ".md",
+    "frontmatter": [],
+    "args": null,
+    "args_note": "the text you typed after the command name",
+    "invoke": "/<name>"
+  },
+  "agent": {
+    "format": "md",
+    "ext": ".md",
+    "frontmatter": [
+      "name",
+      "description"
+    ],
+    "readonly_key": "readonly",
+    "readonly_value": "true",
+    "dispatch": "invoke it as /<name> <brief>, or name it in the prompt; several run in parallel",
+    "address": "/<name>"
+  },
+  "hook": {
+    "format": "cursor",
+    "event": "beforeShellExecution",
+    "supports_ask": true,
+    "config_shape": "json"
+  },
+  "capabilities": {
+    "subagents": true,
+    "hooks": true,
+    "workflows": false,
+    "mcp": true,
+    "tool_restriction": true
+  },
+  "memory": "AGENTS.md",
+  "headless": "cursor-agent -p"
+}

package/core/runtimes/gemini.json

@@ -0,0 +1,75 @@
+{
+  "id": "gemini",
+  "label": "Gemini CLI",
+  "docs": "https://geminicli.com/docs/",
+  "detect": [
+    "~/.gemini"
+  ],
+  "notes": [
+    "Commands are TOML, not markdown: the whole prompt body becomes the `prompt` key, and the",
+    "argument placeholder is {{args}}. Sub-directories namespace with ':'.",
+    "Subagents ARE markdown + frontmatter (.gemini/agents), and are exposed to the main agent as",
+    "a tool of the same name; @agent-name forces one. They cannot call other subagents.",
+    "Hooks live in settings.json under `hooks`, event `BeforeTool`, matched on the tool name",
+    "(run_shell_command). The envelope is {\"decision\": \"deny\", \"reason\": \u2026} with no ask tier.",
+    "Model pins are NOT carried across: the profile names Anthropic aliases (sonnet/haiku), which are meaningless here and would either error or be silently ignored. Agents and commands inherit this runtime's own model selection instead."
+  ],
+  "scopes": {
+    "global": {
+      "root": "~/.gemini",
+      "core": "~/.cohorte/gemini",
+      "commands": "~/.gemini/commands",
+      "agents": "~/.gemini/agents",
+      "hooks": "~/.cohorte/gemini/hooks",
+      "hooks_config": "~/.gemini/settings.json",
+      "workflows": null,
+      "settings": "~/.gemini/settings.json"
+    },
+    "project": {
+      "root": ".gemini",
+      "core": ".cohorte/gemini",
+      "commands": ".gemini/commands",
+      "agents": ".gemini/agents",
+      "hooks": ".cohorte/gemini/hooks",
+      "hooks_config": ".gemini/settings.json",
+      "workflows": null,
+      "settings": ".gemini/settings.json"
+    }
+  },
+  "exclude_commands": [],
+  "command": {
+    "format": "toml",
+    "ext": ".toml",
+    "frontmatter": [
+      "description"
+    ],
+    "args": "{{args}}",
+    "invoke": "/<name>"
+  },
+  "agent": {
+    "format": "md",
+    "ext": ".md",
+    "frontmatter": [
+      "name",
+      "description"
+    ],
+    "dispatch": "the subagent is exposed as a tool of the same name; @<name> forces it",
+    "address": "@<name>"
+  },
+  "hook": {
+    "format": "gemini",
+    "event": "BeforeTool",
+    "matcher": "run_shell_command",
+    "supports_ask": false,
+    "config_shape": "settings"
+  },
+  "capabilities": {
+    "subagents": true,
+    "hooks": true,
+    "workflows": false,
+    "mcp": true,
+    "tool_restriction": false
+  },
+  "memory": "GEMINI.md",
+  "headless": "gemini -p"
+}

package/core/runtimes/opencode.json

@@ -0,0 +1,72 @@
+{
+  "id": "opencode",
+  "label": "OpenCode",
+  "docs": "https://opencode.ai/docs/cli/",
+  "detect": [
+    "~/.config/opencode",
+    "~/.opencode"
+  ],
+  "notes": [
+    "Markdown agents in agents/ with `mode: subagent`, addressed with @<name>.",
+    "The one runtime here with NO hook mechanism \u2014 extension is via plugins (.opencode/plugin/*.js),",
+    "which is a different contract from a blocking PreToolUse hook. The gate therefore runs in",
+    "explicit --check mode, which is advisory by construction.",
+    "`opencode run` is the headless primitive; --agent selects an agent.",
+    "Model pins are NOT carried across: the profile names Anthropic aliases (sonnet/haiku), which are meaningless here and would either error or be silently ignored. Agents and commands inherit this runtime's own model selection instead."
+  ],
+  "scopes": {
+    "global": {
+      "root": "~/.config/opencode",
+      "core": "~/.cohorte/opencode",
+      "commands": "~/.config/opencode/commands",
+      "agents": "~/.config/opencode/agents",
+      "hooks": null,
+      "workflows": null,
+      "settings": null
+    },
+    "project": {
+      "root": ".opencode",
+      "core": ".cohorte/opencode",
+      "commands": ".opencode/commands",
+      "agents": ".opencode/agents",
+      "hooks": null,
+      "workflows": null,
+      "settings": null
+    }
+  },
+  "exclude_commands": [],
+  "command": {
+    "format": "md",
+    "ext": ".md",
+    "frontmatter": [
+      "description",
+      "agent",
+      "subtask"
+    ],
+    "args": "$ARGUMENTS",
+    "invoke": "/<name>"
+  },
+  "agent": {
+    "format": "md",
+    "frontmatter": [
+      "description",
+      "mode"
+    ],
+    "defaults": {
+      "mode": "subagent"
+    },
+    "dispatch": "address the subagent with @<name> and give it the full brief in one message",
+    "address": "@<name>",
+    "ext": ".md"
+  },
+  "capabilities": {
+    "subagents": true,
+    "hooks": false,
+    "workflows": false,
+    "mcp": true,
+    "tool_restriction": false
+  },
+  "memory": "AGENTS.md",
+  "headless": "opencode run",
+  "hook": null
+}

package/core/templates/patch.template.md

@@ -0,0 +1,86 @@
+---
+feature_id: patch-<slug>
+kind: patch # a bug fix, not a feature — /cohorte-build skips contract authoring, /cohorte-ship commits `fix(…)`
+title: <one line: the bug, from the user's side>
+status: draft # draft → frozen → in-progress → in-review → shipped · blocked (see SCHEMA.md §Spec status)
+severity: <critical | major | minor> # drives nothing mechanical; it is what the human triages on
+branch: <patch_branch_prefix><feature_id>
+created: <YYYY-MM-DD>
+reviewed_base: # merge-base sha at the last SHIP verdict — freshness-gate anchor (written by /cohorte-review)
+reviewed_digest: # sha256 (16 hex) of the reviewed source diff vs reviewed_base, specs excluded — /cohorte-ship re-checks
+design_files: [] # omit unless the fix is itself visual
+---
+
+# <one line: the bug, from the user's side>
+
+## 1. Symptom & repro
+
+> What the user sees, and the shortest deterministic path to see it. A repro nobody can run is a
+> hypothesis, not a bug — say so here rather than pretending otherwise.
+
+- **Observed:** …
+- **Expected:** …
+- **Repro:** 1. … 2. … 3. …
+- **Since / trigger:** <version, commit, or "unknown">
+
+## 2. Impact
+
+> Who is affected, how often, and whether there is a workaround. This is what justifies the patch
+> jumping the feature queue — one or two lines.
+
+## 3. Cause
+
+> Confirmed or hypothesis — label which. Name the `file:line` if you have it. If the cause is
+> unknown at freeze, say so: the implementer's first job is then to find it, and the review will
+> check that the stated cause matches the diff.
+
+## 4. Regression test (red first)
+
+> The heart of a patch spec — it replaces §5 CONTRACT as the thing the diff is checked against.
+> Name the test file and what it asserts. It must fail on the current code and pass after the fix.
+
+- **Test:** `<path/to/test>` · asserts: …
+- **Fails today because:** …
+
+## 5. Contract delta
+
+> Usually `none`. A fix that *changes* an existing contract entry describes the change here and
+> `/cohorte-build` propagates it to every surface that names it. A fix that needs **new** contract
+> surface area is not a patch — stop and run `/cohorte-spec` instead.
+
+`none`
+
+## 6. Surface tasks
+
+> One `###` subsection per surface the fix touches — a patch may legitimately span several (an
+> unvalidated field on the API *and* the form that sends it). Each TDD: the §4 test first.
+
+### <surface.key>
+
+- …
+
+## 7. Out of scope
+
+> The adjacent things this patch deliberately does NOT fix. This is the section that keeps a bug fix
+> from turning into a refactor — the reviewer reads it before flagging what you left alone. Real but
+> out-of-scope findings belong in `specs/refactor-backlog.md`, not in this diff.
+
+- …
+
+## 9. Acceptance criteria / DoD
+
+> §9, not §8 — the number is load-bearing, so don't renumber it. `review.md` and
+> `implementer.template.md` both name "contract §5, acceptance §9" verbatim, so a patch spec pins
+> those two sections to the feature spec's numbers and just has no §8 (the feature spec has no §7 —
+> a gap in the sequence is normal here).
+
+- [ ] The §4 regression test exists, and failed before the fix
+- [ ] Each touched surface's tests (TDD) green
+- [ ] `PIPELINE.md` commands.lint · typecheck · test green
+- [ ] The repro in §1 no longer reproduces
+- [ ] Nothing outside §6's surfaces changed
+
+## Remediation
+
+> Filled by `/cohorte-fix` from a REVIEW REPORT; empty otherwise. Each item:
+> `[ ] <SEVERITY> · <file:line> · <spec-violation|quality|security> · <concrete fix>`

package/core/templates/spec.template.md

@@ -4,8 +4,6 @@ title: <Feature title>
 status: draft # draft → frozen → in-progress → in-review → shipped · blocked (see SCHEMA.md §Spec status)
 branch: <feature_branch_prefix><slug>
 created: <YYYY-MM-DD>
-loop_pass: 0 # /cohorte-loop bookkeeping — the review pass it is on; 0 = no loop running. Written by the driver, not by hand
-loop_phase: # /cohorte-loop bookkeeping — build | review | fix | done. With loop_pass, this is what `--resume` reads back
 reviewed_base: # merge-base sha at the last SHIP verdict — freshness-gate anchor (written by /cohorte-review)
 reviewed_digest: # sha256 (16 hex) of the reviewed source diff vs reviewed_base, specs excluded — /cohorte-ship re-checks
 design_files: [] # design page links — full URLs of the form https://claude.ai/design/p/<projectId>?file=<file> (each carries its own project + page); blank until designed; omit if no UI
@@ -64,7 +62,7 @@ design_files: [] # design page links — full URLs of the form https://claude.ai
 
 ## 8. Design brief (the "spec return")
 
-> Only if the project has UI. Standalone; mirrors `.claude/templates/design-brief.md`.
+> Only if the project has UI. Standalone; mirrors `<core>/templates/design-brief.md`.
 
 - **Screens / views:** …
 - **Flows:** …

package/core/templates/steps/init-pipeline/01-detect-stack.md

@@ -37,7 +37,7 @@ Gather evidence, then summarize what you found. Look for:
   `graphify`? Is either already registered in this repo's `.mcp.json` or `claude mcp list`? (Feeds
   the retrieval question + Phase 4 wiring — default provider is `serena`.)
 - **VCS:** `git remote -v` → host + `owner/repo`; the default branch (`git symbolic-ref refs/remotes/origin/HEAD` or `git branch`).
-- **Existing `CLAUDE.md`** — read it; it may already state stack/conventions to fold in. **Existing
+- **Existing `<memory>`** — read it; it may already state stack/conventions to fold in. **Existing
   `PIPELINE.md`** — if present, this is a re-run: load it as the starting draft and only reconcile deltas.
 
 Print a compact **Detection Report**: layout, surfaces (with framework + commands), contract, release

package/core/templates/steps/init-pipeline/02-interview-gaps.md

@@ -47,19 +47,9 @@ Prefer sensible defaults from Phase 1 as the first (Recommended) option in each
 
 - **Kanban** (optional) — mirror this project's pipeline (`/cohorte-brainstorm`…`/cohorte-ship`) onto an Obsidian
   Kanban board? If the human says yes: confirm the shared vault path (`obsidian.vault_path` in
-  `~/.claude/cohorte.config.yaml`; ask if empty) and the board's location inside it (default
+  `<config>`; ask if empty) and the board's location inside it (default
   `<ProjectName>/Tasks.md`). Phase 4 creates the board and records the link. Default: no.
 
 > The **kanban** link is user-scoped (it points at a personal vault, so it never goes in the committed
 > `PIPELINE.md`), but IS wired here because it is per-project — see Phase 4.
 
-- **Telemetry** (optional, machine-scoped — SKIP entirely if `~/.claude/cohorte.config.yaml` already
-  has a `telemetry:` block with a `consent_date`, i.e. the human already answered on this machine).
-  Ask ONE opt-in question, stating exactly: _"Share anonymous usage stats with the cohorte project?
-  One ping per pipeline phase, `/cohorte-brainstorm` through `/cohorte-ship`: core version, OS, phase name, duration,
-  per-surface result counts, and a hash of the feature id — never repo names, paths, code, or IPs.
-  Setup and maintenance commands never ping. Off by default; withdraw anytime
-  (`telemetry.enabled: false`); erase your history anytime (SCHEMA.md §Telemetry). Default: No."_
-  On **yes**: in the global config set `telemetry.enabled: true`, mint `install_id` (`uuidgen`,
-  lowercase), set `consent_date` (ISO date). On **no**: set `enabled: false` + `consent_date` (so
-  no future command re-asks). Never touch `endpoint` — it ships with the template.

package/core/templates/steps/init-pipeline/04-write-render.md

@@ -3,11 +3,11 @@
 ### Phase 4 — Write & render (after go-ahead)
 
 1. **Write `PIPELINE.md`** at the repo root (source: the installer's `pipeline/PIPELINE.template.md`).
-2. **Wire it into `CLAUDE.md`:** if `CLAUDE.md` exists, ensure it references the profile (add a line
+2. **Wire it into `<memory>`:** if `<memory>` exists, ensure it references the profile (add a line
    near the top: `> Project profile & pipeline facts: **@PIPELINE.md**`). If not, create a minimal
-   `CLAUDE.md` with that reference + a one-paragraph project intro.
+   `<memory>` with that reference + a one-paragraph project intro.
 3. **Render one agent per surface** — for each surface, follow SCHEMA.md §"Rendering / reconciling a
-   surface agent" (steps 2–3): render `.claude/agents/<agent>.md` from the installer's
+   surface agent" (steps 2–3): render `<agents>/<agent>.md` from the installer's
    `pipeline/implementer.template.md`, substituting `<SURFACE_AGENT>`, `<SURFACE_LABEL>`, `<SURFACE_PATH>`,
    `<SURFACE_TOOLS>`, `<SURFACE_MODEL>`, `<PROJECT_NAME>`, `<SURFACE_CONVENTIONS>` (the surface's
    baked convention slice — §Shared + its `### Surface:` stanza + its §Testing lines from the
@@ -16,26 +16,24 @@
    only when `uses_design`).
    Leave the fixed agents as-is (generic, shipped by the installer): `review.md`, `release.md`,
    `profile-reader.md`.
-4. **Generate `.claude/gate-config.json`** from the `gate` block — copy all five keys verbatim:
+4. **Generate `<state>/gate-config.json`** from the `gate` block — copy all five keys verbatim:
    `{"deny": [...], "ask": [...], "ask_on_default_branch": [...], "default_branch": "<vcs.default_branch>",
    "preflight": {"enabled": <gate.preflight.enabled>, "agents": [...], "max_age_minutes": <n>}}`
    (profile has no `preflight` block ⇒ omit the key — the hook then skips the phase gate).
+<!-- cohorte:if hooks -->
 5. **Write `.claude/settings.json`** permissions (`ask`/`deny` lists mirroring the gate, **plus an
    `allow` list of the project's read-only / verification commands** so agents don't stall on
    permission prompts — including mid-workflow, where nobody is watching a prompt: the detected
    per-surface `test_cmd`/`lint_cmd`/`typecheck_cmd`/`build_cmd` **and their `*_quiet_cmd`
    variants** and repo-wide `commands.*` equivalents as `Bash(<cmd>:*)` rules, plus read-only git —
    `Bash(git status:*)`, `Bash(git diff:*)`, `Bash(git log:*)`, `Bash(git rev-parse:*)` — plus the
-   shipped pipeline scripts for BOTH cores (`Bash(.claude/pipeline/scripts/:*)` and
-   `Bash(~/.claude/pipeline/scripts/:*)` — preflight, kanban-move, telemetry-send) **plus the
-   `bash`-prefixed form the `/cohorte-loop` driver uses** (`Bash(bash .claude/pipeline/scripts/loop.sh:*)`
-   and `Bash(bash ~/.claude/pipeline/scripts/loop.sh:*)`) — those prefix rules match a command
-   *starting* with the path, so `bash <path>` needs its own entry or `/cohorte-loop` stalls on a permission
-   prompt at every launch, and the
+   shipped pipeline scripts (`Bash(<core>/pipeline/scripts/:*)` — preflight, kanban-move;
+   a prefix rule matches a command *starting* with that path, so a `bash <path>`
+   invocation would need its own entry), and the
    retrieval provider's MCP tools when wired (e.g. `mcp__serena`). Never allowlist anything matching
    a `gate.ask`/`gate.deny` pattern. Mention the human can widen it later with
    `/fewer-permission-prompts`) + the hooks, **conditioned on the install mode:**
-   - **bundled:** register the PreToolUse hook `.claude/hooks/gate.py` with matcher `Bash|Task`
+   - **bundled:** register the PreToolUse hook `<core>/hooks/gate.py` with matcher `Bash|Task`
      (Task is required — the preflight phase gate keys off Task dispatches; a `Bash`-only matcher
      leaves it dead) and the PostToolUse formatter (detected formatter). Before adding, drop any
      existing PreToolUse entry whose command ends in `gate.py` (here AND in `~/.claude/settings.json`
@@ -47,6 +45,14 @@
      registration serves every repo; you only supply this repo's `gate-config.json`. Still write the
      PostToolUse formatter hook + the permissions.
    Preserve any existing custom keys.
+<!-- cohorte:else -->
+5. **No permissions or hook file to write.** This runtime has neither a PreToolUse hook nor a
+   settings.json permission model the pipeline can generate, so the gate is enforced by the
+   commands calling `<core>/hooks/gate.py --check` at the points the profile marks gated. That
+   means `<state>/gate-config.json` (step 4) is not decoration here — it is the ONLY place the
+   deny/ask patterns live, so fill it from the profile exactly and do not skip it. If this repo is
+   also driven from Claude Code, that install's hook reads the same file; nothing to duplicate.
+<!-- cohorte:endif -->
 6. **Wire the retrieval provider** (skip if `retrieval.provider: none`):
    - **serena:** if the `serena` CLI is missing, have the human install it (`uv tool install -p 3.13
      serena-agent`) — or set the provider to `none` if they decline, and say `/cohorte-update-pipeline` can wire
@@ -74,14 +80,14 @@
    slug, DB pattern, port bases, compose file, branch prefix, install/dev/migrate commands, per-surface
    env stanzas). `chmod +x` them. If isolation is disabled, skip and note features build in the main checkout.
 8. **Ensure `specs/_template.md`** exists (copy from the installer's `templates/spec.template.md` if missing).
-9. **Write the pointer** `.claude/pipeline.json` (committed — this is how a teammate who clones the repo
+9. **Write the pointer** `<state>/pipeline.json` (committed — this is how a teammate who clones the repo
    knows which core to install):
    `{ "pipeline": "cohorte", "mode": "<bundled|global>", "core_version": "<contents of the
    installer's pipeline/VERSION>", "install": "<per mode: bundled ⇒ \"npx cohorte install\"
    note that the core is committed under .claude/; global ⇒ \"npx cohorte install --global\"
    (or, without npm: curl -fsSL https://raw.githubusercontent.com/TheBidouilleAgency/cohorte/main/install.sh | sh -s -- --global;
    Windows: install.ps1 -Global from the same repo)> " }`.
-   In **global** mode also add, near the top of `CLAUDE.md`, a one-liner:
+   In **global** mode also add, near the top of `<memory>`, a one-liner:
    `> Pipeline: global core — run the installer above if /cohorte-brainstorm etc. are missing.`
 10. **CI workflow** (if `vcs.host: github` and no existing workflow already runs the profile's
     checks): with the human's go-ahead, generate `.github/workflows/pipeline-ci.yml` — on
@@ -89,18 +95,18 @@
     `commands.install`, then `commands.lint` · `commands.typecheck` · `commands.test` (+ per-surface
     `build_cmd`s that are non-empty). Derive the setup steps from the detected stack — mirror what a
     sibling workflow does if one exists. `/cohorte-ship` watches these checks before the merge.
-11. **Metrics sink, report buffer & preflight stamp:** add `.claude/pipeline-metrics.jsonl` to
+11. **Metrics sink, report buffer & preflight stamp:** add `<state>/pipeline-metrics.jsonl` to
     `.gitignore` — `/cohorte-build`, `/cohorte-review` and `/cohorte-fix` append per-dispatch evidence
     there (SCHEMA §Specialization reads it).
     Also add `specs/reports/` — `/cohorte-review` stages its last report there so a `/cohorte-fix` (or
     `/cohorte-spec` Mode B) survives a `/clear`; it's a derived buffer, not a versioned artifact.
-    And `.claude/preflight.ok` — a local, per-checkout freshness stamp. Versioning it breaks the phase
+    And `<state>/preflight.ok` — a local, per-checkout freshness stamp. Versioning it breaks the phase
     gate for good (a committed stamp describes the tree *before* its own commit, and it rides into every
-    new worktree as a green nobody earned). If it is already tracked: `git rm --cached .claude/preflight.ok`.
+    new worktree as a green nobody earned). If it is already tracked: `git rm --cached <state>/preflight.ok`.
 12. **Design system:** if `design.enabled` with a snapshot dir, note that `/cohorte-align-ds` is active; else the
     `/cohorte-align-ds` command will no-op with a clear message.
 13. **Kanban** (only if the human opted in at Phase 2): wire it per SCHEMA.md §Kanban, writing into the
-    **global** `~/.claude/cohorte.config.yaml` (never into this repo — the board points at a
+    **global** `<config>` (never into this repo — the board points at a
     personal vault). Create the file from `pipeline/cohorte.config.template.yaml` if absent; set
     `kanban.enabled: true` and `obsidian.vault_path` if it was empty. Add a `kanban.boards[<PIPELINE
     name>]` entry with `board: <folder>/Tasks.md`. Then **create the board file**

package/core/templates/steps/init-pipeline/05-report.md

@@ -3,7 +3,7 @@
 ### Phase 5 — Report
 
 Print: the install mode (bundled core under `.claude/` vs global core in `~/.claude/` + the committed
-`.claude/pipeline.json` pointer), the files written/rendered, the surface→agent mapping, and the
+`<state>/pipeline.json` pointer), the files written/rendered, the surface→agent mapping, and the
 tailored workflow line, e.g.
 `/cohorte-brainstorm → /cohorte-spec → (design) → /cohorte-build <id> → test → /cohorte-review → /cohorte-ship`. Tell the human to sanity-check
 `PIPELINE.md`, commit it, and run `/cohorte-brainstorm` to start a feature. Note that this was the one-time

package/core/workflows/review.js

@@ -323,12 +323,10 @@ const staging = await agent(
   `1. Write EXACTLY this content to specs/reports/${feature}.md (overwrite):\n<<<REPORT\n${reportBody}\nREPORT\n` +
   `2. Append one line to $(dirname "$(git rev-parse --git-common-dir)")/.claude/pipeline-metrics.jsonl: ` +
   `{"ts":"<ISO now>","feature":"${feature}","phase":"review","seconds":0,"surfaces":{${results.map(r => `"${r.key}":"${verdict}:${r.kept.length}"`).join(',')}}}\n` +
-  `3. Chain the opt-in usage ping: <core>/pipeline/scripts/telemetry-send.sh review "${feature}" 0 "${verdict}:${kept.length}" || true ` +
-  '(<core> = .claude if .claude/pipeline/scripts/telemetry-send.sh exists, else ~/.claude; script on neither ⇒ skip the ping).\n' +
   // Deferred findings must land in the backlog on EVERY verdict — parked only on a
   // SHIP is parked nowhere the rest of the time, which is the leak this closes.
   (deferredAll.length
-    ? `3b. Route the deferred findings to specs/refactor-backlog.md (create it if absent): for each line below, ` +
+    ? `3. Route the deferred findings to specs/refactor-backlog.md (create it if absent): for each line below, ` +
       `append it under the \`## <domain>\` heading named in its prefix (create that heading if absent) — with \`>>\`, ` +
       `never by rewriting the file, and skip any whose file path + first words already appear there (grep -F first, ` +
       `they may be left from a prior round or an /cohorte-audit):\n` +