Tests: separate consumer archive checks

[noeltock]

Problem

The default repository suite performed two clean consumer/archive builds on every Node version. Those checks are valuable, but they are a separate environment and cost boundary from the deterministic repository tests. Closes #92.

Solution

The two archive builders now run once in a serial test:consumer suite. The default suite excludes only those files; CI’s package-boundary job and the full release matrix explicitly run the consumer suite so its assertions remain release-blocking.

Diff

+114 −153 · 9 files · no assertions removed

npm test              -> deterministic repository suite
npm run test:consumer -> standalone release archive + native adapter archive
CI/release            -> both routes

Testing & verification

Reviewed revision: 768ecf4 · local Node v22.23.1 · npm 10.9.8

• npm run test:consumer — 2 files / 2 tests passed in 31.93s.
• npm run typecheck — passed in 2.876s.
• node --import tsx scripts/authoring-hashes.ts --check — passed in 0.260s.
• Discovery confirmed the default suite contains neither moved archive test and the consumer config contains exactly both moved files.
• git diff --check — passed.

The CI matrix is the compatibility gate for this split. A clean local Node 22.23 install hit an unrelated existing wesper@0.0.3 → zod/v4 ESM-resolution failure in styles.test.ts; it is outside this PR’s files and is not presented as a passing default-suite result.

Risk / rollout

The moved archive checks retain their original 300-second per-test allowance and serial execution. CI and the full release matrix fail if the consumer route fails; reverting this commit restores the former default-suite placement.