feat(FN-3502): add comment-triggered retriage when task is in triage status

Merged four commits implementing comment-driven retriage: triage rules now respond to specific comment patterns (Step 1) and surface needs-replan feedback inputs in the UI (Step 2), with documentation for the new behavior and a bug fix restoring workspace typecheck defaults. Changes span the core ta

Fusion-Task-Id: FN-3502
This commit is contained in:
Fusion
2026-05-05 13:32:10 -07:00
committed by gsxdsm
parent 7d373286d9
commit 511c0c5442
8 changed files with 200 additions and 40 deletions

View File

@@ -263,6 +263,7 @@ describe("buildSpecificationPrompt", () => {
expect(prompt).toContain(feedback);
expect(prompt).not.toContain("Existing Specification");
expect(prompt).toContain("without carrying forward stale assumptions");
expect(prompt).toContain("Treat the current task title and description as required primary inputs");
});
it("includes attachments when provided", () => {
@@ -1170,6 +1171,35 @@ describe("Re-specification flow", () => {
expect(revisionLogEntry?.outcome).toBe("Most recent feedback");
});
it("prefers latest comment-triggered re-spec feedback log over legacy revision requests", () => {
const taskWithCommentTriggeredFeedback: Task = {
...taskWithRevisionRequest,
log: [
{
timestamp: "2026-01-01T00:00:00.000Z",
action: "AI spec revision requested",
outcome: "Older feedback",
},
{
timestamp: "2026-01-01T00:03:00.000Z",
action: "User comment requested re-specification of planned task",
outcome: "Latest feedback",
},
],
};
const feedbackLogEntry = [...taskWithCommentTriggeredFeedback.log]
.reverse()
.find((entry) =>
entry.action === "User comment requested re-specification of planned task"
|| entry.action === "User comment invalidated spec approval — task needs re-specification"
|| entry.action === "AI spec revision requested"
);
expect(feedbackLogEntry?.outcome).toBe("Latest feedback");
});
});
describe("requirePlanApproval setting", () => {