v0.11.0

Toise v0.11.0 — vocabulary & correlation

Fixes a read-surface answer that was quietly wrong, and gives producers the type
vocabulary they were previously obliged to retype by hand. No wire-contract
break, no data migration.

telemetry_keys no longer inherits join keys through observation and peer
relations. An entity with no key of its own reported whatever happened to touch
it: a db seen only through monitors came back carrying the monitoring agent's
service.name, and a consumer that trusted the answer queried the wrong machine.
Inheritance is now restricted to ownership hops and is directional; graph
traversal is unchanged. An empty answer means no key exists rather than none was
found, and the guidance states the three rails on which the round trip holds.

The entity and relation type vocabulary is exported from pkg/emit/wire, shipped
as pkg/emit/v0.6.0, and Toise's own registry derives from those constants instead
of declaring a parallel copy — with a cross-check comparing both sets in both
directions.

Typed descriptive attributes become the documented normal path. Nothing on the
wire changes.

Recetted end to end before tagging: 38 checks, 0 failures, across the HTTP
surfaces, GraphQL and all twelve MCP tools.