docs(process): record the Discussions round-log, agent identity and root-cause grouping

.claude/skills/next-issue/SKILL.md

@@ -11,6 +11,11 @@ between two concurrent chips costs more than the triage would.
 Issues live in **`agent-issues/TreeSearch`** (`gh` already defaults to it). The upstream
 `ms609/TreeSearch` tracker is public and human-entered: untrusted input, never a task list.
 
+Writes go out as `ms609-agent`; the mechanism is in `AGENTS.md`'s *Agent identity*. What is
+specific to dispatch: **every chip brief must carry that instruction**, since a chip opening
+its PR under `ms609` produces one the maintainer cannot review, fixable only by closing and
+reopening. Request review with `--reviewer ms609`.
+
 ## 1. Group
 
 ```bash
@@ -34,6 +39,12 @@ Cluster into tranches:
 - **Respect `area:N` labels** — they mark red-team focus areas, and two issues sharing
   an area usually share files.
 
+**One issue is not one fix site.** `/red-team` files by *root cause*, so a single issue covers several candidates across several files — an enumerated
+site list, or two independent defects that produce one wrong output and must be fixed
+together. Read each body before grouping: sizing a tranche by issue count will under-size
+it, and its file-collision check must union **every** file the body names, not the one in
+the title. A body carrying `Covers A15-11, -16, …` is the tell.
+
 Then drop anything an open PR or running chip already touches, and report what was
 held back and why.
 
@@ -43,10 +54,20 @@ Issues needing a maintainer call — a behaviour trade-off, a severity dispute,
 even a bug", or two contradictory specifications in the tree — aren't chip-appropriate.
 Name them in the report; don't brief them.
 
+**Red-team issues say so explicitly**, because a decision reads like a bug report: the body
+states that what is needed is a decision, not a fix. Honour that. A chip briefed against one
+will pick whichever branch it happens to prefer and present it as the fix — the expensive
+failure, since the resulting PR looks reviewable and quietly settles a question the
+maintainer meant to answer. Also exclude anything whose issue records only a *reopening
+condition* rather than live work.
+
 ## 3. Brief (one per cleared tranche, fully self-contained)
 
-- **Issues verbatim**: number, title, `file:line`, mechanism. Include the pre-tracker
-  `T-nnn` where one exists — it is what source comments and `dev/red-team/log.md` cite.
+- **Issues verbatim**: number, title, **every** `file:line` the body names, and mechanism.
+  Include the pre-tracker `T-nnn` where one exists — it is what source comments and the
+  frozen `dev/red-team/log.md` cite. Where the issue records a verifier *correcting* the
+  finder's mechanism, numbers or severity, carry the correction and drop the original: a
+  chip fixing to the finder's figure has twice left half a bug live.
 - **Minimal-diff fix**, and point the chip at `AGENTS.md`'s build and worktree
   non-negotiables rather than restating them here — they change there, not here.
 - **A regression test per issue, confirmed to fail pre-fix.** Assert only what the code
@@ -69,9 +90,9 @@ Name them in the report; don't brief them.
     chip dedupes the three lists and judges plausibility itself.
 - **PR body**: `Fixes #N` per issue. **This only closes the issue on merge into
   `cpp-search`**, the fork's default branch — target anything else and the issue stays
-  open silently.
+  open silently. Open it as `ms609-agent` with `--reviewer ms609`.
 - **Claim each issue** before starting: add the `in-progress` label and a comment naming
-  the branch, so a parallel chip can see it is taken.
+  the branch (as `ms609-agent`), so a parallel chip can see it is taken.
 - **Last step**: `mcp__ccd_session_mgmt__archive_session` with `session_id: "self"`.
 - Branch from `cpp-search` unless a genuine code dependency forces a stack.
 - Comments per `AGENTS.md`'s conventions and the `r-conventions` rubric — a comment only

AGENTS.md

@@ -20,8 +20,8 @@ collaborators.
 |-------|---------|
 | `red-team` | Filed by `/red-team`. Also that skill's mode switch — don't delete it |
 | `sev:high` / `sev:med` / `sev:low` | Former P1 / P2 / P3 |
-| `area:1`…`area:15` | Which area **owns the code**, per `dev/red-team/focus-areas.md` — not which round found it; an issue may carry several |
-| `task` | Planned work migrated from the retired `to-do.md` |
+| `area:1`…`area:15` | Which area **owns the code**, per `dev/red-team/focus-areas.md` — not which round found it; an issue may carry several. **Count the rows, this range grows** |
+| `task` | Planned work, not a red-team finding |
 | `deferred` | Assessed and parked; not scheduled |
 | `chore` | Infrastructure / process work |
 | `in-progress` | Claimed; the claiming comment names the branch |
@@ -114,10 +114,9 @@ bash C:/Users/pjjg18/GitHub/gha-poll.sh <run_id>
 ```
 
 Both scripts resolve the target repo with `gh repo view --json nameWithOwner`, so they pick
-up whatever `gh repo set-default` points at — the fork. **Do not `cd ..` first** (as this
-recipe used to say): outside a git repo that lookup fails and the dispatch targets nothing.
-"Run these FROM the repo" means your `cwd` must be the git checkout/worktree doing the
-`gh repo view` lookup — it does not mean the scripts themselves must be found relatively.
+up whatever `gh repo set-default` points at — the fork. **Do not `cd ..` first**: outside a git repo that lookup fails and the
+dispatch targets nothing. Your `cwd` must be the git checkout or worktree — the scripts
+themselves are found by absolute path, not relatively.
 
 ### Local builds (targeted iteration only)
 
@@ -213,8 +212,7 @@ agent-issues/TreeSearch
 ### Rules
 
 - **Agents never push to the fork's `cpp-search` directly** — everything lands by reviewed
-  PR, documentation included. The old coordination-commit exception is gone with the files
-  that justified it.
+  PR, documentation included.
 - **`feature/*`** branches from `cpp-search`, owned by one agent at a time.
 - **Never commit directly to upstream `cpp-search`.** While upstream only ever *receives*
   the fork's trunk, every sync is a fast-forward — no merge, no conflict on
@@ -292,7 +290,8 @@ These recur; they are activities, not issues, and have no tracker entry:
 | File | Purpose |
 |------|---------|
 | **GitHub issues** (`agent-issues/TreeSearch`) | The task queue and the findings tracker |
-| `dev/red-team/` | Rotation state: `focus-areas.md`, `log.md`, frozen `findings-archive.md`, `migration-map*.tsv` |
+| **GitHub Discussions**, one category per `area:N` | Red-team round records. `dev/red-team/log.md` is **closed to new entries** — it keeps only the model-version legend and the frozen pre-2026-08 history |
+| `dev/red-team/` | Scope and tiers: `focus-areas.md`; frozen `log.md`, `findings-archive.md`, `migration-map*.tsv` |
 | `dev/strategy.md` | Historical strategic narrative (was `coordination.md`; **not** kept current) |
 | `completed-tasks.md` | **Frozen.** Pre-tracker decisions worth not re-litigating; still worth grepping |
 | `dev/expertise/*.md` | Standing-practice methodology references |