v0.3.13

Weavatrix 0.3.13

0.3.13 fixes two misleading verification and graph-path signals found while
dogfooding a real duplicate-removal refactor. It also bounds cross-repository
contract responses with revision-bound pagination.

Honest refactor verification

• verified_change no longer reports an enabled duplicate ratchet as
  SKIPPED: duplicate ratchet disabled during the planning phase. An enabled
  plan now reports PLANNED, enabled: true, and states that the ratchet runs
  during phase="verify". An explicit duplicate_ratchet: false remains the
  only disabled state.
• shortest_path remains an undirected connectivity query, but every rendered
  hop now preserves the stored graph-edge direction. Reverse traversal renders
  <--imports-- or <--calls-- instead of inventing a forward dependency.
  Repeated and generic file names are widened in both the header and hop lines.

Bounded cross-repository contract evidence

• trace_api_contract response schema v4 returns compact, paginated evidence
  by default. page_size, per_item_limit, and a revision/filter-bound opaque
  cursor keep responses bounded; response_detail="full" remains an explicit
  opt-in and is still paginated.
• Invalid, stale, or cross-query cursors fail closed with INVALID_CURSOR.
• Repository graph reconciliation now reuses a persisted fresh graph before
  invoking a rebuild, while stale or failed refreshes retain their explicit
  completeness status.

Layer compatibility

The read-only core keeps its 34-tool surface and weavatrix.edit-plan.v1
contract unchanged. weavatrix-refactor 0.1.1 and weavatrix-online 0.2.0
are the paired upper-layer releases for this core version.

Full Changelog: v0.3.12...v0.3.13