AutoCoder Engine was updated and rolled out to fix incomplete Gitea pull request listing during deployment and wrap-up flows.
The previous implementation did not reliably traverse all Gitea pull request pages. For issues with older merged PRs beyond page 1, wrap-up could miss merged history and reopen already-completed issues as wrapup:reopened-unclean-state / Autocoder Error. AutoCoder/AutoCoder-Engine#2294 was the confirmed example.
f4e12e91eaaae69f8010b09ead512e8a875ddbfdgitea.app.lan/autocoder/autocoder-engine:sha-f4e12e91eaaa1427The Gitea pull request client now paginates /repos/{owner}/{repo}/pulls using Gitea's effective 50-item page cap until the final short page.
An earlier rollout, commit 244dac2ee8203df0f596d4481e3e78032023a848 / run 1424, added pagination with a requested page size of 100. That was superseded because the live Gitea API caps responses at 50 items, so page 2 still had to be requested explicitly.
cargo fmt --check passed.cargo test list_pull_requests_paginates_until_short_page passed.cargo test --lib --bins passed: 466 main tests, 46 Gitea MCP tests, 16 Kubernetes MCP tests.cargo test unit phases passed; doctest phase could not run because rustdoc is not installed on the host.deploy/autocoder-engine is ready on sha-f4e12e91eaaa.#2294 was commented with the root cause and deployment details, then marked as wrap-up complete and closed. AutoCoder subsequently detected that the dirty local worktree was stale because the issue branch was already merged, applied wrapup:complete-no-followup, and cleaned up without reopening the issue.