Keep tablet and desktop layouts stable when the virtual keyboard shrinks viewport height. - Gate short-height mobile detection on phone-class physical screen size. - Reuse the shared mobile viewport helper across board, terminal, and workflow editor layout decisions. - Cover tablet keyboard and landscape phone viewport behavior with regression tests and document the UI bug pattern. - Preserve quarantine exclusions while resolving the squash merge conflict. Files changed: .../ui-bugs/tablet-keyboard-viewport-mode-flip.md | 54 +++++++++++++ packages/dashboard/app/components/Board.tsx | 4 +- .../dashboard/app/components/SessionTerminal.tsx | 16 +--- .../app/components/WorkflowNodeEditor.tsx | 41 +++++----- .../__tests__/SessionTerminal.mobile.test.tsx | 57 ++++++++++---- .../app/hooks/__tests__/useViewportMode.test.ts | 90 +++++++++++++++++++++- packages/dashboard/app/hooks/useViewportMode.ts | 26 ++++++- packages/engine/vitest.config.ts | 1 + scripts/lib/test-quarantine.json | 5 ++ 9 files changed, 239 insertions(+), 55 deletions(-) Fusion-Task-Id: FN-6213 Fusion-Task-Lineage: 01af6489-8c34-4318-9cff-1bceb1fa5a5d
31 lines
3.1 KiB
JSON
31 lines
3.1 KiB
JSON
{
|
|
"$comment": "Flaky-test quarantine ledger (deletion ratchet — see AGENTS.md 'Flaky tests: quarantine on sight' and docs/testing.md 'Quarantine ledger and the deletion ratchet'). A test observed failing without a corresponding real bug is quarantined ON SIGHT: add an entry here AND a matching one-line `exclude` entry in that package's vitest config, in the same commit. Every entry needs a non-empty `reason` (link the failing run) and a `quarantinedAt` date — the entry expires 14 days later, at which point the test file is DELETED unless someone rescues it with evidence it catches real regressions plus a root-cause fix (never appeasement). There is deliberately no loader module and no automation around this file: it is a dated record, the vitest config exclude is the mechanism, and the sweep is policy executed by whoever touches the suite.",
|
|
"entries": [
|
|
{
|
|
"file": "packages/engine/src/__tests__/project-engine-manager.test.ts",
|
|
"reason": "Flake: setInterval-driven reconciliation races with vitest fake-timer contention under full reliability-suite load. Test passes standalone (~46ms) but times out (30s) when reliability-pool files are co-resident. FN-6206.",
|
|
"quarantinedAt": "2026-06-10"
|
|
},
|
|
{
|
|
"file": "packages/engine/src/__tests__/merger-file-scope-invariant.test.ts",
|
|
"reason": "Flake: vi.mock('node:child_process') occasionally doesn't take under workspace-concurrent runs, letting real git binary leak and report staged files unrelated to test scope (trips FileScopeViolationError). Same logic covered by real-git fixture tests in reliability-interactions/workflow-and-file-scope. FN-6206.",
|
|
"quarantinedAt": "2026-06-10"
|
|
},
|
|
{
|
|
"file": "packages/engine/src/__tests__/self-healing-already-merged.real-git.test.ts",
|
|
"reason": "Flake observed during FN-6226 verification: full `pnpm --filter @fusion/engine test` expected two run-audit events but saw four after unrelated real-git/self-healing cleanup activity. The failure is outside fast-mode workflow changes and indicates suite-order/temp-state sensitivity.",
|
|
"quarantinedAt": "2026-06-10"
|
|
},
|
|
{
|
|
"file": "packages/engine/src/__tests__/merger-ai-cleanup-active-session.test.ts",
|
|
"reason": "Flake: pruneExistingAiMergeWorktrees skips active-session paths — active-session temp AI merge dir was unexpectedly pruned during pnpm --filter @fusion/engine test in FN-6206 verification, while the same file passed standalone. Root cause suspected: realpathSync resolution mismatch or readdirSync mock interaction with activeSessionRegistry singleton under concurrent engine suite load. Discovered during FN-6206.",
|
|
"quarantinedAt": "2026-06-10"
|
|
},
|
|
{
|
|
"file": "packages/engine/src/__tests__/merger-ai-cleanup.test.ts",
|
|
"reason": "Flake observed during FN-6206 verification: `pruneExistingAiMergeWorktrees skips active-session paths` failed in full `pnpm --filter @fusion/engine test` runs while the file passed standalone, indicating suite-order/concurrency sensitivity. Follow-up FN-6207.",
|
|
"quarantinedAt": "2026-06-10"
|
|
}
|
|
]
|
|
}
|