chore(deps): update fallow to 3.34.0

[thymikee]

Summary

Update Fallow from 3.32.0 to 3.34.0 to pick up the tsconfig-reference traversal fix from fallow-rs/fallow#3504, which fixes fallow-rs/fallow#3503.

Across six files, preserve recursive matching with explicit ** globs under the new matcher and remove outdated slowdown explanations. Keep the separate typecheck config because Freerange still needs it. No runtime behavior changes or scope expansion.

Validation

Tested head: 2761c5c53d3b6dccafba2596ba2171e6516021c8.

• pnpm check:affected --run --head 2761c5c53d3b6dccafba2596ba2171e6516021c8: passed. Receipt run-gBtLhB: 36 passed, 25 skipped, 2 deduplicated; exactCommit=true, checkoutChanged=false.
• Related Vitest suite: 15,956 passed, 1 skipped. Fallow audit, production exports, lint, format, typecheck, build, package and repository guards passed.
• Independent review: no findings.
• GitHub-owned coverage, provider integration, native/device and compatibility lanes remain CI obligations. No known local blockers.

[cubic-dev-ai]

No issues found across 6 files

_{You’re at about 98% of the monthly reviewed-line limit. You may want to disable incremental reviews to conserve quota. Reviews will continue until that limit is exceeded. If you need help avoiding interruptions, please contact contact@cubic.dev.}

_{View guided diff | Turn on auto-fix | Re-trigger cubic}

[thymikee]

The tooling change looks fine, but CI has no signal yet on 2761c5c. Every job that runs pnpm install --frozen-lockfile fails at install with ERR_PNPM_MINIMUM_RELEASE_AGE_VIOLATION. The cause is the 10 new fallow 3.34.0 entries starting at pnpm-lock.yaml:1158. fallow 3.34.0 and its platform and type-aware sub-packages were published on 2026-10-17 at about 15:53Z. They are still inside the 24h minimumReleaseAge window. All 15 failing checks, including Integration Tests, Lint/Typecheck/Package, Coverage, Smoke Tests and the docs gates, fail this way before any repo code runs. So none of them has tested the glob or comment edits. Main passes because it pins 3.32.0, which is old enough. The fix is to re-run CI after about 2026-10-18T15:55Z and confirm install passes. Please do not add the fallow packages to minimumReleaseAgeExclude. That would weaken the policy for a bump with no urgency. Not blocking: the move of @agent-device/testmu and the changed position of yauzl in package.json:323 look unrelated to the bump, so revert the reorder or mention it in the PR body, whichever you prefer. After the re-run, the next step before merge is to check that the fallow audit gates pass with the new globs.