Conversation on the new loop (M2.7)

- Questions never change state (L5, #77): a message ending in "?" to a
  waiting project item starts a question run (reply and look-only tools,
  an instruction to change nothing), and the item goes back to the very
  wait it was in: a restatement up stays up and a go binds to it; the
  agent's own question stays open.
- Explanations: a restatement gives its reasons and the main alternative;
  a revision says what changed (restate(changed), sent back without it);
  a milestone's summary says what was done, verified and left open.
- Progress in prose (#42): the driver's and a helper's own words for a
  turn are posted, trimmed, at most once a minute per item; `details`
  shows the last tool calls; a message arriving mid-run is acknowledged at
  once ("Noted; ...").
- CI: the e2e job's comments and the plan no longer claim a newer push
  cancels the run it supersedes (Gitea here doesn't); the concurrency
  block goes.

Tests: conversation unit tests (questions in a go-ahead and an answer wait,
an unanswerable question, revisions, progress rate and trimming, details,
mid-run notes), the helper's progress, the walk asking questions in every
state with a questions_change_nothing property (routing questions the old
way fails 32 of 48 seeds), and an e2e question while a restatement is up.

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

.gitea/workflows/ci.yml

@@ -58,18 +58,15 @@ jobs:
   e2e:
     # The end-to-end suite (scripts/e2e.sh): the whole agent against real
     # services, every role on a local model, so it spends nothing but keeps
-    # the RTX 4090 busy for ~25 minutes. On PRs only, as its own job so the
-    # checks above report first; a newer push to the same PR cancels the
-    # run it supersedes. Locally, run only what you're writing (-k) or
-    # diagnosing (--lf). Only after the checks pass: a PR that's red already
-    # doesn't spend the GPU.
+    # the RTX 4090 busy for ~25 minutes. On PRs only, and only after the
+    # checks pass: a PR that's red already doesn't spend the GPU. There is
+    # one runner and Gitea doesn't honour cancel-in-progress, so a run a
+    # newer push supersedes holds the runner until it's cancelled by hand.
+    # Locally, run only what you're writing (-k) or diagnosing (--lf).
     if: github.event_name != 'push'
     needs: checks
     runs-on: ubuntu-latest
     timeout-minutes: 90
-    concurrency:
-      group: e2e-${{ github.head_ref || github.ref }}
-      cancel-in-progress: true
     steps:
       - uses: actions/checkout@v4