@flame0510/project-aether 1.1.14 → 1.2.0

package/docs/dev/DATABASE.md

@@ -1,6 +1,6 @@
 # Rev4a — Database Reference
 
-> **Last updated:** 2026-06-30
+> **Last updated:** 2026-08-28
 
 Rev4a uses a single SQLite file (`events.db`) in WAL mode.
 
@@ -182,7 +182,9 @@ CREATE TABLE credential_secrets (
 );
 ```
 
-Payloads are stored as JSON strings. In a future release they will be AES-256-GCM encrypted.
+`payload` holds the secret as raw JSON — **not encrypted**. Anything that can read
+this file, or reach `POST /api/credentials/[id]/reveal` with a valid session, has
+the secrets in the clear.
 
 ### `credential_audit_log` — append-only audit trail
 
@@ -197,7 +199,10 @@ CREATE TABLE credential_audit_log (
 );
 ```
 
-Actions: `create`, `update`, `delete`, `sync`, `reveal`.
+Actions: `create`, `update`, `delete`, `sync`, `desync`, `reveal`.
+
+Nothing reads `credential_audit_log`: it is written by `appendAudit()` and exposed
+through no route or view.
 
 ---
 

package/docs/dev/GATEWAY.md

@@ -95,7 +95,7 @@ OpenClaw defaults to merging config models with auto-discovered models.
 
 ### Model Catalogue
 
-The model catalogue lives in [`models.config.json`](../models.config.json) at the project root.
+The model catalogue lives in [`models.config.json`](../../models.config.json) at the project root.
 This file is **tracked in the repository** and serves as the default model configuration
 for anyone cloning the project. It defines all known models across all providers:
 
@@ -184,18 +184,20 @@ via `openclaw models status --json` inside each container.
 
 ### `PUT /api/gateway/provider`
 
-Triggers a full provider model sync to all agent containers. Only writes
-`models.providers.rev4a` — does NOT touch model references.
+Enables or disables a single model in the catalogue, then syncs every agent.
+Only writes `models.providers.rev4a` — does NOT touch model references.
 
-**Body:** none (reads current provider state from `models.config.json` and
-`data/provider-keys.json`)
+**Body:** `{ "modelId": "deepseek/deepseek-chat", "enabled": true }` — both
+required. Missing either returns `400`; an unknown `modelId` returns `404`.
 
 **Response:**
 ```json
 {
   "status": "ok",
-  "activeModels": 2,
-  "results": ["Active models: 2 across 1 agent(s)"]
+  "modelId": "deepseek/deepseek-chat",
+  "enabled": true,
+  "provider": "deepseek",
+  "sync": ["Active models: 2 across 1 agent(s)"]
 }
 ```
 

package/docs/dev/PROVIDERS.md

@@ -1,14 +1,10 @@
 # Provider Gateway & Key Management
 
-> **Last updated:** 2026-07-31
+> **Last updated:** 2026-08-28
 
-This document covers the Rev4a Provider Gateway (proxy),
-the vault key endpoint, and how agent containers authenticate against the
-Rev4a proxy.
-
-> **Note:** The old `/providers` UI page and its API routes (`/api/providers/*`,
-> `/api/agent-providers`) have been removed (2026-07-27). Provider/API-key
-> configuration is now centralized in the [Gateway](../GATEWAY.md) page.
+This document covers the Rev4a Provider Gateway (proxy), the provider key
+endpoints, and how agent containers authenticate against the Rev4a proxy.
+Provider and API-key configuration lives in the [Gateway](GATEWAY.md) page.
 
 ---
 
@@ -130,50 +126,41 @@ The proxy authenticates using the provider's real API key from
 
 ## Vault & Provider Key Endpoints
 
-### `GET /api/vault/provider/key`
+### `GET /api/gateway/provider`
 
-Returns the full API key for a provider. Used by the Providers page SHOW KEY flow.
+Provider state and the model catalogue.
 
 **Query params:**
 
 | Param | Required | Description |
 |---|---|---|
-| `provider` | Yes | Provider identifier (e.g. `openai`, `deepseek`) |
-| `agent` | No | Docker container name for agent-targeted reads; omitting reads the VPS host |
+| `summary` | No | `1` returns only which providers have a key — no models, no pricing. The full response waits on live pricing from OpenRouter, a network round trip costing seconds; callers that need just the boolean must not pay for it. |
 
-**Auth:** browser cookie
+**Auth:** browser cookie or bearer token
 
-**Response (200):**
-```json
-{
-  "provider": "deepseek",
-  "apiKey": "sk-...full-key...",
-  "masked": "sk-...be03",
-  "source": "local"
-}
-```
+### `POST /api/gateway/provider`
 
-**Source values:**
-- `local` — read from `data/provider-keys.json` on the VPS host
-- `container` — read from inside the agent container config
+Store a provider API key, or re-run the sync without changing keys.
 
