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

feat(FN-4754): complete Step 7 — document dashboard diff boundary coverage

Browse Source 
Fusion-Task-Id: FN-4754
Fusion-Task-Lineage: 69980e60-c1ad-4e19-bee0-970312669d70
This commit is contained in:
Fusion (runfusion.ai)
2026-05-16 10:45:37 -07:00
committed by gsxdsm
parent 05bd4fcdf9
commit 78402db294
1 changed files with 1 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

1
AGENTS.md
View File

@@ -990,5 +990,6 @@ If you're tempted to add `min-height: calc(var(--space-xl) + var(--space-md))` (
Reliability governance freeze is **LIFTED** (user directive, 2026-05-14, #product). Reliability-layer behavior changes are unblocked — a reliability pass is in scope. Standard review/test rigor still applies.
Reliability interaction regression backstops live in `packages/engine/src/__tests__/reliability-interactions/` and are the canonical location for cross-layer reliability coverage. Any task that adds or changes a reliability layer must add/update interaction tests in that directory for each plausible pair with existing layers (merge path, workflow/pre-merge, self-healing, scheduler/watchdog/restart recovery, and governance gates).
- FN-4754 adds a dashboard-diff display boundary backstop via `packages/engine/src/__tests__/reliability-interactions/dashboard-diff-boundary.test.ts` plus dashboard read-only guards in `packages/dashboard/src/__tests__/routes-diff-display-read-only.test.ts` and `packages/dashboard/src/__tests__/routes-diff-rebase-range.test.ts`.
**Auto-recovery dispatcher (FN-4533 governance exception).** The auto-recovery orchestrator at `packages/engine/src/auto-recovery.ts` composes on top of existing reliability layers (FN-4500 fast-path, FN-4508 deterministic branch-conflict classifications, FN-4499 bootstrap-misbinding re-anchor, FN-4428 contamination classifier, `mergeAuditAutoRecovery` Stages 1–5, self-healing sweeps) to handle residual failures in six classes: file-scope invariant violation at squash, branch misbinding / ghost worktree, verification-fix scope leak, contamination with foreign-attributed commits, `branch-conflict-unrecoverable` residuals, and room-post / message-send failures. Dispatcher invocation is additive at existing call sites — no existing layer's behavior is changed; see the FN-4533 design document for the composition contract and FN-4359 governance scope.