Closed-Circle Operations

Operate the control plane without touching production shells.

Phase 4 starts with a narrow, internal-only operator surface. This shell gives the next read and write plans a real protected entrypoint instead of inventing admin UX in the middle of feature work.

UsersUpcoming views for Telegram identity, last seen, and current config state.

BillingQueued for direct payment lookups and subscription status triage in the next wave.

ConfigsManual issuance, block/unblock, and regeneration routes land after the auth shell.

Operator Sign-In

Admin session handshake

Credentials stay server-side. The form posts to the backend auth boundary, stores the signed HTTP-only session cookie, and then hands protected routing over to middleware plus server-side session checks.

Local default API target: http://api:3000