Repository navigation
v0.15.0
Answers that explain themselves. The graph already held the answers; this release improves how they read, especially for AI agents. Additive, no data migration, one small behaviour change on GraphQL.
Added
- MCP
instructionsnow tell every client, at initialisation, what changes how an answer should be read. - Disappearances in plain language. Each
delete_sourceis glossed in a newdisappearancefield, which also says what it does not mean: none of the values says an operator removed anything. recent_changesacceptsfrom/to. Every answer names the window it read, and a truncated answer says what it left out incovered.DependsOnLocalEndpointinpkg/emitv0.10.0 builds the identity of a host-local endpoint and applies the canonicalisation rules.- The debug UI names its tenant, with a switcher when tenant selection is client-controlled.
Changed
- The 1.0 freeze audit walked the whole MCP surface. Two conventions are stated once in the stability policy: absence is an empty string for scalars, and
countis scoped to its object whiletotalis the population before the limit. - The MCP golden pins shape, not wording.
- The docs now cover the 15-minute resurrection window and what HA replicas agree on.
Upgrading
GraphQL entityHistory and recentChanges now exclude heartbeats by default, as MCP does. Pass includeHeartbeats: true to keep them.
Docs: https://toise.dev/docs/0.15.0/
Full details in the changelog.