fix: bind tokenless examples to loopback

cmcp-runtime now restricts tokenless dev mode to loopback addresses (a wildcard
or LAN bind requires CMCP_BEARER_TOKEN). The financial-services, healthcare, and
startup-tpm examples run tokenless in dev mode and bound 0.0.0.0:8443, so they
would fail to start on the current runtime. Bind them to 127.0.0.1:8443 and note
why. industrial-embodied-ai already binds loopback.

Verified all three gateways start cleanly on loopback.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

Author: imran-siddique

financial-services/cmcp-config.yaml

@@ -1,6 +1,6 @@
 policy_bundle_path: ./policy
 catalog_path: ./catalog.json
-listen_addr: 0.0.0.0:8443
+listen_addr: 127.0.0.1:8443  # tokenless dev mode binds to loopback; set CMCP_BEARER_TOKEN for non-loopback binds
 max_response_size_bytes: 2097152
 attestation:
   provider: auto

healthcare/cmcp-config.yaml

@@ -1,6 +1,6 @@
 policy_bundle_path: ./policy
 catalog_path: ./catalog.json
-listen_addr: 0.0.0.0:8443
+listen_addr: 127.0.0.1:8443  # tokenless dev mode binds to loopback; set CMCP_BEARER_TOKEN for non-loopback binds
 audit_db_path: ./audit.db
 attestation:
   provider: auto

startup-tpm/README.md

@@ -106,8 +106,8 @@ cmcp start --config cmcp-config.yaml
 Expected startup output ends with:
 
 ```
-cMCP Runtime starting: TEE: software-only, listen: 0.0.0.0:8443
-INFO:     Uvicorn running on http://0.0.0.0:8443
+cMCP Runtime starting: TEE: software-only, listen: 127.0.0.1:8443
+INFO:     Uvicorn running on http://127.0.0.1:8443
 ```
 
 ---

startup-tpm/cmcp-config.yaml

@@ -1,6 +1,6 @@
 policy_bundle_path: ./policy
 catalog_path: ./catalog.json
-listen_addr: 0.0.0.0:8443
+listen_addr: 127.0.0.1:8443  # tokenless dev mode binds to loopback; set CMCP_BEARER_TOKEN for non-loopback binds
 attestation:
   provider: auto
   enforcement_mode: advisory