Release libmcp 1.1.0v1.1.0

3 files changed, 12 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 bddbc53..aefe25d 100644
--- a/assets/codex-skills/mcp-bootstrap/references/bootstrap-fresh.md
+++ b/assets/codex-skills/mcp-bootstrap/references/bootstrap-fresh.md
@@ -11,6 +11,8 @@ execution.
   policy, rollout, and user-facing error shaping.
 - The worker owns backend runtimes, backend-specific retries, and tool
   execution.
+- Use `libmcp`'s host-session kernel and snapshot-file handoff instead of
+  rolling custom initialize seed and reexec glue.
 
 If the worker dies, the session should survive.
 
@@ -53,6 +55,9 @@ Porcelain should be:
 
 Structured `render=json` should remain available.
 
+Use library rendering helpers where possible. Do not default to pretty-printed
+JSON dumps and call that porcelain.
+
 ## 5. Boundary normalization
 
 Normalize model-facing input where it is clearly safe:
diff --git a/assets/codex-skills/mcp-bootstrap/references/bootstrap-retrofit.md b/assets/codex-skills/mcp-bootstrap/references/bootstrap-retrofit.md
index 5a766a6..146733c 100644
--- a/assets/codex-skills/mcp-bootstrap/references/bootstrap-retrofit.md
+++ b/assets/codex-skills/mcp-bootstrap/references/bootstrap-retrofit.md
@@ -11,6 +11,9 @@ scratch.
 4. Add health, telemetry, and recovery tests.
 5. Only then promise hot rollout or stronger operational guarantees.
 
+When `libmcp` is in play, prefer its host-session kernel and render helpers over
+consumer-local copies.
+
 ## Specific Warnings
 
 - Do not add retries before replay legality is explicit.
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?