4.4 Post-Deploy Synthetic CI Canary
chinwag ci canary --url https://your-app.comVerify live production and preview edge deployments with TLS checks, 176/176 DOM physics, MCP protocol probes, and automatic rollback triggers.
4.4 Post-Deploy Synthetic CI Canary
chinwag ci canary --url https://your-app.com
Passing unit tests and local builds does not guarantee a healthy edge deployment. Misconfigured CDN headers, missing Worker bindings, broken /docs/* route mounts, or stale asset hashes only surface once traffic hits the edge.
chinwag ci canary (WP-15) runs a 5-stage synthetic verification suite against your preview or production URL immediately after deploy · and automatically triggers a rollback or ++ Triage escalation if any stage fails.
chinwag ci canary \
--url https://docs.chinwag.sh \
--verify-mcp https://docs.chinwag.sh/mcp \
--verify-llms \
--rollback-on-fail
The 5 Synthetic Canary Stages
| Stage | Name | What It Verifies on the Live Edge | Target Latency |
|---|---|---|---|
| Stage C1 | TLS, HTTP/3 & Security Headers | Verifies 200 OK, TLS 1.3 certificate validity, Strict-Transport-Security, X-Content-Type-Options: nosniff, and zero 5xx edge Worker exceptions. | < 120ms |
| Stage C2 | Sitemap & Route Integrity | Crawls all canonical routes, section aliases (/delivery/*, /extensions/*), and /docs/* proxy mounts to confirm 0 broken internal links (404). | < 600ms |
| Stage C3 | AI Discovery & Onboard MCP Probe | Verifies /llms.txt, /llms-full.txt, /.well-known/mcp.json, and executes a live JSON-RPC 2.0 initialize + tools/list + tools/call handshake against /mcp. | < 250ms |
| Stage C4 | Live 176/176 DOM Physics Sweep | Runs Stage 1 chinwag ui-gate (8 viewports × 2 themes) against the live deployed URL to guarantee CSS bundles and web fonts hydrated cleanly. | < 950ms |
| Stage C5 | First-Party Telemetry Beacon Probe | Sends a synthetic canary ping to POST /e/track and verifies a 200 OK privacy-scrubbed edge proxy receipt (proxied: "posthog_docs_edge_v1"). | < 150ms |
GitHub Actions Post-Deploy Workflow
Drop chinwag ci canary directly into your deployment workflow right after wrangler deploy:
name: Deploy & Synthetic Canary
on:
push:
branches: [main]
jobs:
deploy-and-verify:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v4
- name: Deploy to Cloudflare Workers
run: npx wrangler deploy
- name: Run 5-Stage Chinwag Synthetic Canary
run: |
chinwag ci canary \
--url https://docs.chinwag.sh \
--verify-mcp https://docs.chinwag.sh/mcp \
--verify-llms \
--rollback-cmd "npx wrangler rollback --message 'Canary failure auto-rollback'"
Signed Canary Receipt (CanaryReceiptV1)
Every passing canary emits an Ed25519-signed CanaryReceiptV1 artifact attached to your release commit and synced to your GitHub Projects v2 or Linear board:
{
"schema": "chinwag.ci.canary.v1",
"url": "https://docs.chinwag.sh",
"stages": {
"c1_tls_headers": "PASS",
"c2_routes_200_ok": "PASS (42/42 routes)",
"c3_mcp_and_llms": "PASS (4 MCP tools + llms-full.txt verified)",
"c4_dom_physics_176": "PASS (176/176)",
"c5_telemetry_proxy": "PASS (posthog_docs_edge_v1)"
},
"duration_ms": 1840,
"credits_charged": 0,
"ed25519_sig": "✓ed25519:9f4c2a..."
}
Next Section: Chinwag Delivery-2 Autonomous AI Program Manager
Now that you have seen how Chinwag verifies visual geometry, copy, and live edge deploys, explore how Chinwag Delivery-2 orchestrates your backlog and prevents CI cascades automatically.
- Next: Chinwag Delivery-2: Your Autonomous AI Program Manager (Chinwag Reflex-1 & Chinwag Delivery-2)
- Ready to protect every production deploy? Reserve Your Organization Credit Pack →
64/64 Declaration Copy Gate
How Chinwag enforces editorial clarity, canonical product terminology, and zero leak invariants across marketing and documentation commits.
Overview: Dual-Brain AI PM
How DELIVERY combines Chinwag Reflex-1 (<50ms risk/cost radar) and Chinwag Delivery-2 (multi-step dependency planning) to keep engineering teams shipping.