feat(FN-5405): remove broad-scope triage heuristics and UI advisory chips/b

Removes the broad-scope detection feature end-to-end: the TaskCard chip and TaskDetailModal advisory banner are gone from the dashboard, the triage heuristic that flagged tasks as broad-scope has been deleted from the engine along with its associated run-audit events, and documentation references ha

Fusion-Task-Id: FN-5405
This commit is contained in:
Fusion (runfusion.ai)
2026-05-21 15:06:17 -07:00
committed by gsxdsm
parent 5a76a89071
commit b8147dd3b1
15 changed files with 51 additions and 935 deletions

View File

@@ -55,7 +55,6 @@ Features:
- PR/issue badges with live updates
- GitHub provenance marker on task cards imported from GitHub (`sourceType: github_import`), shown alongside existing footer metadata like timers
- Agent-created provenance badge in task card headers for agent-originated tasks (`sourceType: agent_heartbeat` or `sourceType: automation`, or legacy tasks with `sourceAgentId`), with labels preferring `sourceMetadata.agentName` over raw agent IDs
- Broad-scope advisory surfacing from `task.sourceMetadata.broadScopeFlag`: TaskCard shows a warning-tinted `Broad scope` chip with score/reasons tooltip, and TaskDetailModal shows a read-only `Triage broad-scope advisory` banner with score, humanized reasons, and signal summary. This is informational only and does not alter lifecycle, scheduling, pause state, or merge behavior.
- Column ordering semantics: `todo` mirrors scheduler pickup order (priority descending, then oldest `createdAt`, then task ID); `triage`, `in-progress`, `in-review`, and `archived` remain priority-first with task-ID tie-breaks; `done` is ordered by most recent completion first (`columnMovedAt`, then `updatedAt`, then `createdAt` fallback)
![Board view](./screenshots/dashboard-overview.png)

View File

@@ -75,14 +75,6 @@ Direct-report stale decisions in `HeartbeatMonitor.buildReportsHealthSection()`
- `heartbeatAgeMs` is the report's current heartbeat age at classification time
- Healthy reports do not emit this diagnostic; only stale decisions do
## Broad-scope triage intake (`[triage]`)
- Trigger shape: `TriageProcessor.finalizeApprovedTask()` scores the prompt/description against `packages/engine/src/triage-broad-scope-heuristics.ts` and flags advisory decomposition risk when the score reaches `>= 3`.
- Diagnostic: `[triage] <taskId>: broad-scope flag at triage — score=<n>, reasons=<csv>`.
- Fail-soft diagnostic: `[triage] <taskId>: broad-scope heuristic failed open: <message>` when the helper throws; the task still proceeds to `todo`.
- Audit event: `task:broad-scope-flagged-at-triage` with `{ score, reasons, signals, thresholds, version }`.
- Task log side effect: `Broad-scope triage flag` advising operators to decompose via `fn_task_create` or set `breakIntoSubtasks=true` before execution.
## Resume instrumentation (FN-5389, Phase 1)
Dashboard Phase 1 resume instrumentation adds observation-only client/server traces for refetch/reconnect attribution. It does not change visibility/pageshow/SSE behavior; FN-5392 consumes this data for fixes.