opencode-gitlab-dap 1.4.2 → 1.5.0

package/README.md

@@ -49,12 +49,29 @@ Type `@Flow Name` followed by your goal to execute a flow:
 
 The plugin:
 
-1. Intercepts the `@` mention via `chat.message` hook
-2. Dispatches a subagent that fetches the flow definition
-3. Gathers required inputs using available GitLab tools
-4. Executes the flow via `POST /api/v4/ai/duo_workflows/workflows`
-5. Monitors workflow status until it starts running
-6. Reports the workflow URL for tracking in GitLab UI
+1. Registers the flow as a subagent with a built-in prompt containing flow execution instructions
+2. The subagent fetches the flow definition and parses what `context:goal` maps to (e.g., `merge_request_iid`, `pipeline_url`)
+3. Resolves the goal to the exact value the flow expects (e.g., just `14` for an MR IID, not a sentence)
+4. Gathers required additional inputs using available GitLab tools
+5. Executes the flow via `POST /api/v4/ai/duo_workflows/workflows`
+6. Monitors workflow status and reports the workflow URL for tracking in GitLab UI
+
+### Parallel Multi-Flow Dispatch
+
+Mention multiple flows in a single message to execute them simultaneously:
+
+```
+@AppSec Security MR Reviewer @Code Review 🦊 review all open MRs
+```
+
+When multiple flows are mentioned:
+
+1. The `chat.message` hook detects multiple `@` mentions and produces a single combined dispatch instruction
+2. A single `general` subagent is dispatched via the Task tool
+3. The subagent executes all flows concurrently — it calls `gitlab_get_flow_definition` for all flows at once, then `gitlab_execute_project_flow` for all flow+resource combinations, then polls all statuses
+4. For batch operations ("for each MR", "all open MRs"), the main agent lists resources first, then the subagent dispatches N flows × M resources in parallel
+
+The `experimental.chat.system.transform` hook injects system prompt guidelines that instruct the main agent on how to handle multi-flow and batch dispatch scenarios.
 
 ### 13 DAP Tools
 
@@ -97,7 +114,7 @@ User-defined agents from the AI Catalog. Appear in `/agents` with `[GitLab Custo
 
 ### Flows (Foundational & Custom)
 
-Multi-step workflows. Appear in `@` menu with `[GitLab Flow]` label. Executed via subagent dispatch.
+Multi-step workflows. Appear in `@` menu with `[GitLab Flow]` label. Each flow is registered as a subagent with a built-in prompt that handles flow definition parsing, goal resolution, and execution. Single flows dispatch natively; multiple flows are batched into a single `general` subagent for parallel execution.
 
 ### External Agents
 
@@ -128,7 +145,7 @@ export GITLAB_INSTANCE_URL=https://your-instance.com
 
 ```bash
 npm install
-npm test          # Run tests (48 tests)
+npm test          # Run tests (58 tests)
 npm run build     # Build (auto-runs vendor:generate)
 npm run type-check
 ```
@@ -154,26 +171,36 @@ git commit -m "chore: update vendored foundational flow definitions"
 
 ```
 Plugin init
-  ├─ readAuth()              reads ~/.local/share/opencode/auth.json
-  ├─ GitLabModelCache        reads model cache (no network call)
+  ├─ readAuth()                          reads ~/.local/share/opencode/auth.json
+  ├─ GitLabModelCache                    reads model cache (no network call)
   ├─ fetchCatalogAgents()
-  │    ├─ aiFoundationalChatAgents (GraphQL) → foundational agents
-  │    └─ aiCatalogConfiguredItems (GraphQL) → custom agents + flows
-  │         └─ aiCatalogAgentFlowConfig (GraphQL) → flow config YAML
-  ├─ config hook             injects agents (primary) + flows (subagent)
-  ├─ chat.message hook       intercepts @flow mentions → subagent dispatch
-  └─ tool hook               13 DAP tools
-
-Flow execution (@FlowName):
-  ├─ chat.message hook       replaces AgentPart with subagent instructions
-  ├─ Primary agent           dispatches Task subagent
-  ├─ Subagent Step 1         gitlab_get_flow_definition → read inputs
-  ├─ Subagent Step 2         GitLab tools → gather input values
-  ├─ Subagent Step 3         gitlab_execute_project_flow → POST to DWS
-  └─ Subagent Step 4         gitlab_get_workflow_status → confirm started
+  │    ├─ aiFoundationalChatAgents       foundational agents (GraphQL)
+  │    └─ aiCatalogConfiguredItems       custom agents + flows (GraphQL)
+  │         └─ aiCatalogAgentFlowConfig  flow config YAML (GraphQL)
+  ├─ config hook                         injects agents (primary) + flows (subagent with prompt)
+  ├─ chat.message hook                   intercepts multi-@flow → combined dispatch
+  ├─ experimental.chat.system.transform  injects flow dispatch guidelines
+  └─ tool hook                           13 DAP tools
+
+Single flow execution (@FlowName goal):
+  ├─ Native subagent dispatch   opencode routes to registered subagent
+  ├─ Subagent Step 1            gitlab_get_flow_definition → parse context:goal mapping
+  ├─ Subagent Step 2            Resolve goal to exact value (MR IID, URL, etc.)
+  ├─ Subagent Step 3            Gather additional_context inputs via GitLab tools
+  ├─ Subagent Step 4            gitlab_execute_project_flow → POST to DWS
+  └─ Subagent Step 5            gitlab_get_workflow_status → report status + URL
+
+Multi-flow execution (@Flow1 @Flow2 goal):
+  ├─ chat.message hook          detects multiple @mentions → combined dispatch
+  ├─ Primary agent              dispatches ONE general subagent via Task tool
+  ├─ General subagent           calls gitlab_get_flow_definition for all flows (concurrent)
+  ├─ (if batch)                 lists resources via GitLab API
+  ├─ General subagent           calls gitlab_execute_project_flow × N (concurrent)
+  ├─ General subagent           calls gitlab_get_workflow_status × N (concurrent)
+  └─ General subagent           presents summary table
 
 Enable/disable:
-  └─ refreshAgents()         clears cache, re-fetches, updates cfg.agent
+  └─ refreshAgents()            clears cache, re-fetches, updates cfg.agent
 ```
 
 ## License