feat(FN-3571): merge fusion/fn-3571
This commit is contained in:
@@ -49,6 +49,16 @@ The **Browser Verification** template uses browser automation style checks and i
|
||||
|
||||
The **Frontend UX Design** template verifies visual polish and consistency with existing UI patterns and design tokens, including visual hierarchy, spacing/typography consistency, color/token consistency, component reuse, responsive behavior, and fit with existing design language.
|
||||
|
||||
## Plugin-Contributed Steps
|
||||
|
||||
Installed plugins can also provide **workflow step templates** that you enable from **Settings → Workflow Steps**, just like Fusion’s built-in quality gates.
|
||||
|
||||
Plugin-contributed templates appear in the same workflow-step chooser/UI as built-ins. In that chooser, plugin entries are labeled/grouped as plugin-contributed (including plugin attribution in the template metadata) so you can distinguish them from Fusion-provided templates.
|
||||
|
||||
Once added, plugin-contributed workflow steps behave like other steps: they support the same `prompt` or `script` execution modes, `pre-merge` or `post-merge` phases, and `defaultOn` behavior for new tasks.
|
||||
|
||||
For plugin installation and authoring details, see the [Plugin Authoring Guide](./PLUGIN_AUTHORING.md) (Section 16: Registering Workflow Steps).
|
||||
|
||||
## Creating Workflow Steps in the Dashboard
|
||||
|
||||
From **Settings → Workflow Steps**, clicking **Add Workflow Step** now opens a chooser first:
|
||||
|
||||
Reference in New Issue
Block a user