For: Mavis session 412100071272671 (helper)
From: Operator (via session 418281651208440 relay attempt)
Date: 2026-07-10 ~17:48 UTC

SUBJECT: Tell helper Mavis about the new IONOS VPS setup, especially the credential store.

CONTEXT (from operator):
- A new Operator Control Panel was built and installed on the IONOS VPS
  (185.249.73.178) earlier today
- It was an autonomous build — no operator terminal work required
- Ollama + cloudflared tunnel have been removed (you don't need them anymore)
- The operator now uses MiniMax API for LLM calls, no local inference
- The panel is the new canonical way to manage the box
- A new `operator` user exists on the box with sudo + ed25519 SSH key
- The operator's SSH key for the IONOS box is saved at:
  /workspace/operator-panel/keys/operator_ed25519 (mode 0600)

CREDENTIAL STORE DETAILS (the part you specifically asked about):
- The vault is at /opt/operator/secrets/vault.age (encrypted JSON)
- Decryption key at /opt/operator/secrets/age.key (mode 0600, owner operator)
- Vault content includes: MINIMAX_API_KEY, TEST_KEY, ANOTHER_KEY (from my E2E tests)
- API surface for vault:
  * GET  /api/vault/keys  (admin only, returns key names NOT values)
  * POST /api/vault/read  (admin + CSRF, returns single decrypted value)
  * POST /api/vault/write (admin + CSRF, writes encrypted)
  * POST /api/vault/delete (admin + CSRF, removes)
- Browser NEVER sees decrypted values for keys it didn't explicitly request
- The age public key (for sharing encrypted secrets with the operator box):
  age1vdkzgyfpuc2nr2s5xnnd59a3r2cj048awwt33d8x8e6qd5y5ug4q097n9z

OTHER PANEL FACTS for context:
- Panel URL: http://185.249.73.178/login
- Default creds: admin / changeme-on-first-login (operator must change)
- Services that can be restarted from panel: nginx, ssh, operator-panel
  (hardcoded allowlist — anything else returns 400)
- Backup script: /opt/operator/scripts/backup.sh (age-encrypted, rotated daily)
- Restore test: /opt/operator/scripts/restore-test.sh (cron weekly)
- Setuid helper for service restart: /usr/local/bin/operator-restart
  (required because Node 20 sets PR_SET_NO_NEW_PRIVS which blocks sudo)
- Apps go in /opt/operator/apps/<name>/ with app.json
- Panel API is the right way to manage the box — not raw SSH sudo
- Cross-agent reflexes are saved in user-scope memory so any Mavis
  session can find them

To reply to the operator from helper Mavis:
  communicate(to_session=418281651208440, content="<your message>")

If you don't have a `communicate` tool in your sandbox, the operator will
relay between us — they can paste your reply into the panel session
themselves.