amadan
Record verified signup timeout release and remaining platform adoption fix
Co-Authored-By: Codex <codex@openai.com>
1 file changed,
+3
−1
docs/infinity/status.md+3 −1
Intent
diff --git a/docs/infinity/status.md b/docs/infinity/status.md| index 1827e85..995521c 100644 |
| --- a/docs/infinity/status.md |
| +++ b/docs/infinity/status.md |
| @@ -14,7 +14,7 @@ A hosted WebKit drive on `https://ocho.chat` passed public registration of two f |
| ## Hosted state |
| -Account `ocho` / `bdy`; apps `infinity` and `infinity-home`; channel `canary/infinity`. Both apps now report build `47a9b014` from their own `/api/version` handlers; registration also reports it on `https://ocho.chat`. The registration watch initially timed out despite the edge header having advanced, because the existing process was still running the previous binary. An app-scoped `carlos restart` completed convergence; no fleet restart or database change was needed. |
| +Account `ocho` / `bdy`; apps `infinity` and `infinity-home`; channel `canary/infinity`. Both apps now report build `f0b34405` from their own `/api/version` handlers; registration also reports it on `https://ocho.chat`. The registration watch initially timed out despite the edge header having advanced, because the existing process was still running the previous binary. An app-scoped `carlos restart` completed convergence; no fleet restart or database change was needed. |
| Earlier restarts failed with `SQLITE_IOERR_SHMSIZE (4874)`. Read-only host metadata showed correct file ownership, 4 KB shared-memory files and roughly 95 MB of usable storage left on a 20 GiB root volume. Both canaries later woke successfully, with 32 KB shared-memory files, without database intervention. No database or WAL has been deleted/reset. A later capacity check reported roughly 114 MB available. Shared-volume expansion was prepared but not executed. A subsequent external cleanup freed roughly 9 GB; the baseline push then succeeded. Capacity was a suspected contributor to the earlier startup failure, not a proven errno diagnosis. |
| @@ -37,3 +37,5 @@ Personal release `47a9b014` is verified live, including the reserved user invita |
| ## Signup delay correction — 2026-09-06 (Codex) |
| A real signup after the successful public smoke encountered the platform’s already-staged live-symlink permission failure: the release existed but a new personal hostname could not get its live link. No account/database reset is needed. The reviewed platform fix `90b0878` remains the durable remedy. Client requests now abort after 30 seconds, and the registration attempt has a two-minute overall deadline instead of up to 80 slow readiness requests. It distinguishes device checking from allocation and startup, re-enables retry on failure, and preserves the registration nonce so retry continues the same account. Chromium/WebKit regression simulates a stalled challenge request and checks timeout, form recovery and nonce reuse. |
| + |
| +Release `f0b34405` is now live for both apps. Its new staging pass unblocked the waiting user instance; a read-only profile check returned HTTP 200 with setup still unclaimed. Existing processes needed app-scoped restarts to load the new live binaries. A deployed WebKit test on `ocho.chat` passed simulated request timeout, retry button recovery and registration-nonce reuse without submitting a registration. The permanent platform fix is still being prepared; later signups can encounter the already-staged permission bug until that platform rollout is complete. |