Refresh Kaiju Coder 7 paid API readiness evidence

FINAL_RELEASE_REPORT.md

@@ -1,6 +1,6 @@
 # Kaiju Coder 7 Final Release Report
 
-Generated: `2026-06-03T20:41:56Z`
+Generated: `2026-06-03T21:00:45Z`
 
 Product name: `Kaiju Coder 7`
 Public model id: `kaiju-coder-7`
@@ -15,9 +15,10 @@ commercial API launch yet. The local model path, OpenCode profile, harnessed
 business-owner evals, staged helper repos, runtime-quantized recipe, and paid
 API scaffold are in place. The adapter, OpenCode helper, runtime helper, and
 merged 53.8GB model are uploaded under `RMDWLLC` with public visibility. The
-paid API has human approval, but operational launch still requires live
-Cloudflare bindings, secrets, Stripe staging evidence, Worker-to-Gojira proof,
-rollback proof, and latency evidence.
+paid API has human approval and a live Worker staging route with Cloudflare
+bindings, Worker-to-Gojira proof, rollback proof, and latency evidence. Public
+charging still requires a custom API domain plus real Stripe webhook and
+Checkout top-up evidence.
 
 ## Runtime
 
@@ -41,7 +42,7 @@ stability and speed.
 | Hugging Face release readiness | `ready=True pass=23 fail=0 manual=1 rc=0` |
 | Public launch readiness | `ready=False pass=23 fail=1 manual=0 rc=1` |
 | Hugging Face staging integrity | `ready=True pass=6 fail=0 manual=0 rc=0` |
-| Paid API launch readiness | `ready=False pass=21 fail=0 manual=6 rc=1` |
+| Paid API launch readiness | `ready=False pass=24 fail=0 manual=3 rc=1` |
 
 ## Hugging Face Upload Evidence
 
@@ -60,24 +61,21 @@ stability and speed.
 
 | Status | Check | Detail |
 |---|---|---|
-| manual | paid API launch preflight | 21 pass, 0 fail, 6 manual |
+| manual | paid API launch preflight | 24 pass, 0 fail, 3 manual |
 
 ## Public Launch Blockers
 
 | Status | Check | Detail |
 |---|---|---|
-| fail | paid API launch preflight | 21 pass, 0 fail, 6 manual |
+| fail | paid API launch preflight | 24 pass, 0 fail, 3 manual |
 
 ## Paid API Launch Blockers
 
 | Status | Check | Detail |
 |---|---|---|
-| manual | public route mode | attach sanitized evidence in /Users/richardecholsai7/Apps/kaiju-coder/release/paid-api-launch-evidence.json key `public_route_mode` |
-| manual | wrangler secret list confirms KAIJU_ORIGIN_URL, KAIJU_ORIGIN_SECRET, and KAIJU_STRIPE_WEBHOOK_SECRET | attach sanitized evidence in /Users/richardecholsai7/Apps/kaiju-coder/release/paid-api-launch-evidence.json key `wrangler_secrets_verified` |
+| manual | public route mode | public route evidence must use exposure_mode=custom_domain before paid launch |
+| manual | wrangler secret list confirms KAIJU_ORIGIN_URL, KAIJU_ORIGIN_SECRET, and KAIJU_STRIPE_WEBHOOK_SECRET | secret-name evidence missing: KAIJU_STRIPE_WEBHOOK_SECRET |
 | manual | Stripe Checkout top-up products and webhook endpoint tested with metadata.kaiju_api_key_id | attach sanitized evidence in /Users/richardecholsai7/Apps/kaiju-coder/release/paid-api-launch-evidence.json key `stripe_checkout_topup_staging` |
-| manual | staging request passed through Worker to Gojira-B origin with model=kaiju-coder-7 | attach sanitized evidence in /Users/richardecholsai7/Apps/kaiju-coder/release/paid-api-launch-evidence.json key `worker_to_gojira_staging_request` |
-| manual | rollback command or route switch was exercised and recorded | attach sanitized evidence in /Users/richardecholsai7/Apps/kaiju-coder/release/paid-api-launch-evidence.json key `rollback_exercised` |
-| manual | p95 latency for paid routes is recorded after staging traffic | attach sanitized evidence in /Users/richardecholsai7/Apps/kaiju-coder/release/paid-api-launch-evidence.json key `paid_route_latency` |
 
 ## Evidence Paths
 

GOAL_COMPLETION_AUDIT.md

@@ -1,11 +1,11 @@
 # Kaiju Coder 7 Goal Completion Audit
 
-Generated: `2026-06-03T20:42:32Z`
+Generated: `2026-06-03T21:00:45Z`
 
 Overall: `not complete`
 Summary: `17 passed / 1 blocked / 0 manual`
 
-This audit maps the active Kaiju Coder 7 objective to current evidence. It is stricter than local readiness: local public testing can pass while Hugging Face upload, human review, and paid API launch remain blocked.
+This audit maps the active Kaiju Coder 7 objective to current evidence. It is stricter than local readiness: local public testing and Hugging Face release checks can pass while paid API launch remains blocked.
 
 ## Readiness Commands
 
@@ -40,12 +40,12 @@ This audit maps the active Kaiju Coder 7 objective to current evidence. It is st
 | Quality | Model/harness prompts produce file-oriented business-owner artifacts rather than vague advice. | `passed` | kaiju_harness/business_suite.py; release/EVAL_SCOREBOARD.md |  |
 | Provenance | Training/eval provenance is preserved and public docs avoid internal checkpoint naming except license/provenance attribution. | `passed` | release/SOURCE_INVENTORY.md; release/DATA_PROVENANCE_DRAFT.md; release/PUBLIC_TESTING_QUICKSTART.md |  |
 | Paid API | Paid API scaffold covers API keys, Stripe billing, rate limits, logging controls, abuse controls, rollback plan, and pricing assumptions. | `passed` | python3 scripts/check_paid_api_readiness.py --mode scaffold; gateway/cloudflare-worker tests |  |
