test: bound fuzz promotion work and align provider budget
Summary
Two existing tests exceeded their five-second deadline during the full related suite on unchanged main, blocking the #3554–#3562 rebase.
Split fuzz artifact promotion into independently initialized empty/seeded-corpus cases, each running the public CLI once. Both retain exact deduplication assertions; the empty case also proves promotion uses the rerun failure rather than saved artifact metadata.
Apply the existing ten-second provider-scenario timeout to canonical press @ref, matching its sibling. Production deadlines, worker count, integration slow-test limits, and response assertions are unchanged. Two test files; no production changes.
Validation
Head: 254a19d46f6c00164ac5532a0f00e602ba8481fe; base: f70224ad8239eec93f9063accf4711ce89b2113a. Node 24.13.1.
Same command: pnpm exec vitest run --project unit-core scripts/fuzz/harness.test.ts:
| Base | Head |
|---|---|
| 13 passed | 14 passed |
Both focused files: 24 passed. Prior full related selection reproduced the unmodified canonical-ref timeout and 6,205ms promotion case; isolated runs passed. Temporary promotion-omission, broken-dedup, and artifact-copy mutants produced the intended assertion failures and were reverted.
Independent fresh-context review: no findings. Frozen install/build and repository-wide formatting pass. pnpm check:affected --base f70224ad8 --run passes on this head (all runnable selected gates). CI is pending publication; Coverage and Integration remain authoritative. This prerequisite must land before publishing the repaired rebase.