2 Commits

Include renames

Author	SHA1	Message	Date
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	b9f52be42c	Add the end-to-end test, run after each milestone (M1.6) ... tests/integration/test_end_to_end.py drives the whole assembled agent (real models, the Gitea sandbox, a real build host) through a milestone with a scripted operator, and checks what bring-up run 3 checked by hand: a PR holding only the work, pushed with the push credential; no credential in the clone; the planner's view carrying facts, not the executor's turns. It cleans up after itself on the sandbox and the build host. scripts/e2e.sh runs it on the bring-up build VM (or --local). It has its own marker, e2e, kept out of check.sh and CI since it spends tokens. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01PPQ14L3LikyefCMFBqEbKE	2026-10-02 22:59:13 +00:00