3 Commits

Include renames

Author	SHA1	Message	Date
Omar Sobh	6e10528bc2	loops: restore .sqlx entries for test-only queries ... An earlier `cargo sqlx prepare --workspace` (without --all-targets) deleted two query cache files used only by tests (cm-runtime/tests/run_loop.rs and one topology_runs insert). CI builds with SQLX_OFFLINE=true and needs them present. Regenerate with --all-targets to include the integration test binaries.	2026-07-08 08:04:43 -07:00
Omar Sobh	a6da19430f	loops: repo picker + agent/team/org staffing + sidebar edit/delete ... Adds the missing pieces the wizard needed and the sidebar controls around it: - LoopsWizard is now a 6-step flow (identity → repo → task/topology → triggers → repeat → assign agents) plus the existing secrets card. ResearchWizard picks up the same repo step and a hard gate when the workspace has zero agents. - New LoopStaffingStep with three tabs — Individual / Team / Organization — that mix freely per loop; selections persist via new loop_agents / loop_teams / loop_orgs join tables (0035 migration), each cascading on loop_id so hard-delete stays a single-row DELETE. - Backend CreateLoopRequest / UpdateLoopRequest accept the three lists and apply_staffing does a transactional replace-all; list_loops / get_loop hydrate the lists via a flattened LoopWithStaffing response. - LoopsList sidebar gains per-row enable/disable, edit (reopens the wizard prefilled with the current loop, PATCHes on submit), and delete with an inline confirm. - NoAgentsGate blocks launching a loop or research topic from a workspace with no roster; the sidebar `+` buttons also disable with a tooltip pointing at the TEAM tier. Not yet wired: the run driver still fills role slots from the workspace-wide pool; teaching enqueue_iteration to prefer loop_agents/loop_teams/loop_orgs is a follow-up.	2026-07-07 22:09:06 -07:00
Omar Sobh	8a4e222aec	research: auto-transition processing → reviewing on last run ... Hooks the topology_worker's post-terminal path into a new notify_run_completed repo helper that atomically transitions the topic processing → reviewing when the completed run has research_topic_id set AND no siblings for that topic are still queued or running. Guarded on status='processing' so a retry, a re-fire, or a topic already past processing are all no-ops. Best-effort at the worker; DB hiccups are logged and never fail the run. The manual /submit-review endpoint stays as an escape hatch for topics that end up parked in processing with nothing to complete (updated the doc comment).	2026-07-06 12:32:18 -07:00