# Nexus Console 1.0 POC — Manual Screenshot Evidence

Capture these screenshots after building and running Nexus Shell in Release mode.

## Prerequisites

1. Build: `dotnet build -c Release` from `source/nexus-shell/NexusShell`
2. Run Nexus Shell and log in as **admin@nexus.local** (MasterDeveloper role)
3. Open Nexus Console via **Ctrl+Shift+Alt+N** or **Indstillinger → System → Åbn Nexus Console**

## Required screenshots

| File | What to capture |
|------|-----------------|
| `console-open.png` | Nexus Console window with header (Nexus Console, Role, Session: Local POC), welcome text, and `nexus>` prompt — dark glass UI with cyan/purple glow |
| `console-help.png` | Run `help` — show full whitelist of Nexus commands in monospaced output |
| `console-blocked-command.png` | Run a blocked command (e.g. `powershell` or `explorer`) — show blocked message, not a Windows shell |

## Optional checks

- **Access denied**: Log in as **user@nexus.local** (User role), press Ctrl+Shift+Alt+N — dialog: *Adgang nægtet. Nexus Console kræver Developer-adgang.*
- **Audit log**: Verify `%LocalAppData%\NinjaNexus\audit\nexus-console-audit.jsonl` contains timestamp, user, role, command, result, allowed fields
- **Integration**: `update-check`, `lockdown-status`, `browser-test`, `files-test` commands work without opening Windows CMD/PowerShell/Explorer

## Notes

- Nexus Console is **not** Windows CMD or PowerShell — no general execute or Windows passthrough.
- Whitelisted commands only; unknown commands show: *Unknown Nexus command. Type help.*
- Legacy Developer Console window remains in codebase but is not opened by the key chord.
