3 Commits

Include renames

Author	SHA1	Message	Date
dongarandClaude Opus 5.5	a921b73d34	M4.4: an unreachable build VM blocks its projects until it's back (#137) ... M4.3's block, with new triggers and a way out. A VM out of reach at the check before a run, in a run (which ends there: the driver, a toolchain step and a requested step), or while preparing the workspace blocks every project on it; the item stays ready, waiting on no one. On the intake round it is tried again every tuning.build_vm.retry_s (300), and once it answers it must still answer settle_s (180) later; then the work a lost run left there is parked (pushed), the VM unblocked, and that said once. A changed host key, at the check or on a retry, blocks the VM too, until the operator's `vm ready`, which trusts the new key: `trust new host key` is retired, and the message says it's a key problem that may be an impersonation. Questions are answered while a VM is blocked, without it. Starting the agent with a VM down no longer fails. The walk breaks the VM's SSH, now or partway through a run, and checks that no model works on a VM that is down; loop.qnt models the VM going and coming back (unblocked_only_when_up). Together they found: a lost run's work set aside by the next item there; a question left behind a block; a lost VM swallowed while the toolchain step checked or recorded it; and a remark waiting to be answered that outlived its PR's merge. All fixed. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01J5Utyfzw7gF7UhjRDEtjTk	2026-10-08 21:06:05 +00:00
dongarandClaude Opus 5.5	0064ec7696	Fixes from the rest of the live session ... - A near miss for abandon ("abort", "cancel", "drop it", ...) in an item's thread is asked about, and changes nothing. - The driver is told only the operator stops or closes an item, so it doesn't claim to have done either. - An issue assigned again after its item closed starts a new item that notes the one before (Gitea's timeline gives the assignment time); item_for_issue returns the latest item. - Abandoning an issue Gitea won't close because of open dependencies says so, naming them. - An agreed item isn't offered restate. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01PPQ14L3LikyefCMFBqEbKE	2026-10-08 02:16:51 +00:00
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