Skip to content

Release status

This page is generated during each documentation build from the gate checklist. It includes gate names and status only. Test logs, commands, local paths, and environment values stay in the repository's internal release ledger.

17 of 24 gates complete.

Gate Requirement Status
G18 Public documentation builds from the existing Markdown sources with strict navigation/link validation and no private build inputs in the artifact. Complete
G19 The operations overview reports current release-gate status without publishing raw evidence, local paths, or secrets. Complete
G20 GitHub Pages is enabled for the public repository and the latest main build is available at the GitHub Pages URL. Complete
G21 Markdown, documentation assets, and local browser/agent state are excluded from every declared Docker build context. Complete
G1 Current CloudCLI package, auth boundary, workspace discovery and session recovery behavior are verified against the pinned upstream release. Complete
G2 IDE, CloudCLI, Codex, Claude Code, SSH, agent configuration, projects and task state use one persistent /workspace mount; application processes other than sshd/supervisor run as UID 1000 without capabilities. Complete
G3 Every browser route is authenticated, SSH accepts keys only, and no shared service port or administrator secret is exposed to agent processes. Complete
G4 CloudCLI is protected by authenticated TLS proxying and serves alongside VS Code at /vscode/; WebSocket upgrades work on the Railway HTTPS domain. Open
G5 Starting Codex or Claude from native VS Code produces a session CloudCLI can discover and resume, and follow-up changes share the same project files. Open
G6 Agent activity continues after browser/desktop disconnect. Restart handling marks in-flight work interrupted and exposes supported recovery without claiming a killed process continued. Complete
G7 Forgejo, PostgreSQL, OmniRoute and the always-on workspace start locally with required persistence, health and authentication behavior. Complete
G8 A real private Forgejo repository round-trip works from the shared workspace and persists across restart. Complete
G9 A mock LLM endpoint verifies authenticated model listing and full Codex/Claude request forwarding through OmniRoute without paid API calls. Complete
G10 Railway IaC type-checks against the current pinned official package. Complete
G11 A safe railway config plan in a dedicated fresh test project shows the expected services, volumes, references, TCP proxy, and no destructive changes. Complete
G12 A fresh Railway deployment in europe-west4-drams3a proves TCP SSH, public HTTPS auth, no serverless sleep, shared storage, desktop/mobile handoff and recovery after service restart. Open
G13 Restore drills prove the workspace, Forgejo, PostgreSQL and OmniRoute data can be recovered from documented backups. Complete
G14 Marketplace template is created, published, and successfully test-deployed. No template ID or verified badge is claimed before Railway confirms it. Open
G15 OmniRoute dashboard dependency vulnerabilities are patched in a rebuilt upstream image and authenticated runtime checks pass before its public domain is enabled. Open
G16 Every IaC preserve() variable has an explicit Railway Template Composer value or a documented operator input. Generated credentials use per-deployment secret() functions; provider master keys are excluded. Complete
G17 All four local Compose images are scanned, high and critical findings are triaged, and the exact release images pass the documented deployment security criteria. Open
G22 Off-platform backup artifacts are encrypted to an operator-controlled recipient without plaintext archives on durable storage, and an isolated restore validates all four local stores. Complete
G23 Public repository metadata and the documentation crawl/social cards are read back from the published site, and the repository social preview is uploaded. Open
G24 An isolated application-level restore verifies a private Forgejo repository, its PostgreSQL roles, OmniRoute authentication/provider metadata, and workspace configuration. Complete

A completed local check does not prove a Railway deployment, Marketplace publication, device acceptance, or full restore. Read the release checklist before treating a deployment as ready.