8caced6b57
Remove the CLI extension integration suite's hidden Vitest timeout override while keeping its explicit build-only allowance. - Replace the file-wide 30s Vitest test and hook timeout override with a scoped comment documenting default caps. - Derive the extension bundle path from the CLI root in the test file. - Use a SQLite collision trigger instead of a TaskStore prototype spy and fix the agent delete tool payload. - Clear the timeout appeasement allowlist now that the CLI test exemption is gone. Files changed: .../src/__tests__/extension-integration.test.ts | 25 ++++++++++++++++------ .../lib/test-timeout-appeasement-allowlist.json | 8 +------ 2 files changed, 20 insertions(+), 13 deletions(-) Fusion-Task-Id: FN-6436 Fusion-Task-Lineage: 670f41ea-f98f-400c-aa16-6a1cbb1e9bea
5 lines
579 B
JSON
5 lines
579 B
JSON
{
|
|
"$comment": "Vitest timeout-appeasement allowlist (temporary exemption ledger — see AGENTS.md 'Do Not Add Slow Tests' and docs/testing.md 'Quarantine ledger and the deletion ratchet'). The guard blocks new per-file or suite-level `testTimeout` / `hookTimeout` bumps in tracked test files. Every entry needs a repo-relative `file`, non-empty `reason` linking the owning cleanup/quarantine work, and `allowlistedAt` date. The goal is removal, not permanence: quarantine the flaky test or narrow the slow seam, then delete the timeout bump and this entry.",
|
|
"entries": []
|
|
}
|