Proxy readiness and terminal sessions

Proxy readiness determines whether default access URLs and routes work. Proxy repair is an explicit operation.

The server edge proxy kind is future route intent: none means generated access or custom-domain routes should not choose this server as a proxy-backed target; traefik and caddy let later proxy readiness or deployment ensure flows realize provider-owned proxy configuration. Changing the kind does not start the proxy immediately, delete existing route snapshots, or clean up deployment/domain/audit history.

appaloft server proxy configure srv_primary --kind traefik

When changing from none to traefik or caddy, run explicit repair or let a later deployment ensure step handle proxy readiness:

appaloft server proxy repair srv_primary

Terminal sessions are controlled troubleshooting tools, not the normal deployment path.

The CLI keeps terminal opens scriptable by printing the session descriptor by default. Add --attach to appaloft server terminal <serverId> or appaloft resource terminal <resourceId> when you want the local terminal to connect directly to the accepted session.

Use terminal session lifecycle operations to list active sessions, show one session's safe metadata, close one active session, or expire old active sessions. These operations return session ids, scope, target ids, provider key, transport path, timestamps, and status only. They do not expose terminal input, terminal output, raw commands, private keys, access tokens, or environment secret values.

The Web Instance page shows the same active-session lifecycle view. It can close one active session or expire sessions older than one hour without attaching to the terminal transport or reading terminal output.

Opening and closing a terminal writes safe audit metadata: session id, scope, target ids, actor, entrypoint, provider key, timestamps, and close reason. Audit records do not store terminal input, terminal output, raw commands, private keys, access tokens, or environment secret values.

Terminal output can contain paths, environment details, or runtime data. Prefer diagnostic summaries before sharing output.