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

chore(engine): remove workflow-step mock routing + stale FN-5482 docs

Browse Source 
Drops the "workflow-step" MockSessionPurpose enum value and the
workflowStepId / workflowStepTemplateId plumbing through
agent-runtime, agent-session-helpers, mock-provider, executor, and
merger. The seeded-workflow-prompts script loses its FN-5205
rationale comment + test (no longer applicable now that workflow
steps run through the regular session purposes).

Also strips the stale FN-5482 architecture-invariant bullet from
AGENTS.md and the corresponding audit-event line from
docs/architecture.md (the self-healing reclaim invariant they
described no longer holds).

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
This commit is contained in:
gsxdsm
2026-05-23 03:09:00 -07:00
parent ba6b41f533
commit 2209c57dd6
14 changed files with 23 additions and 302 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
docs/workflow-steps.md
View File

@@ -79,8 +79,6 @@ All seven built-in templates emit the structured `{"verdict":"APPROVE|APPROVE_WI
The **Browser Verification** template uses browser automation style checks and is designed for UI validation flows.
**Test mode behavior:** when Fusion test mode is active (`testMode: true` or `defaultProvider === "mock"`), Browser Verification routes to the FN-5203 mock provider and returns the canonical `{"verdict":"APPROVE","notes":""}` output without spawning a real model or `agent-browser`. Tests can force gate failures with `mockScriptRegistry.setMockScript({ sessionPurpose: "workflow-step", workflowStepTemplateId: "browser-verification" }, customScript)`. The seeded prompt body is unchanged; this behavior is provider-layer routing only.
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.
> **FN-3906 + FN-4343 auto-skip behavior:** The pre-merge orchestrator auto-skips the built-in `frontend-ux-design` step before pause/defer checks when workflow relevance signals show no frontend/UI scope. It now evaluates both (1) the task diff scope and (2) declared `## File Scope` from `PROMPT.md`. Scope relevance includes extensions (`.tsx`, `.jsx`, `.vue`, `.svelte`, `.astro`, `.html`, `.css`, `.scss`, `.sass`, `.less`, `.styl`), common UI path segments (`/components/`, `/app/components/`, `/dashboard/`, `/frontend/`, `/ui/`, `/styles/`, `/themes/`, `/design-system/`, `/design-tokens/`), and token/theme filenames (`tokens.(ts|js|json|css)`, `theme.(ts|js|json|css)`). If both signals are empty (or capture fails), Fusion preserves legacy behavior and runs the step.