feat(FN-4493): complete Step 8 — finalize docs and release metadata

Fusion-Task-Id: FN-4493
Fusion-Task-Lineage: 966c7c55-fd51-4263-9d4e-87e9d06bfb6f
This commit is contained in:
Fusion
2026-05-14 12:29:34 -07:00
committed by gsxdsm
parent a24717da39
commit 716b9abbb5
3 changed files with 14 additions and 0 deletions

View File

@@ -0,0 +1,5 @@
---
"@runfusion/fusion": patch
---
Migrate the six remaining built-in prompt-mode workflow step templates (documentation-review, qa-check, security-audit, performance-review, accessibility-check, browser-verification) to emit the structured {verdict, notes} JSON contract introduced in FN-4367. Fix the frontend-ux-design template's verdict enum to match the parser's accepted set (APPROVE | APPROVE_WITH_NOTES | REVISE). Ships scripts/replace-seeded-workflow-prompts.mjs as a one-off operator tool to bring already-materialized project DB rows (e.g. WS-004) onto the new prompts; the prose-fallback path remains intact for backward compatibility.

View File

@@ -75,6 +75,8 @@ Fusion ships seven templates:
6. Browser Verification 6. Browser Verification
7. Frontend UX Design 7. Frontend UX Design
All seven built-in templates emit the structured `{"verdict":"APPROVE|APPROVE_WITH_NOTES|REVISE","notes":"..."}` envelope introduced in FN-4367 (final line JSON only). The legacy `REQUEST REVISION` prose path remains as a backward-compatible fallback. See [Prompt-mode Structured Verdict Contract](#prompt-mode-structured-verdict-contract).
The **Browser Verification** template uses browser automation style checks and is designed for UI validation flows. The **Browser Verification** template uses browser automation style checks and is designed for UI validation flows.
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. 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.

View File

@@ -53,6 +53,13 @@ test("replaces seeded workflow prompts and remains idempotent", async () => {
}, },
]); ]);
const runCheckStale = spawnSync("node", [scriptPath, `--db=${dbPath}`, "--check"], {
encoding: "utf8",
cwd: root,
});
assert.equal(runCheckStale.status, 0);
assert.match(runCheckStale.stdout, /WS-004: differs/);
const run1 = spawnSync("node", [scriptPath, `--db=${dbPath}`], { encoding: "utf8", cwd: root }); const run1 = spawnSync("node", [scriptPath, `--db=${dbPath}`], { encoding: "utf8", cwd: root });
assert.equal(run1.status, 0); assert.equal(run1.status, 0);
assert.match(run1.stdout, /WS-004: updated/); assert.match(run1.stdout, /WS-004: updated/);