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

feat(FN-3942): surface high fan-out blockers in task cards and executor sta

Browse Source 
Adds a "high fan-out" indicator that surfaces when a task blocks an unusually large number of downstream tasks, displayed as a warning badge on TaskCards and in the ExecutorStatusBar. The feature includes core type definitions, dashboard UI updates to render the warning with appropriate styling and

Fusion-Task-Id: FN-3942
This commit is contained in:
Fusion
2026-05-10 15:55:09 -07:00
committed by gsxdsm
parent 9044fbc5a5
commit e9834def83
13 changed files with 247 additions and 16 deletions
Download Patch File Download Diff File Expand all files Collapse all files

8
docs/dashboard-guide.md
View File

@@ -409,15 +409,17 @@ Inspect task definition, logs, review feedback, comments, documents, workflow ou
### Identifying high-impact blockers
Use the `Blocks N` badge on task cards to spot blockers with high downstream impact:
Use blocker fan-out signals on task cards and in the footer status bar to spot blockers with high downstream impact:
- `Blocks N` counts active downstream dependents in `triage`, `todo`, `in-progress`, or `in-review`.
- A card is escalated to **High fan-out** when it has at least **5 active `todo` dependents** (`activeTodoCount >= 5`).
- Done and archived downstream tasks remain visible for debugging context but do **not** count toward the 5-todo alert threshold.
- The badge tooltip shows total active dependents plus how many are currently waiting in `todo`.
- Open a task to the **Blocking** section in Task Detail to view each downstream dependent and click through quickly.
- `(stale)` markers mean the dependent is blocked through `blockedBy` and matches stale conditions that `clearStaleBlockedBy` self-healing should clear automatically.
- Stale `dependencies[]` links are shown for awareness but are not auto-cleared by `clearStaleBlockedBy`.
- The executor footer shows the current worst high fan-out blocker (in-progress/in-review only), ranked by highest todo fan-out, then highest total fan-out, then stable task ID order.
Recommended workflow: when a blocker has high fan-out, prioritize unblocking first (reassign, split, or resolve immediately) before lower-impact tasks.
Recommended workflow: ordinary chains stay as `Blocks N` so noise stays low; when a blocker crosses the 5-todo threshold, prioritize unblocking first (reassign, split, or resolve immediately) before lower-impact tasks.
### Logs → Agent Log view