Complete name-first MCP write-plan composition

2026-07-26 17:05:05 +03:00
parent 92a331f149
commit 1ca47dce13
9 changed files with 345 additions and 18 deletions
@@ -262,8 +262,11 @@ Client, MCP, and agent code must not add conditions for concrete object names;
 the adapter owns generic selector normalization.

 Saved-state client calls use the same name-first selectors together with
-`layer=base_saved_state|extension_saved_state`. SQL tables, file names, GUID
-owners, and module handles are diagnostic continuations exposed only with
+`layer=base_saved_state|extension_saved_state`. Public module search results
+include a name-first `write_plan_target` (`ref`, form/module names, and a
+1-based stream ordinal); `metadata.write.plan` resolves its physical handle
+internally. SQL tables, file names, GUID owners, module handles, and payload
+hashes remain diagnostic continuations exposed only with
 `include_storage=true`. Every public RPC follow-up is shaped as
 `{"method": "...", "params": {...}}`; `payload` is not the arguments field of
 `next_call` or `next_resolution`.