-| Paid API | Paid API is ready for public charging. | `blocked` | python3 scripts/check_paid_api_readiness.py --mode launch | Requires Wrangler secret-name evidence, Stripe staging evidence, Worker-to-Gojira staging request, rollback proof, and paid-route latency evidence. |
+| Paid API | Paid API is ready for public charging. | `blocked` | python3 scripts/check_paid_api_readiness.py --mode launch | Requires a custom API domain, KAIJU_STRIPE_WEBHOOK_SECRET, and real Stripe Checkout top-up staging evidence. |
 | Final Report | Final report includes exact commands run, eval results, changed files, remaining risks, and what Richard should test first. | `passed` | release/FINAL_RELEASE_REPORT.md |  |
 
 ## Blocking Items
 
-- Paid API: Paid API is ready for public charging.: Requires Wrangler secret-name evidence, Stripe staging evidence, Worker-to-Gojira staging request, rollback proof, and paid-route latency evidence.
+- Paid API: Paid API is ready for public charging.: Requires a custom API domain, KAIJU_STRIPE_WEBHOOK_SECRET, and real Stripe Checkout top-up staging evidence.
 
 ## Commands To Re-run
 

PAID_API_READINESS.md

@@ -64,15 +64,45 @@ Live Cloudflare resources were created on 2026-06-03 after Wrangler login:
 - R2 `kaiju-api-artifacts` bound as `KAIJU_ARTIFACT_BUCKET`
 - D1 migration `0001_paid_api.sql` applied successfully
 
-Current launch preflight after those resources:
+The Worker was deployed on 2026-06-03 at:
 
 ```text
-21 pass / 0 fail / 6 manual
+https://kaiju-api-gateway.kiyomi-api.workers.dev
 ```
 
-The remaining manual items are public route mode, required Wrangler secret-name
-verification, Stripe Checkout/webhook staging, Worker-to-Gojira staging request,
-rollback exercise, and paid-route p95 latency evidence.
+Gojira-B now advertises `kaiju-coder-7` from its public health endpoint. The
+origin secret was rotated during launch verification and re-applied to
+Cloudflare without writing the value to this repo.
+
+Current launch preflight after live staging traffic and rollback verification:
+
+```text
+24 pass / 0 fail / 3 manual
+```
+
+Passed live launch evidence:
+
+- `workers.dev` public staging route resolves to the Kaiju Worker.
+- `KAIJU_ORIGIN_URL` and `KAIJU_ORIGIN_SECRET` are present by Wrangler secret
+  name; `KAIJU_STRIPE_WEBHOOK_SECRET` is intentionally not marked present until
+  a real Stripe webhook signing secret is configured.
+- Worker-to-Gojira staging request passed through `/v1/chat/completions` with
+  `model=kaiju-coder-7`, HTTP `200`, and streaming enabled.
+- Paid-route latency was measured over five staging samples with p95
+  `17686.74ms`.
+- Rollback drill succeeded by deploying same-code version
+  `e838e01d-2d72-4eb7-9814-b95b7e2cef14`, rolling traffic back to verified
+  version `d37d60d1-7bfc-4ac9-a69c-e9339b5e495f`, and rechecking `/health`.
+
+Remaining paid-launch manual items:
+
+- Attach a real custom API domain. The current route is public and usable for
+  staging, but the launch checker requires `exposure_mode=custom_domain`.
+  `rmdw.ai` currently uses Vercel DNS, so a Cloudflare custom domain requires a
+  Cloudflare-managed zone, partial/CNAME setup, or a separate API domain.
+- Configure `KAIJU_STRIPE_WEBHOOK_SECRET` from a real Stripe webhook endpoint.
+- Test a real Stripe Checkout top-up that sends `checkout.session.completed`
+  with `metadata.kaiju_api_key_id`, including duplicate webhook idempotency.
 
 Covered locally:
 
@@ -187,9 +217,11 @@ python3 scripts/apply_paid_api_cloudflare_bindings.py \
 ```
 
 `--mode scaffold` verifies the local gateway implementation and should pass.
-`--mode launch` is stricter and should fail until real Cloudflare bindings,
-Wrangler secrets, Stripe webhook evidence, staging traffic, latency evidence,
-and rollback proof are attached.
+`--mode launch` is stricter. It should remain red until a real custom API
+domain, Stripe webhook signing secret, and Stripe Checkout top-up staging
+evidence are attached. Live Cloudflare bindings, Worker-to-Gojira staging
+traffic, paid-route latency evidence, and rollback proof are already recorded
+in `release/paid-api-launch-evidence.json`.
 
 Launch evidence is attached through a sanitized JSON file:
 
@@ -257,7 +289,10 @@ Current quality evidence:
 
 ## Release Blockers
 
-- Raw OpenCode customer-readiness task currently times out on multi-file work.
+- Paid API launch still needs a custom API domain and real Stripe
+  Checkout/webhook evidence before public charging.
+- Raw OpenCode customer-readiness task currently times out on multi-file work;
+  the harnessed business-owner route is the reliable first paid API product.
 - Harnessed customer-readiness route passes; paid API must route through that
   deterministic product path until a faster raw/quantized path passes.
 - Context-size benchmarks passed at 12k, 16k, 24k, and 32k, but the current