root/fusion
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

feat(FN-4150): complete Step 4 — document workflow step resolver support

Browse Source 
Fusion-Task-Id: FN-4150
Fusion-Task-Lineage: 153c239b-f6cd-49e4-bc13-216e0d2ca815
This commit is contained in:
Fusion
2026-05-13 20:38:43 -07:00
committed by gsxdsm
parent 97740be8b7
commit 6529c065b4
3 changed files with 12 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
docs/PLUGIN_AUTHORING.md
View File

@@ -1467,6 +1467,8 @@ const workflowSteps: PluginWorkflowStepContribution[] = [
Use `mode: "prompt" | "script"` and `toolMode: "readonly" | "coding"`.
Plugin-contributed workflow steps are materialized through core `resolvePluginWorkflowStep(...)`; `mode`, `phase`, `scriptName`, `toolMode`, `defaultOn`, `modelProvider`, and `modelId` are preserved from your contribution (with defaults when omitted).
## 17. Contributing Prompt Modifications
Prompt contributions let a plugin inject additional instructions into specific prompt surfaces.

4
docs/design/cli-printing-press-plugin.md
View File

@@ -522,7 +522,9 @@ interface CppWorkflowStep {
}
```
This is registered via `definePlugin({ workflowStepTemplates: [...] })` following `docs/PLUGIN_AUTHORING.md` Section 16.
This is registered via `definePlugin({ workflowSteps: [...] })` following `docs/PLUGIN_AUTHORING.md` Section 16.
> **Implemented in FN-4150:** the plugin now contributes `stepId: "run-service-cli"` as a script-mode pre-merge workflow step with `scriptName: "cli-printing-press:run-service-cli"`.
### 7.3 Execution Flow