cohorte 1.1.0 → 1.1.1

package/CHANGELOG.md

@@ -3,6 +3,15 @@
 Entries are shown by `/update-pipeline` ("What's new") after a core refresh. Keep them short,
 user-facing, most recent first. One `## <version> — <YYYY-MM-DD>` section per release.
 
+## 1.1.1 — 2026-07-29
+
+- **Fix: pipeline metrics survive worktree teardown.** With `isolation.enabled` the lead session
+  runs inside the feature worktree, so metrics lines landed in the worktree's `.claude/` and were
+  deleted with it — defeating their purpose (cross-feature evidence for surface splits, dashboard
+  history). All phases now append to the **main checkout's** `.claude/pipeline-metrics.jsonl`,
+  resolved from anywhere via `git rev-parse --git-common-dir`; `/doctor` flags a stray metrics file
+  inside a worktree as a stale-core sign.
+
 ## 1.1.0 — 2026-07-29
 
 > **The token-economy release.** A full audit of the core (40 verified fixes) cuts the pipeline's

package/core/commands/build.md

@@ -93,8 +93,11 @@ tree. For each surface in `surfaces`:
 
 When all return, flag any contract mismatch or failing test from the handoffs; otherwise print one
 status line per surface (`<key> · tests pass/fail · <n> TODOs`) — do not restate handoff content.
-Append **ONE line for the batch** to `.claude/pipeline-metrics.jsonl` (create it if absent; it must
-be gitignored), computing the elapsed time in the same Bash call
+Append **ONE line for the batch** to the **main checkout's** `.claude/pipeline-metrics.jsonl` —
+NOT the worktree's, which dies at teardown while metrics must accumulate across features. Resolve
+it from anywhere: `$(dirname "$(git rev-parse --git-common-dir)")/.claude/pipeline-metrics.jsonl`
+(in the main checkout this resolves to itself). Create it if absent; it must be gitignored.
+Compute the elapsed time in the same Bash call
 (`echo "{...\"seconds\":$(($(date +%s)-<start epoch from §2>)),...}" >> …`):
 `{"ts":"<ISO date>","feature":"$ARGUMENTS","phase":"build","seconds":<wall-clock>,"surfaces":{"<key>":"ok|error",…}}`
 — this is the evidence SCHEMA.md §Specialization asks for before splitting a surface.

package/core/commands/doctor.md

@@ -55,7 +55,10 @@ fix only with the human's go-ahead (or hand them the command).
    against stale code ⇒ suggest rebasing it.
 7. **Specs & metrics.** Every `specs/*.md` front-matter `status` is a valid stage; `shipped` specs
    with a live worktree flagged (see 6). `.claude/pipeline-metrics.jsonl` and `specs/reports/` (the
-   `/review`·`/smoke` report buffer that lets a `/fix` survive a `/clear`) are gitignored.
+   `/review`·`/smoke` report buffer that lets a `/fix` survive a `/clear`) are gitignored. Metrics
+   belong to the **main checkout** — a `pipeline-metrics.jsonl` inside a live feature worktree is a
+   stale-core sign (its lines die at teardown) ⇒ suggest appending its lines to the main checkout's
+   file and deleting the stray.
 
 ## Report
 

package/core/commands/fix.md

@@ -60,7 +60,7 @@ When the agents return:
   re-reads each loop. Keep any round with ≥1 still-open `- [ ]` item fully expanded (§2's skip logic
   needs those checkboxes).
 - Print one status line per surface (`<key> · items fixed <n>/<m> · tests pass/fail`) — do not restate
-  handoff content — and append ONE metrics line for the batch to `.claude/pipeline-metrics.jsonl`
+  handoff content — and append ONE metrics line for the batch to `pipeline-metrics.jsonl`
   (see `/build` §4, `phase: "fix"`).
 - Tell the human: re-run `/smoke` if the failures were runtime ones, and `/review $ARGUMENTS` for the
   re-verdict — the re-review is what *verifies* the ticked items actually hold (a regression simply

package/core/commands/review.md

@@ -56,8 +56,8 @@ metrics line needs it.
 
 Merge the returned reports into **one** REVIEW REPORT (same template): findings concatenated and
 re-ordered by severity, counts summed, duplicates collapsed, verdict = the worst returned
-(`BLOCK` > `REVISE` > `SHIP`). Append ONE metrics line for the batch to `.claude/pipeline-metrics.jsonl`
-(gitignored): `{"ts":"<ISO>","feature":"$ARGUMENTS","phase":"review","seconds":<wall-clock>,"surfaces":{"<key>":"<verdict>:<finding count>",…}}`.
+(`BLOCK` > `REVISE` > `SHIP`). Append ONE metrics line for the batch to `pipeline-metrics.jsonl`
+(main-checkout path + rules in `/build` §4): `{"ts":"<ISO>","feature":"$ARGUMENTS","phase":"review","seconds":<wall-clock>,"surfaces":{"<key>":"<verdict>:<finding count>",…}}`.
 **Stage the full report to `specs/reports/$ARGUMENTS.md`** (overwrite) — a gitignored buffer so a
 `/fix` after a `/clear` can still read the findings; the `specs/reports/` subfolder is skipped by the
 non-recursive `specs/*.md` glob, so it's never mistaken for a spec (no phantom card, no bogus stage).

package/core/commands/smoke.md

@@ -33,7 +33,8 @@ human; that's expected.
 ## 3. Relay the verdict
 
 - Print the agent's return as-is (verdict + ❌ lines + report path) — it is already minimal.
-- Append ONE metrics line to `.claude/pipeline-metrics.jsonl` (see `/build` §4, `phase: "smoke"`).
+- Append ONE metrics line to `pipeline-metrics.jsonl` (main-checkout path + rules in `/build` §4,
+  `phase: "smoke"`).
 - **PASS** → tell the human to run `/review $ARGUMENTS`. **FAIL** → the failures are findings: feed
   them to `/fix $ARGUMENTS`, re-run `/smoke` after. Either way the report is on disk —
   **recommend a `/clear`** before the next command.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "cohorte",
-  "version": "1.1.0",
+  "version": "1.1.1",
   "description": "Portable, stack-agnostic multi-agent development pipeline for Claude Code — install the core, run /init-pipeline, and it adapts to your project's stack.",
   "bin": {
     "cohorte": "bin/cli.js"

package/profile/SCHEMA.md

@@ -155,10 +155,12 @@ the frozen contract as the only cross-surface channel**. So specialization means
 
 Coarse first, specialize on evidence: start with one `frontend` / `backend` surface each; split only a
 surface that's proven slow and cleanly separable. The evidence lives in
-`.claude/pipeline-metrics.jsonl` (gitignored) — one JSONL line per phase batch
+the **main checkout's** `.claude/pipeline-metrics.jsonl` (gitignored) — one JSONL line per phase batch
 (`ts`/`feature`/`phase`/`seconds`/`surfaces:{key: result}`), appended by `/build`, `/review`, `/fix`
-and `/smoke`. Read it before proposing a split: split the surface that actually dominates wall-clock,
-not the one that feels big.
+and `/smoke`. Always the main checkout, never the feature worktree (which dies at teardown while
+metrics must accumulate across features) — resolve from anywhere with
+`$(dirname "$(git rev-parse --git-common-dir)")/.claude/pipeline-metrics.jsonl`. Read it before
+proposing a split: split the surface that actually dominates wall-clock, not the one that feels big.
 
 ## Measuring cost — what's slow vs what's expensive