Ragnor Comerford f4c38bb75a Scope the stored-query 404-hiding claim to non-invoke_query callers ... Review found the deny==404 catalog-hiding was overstated as a contract: it holds only at the outer invoke_query gate. A caller that HOLDS invoke_query but lacks read/change gets the inner gate's 403 for an existing query vs 404 for an unknown one — so existence is visible to grant-holders by design (the intended double-gate). The handler docstring, OpenAPI 404 description, and server.md all claimed the 404 was airtight against any denied actor. Correct the wording in all three (no behavior change) and add the missing symmetric test (invoke_query but no read -> 403 for an existing query, 404 for unknown) so the actual contract is pinned. Also document that in default-deny mode (tokens, no policy) every invocation 404s until an invoke_query rule is configured. Nits: the from_specs collision comment said "first declared wins" but it is lexicographically-first by name (BTreeMap); the effective_tool_name docstring overclaimed the CLI display routes through it (it resolves the rule on its own output DTO).		2026-05-30 23:33:27 +02:00
..
dev	docs: breadboard + slice Shape A in RFC-002	2026-05-30 18:25:25 +02:00
releases	feat: inline query strings in CLI and HTTP server (#110)	2026-05-29 13:41:54 +02:00
user	Scope the stored-query 404-hiding claim to non-invoke_query callers	2026-05-30 23:33:27 +02:00