-**Error (404):** `{ "error": "not_found" }` — provider has no key
+**Body:** `{ "provider": "deepseek", "apiKey": "sk-..." }`, or `{ "_syncOnly": true }`
+to push the current configuration to every agent container without touching any key.
 
-### `POST /api/vault/provider`
+**Response:** `{ "status": "ok", ... }`. Unknown provider names are rejected with
+`400` and the list of known providers.
 
-Add or update a stored provider credential in the vault.
+**Auth:** browser cookie or bearer token
 
-**Body:** `{ "provider": "deepseek", "apiKey": "sk-...", "baseUrl": "https://api.deepseek.com" }`
+### `PUT /api/gateway/provider`
 
-**Response:** `{ "status": "ok", "provider": "deepseek", "masked": "sk-...be03", "updatedAt": 1749200000000 }`
+Enable or disable a single model in the catalogue.
 
-### `DELETE /api/vault/provider`
+**Body:** `{ "modelId": "deepseek/deepseek-chat", "enabled": true }` — both fields
+required. Unknown `modelId` returns `404`.
 
-Remove a stored provider credential from the vault.
+**Auth:** browser cookie or bearer token
 
-**Body:** `{ "provider": "deepseek" }`
+There is no `DELETE`: a provider key is cleared by storing an empty one.
 
-**Response:** `{ "status": "removed" }`
 
 ---
 
@@ -218,7 +205,7 @@ Key points:
 
 ## Security Notes
 
-- The `GET /api/vault/provider/key` endpoint calls `requireAuthJWT` directly
+- The `GET /api/gateway/provider` endpoint calls `requireAuthJWT` directly
   (browser cookie or bearer token) — API routes are never covered by `proxy.ts`
   (it explicitly exempts `/api/*`), so each route must guard itself. Only
   authenticated users can reveal keys.

package/docs/rag/GLOSSARY.md

@@ -1,6 +1,6 @@
 # Rev4a Glossary
 
-> **Last updated:** 2026-07-15
+> **Last updated:** 2026-08-28
 
 Terms you'll encounter while using the Rev4a dashboard.
 
@@ -19,7 +19,7 @@ A small inline label component used for status indicators and channel chips. Sup
 A compressed archive (`.tar.gz`) of an agent's persistent volume (`/root/`). Backups exclude the npm cache to keep sizes small (~1.5 MB). Stored in the `rev4a-backups` Docker volume. Used for restore operations and auto-created before each recreate.
 
 ## Container
-A Docker container running on the server. Each agent runs in its own container. The Containers page shows all containers, including infrastructure ones (databases, reverse proxies, etc.), with CPU/memory metrics, logs, and a web terminal.
+A Docker container running on the server. Each agent runs in its own container. The Containers page shows all containers, including infrastructure ones (databases, reverse proxies, etc.), with CPU/memory metrics and a web terminal.
 
 ## Channel
 A communication channel (Telegram) configured on an agent. Channels allow users to send DMs to the agent via messaging apps. The Channel Manager modal lets you connect/disconnect Telegram and manage pairings (approve/reject senders).
@@ -34,13 +34,13 @@ The estimated cost of an agent session in USD, calculated from tokens used and p
 A manual correction for a month's total cost. If the automatic calculation doesn't match the actual invoice, you can set an override value for that month with an optional note.
 
 ## Credential
-A third-party service token (GitHub PAT, Trello API key, Vercel token, Supabase access key, Notion API token) stored in the Rev4a vault. Credentials can be scoped to specific agent containers and synced via CLI auth or config files. Every reveal is logged in the audit trail.
+A third-party service token (GitHub PAT, Trello API key, Vercel token, Supabase access key, Notion API token) stored in the Rev4a vault. A credential is installed into a container only when the user syncs it, and removed on de-sync; any credential can be synced to any container. Every reveal is written to an audit table that no route or view reads.
 
 ## Cron / Cron Job
 A scheduled task that runs an agent automatically at a fixed time (e.g. every night at 3:15 AM). Configured with standard cron syntax. Jobs can be enabled/disabled per entry.
 
 ## Dashboard
-The main page of Rev4a (`/`). Shows live sessions, cost summary, system health metrics (CPU, RAM, disk, load average), and a real-time event feed. A setup banner appears if the onboarding wizard is incomplete.
+The main page of Rev4a (`/`). Shows live sessions, cost summary, system health metrics (CPU, RAM, disk, load average), and a real-time event feed. A setup banner appears if the first-run wizard is incomplete.
 
 ## Event
 A lifecycle occurrence for a session: spawned, completed, errored, or a tool call made. Events appear in the live feed on the Dashboard and are pushed via SSE every ~3 seconds.
