Boot doesn't re-attach the Gitea plan and review pollers #59

New Issue

2026-09-29T15:52:29Z

dev-agent commented

2026-09-29 15:52:29 +00:00

Found while fixing #57.

Orchestrator._watch is only called when a plan is posted to its Gitea issue (_post_plan_to_board) or a milestone PR is published (_publish_milestone). Orchestrator.start never calls it. After a restart:

Open plan gate: approvals posted as comments on the Gitea plan issue go unseen until the next plan revision is posted. Matrix approvals still work.
PR_OPEN: review comments on the PR go unseen, so the agent never responds to them.

Nothing errors or warns, so the operator has no sign their Gitea comments are being ignored.

Expected: on boot, re-attach the plan watch when a gate is open and board data holds an issue, and the review watch in PR_OPEN from the saved pr data. prime then skips comments that were already handled. Open question for review: comments posted while the agent was down would also be marked seen and skipped. Should the poller catch up on those since the last recorded comment instead?

Test: open a gate with a fake poller factory, restart the orchestrator on the same store, and check that a plan watch exists and a Gitea approval comment is applied. Do the same for review in PR_OPEN.

🤖 Generated with Claude Code

Found while fixing #57. `Orchestrator._watch` is only called when a plan is posted to its Gitea issue (`_post_plan_to_board`) or a milestone PR is published (`_publish_milestone`). `Orchestrator.start` never calls it. After a restart: - **Open plan gate:** approvals posted as comments on the Gitea plan issue go unseen until the next plan revision is posted. Matrix approvals still work. - **`PR_OPEN`:** review comments on the PR go unseen, so the agent never responds to them. Nothing errors or warns, so the operator has no sign their Gitea comments are being ignored. **Expected:** on boot, re-attach the `plan` watch when a gate is open and `board` data holds an issue, and the `review` watch in `PR_OPEN` from the saved `pr` data. `prime` then skips comments that were already handled. Open question for review: comments posted while the agent was down would also be marked seen and skipped. Should the poller catch up on those since the last recorded comment instead? **Test:** open a gate with a fake poller factory, restart the orchestrator on the same store, and check that a `plan` watch exists and a Gitea approval comment is applied. Do the same for `review` in `PR_OPEN`. 🤖 Generated with [Claude Code](https://claude.com/claude-code)

dev-agent referenced this issue

2026-09-29 16:33:43 +00:00

Let the agent merge its PRs once the operator has approved them #65

dev-agent referenced this issue

2026-09-29 16:39:20 +00:00

Never leave the agent stranded in a working state #66

dev-agent referenced a pull request that will close this issue

2026-09-29 17:33:41 +00:00

Keep Gitea threads watched across restarts and interruptions #68

dev-agent referenced this issue from a commit

2026-09-29 17:33:42 +00:00

Keep Gitea threads watched across restarts and interruptions