amadan
docs: record restored capacity and successful fork baseline push
Co-Authored-By: Codex <noreply@openai.com>
1 file changed,
+2
−2
docs/infinity/status.md+2 −2
Intent
diff --git a/docs/infinity/status.md b/docs/infinity/status.md| index 9038b3d..38ec71f 100644 |
| --- a/docs/infinity/status.md |
| +++ b/docs/infinity/status.md |
| @@ -16,7 +16,7 @@ A hosted WebKit drive using two already-provisioned test instances passed setup, |
| 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. 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. |
| +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. |
| 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. |
| @@ -26,4 +26,4 @@ The separate platform adoption fix is `90b0878`, branch `fix/relay-blocked-live- |
| This is an early text-chat implementation, not an independently audited security product. Recipient-key encryption has no double-ratchet forward secrecy. Group removal takes effect at a sender when it receives the membership update; old epochs remain valid for authenticated history, with no global cutoff for delayed/backdated old-epoch messages. Web clients trust code served by their origin. Routing metadata, timing, sizes, public keys and outbound delivery capabilities are server-visible. Recovery clones the identity across devices; independent device revocation and passkey-based recovery remain future work. Apple apps share the tested web UI; universal links, background push and App Store signing are not configured. Attachments, voice and video are not implemented. |
| -Source work is on `infinity-v1` in the isolated `.worktrees/infinity` checkout. The root checkout preserves the Eleven fork baseline; no main-branch merge has been performed. The user created `https://amadan.net/eleven/ocho` on 2026-09-06. The disclosed `codex` agent now has `eleven` and `carlos` grants, and local authentication has been verified. Codex CLI and Git authentication are configured. The initial baseline push was rejected by Amadan with `No space left on device`; the remote remains empty. A current host check found only about 1.4 MB available to the application user. The baseline and `infinity-v1` remain committed locally, awaiting approved storage expansion before retrying. All credentials remain outside the repository; no remote code writes should use another agent's identity. |
| +Source work is on `infinity-v1` in the isolated `.worktrees/infinity` checkout. The root checkout preserves the Eleven fork baseline; no main-branch merge has been performed. The user created `https://amadan.net/eleven/ocho` on 2026-09-06. The disclosed `codex` agent now has `eleven` and `carlos` grants, and local authentication has been verified. Codex CLI and Git authentication are configured. The initial baseline push was rejected with `No space left on device`. After external cleanup, the host had roughly 9 GB available and the original Eleven baseline was successfully pushed as `main`. The ∞ implementation is on the separate `infinity-v1` review branch; no implementation merge has been performed. All credentials remain outside the repository; no remote code writes should use another agent's identity. |