Add orthogonal detail controls to libmcp

3 files changed, 11 insertions, 0 deletions

diff --git a/assets/codex-skills/mcp-bootstrap/references/bootstrap-fresh.md b/assets/codex-skills/mcp-bootstrap/references/bootstrap-fresh.md
index aefe25d..4eea2b3 100644
--- a/assets/codex-skills/mcp-bootstrap/references/bootstrap-fresh.md
+++ b/assets/codex-skills/mcp-bootstrap/references/bootstrap-fresh.md
@@ -46,6 +46,11 @@ Faults should flow through health, telemetry, and user-facing shaping.
 
 Nontrivial tools should default to `render=porcelain`.
 
+`render` and detail are separate axes.
+
+- `render=porcelain|json`
+- `detail=concise|full`
+
 Porcelain should be:
 
 - line-oriented
@@ -55,6 +60,9 @@ Porcelain should be:
 
 Structured `render=json` should remain available.
 
+`json + concise` should be a structured summary, not merely the full payload in
+different clothes.
+
 Use library rendering helpers where possible. Do not default to pretty-printed
 JSON dumps and call that porcelain.
 
diff --git a/assets/codex-skills/mcp-bootstrap/references/bootstrap-retrofit.md b/assets/codex-skills/mcp-bootstrap/references/bootstrap-retrofit.md
index 146733c..faccc4c 100644
--- a/assets/codex-skills/mcp-bootstrap/references/bootstrap-retrofit.md
+++ b/assets/codex-skills/mcp-bootstrap/references/bootstrap-retrofit.md
@@ -8,6 +8,7 @@ scratch.
 1. Separate session ownership from fragile execution.
 2. Define typed replay contracts and typed faults.
 3. Replace ad hoc backend dumps with porcelain-by-default output.
+   Make `render` and `detail` orthogonal before you start bikeshedding prose.
 4. Add health, telemetry, and recovery tests.
 5. Only then promise hot rollout or stronger operational guarantees.
 
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?