@@ -57,14 +57,14 @@ Files that store an agent's persistent knowledge and personality: MEMORY.md, SOU
 ## Model
 The AI model used by an agent or session. Examples: GPT-5.4, Claude Sonnet 4, DeepSeek V4 Flash. Models are linked to specific providers. The Gateway page manages which models are enabled and which agent uses which model.
 
-## Onboarding
-First-time setup wizard at `/onboarding`. Four steps: Welcome → Providers → First Agent → Ready. Progress is tracked per-step in `data/onboarding-progress.json`. A badge in the sidebar shows remaining steps (e.g. "2/3"). Always accessible from the sidebar or mobile navbar.
+## First-run wizard
+First-time setup wizard at `/wizard`. Steps: Welcome → Providers → First Agent → Ready. Completion is recorded in `wizard.json` under the data directory. Always accessible from the sidebar or mobile navbar.
 
 ## Plugin
 An extension that adds new tools and capabilities to agents. Plugins are installed in the workspace and appear in the Plugins page with enable/disable toggles.
 
 ## Provider
-An AI service provider (OpenAI, Anthropic, Groq, OpenRouter, DeepSeek, etc.) that hosts models. Provider API keys are configured in the Gateway page or via the onboarding wizard.
+An AI service provider (OpenAI, Anthropic, Groq, OpenRouter, DeepSeek, etc.) that hosts models. Provider API keys are configured in the Gateway page or via the first-run wizard.
 
 ## Provider Gateway
 Rev4a's built-in proxy that gives all agents unified access to configured LLM providers. Agents point to `http://host.docker.internal:3740/api/provider/v1` and Rev4a routes requests to the correct upstream using the stored API keys.
@@ -116,7 +116,7 @@ A record of an agent using a tool during a session. Useful for auditing what an
 Optional reverse proxy for routing web traffic to agent containers. If configured, an agent gets a public URL. Rev4a itself runs on port 3740 and does not require Traefik.
 
 ## Vault
-Rev4a's credential storage system. Stores provider API keys and third-party service tokens with per-agent permission scoping. Supports reveal (with audit trail), sync to containers, and live detection of installed credentials.
+Rev4a's store for third-party service tokens (GitHub, Trello, Vercel, Supabase, Notion). Provider API keys live separately in `provider-keys.json`, managed from the Gateway page. Supports reveal (written to an audit table no route or view reads), sync to and from containers, and live detection of which credentials are actually installed. Secrets are stored unencrypted.
 
 ## Workspace
 The directory where an agent's operational files live (config, memory files, skills, plugins, scripts). The Workspace page lets you browse, view, and edit files across the VPS host and all agent containers.

package/docs/rag/REV4A-OVERVIEW.md

@@ -1,15 +1,15 @@
 # What is Rev4a?
 
-> **Last updated:** 2026-07-18
+> **Last updated:** 2026-09-05
 
 Rev4a is the control panel for your AI agent infrastructure. It shows you everything your agents are doing, how much they cost, and whether the system is healthy — all in one dashboard.
 
 ## What can you do in Rev4a?
 
 ### Dashboard (`/`)
