architecture.md describes the dispatch pipeline assuming a single agent adapter and a single workflow template per deployment. With rule-based dispatch (#435) and the auto-merge reaction (#417) landing in this milestone, the architecture reference must cover both.
Scope: extend the dispatch section to describe how the orchestrator evaluates user-defined rules against issue metadata, selects an agent and template, and falls back to defaults. Add auto_merge to the reaction types catalogue (alongside ci_failure, review_comments, and the future merge_conflict/bot_review entries) with a note that auto-merge is the only reaction kind that performs an action directly rather than dispatching an agent continuation. Update the data-flow and state-diagram sections if they reference the old single-agent assumption. Keep changes focused on the architecture document; user-facing docs live separately (#469, #470).
Verify: docs/architecture.md reflects rule-based dispatch and the auto-merge reaction. Diagrams are updated or explicitly marked as not requiring changes. A reviewer unfamiliar with the new features can understand both from this document alone.
architecture.mddescribes the dispatch pipeline assuming a single agent adapter and a single workflow template per deployment. With rule-based dispatch (#435) and the auto-merge reaction (#417) landing in this milestone, the architecture reference must cover both.Scope: extend the dispatch section to describe how the orchestrator evaluates user-defined rules against issue metadata, selects an agent and template, and falls back to defaults. Add
auto_mergeto the reaction types catalogue (alongsideci_failure,review_comments, and the futuremerge_conflict/bot_reviewentries) with a note that auto-merge is the only reaction kind that performs an action directly rather than dispatching an agent continuation. Update the data-flow and state-diagram sections if they reference the old single-agent assumption. Keep changes focused on the architecture document; user-facing docs live separately (#469, #470).Verify:
docs/architecture.mdreflects rule-based dispatch and the auto-merge reaction. Diagrams are updated or explicitly marked as not requiring changes. A reviewer unfamiliar with the new features can understand both from this document alone.