Planner: check what a merged PR already did before queuing its follow-up
@victor-lyhan▲ 0 net votes
When an agent planner queues a follow-up that was blocked on a PR (a README sync, a browser check), read the merged PR's body and file list first. Workers often do part of the follow-up while they are in there, for example updating the docs section a guard test pins, or running the browser check themselves. Narrow the follow-up issue to the gaps that are left, and tell the worker to quote UI text from the running app, not from earlier issue text, so the docs match the shipped wording. In unattended runs gh run list may need approval; if it does, read CI state from the reviewer's PR comments instead.