feat: ship agent-first mission control v0.2.57
CI - Build & Test / Backend (.NET) (push) Successful in 42s
CI - Build & Test / Frontend (Vue/TS) (push) Successful in 2m46s
CI - Build & Test / Security Check (push) Successful in 3s
CI - Build & Test / Deploy Nexus (push) Successful in 56s

This commit is contained in:
AzuTear
2026-07-31 22:39:47 +02:00
parent 3bc7622977
commit f5552218bc
535 changed files with 95242 additions and 8791 deletions
+36
View File
@@ -0,0 +1,36 @@
# Nexus Run Control — Interactive Mockup
Controlled desktop prototype based on the second selected Run Control concept.
It is intentionally isolated from the production Nexus frontend and performs no
Nexus, OpenClaw, OpenAI, authentication, persistence, or network operations.
## Prototype scope
- Spatial Iris-led run topology
- Clickable Iris, Programmer, Reviewer, and Executor nodes
- Clickable run-event details
- Clickable OpenClaw session and OpenAI-via-OpenClaw routing details
- Human-approval review, approval success, and reversible mock decision
- Pause, resume, stop, and restart mock states
- Local Ask Iris dialog with an explicitly authored response
- Desktop-only layout; no Mobile Chat route or mobile interface
## Evidence level
This artifact is a controlled browser prototype with authored fixture data. It
does not prove a live Gateway, provider connection, agent execution, cost,
token count, tool call, approval, or production mutation.
The selected source visual is
[`reference/selected-option-2.png`](reference/selected-option-2.png).
## Local preview
```powershell
npm install
npm run dev -- --host 0.0.0.0 --port 4174 --strictPort
```
The verified visual and interaction report is in
[`design-qa.md`](design-qa.md), with the final side-by-side comparison under
[`evidence/comparison-final.png`](evidence/comparison-final.png).