-The main page. See live sessions (who's working right now), cost summary by model and time period (today, 7 days, 30 days), system health (CPU, RAM, disk, load average), and a real-time event feed. Click any session row to open the Session Drawer and see every tool call the agent made. If the onboarding wizard is incomplete, a banner appears at the top with a link to continue.
+The main page. See live sessions (who's working right now), cost summary by model and time period (today, 7 days, 30 days), system health (CPU, RAM, disk, load average), and a real-time event feed. Click any session row to open the Session Drawer and see every tool call the agent made. If the first-run wizard is incomplete, a banner appears at the top with a link to continue.
 
-### Onboarding (`/onboarding`)
+### First-run wizard (`/wizard`)
 First-run setup wizard that guides new users through configuration. Four steps:
 1. **Welcome** — what Rev4a is and what it can do
 2. **Providers** — add API keys for DeepSeek, OpenAI, OpenRouter, or Groq (saved via the Provider Gateway)
@@ -68,7 +68,7 @@ Live web terminal into a Docker container. Run commands, inspect files, debug is
 File explorer for the OpenClaw workspace. Browse, view, and edit files across workspaces: the VPS host workspace and every agent container workspace. Switch between workspaces via a dropdown. Supports binary file preview (images) and text editing with syntax awareness.
 
 ### Credentials (`/credentials`)
-Manage third-party service credentials: GitHub, Trello, Vercel, Supabase, Notion. Each credential can be scoped to specific agent containers. Sync pushes credentials into containers via CLI auth (gh, vercel, supabase) or config files (trello, notion). Live detection shows which credentials are actually installed in each container. Audit trail for every reveal action.
+Manage third-party service credentials: GitHub, Trello, Vercel, Supabase, Notion. Sync installs a credential into the containers you pick — as that CLI's own config for GitHub, Vercel and Supabase, or as a config file the agent reads for Trello and Notion, which are used through their REST API; de-sync removes it from one container. Any credential can be synced to any container — there is no per-agent permission model. Live detection shows which credentials are actually installed in each container: a green tick when the installed token is the profile's own, a yellow diamond marked "unknown credential" when the container holds a token for that provider that no stored profile accounts for — an edited-but-not-resynced credential, one installed by hand, or the remains of a deleted profile. Every reveal is recorded in an audit table, which no route or view reads. Secrets are held unencrypted in `credentials.db`.
 
 ### Crons (`/crons`)
 Scheduled tasks auto-discovered from the host OpenClaw gateway (via `openclaw cron list --json`) and every running Docker container with the `AGENT_ID` label (via `docker exec openclaw cron list --json`). Filter jobs by agent using the toolbar tabs. Each job shows name, description, cron expression, next run, last run, and last status. Toggle on/off per job. The run history panel shows recent cron run executions for the selected job, loaded on demand from the container's gateway.
@@ -93,22 +93,19 @@ Skill registry showing all skills across three sources:
 
 Filter by source, view and edit SKILL.md content, and **promote** agent-local skills to shared with one click.
 
-### Plugins & Skills (`/plugins-skills`)
-Combined view showing both plugins and skills side by side.
+### Setup (`/setup`)
+First-run password setup. Reachable before a password exists; it sets `REV4A_PASSWORD` and the JWT secret, after which every page requires a session.
 
 ### Login (`/login`)
 Password-protected access to the dashboard. Enter the Rev4a password to authenticate. Session persists via a JWT cookie (7-day expiry).
 
-### Vault (`/vault`)
-Credential storage with per-agent permissions. Store API keys and service tokens, scope them to specific agents, and manage permissions via the UI.
-
 ## What about Pulse?
 
 Pulse is the AI assistant embedded in Rev4a. She appears as a floating chat button in the bottom-right corner of every page. She can:
 
 - Explain what any page does
 - Guide you through features ("how do I create an agent?")
-- Answer questions about agents, providers, costs, sessions, containers, crons, credentials, and onboarding
+- Answer questions about agents, providers, costs, sessions, containers, crons, credentials, and the first-run wizard
 - Give practical tips based on the page you're on
 
 Pulse does NOT have access to live data — she knows the page layout and features, but you need to look at the dashboard for real-time information.

package/docs/rag/WHAT-I-CAN-ANSWER.md

@@ -1,6 +1,6 @@
 # What PULSE Can Answer
 
-> **Last updated:** 2026-07-18
+> **Last updated:** 2026-08-28
 
 PULSE is the in-dashboard AI concierge for Rev4a. This document defines what she can and cannot answer.
 
@@ -10,7 +10,7 @@ PULSE is the in-dashboard AI concierge for Rev4a. This document defines what she
 
 - "Where do I find the agents page?"
 - "How do I get to the container list?"
-- "Where can I see the onboarding wizard?"
+- "Where can I see the first-run wizard?"
 - "Is there a page for cron jobs?"
 - "Where can I see my AI providers?" — The Gateway page (`/gateway`) shows providers, models, agent assignments.
 - "How do I create a new agent?"
@@ -34,7 +34,7 @@ PULSE is the in-dashboard AI concierge for Rev4a. This document defines what she
 
 - "How do I create an agent?"
 - "How do I set up Rev4a for the first time?"
-- "How do I complete the onboarding wizard?"
+- "How do I complete the first-run wizard?"
 - "How do I add an API key for a provider?"
 - "How do I filter agents by status?"
 - "How do I open a terminal for a container?"
@@ -75,8 +75,7 @@ PULSE is the in-dashboard AI concierge for Rev4a. This document defines what she
 - "What happens when I recreate an agent?"
 - "How do agent backups work?"
 - "What is an agent persistent volume?"
-- "What is the onboarding wizard?"
-- "What is the difference between Gateway and Providers pages?"
+- "What is the first-run wizard?"
 - "What is the Provider Gateway proxy?"
 - "How does the SSE stream work?"
 - "What is the shared gateway token?"
@@ -92,9 +91,10 @@ PULSE is the in-dashboard AI concierge for Rev4a. This document defines what she
 - "Why are costs missing for some sessions?"
 - "Why can't I connect to the container terminal?"
 - "Why is the gateway sync not working?"
-- "Why am I seeing an onboarding banner?"
+- "Why am I seeing a setup banner?"
 - "How do I check if the daemon is running?"
 - "Why are credentials not showing in my agent?"
+- "What does the yellow diamond next to an agent mean?"
 - "Why is the agent base image banner showing?"
 - "How do I fix 'image is outdated'?"
 - "What happens if I abort a build?"