release: bump scheduling-bridge to 0.7.1 (TIN-2098)

[Jesssullivan]

Summary

• bump scheduling-bridge from 0.7.0 to 0.7.1
• make the released bridge package/registry surface carry the already-merged kit 0.9.2 fuzzy matcher dependency
• update consumer docs and generated repo facts so package truth matches the release artifact

Why

TIN-2098 graduated the fuzzy/date/field matcher implementations to @tummycrypt/scheduling-kit/fuzzy and merged bridge consumption in #166. Without a bridge patch release, the live v0.7.0 tag and registry entry still point at kit 0.9.1, so downstream consumers cannot resolve the bridge artifact that actually consumes kit 0.9.2.

Validation

• pnpm docs:generate
• pnpm check:release-metadata
• pnpm check:artifact-authority
• git diff --check
• bazel build //:typecheck
• bazel test //:test
• bazel build //:pkg
• pnpm check:package

Release Notes

Patch release for TIN-2098. This is the bridge release-surface catch-up for the kit fuzzy scorer graduation:

• bridge source now imports the reusable fuzzy/date/field matcher surfaces from @tummycrypt/scheduling-kit/fuzzy
• bridge package metadata requires @tummycrypt/scheduling-kit ^0.9.2
• Bzlmod resolves tummycrypt_scheduling_kit 0.9.2 from the public tinyland registry

No npmjs publish: npmjs remains frozen at 0.5.11; GitHub Packages is derived from the Bazel //:pkg artifact.