amadan
docs: record verified broker release and outstanding launch gates
Co-Authored-By: Codex <noreply@openai.com>
1 file changed,
+2
−2
docs/infinity/status.md+2 −2
diff --git a/docs/infinity/status.md b/docs/infinity/status.md| index e79b4f9..e091fc0 100644 |
| --- a/docs/infinity/status.md |
| +++ b/docs/infinity/status.md |
| @@ -14,9 +14,9 @@ A hosted WebKit drive using two already-provisioned test instances passed setup, |
| ## Hosted state |
| -Account `ocho` / `bdy`; apps `infinity` and `infinity-home`; channel `canary/infinity`. At 22:58 UTC the personal review endpoint `https://infinity-test.bdy.oncarlos.com` served `7daa45a0`; registration at `https://infinity-home-test.bdy.oncarlos.com` served `4c6bb26b`. Both adopted after their deployment watches timed out. The subsequent provisioning-idempotency change is validated locally and awaiting deployment. |
| +Account `ocho` / `bdy`; apps `infinity` and `infinity-home`; channel `canary/infinity`. As verified after the final broker deployment, the personal review endpoint `https://infinity-test.bdy.oncarlos.com` served `7daa45a0`; registration at `https://infinity-home-test.bdy.oncarlos.com` served `9ef43843`, including the provisioning-idempotency change. Earlier watches timed out before adoption; the final broker deployment completed its version watch successfully. |
| -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. Shared-volume expansion from 20 to 40 GiB is prepared and awaiting approval; capacity is a suspected contributor, not a proven errno diagnosis. |
| +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 from 20 to 40 GiB is prepared and awaiting approval; capacity is a suspected contributor, not a proven errno diagnosis. |
| The separate platform adoption fix is `90b0878`, branch `fix/relay-blocked-live-adoption` in `carlos/platform`. It relays permission errors replacing staged live symlinks through the existing privileged adoption pass. Its regression failed before the fix and passes afterward; independent review and full forge CI passed. The branch was pushed, but no platform change has been merged or deployed. |