10/10 launch gate

Codee must try to break itself before public blast.

The failure hunter is the strict scan that looks past normal 200 responses. It checks critical pages, local links, manifests, cache versions, old public naming, placeholder tokens, launch blockers, scale-claim guardrails, CLI update rules, domain-support wiring, and optional live route proof.

Open Failure Hunter Config Scale Readiness Launch Hardening Launch Control JSON

strict clean

Local strict scan

The current strict hunter pass returned zero critical findings and zero warnings after stale cache and manifest warnings were patched.

python3 tools/codee_failure_hunter.py --strict

live proof

Route proof

The live route loop remains required before promotion. It checks public pages, manifests, backend health, nonprofit surfaces, and AI K9 routes.

python3 tools/codee_404_loop.py --loops 1 --timeout 30

combined

Full failure pass

Use this when changing public launch pages, policies, delivery rooms, CLI pages, remote support, or service manifests.

python3 tools/codee_failure_hunter.py --strict --run-route-loop

support

Domain support

Hosted service lanes must save optional client-owned domain and white-label support choices without requiring DNS access before checkout.

domain_connect_preference + custom_domain_name

finds

What it catches

Missing critical files, invalid JSON, stale PWA cache tokens, old public Digi wording, local broken links, placeholders, launch blockers, stale route-proof counts, domain gaps, and unproven scale claims.

limits

What still needs people

Legal, CPA, privacy, security, insurance, remote-control, and very high traffic claims still need qualified review and live proof.

rule

No 10/10 without this

Codee should not be called 10/10 launch-ready unless strict failure hunter and live route loop both pass cleanly.