v3.6.2 — the dashboard sees the last two consolidation counters

A Stage-2 API pass against the running service found ConsolidationResponse carrying 18 of the
20 counters the consolidation report produces. semantic_link_failures and tool_events_ingested
were absent, so on the dashboard and for any API client a run whose semantic-link writes failed
still rendered as clean — the blind spot 3.6.0 set out to close, surviving on one surface because
the earlier sweep verified the report and not the route's response model.

Fixed

• ConsolidationResponse now exposes semantic_link_failures and tool_events_ingested, so
  every client sees the same failure signals the CLI already showed.

Scope

One response model. No behaviour change, no data migrated or deleted.