From 84e898d9ba699451d5d13fe384e7bbe220564bc1 Mon Sep 17 00:00:00 2001 From: main Date: Thu, 19 Mar 2026 17:15:25 -0400 Subject: Add orthogonal detail controls to libmcp --- assets/codex-skills/mcp-bootstrap/references/checklist.md | 2 ++ 1 file changed, 2 insertions(+) (limited to 'assets/codex-skills/mcp-bootstrap/references/checklist.md') diff --git a/assets/codex-skills/mcp-bootstrap/references/checklist.md b/assets/codex-skills/mcp-bootstrap/references/checklist.md index f2eeffd..babb157 100644 --- a/assets/codex-skills/mcp-bootstrap/references/checklist.md +++ b/assets/codex-skills/mcp-bootstrap/references/checklist.md @@ -9,6 +9,8 @@ Use this checklist when reviewing a `libmcp` consumer. - Are replay contracts typed and local to the request surface? - Are faults typed and connected to recovery semantics? - Do nontrivial tools default to porcelain output? +- Are `render` and `detail` treated as orthogonal controls? +- Does `detail=concise` return an actual summary rather than the full payload? - Are library render helpers used where bespoke porcelain has not yet been justified? - Is structured JSON still available where exact consumers need it? -- cgit v1.2.3