4 Commits

Include renames

Author	SHA1	Message	Date
dongarandClaude Opus 5.5	cceb30c729	The queue: parking, the operator's order, blocked items (M2.2) ... Several work items on the new loop (L1, D4): - Switching parks the item on the workspace: its work is committed and its branch pushed; resuming checks the item's branch back out. Branches of open items are never set aside by a fresh workspace. - Next item: the operator's "do #N next" first, otherwise the oldest. - Issues with open Gitea dependencies are blocked until they close, checked at intake and on every round; status shows blocked items and the line. Tests: queue unit tests, the property walk over several issues with dependencies and a new parked_work_safe property (it catches parking disabled), and an end-to-end test with two issues where B depends on A. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01PPQ14L3LikyefCMFBqEbKE	2026-10-04 13:34:09 +00:00
dongarandClaude Opus 5.5	651551aab4	Answer where asked, wait on a merge, and let the driver title PRs ... From the new loop's first live run (sandbox #255, PR #256): - A question asked on the PR is answered on the PR (an inline one quoted with its file and line, since the API can't reply in its thread), with a pointer in the item's Matrix thread; one asked in Matrix stays there. - wait_for_review: when a review needs no change, or only the operator's merge is left, the item waits on the merge instead of on an answer. - finish_milestone takes the PR's title from the driver. The e2e test's merge waits out Gitea's brief 'try again later' after a push. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01PPQ14L3LikyefCMFBqEbKE	2026-10-03 17:29:28 +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
dongarandClaude Opus 5.5	897181b0f4	Add the end-to-end test of the new loop's slice (M2.1, PR D part 2) ... From an issue the scripted operator files and assigns in Gitea, through the restatement, go-ahead, milestone and PR, a review comment answered with a pushed fix, to an approved and merged PR and a closed item and issue. The operator acts in Gitea through its own test account (NISSE_OPERATOR_TOKEN) and in the item's thread through the in-memory transport. Runs from scripts/e2e.sh. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01PPQ14L3LikyefCMFBqEbKE	2026-10-03 14:20:07 +00:00