Files
fusion/scripts/lib/test-quarantine.json
gsxdsm cc793987b2 FN-6596: guard compound engineering debug launches
Guard Compound Engineering debug stage launches against stale stage settings and artifacts.

- Add source-level coverage proving stale enabledStages snapshots do not block registered CE stages, including debug.
- Add dist freshness checks for the disabledStages opt-out launch model so stale compiled plugin artifacts fail fast.
- Mirror newly observed core suite-load flakes in the quarantine ledger and Vitest excludes.

Files changed:
 packages/core/vitest.config.ts                     |  5 ++
 .../src/__tests__/dist-freshness.test.ts           | 38 +++++++++++++++
 .../src/__tests__/stage-launch-guard.test.ts       | 57 ++++++++++++++++++++++
 scripts/lib/test-quarantine.json                   | 10 ++++
 4 files changed, 110 insertions(+)

Fusion-Task-Id: FN-6596

Fusion-Task-Lineage: 3cd75e5f-c6f8-4bde-8202-54eeac82b894
2026-06-17 17:21:22 -07:00

46 lines
4.9 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/dashboard/src/__tests__/github-tracking-hook.test.ts",
"reason": "FN-6496 merge verification: pnpm test failed in dashboard-api-quality-backfill with ENOTEMPTY while removing a temp task directory; isolated rerun of the file passed, so classify as unrelated cleanup flake. Failing command: pnpm test; confirming command: pnpm --filter @fusion/dashboard exec vitest run src/__tests__/github-tracking-hook.test.ts --reporter=dot --silent=passed-only.",
"quarantinedAt": "2026-06-16"
},
{
"file": "packages/engine/src/__tests__/cli-agent-executor.test.ts",
"reason": "FN-6492 verification observed the hard-cancel CLI session test fail only in the full @fusion/engine package lane (activeCliTaskSessions false plus ENOTEMPTY temp cleanup), while an immediate file-specific rerun passed; quarantined as a concurrency/temp-cleanup flake per the deletion ratchet.",
"quarantinedAt": "2026-06-16"
},
{
"file": "plugins/fusion-plugin-compound-engineering/src/__tests__/orchestrator-flow.test.ts",
"reason": "FN-6587 broad pnpm test investigation: this CE orchestrator file was reported as timing out at Vitest's 5000ms test limit only in the broad pnpm test workflow; isolated two-file repro and loaded compound-engineering-node runs passed, and the broad command hit its external 900s workflow timeout before reproducing the named CE timeout. Quarantined per deletion-ratchet policy without timeout bumps, retries, or assertion loosening.",
"quarantinedAt": "2026-06-17"
},
{
"file": "plugins/fusion-plugin-compound-engineering/src/__tests__/skill-wiring.test.ts",
"reason": "FN-6587 broad pnpm test investigation: this CE skill-wiring file was reported as timing out at Vitest's 5000ms test limit only in the broad pnpm test workflow; isolated two-file repro and loaded compound-engineering-node runs passed, and the broad command hit its external 900s workflow timeout before reproducing the named CE timeout. Quarantined per deletion-ratchet policy without timeout bumps, retries, or assertion loosening.",
"quarantinedAt": "2026-06-17"
},
{
"file": "plugins/fusion-plugin-compound-engineering/src/__tests__/sync.test.ts",
"reason": "CE broad package verification under NODE_ENV=production fix hit a 10000ms beforeEach hook timeout only in the full @fusion-plugin-examples/compound-engineering lane, while an immediate isolated compound-engineering-node run of sync.test.ts passed in 15.43s. Quarantined per deletion-ratchet policy without hookTimeout increases, retries, or assertion loosening.",
"quarantinedAt": "2026-06-17"
},
{
"file": "plugins/fusion-plugin-compound-engineering/src/__tests__/work-bridge.test.ts",
"reason": "CE broad package verification under NODE_ENV=production fix hit a 10000ms beforeEach hook timeout only in the full @fusion-plugin-examples/compound-engineering lane, while an immediate isolated compound-engineering-node run of work-bridge.test.ts passed in 10.96s. Quarantined per deletion-ratchet policy without hookTimeout increases, retries, or assertion loosening.",
"quarantinedAt": "2026-06-17"
},
{
"file": "packages/core/src/__tests__/task-list-format.test.ts",
"reason": "FN-6596 verification: pnpm test failed in the broad changed-package @fusion/core lane with a beforeEach hook timeout in task-list-format after the merge gate had passed; immediate isolated rerun of the file passed. Quarantined as a suite-load timeout flake without timeout bumps, retries, or assertion loosening.",
"quarantinedAt": "2026-06-17"
},
{
"file": "packages/core/src/__tests__/test-project.test.ts",
"reason": "FN-6596 verification: pnpm test failed in the broad changed-package @fusion/core lane with a test timeout in test-project after the merge gate had passed; immediate isolated rerun of the file passed. Quarantined as a suite-load timeout flake without timeout bumps, retries, or assertion loosening.",
"quarantinedAt": "2026-06-17"
}
]
}