fix(test): stabilize default timeouts and perf budget

[eduardbar]

Summary

• set global Vitest defaults (testTimeout and hookTimeout) to 15s to reduce timeout flakes in heavier local/CI runs
• tune scan runtime perf budget (benchmarks/perf-budget.v1.json) to reduce false-positive regressions while preserving guardrail intent
• document the stabilization change in the unreleased changelog

Validation

• npm test
• npm run check:runtime-policy
• npm run check:docs-drift
• npm run check:perf-budget

[github-actions]

drift trust

drift trust

• Trust Score: 86/100
• Merge Risk: LOW
• Target: /home/runner/work/drift/drift

Diff signals

• Base ref: origin/master
• Diff status: NEUTRAL
• Score delta: +0
• Issues: +0 new / -0 resolved
• Trust adjustment: +0 penalty / -0 bonus (net +0)

Top reasons

• Maintenance hotspots: Maintenance risk is LOW (28/100). (impact 7)
• Highest-risk file: /home/runner/work/drift/drift/benchmarks/fixtures/critical/src/domain/policies.ts has hotspot risk 40/100. (impact 6)
• Drift score pressure: Repository drift score is 1/100. (impact 1)

Fix priorities

• feat(review): drift review command with PR comment output #1 unused-export (warning, x10, effort: medium) - Address this rule in the highest-scored files first.
• feat(score): repository quality score breakdown in scan/json #2 dead-file (warning, x2, effort: medium) - Delete or wire dead files to avoid stale merge artifacts.
• feat(ai): ai_likelihood and files_suspected in AI output #3 magic-number (info, x6, effort: low) - Address this rule in the highest-scored files first.
• feat(architecture): configurable architecture rules in drift.config.ts #4 high-coupling (warning, x1, effort: medium) - Address this rule in the highest-scored files first.

drift review

drift review

ℹ️ No drift changes detected against base ref.

• Base ref: origin/master
• Score delta: +0
• New issues: 0
• Resolved issues: 0

File breakdown

• No file-level deltas detected