docs: show what the demos and the quickstart actually print

[imran-siddique]

Both pages describe outcomes in prose and never show the output. For pages whose whole pitch is "don't take the spec on trust. Run it.", the output is the argument.

I ran them

• The published quickstart, end to end, against cmcp-runtime 0.4.0: config validates, the runtime starts, the forbidden call returns 403 POLICY_DENY, the session closes into a signed claim, and cmcp verify reports FAIL (partially_verified) and exits 1.
• Demo 6 against weight-custody-manifest 0.25.0: all four bullets on the card are accurate.

Nothing here corrects a claim about behaviour. Both pages were already right. What changes is that a reader can see it before installing anything.

Quickstart

• Step 4 now shows the response body the runtime really returns, in place of a one-line prose summary of it.
• That body carries a call_id, and the same id lands in the audit chain. That is the thread from the block in step 4 to the signed record in step 5, and the page never mentioned it. It is arguably the point of the whole exercise: a refusal nobody can check afterwards is just a log line.
• Step 5 shows the CRYPTO-001 advisory the CLI prints before the checks table. It is not a failure, but it is the first thing on screen and the page did not prepare anyone for it.
• Records which version the page was last verified against, and says that a step not behaving as written is a bug worth reporting.

Demos

Was	Now
"These five govern the tool boundary" above six cards	Six, of which five are the tool call and demo 10 is the model call
"about twelve minutes"	Thirteen. The card times sum to 270s + 510s
export CMCP_BEARER_TOKEN=demo-token	Dropped. demo.py sets it, as the repo README says
No mention of --no-pause	Added. Without it the runner waits for a keypress before every demo
No output anywhere	Demo 6's verbatim output

Noted, not fixed here

• demos/demo.py says run only demo 2 (1 through 9) in its --help docstring. There are ten.
• cmcp validate-config crashes on a Windows console ('charmap' codec can't encode '✓') unless PYTHONUTF8=1 is set. The page scopes itself to macOS and Linux, so this is a cmcp issue rather than a page issue.

🤖 Generated with Claude Code

https://claude.ai/code/session_013EQx4N5BzTQbY8kvXUsdkY