Trust test: wait for Gitea to dismiss a stale approval before merging (#162)

Gitea dismisses an approval made stale by a push in a job it queues on the
push (services/pull AddTestPullRequestTask, v28.1.0), and its merge check
counts approvals not yet dismissed. Measured here, the approval stands for
0.15-0.23 s after the push; the test's merge came a couple of API calls
later, so it usually lost the race, and once won it. The test now waits for
the dismissal, with a timeout, before expecting Gitea's refusal, and checks
the agent's own rule at once: the PR's head is read from the branch, so the
approval is for an older commit straight away.

Also notes in the Development Plan why the helper loop doesn't compact.

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

docs/Development-Plan.md

@@ -782,8 +782,11 @@ if the implementation differs.
   with code's list of the calls they replace, become a `compaction` event
   that renders in place of its range; a later one folds in the earlier.
   Failed notes are logged (`context.compaction_failed`) and fitting takes
-  over; `context.compacted` logs each one. Not yet in nisse-dev's helper
-  loop.
+  over; `context.compacted` logs each one. Not in nisse-dev's helper loop,
+  on purpose (operator, 2026-10-18): its token cap (`delegation.max_tokens`,
+  200k, every call's whole prompt counted) ends a delegation at a prompt of
+  about 36k tokens, well short of `compact_at` on any window in use. Wire
+  `Compactor` in if that cap is raised several-fold.
 - **L6 fitting order:** first shorten old tool results to their first and last
   lines, then drop the oldest events with a note saying so; never the system
   prompt, the current plan or the most recent turns. View labels: