Find the last proven connection.

Audit finding: Repository and merged-release deployment status were inspected. This does not establish the release currently serving users.

Direction: Keep the current private repository; recover a verified mirror and release archive outside its failure boundary.

Exit test: Restore the exact release and review history from an independent copy.

Audit finding: GitHub reported a successful deployment for the reviewed release. Active domains, protected settings, quota and rollback remain unverified.

Direction: Use the existing integration. Optional backup status requires an independently working primary runtime and a recovery trial.

Exit test: Identify the serving release and existing project authority; verify a separate target before changing traffic.

Audit finding: Existing runtime plans were recovered. Server capacity, deployed services and Coolify installation were not inspected in this audit.

Direction: Assess the existing server and Coolify setup before adding infrastructure. Keep deployment packages portable to another host.

Exit test: Read-only host inventory, then an isolated exact-release installation and rollback trial.

Audit finding: The latest reviewed allowance receipt records a disabled, unfunded policy. This audit view does not poll the database or verify web-to-database configuration.

Direction: Retain the working service while designing a restore path for database, authentication, policies, files and service configuration together.

Exit test: Restore into an isolated target and verify account ownership and permission behavior before any migration.

Audit finding: Dependency and configuration-format registries exist. The public Key Master surface uses samples; private delivery and the dedicated allowance secret remain unverified.

Direction: Track protected references and configuration revisions per environment. Keep secret values outside public views and repository files.

Exit test: Verify authorized server configuration and rotation without exposing values.

Audit finding: Policy records name cache services; actual instances, persistence and failover were not inspected. Prime allowance enforcement uses the reviewed database path.

Direction: Inventory real consumers before choosing a replacement or assuming a cache dependency is active.

Exit test: Observe queue ownership, retained work, interruption and recovery on the selected runtime.

Audit finding: Prime has a guarded provider admission path. Its allowance stays disabled and unfunded; this view makes no claim about every other provider route.

Direction: Keep TheoB identity and saved work independent of the model vendor; compare adapters through bounded compatibility trials.

Exit test: Complete protected configuration and denied-request observations before any separately approved funded trial.

Audit finding: Connector contracts and local receipts exist. An authenticated inventory of every app, scope, version and affected feature is still required.

Direction: Use Connection OS for status, API Bank for contracts and existing boundary owners for authorization; propose changes from retained evidence.

Exit test: Admit one authenticated provider observation with expiry, affected features and a visible failure case.

Audit finding: Native acceptance remains separate. Signed Mac installation and live account-switch trials are open; automatic updates are inactive.

Direction: Preserve provider-controlled authentication and platform-specific installation/recovery evidence.

Exit test: Accept the signed installation and account-switch trials before claiming trusted automatic delivery.