From f3e0edd25730f1a65287976afa52f01ed0d8a387 Mon Sep 17 00:00:00 2001 From: cliffhall Date: Mon, 14 Sep 2026 09:25:16 -0400 Subject: [PATCH] docs: describe DirectoryReadResultSchema as the shape both eras share (#2374 review) Its doc comment still called it the legacy result, though both eras now parse with it once the codec has removed resultType. Co-Authored-By: Claude Opus 5 (1M context) Claude-Session: https://claude.ai/code/session_01Q3RsrgCxVoFPokLB4vAkxi Signed-off-by: cliffhall --- core/mcp/skillsSchemas.ts | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/core/mcp/skillsSchemas.ts b/core/mcp/skillsSchemas.ts index a91cb2ed..2904c408 100644 --- a/core/mcp/skillsSchemas.ts +++ b/core/mcp/skillsSchemas.ts @@ -235,8 +235,10 @@ export type GetSkillResult = SkillEntry; export const DirectoryChildSchema = ResourceSchema; /** - * `resources/directory/read` result on a **legacy** connection: the directory's - * direct children plus the opaque cursor. + * `resources/directory/read` result on **either** era: the directory's direct + * children plus the opaque cursor. On a modern connection this is the shape + * after the SDK codec has checked and removed `resultType`, which is why no + * modern variant exists — see the note below (#2373). * * `looseObject`, matching every other result schema here: a server that also * sends the caching attributes is not wrong for doing so, and a schema is not