traverse-cli: bump traverse-registry dependency for resolve-hook (Spec 088)

[enricopiovesan]

Summary

Once traverse-framework/registry's Spec 015 ships (crates/traverse-registry emitting a resolve event through the UsageTelemetrySink port), bump traverse-cli's pinned traverse-registry dependency version so the CLI actually picks up the resolve-side instrumentation.

Why

crates/traverse-registry is consumed by traverse-cli as a pinned, published external crate (see this repo's Cargo.toml/Cargo.lock). Spec 088's resolve counter cannot take effect in traverse-cli until that crate publishes the new behavior and this repo bumps its pin — a real cross-repo release-sequencing step, not just a code change here.

Depends on

• Spec 088 approved (PR spec(088): opt-in runtime usage telemetry, decision 42, ADR-0030 #926)
• traverse-framework/registry Spec 015 approved and implemented

Blocked by

• traverse-framework/registryEstablish one canonical documentation entry path for humans and agents #144 (crates/traverse-registry resolve-hook must ship and publish a new crate version first)

Definition of Done

• traverse-cli's traverse-registry dependency version bumped to the release containing the resolve-hook.
• A resolve event is observed end-to-end (e.g. via a test double sink) when registry sync or an equivalent resolution path runs with telemetry enabled.

Validation

• Integration test proving a resolve event fires through the wired sink on a successful version resolution.