Changed MCP server instructions would be re-sent instead of suppressed, but that needs the disabled discovery cache.
Instruction blocks now store each server's own text so changes can re-emit, gated on the MCP discovery cache which is off by default.
What's wrong with this entry?
The record of MCP server instructions now keeps each server's own instruction text next to the rendered block, so a still-connected server whose instructions changed gets its block re-sent instead of suppressed as already present. Re-emitting on change requires the MCP discovery cache, which is not enabled by default.
tengu_mcp_instructions_pool_change
Strings lifted out of the shipped bundle, so the claim above can be checked against them.