feat: add multi-agent support

[abderrahime-elidrissi]

This pull request introduces a comprehensive team-based routing and multi-agent orchestration feature to the F1 platform, enabling advanced parallel development workflows for complex issues. The changes span configuration schemas, runtime logic, and prompt templates, and are validated by a detailed end-to-end test drive. The most notable enhancements include the addition of a teamConfig section for repository configuration, new schema types for routing and quality gates, a team-lead system prompt, and logic for detecting and processing team-labeled issues.

Team Routing and Multi-Agent Configuration:

• Introduced a teamConfig section in the repository configuration (server.ts, config-schemas.ts) to define routing rules, agent roles, execution patterns, model assignments, and quality gates for team-based workflows. This enables flexible mapping of issue labels and complexity to specific agent teams and execution strategies. [1] [2] [3]
• Added new schema types and exports for TeamConfig, RoutingRule, ModelByRole, and QualityGates to support validation and type safety throughout the system. [1] [2] [3] [4]

EdgeWorker and Team Routing Logic:

• Integrated a new TeamRoutingEngine and logic in EdgeWorker to detect team labels (both hardcoded and configured), enabling the selection of team-based procedures and bypassing standard AI routing when appropriate. [1] [2]

Prompt and Agent Session Enhancements:

• Added a new team-lead system prompt (team-lead.md) that instructs the lead agent on decomposing work, spawning subagents, assigning models, and enforcing quality gates, tailored to the team configuration.
• Extended the CyrusAgentSession interface to include a teamRouting field, capturing the selected pattern, agents, model assignments, quality gates, and reasoning for traceability.

Validation and Testing:

• Added a detailed test drive document (007-team-routing-validation.md) that walks through the full workflow, verifies correct routing and prompt assembly, and highlights a current blocker with the Claude SDK integration. The document includes recommendations for further improvements and next steps.

Configuration Schema Updates:

• Updated the label prompts and prompt defaults schemas to support the new team label and prompt type, ensuring that team-based workflows can be configured and triggered via repository settings. [1] [2]

These changes collectively enable robust, configurable, and testable team-based development workflows, laying the groundwork for advanced multi-agent collaboration in the F1 platform.

[Connoropolous]

this looks fun!
have you been test driving it?

[Connoropolous]

@abderrahime-elidrissi

I'm happy to help unblock this, did you want to keep pushing it forward?

[abderrahime-elidrissi]

@abderrahime-elidrissi

I'm happy to help unblock this, did you want to keep pushing it forward?

Hi @Connoropolous,
Thanks! I took a few days off and didn’t have time to finish my tests on the feature.
I’ll pick it up again next week :)