Summary

• add an isolated FakeCo staging configuration for ClickClack's existing single-container runtime
• seed deterministic synthetic users, channels, roots, and thread replies behind an explicit fakeco environment guard
• add correlation-aware health/readiness, normalized safe request logs, and opt-in metadata-only Prometheus metrics
• add a human-session canary that proves the ClickClack → OpenClaw → ClawRouter → quoted bot reply path
• document the small-VM topology, SecretRefs, operator proof, backup, and teardown

Runtime decision

Production remains the existing Cloudflare Worker + Cloudflare Container deployment and is untouched. FakeCo uses the repository's coherent Docker/single-binary path with SQLite on one small isolated VM; this does not introduce an AWS-native ClickClack platform.

Safety and integration contract

• no embedded credentials; OpenClaw resolves ClickClack, ClawRouter, and Gateway credentials through env-backed SecretRefs
• no models: [] workaround; the template uses the canonical dynamic ClawRouter provider overlay
• ClawRouter model refs use clawrouter/<catalog-provider>/<catalog-model>
• request metrics and logs exclude query values, message content, credentials, and concrete resource IDs
• Compose defaults to loopback binding, a read-only filesystem, dropped capabilities, resource bounds, and a dedicated named volume
• production Cloudflare configuration, domains, database, and R2 resources are outside this change

Validation

• pnpm check
• pnpm coverage — 86.6% total, above the 85% gate
• pnpm docs:site
• Docker Compose config, image build, container health/readiness, and non-destructive teardown
• deterministic seed rerun: identical fakeco.seed.v1 manifests with 3 users, 4 channels, and 7 seeded message IDs
• source-blind behavior validation: exact quoted bot sentinel after a 100-message burst; gateway, invalid-correlation, and bot-caller probes failed closed without credential leakage
• pre-commit autoreview: two canary issues fixed (paged polling and exact sentinel), then clean

Out of scope

No cloud deployment, account or secret creation, production mutation, release, version bump, or tag is included.