swarm repositories / source
summaryrefslogtreecommitdiff
path: root/assets/codex-skills/mcp-bootstrap/references/checklist.md
diff options
context:
space:
mode:
authormain <main@swarm.moe>2026-03-19 11:19:42 -0400
committermain <main@swarm.moe>2026-03-19 11:19:42 -0400
commit478b0bc47fade5864f4f397de7ea519beddab749 (patch)
treefa3a555f8980afa0f3eb2bdeca6f3bc76eac8061 /assets/codex-skills/mcp-bootstrap/references/checklist.md
parent08a1139eaa7a4862ab8c0e5fb5fc6845fc711208 (diff)
downloadlibmcp-da1c2c0eb4116b74cfb308334723dd3754740e14.zip
Release libmcp 1.1.0v1.1.0
Diffstat (limited to 'assets/codex-skills/mcp-bootstrap/references/checklist.md')
-rw-r--r--assets/codex-skills/mcp-bootstrap/references/checklist.md4
1 files changed, 4 insertions, 0 deletions
diff --git a/assets/codex-skills/mcp-bootstrap/references/checklist.md b/assets/codex-skills/mcp-bootstrap/references/checklist.md
index b20a836..f2eeffd 100644
--- a/assets/codex-skills/mcp-bootstrap/references/checklist.md
+++ b/assets/codex-skills/mcp-bootstrap/references/checklist.md
@@ -3,10 +3,14 @@
Use this checklist when reviewing a `libmcp` consumer.
- Does a stable host own the public session?
+- Is the public session backed by the shared host-session kernel rather than
+ ad hoc initialize/reexec glue?
- Is worker fragility isolated behind an explicit replay policy?
- 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 library render helpers used where bespoke porcelain has not yet been
+ justified?
- Is structured JSON still available where exact consumers need it?
- Are inputs normalized where the semantics are still unambiguous?
- Are health and telemetry available?