Threads, commands and labels on the new loop (M2.3)

- Commands that name their item ("go #14", "abandon #14", "stop #14")
  apply to it wherever they're said; go, approve and abandon alone at top
  level are asked about (L5). stop is never taken as an answer.
- A plain-language reply to a restatement is read by GoAheadReader, one
  model call that agrees only on a clear yes; questions never reach it. The
  agent says "taking that as a go-ahead on rev-N" first, bound to the
  revision on screen at arrival (L3, L5, D1).
- Labels steer (D1): `bug` goes ahead after tuning.loop.bug_grace_s
  (default 600 s) unless the operator replies; `discuss` isn't offered
  restate until the operator has spoken; `bug`, `discuss` and `design` add
  to the driver's instructions. A restatement asks no questions.

Tests: label and command unit tests, the property walk with labelled
issues, plain yeses, named gos and time passing (grace_only_unanswered,
discuss_talks_first), and e2e tests for a bug proceeding after its grace
period and a plain-language go-ahead.

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01PPQ14L3LikyefCMFBqEbKE

docs/Development-Plan.md

@@ -27,7 +27,7 @@ Only `nisse-dev` has real code; `nisse-core` and `nisse-ops` are placeholders.
 | **L2** Agent loop | partial | `control.py`, a fixed state machine with no-stranding, `stop`, `abandon`. Replaced by the new loop (Phase 2) |
 | **L3** Authority | partial | Revision binding and arrival stamping (`gates.py`); scope is still plan approval, not the issue and its conversation |
 | **L4** Classifier | none | |
-| **L5** Conversation | partial | Matrix transport, mentions, lenient commands; no threads, no question handling, little explanation |
+| **L5** Conversation | partial | Matrix transport, mentions, lenient commands; on the new loop, a thread per item, named and ambiguous commands, plain-language go-aheads (M2.3); little explanation |
 | **L6** Context | partial | Context fitting, per-role views and orchestrator facts (M1.2); no scope or agent memory |
 | **L7** Canonical log | partial | Work item and actor on every event, `fact` (M1.1, M1.2); no `classifier_verdict`, `knowledge_retrieved` |
 | **L8** Durability | mostly done | WAL store, intents, boot reconciliation, PR adoption, comment redelivery; to move onto the new loop |
@@ -36,7 +36,7 @@ Only `nisse-dev` has real code; `nisse-core` and `nisse-ops` are placeholders.
 | **L11** Injection | partial | Operator allowlists on every channel; no classifier |
 | **L12** Secrets, logging | partial | Structured state-change log; secrets in `.env`; no per-operation handout or redaction |
 | **L13** Execution | none | Tools run locally in the agent's process. The token leaks into the clone (#89) |
-| **D1–D2** Workflow | none | Plans posted to a Gitea issue and gated; no issue intake, labels, or documents in the repo |
+| **D1–D2** Workflow | partial | On the new loop: issue intake, restatement and go-ahead (M2.1), labels (M2.3); no documents in the repo |
 | **D3–D4** Workspace, git | partial | Idempotent publishing; no fresh workspace (#62), `git add -A` (#80) |
 | **D5** Review | partial | PR conversation comments only (#69), watch stall (#70) |
 | **D7–D8** Deployment, projects | none | Runs from a venv as a systemd unit on this box; one project in config |
@@ -154,9 +154,18 @@ dependencies, a closed PR handled (L1, D4). End-to-end: two issues and a depende
   and checks that parked work is never lost (every file an open item wrote is on
   the workspace or in the forge).
 
-**M2.3 Threads and labels.** *Pre-approved.* Routing by thread, ambiguous commands
-asked about (L5); `bug` grace periods, `discuss`, `design`; questions and
-plain-language go-aheads (D1). End-to-end: a bug and a feature, labelled and not.
+**M2.3 Threads and labels.** *Pre-approved.* **Done** (this PR). Routing by thread,
+ambiguous commands asked about (L5); `bug` grace periods, `discuss`, `design`;
+questions and plain-language go-aheads (D1). End-to-end: a bug and a feature,
+labelled and not.
+- Commands naming their item ("abandon #14") apply to it anywhere; `go`, `approve`
+  and `abandon` alone at top level are asked about. `stop` is never an answer.
+- A plain-language go-ahead is read by one model call (`GoAheadReader`, on the
+  driver's model until the classifier role, M2.6); questions never reach it.
+- `bug` waits `tuning.loop.bug_grace_s` (default 10 minutes) after its restatement;
+  any reply stops the countdown. `discuss` isn't offered `restate` until the
+  operator has spoken; `design` is steered by the driver's instructions.
+- Labels are read at intake; a label changed later is not picked up yet.
 
 **M2.4 Multi-milestone work and documents.** *Pre-approved.* Build plans in the
 repository, `ARCHITECTURE.md` kept current, waiting for merges between milestones

docs/Tuning-Guide.md

@@ -513,3 +513,16 @@ Later work that will add knobs, each with its own section here:
   model and a policy for what is safe to summarize.
 - **Benchmarking the other roles:** planner and delegate, with delegation
   turned back on for comparisons across frontier tiers.
+
+### `tuning.loop.bug_grace_s` — default 600
+
+How long the restatement of an issue labelled `bug` waits for a reply before
+the agent goes ahead on its own (architecture D1). Any reply in the item's
+thread stops the countdown, and `go` starts at once.
+
+- **Too low:** you can't read the restatement before the fix starts, so a
+  misread report costs a wasted milestone.
+- **Too high:** bugs wait as long as features, and the label buys nothing.
+- **Deciding:** about the time it takes you to notice a message and read it
+  when you're around. A wrong start costs only time, since the fix still comes
+  as a PR you review.