2 Commits

Include renames

Author	SHA1	Message	Date
dongarandClaude Opus 5.5	659915d309	Fixes from the first live session of the new loop ... Found live on 2026-10-07 (bring-up on nisse-testing-operator/nisse-bringup, Opus as driver): - The driver's prose nudge went into the system prompt, so the retry ended on the model's own reply. Opus 5.5 refuses that ("does not support assistant message prefill. The conversation must end with a user message"). The nudge is now a harness fact in the conversation. The delegation harness's prose path did the same and is fixed likewise. - A helper's first request ended with its own delegation_started event, rendered as an assistant message: every delegation would have failed on Opus. The helper now sees it as the harness handing over its task. - model_contract checks that every request ends on the user's side, so scripted tests catch this from now on (each fix is mutation-checked). - `status` (and `details`) in an item's thread were taken as replies: they woke the driver and cancelled a bug's countdown. They now answer at once and change nothing. - The driver had no way to answer a remark without changing the item, so it answered in prose. Every run woken by a message (or a review comment) now offers `reply`, which answers where asked and returns to the very wait that was interrupted. Also: scripts/bringup-repo.sh makes the bring-up's test repository (make_repo/delete_repo, split out of fresh_repo), and made repositories get the agent's labels (bug, discuss, design). Tests: test_loop_live_fixes.py (one per finding); the walk sends `status` into threads (status_changes_nothing) and its scripted driver sometimes answers remarks with reply. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01PPQ14L3LikyefCMFBqEbKE	2026-10-08 00:02:50 +00:00
dongarandClaude Opus 5.5	37965aefca	Fix the run-breaking tool-result order; e2e test runs the slice (M2.1, PR D) ... The first live run of the new loop's e2e test found that a fact recorded while start_milestone was in flight landed between the tool call and its result; both API formats reject that, so every later request in the run failed. Views now keep each result right after its call. Scripted test models check the APIs' ordering rules, so this can't pass unit tests again. The e2e tests no longer depend on the sandbox's history: each run asks for a uniquely named function and works against a base branch of its own, deleted afterwards. The review step asks for a change that can't already be there. The scripted operator gives up after five fruitless answers, and each run keeps its state store for inspection. The driver's prompt says review fixes stay in the current milestone. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01PPQ14L3LikyefCMFBqEbKE	2026-10-03 15:11:06 +00:00