Update RedDock Phase 1 release presentation

Replace the Phase 0 dashboard capture with real Phase 1 screenshots taken
against the running container on loopback: the dashboard with its discovery
audit trail, and the Dockyard workspace showing a target cleared by DockGuard
before discovery can be launched.

Both use clearly fictional local sample data, including a deliberately
out-of-scope target so the denial is visible. Documentation only; no
application code, tests, or tags were touched.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

Author: chriswayneh

README.md

@@ -41,13 +41,19 @@ Its operating model is simple: **AI proposes. Policy authorizes. Tools execute.
 | Persistence | SQLite and evidence stored in a named Docker volume |
 | Safety | Non-invasive profiles only; no scripting, brute force, evasion, or exploitation |
 
-## Dashboard
+## Screenshots
 
 <div align="center">
 
-<img src="docs/screenshots/dashboard.png" alt="RedDock dashboard with an empty Dockyard state" width="900">
+<img src="docs/screenshots/dashboard.png" alt="RedDock dashboard showing workspace metrics and a discovery run audit trail" width="900">
 
-<sub>RedDock running locally with an empty Dockyard state. This capture predates the Phase 1 discovery workspace.</sub>
+<sub>The dashboard: workspace metrics and the discovery audit trail, including a run DockGuard denied.</sub>
+
+<br><br>
+
+<img src="docs/screenshots/workspace.png" alt="RedDock Dockyard workspace showing the discovery launch flow beside a DockGuard ALLOWED decision" width="900">
+
+<sub>The Dockyard workspace: a target must pass DockGuard before discovery can be launched.</sub>
 
 </div>
 

docs/screenshots/README.md

@@ -1,5 +1,7 @@
 # Screenshots
 
-`dashboard.png` is a real, scrubbed capture of the running dashboard. It still shows the Phase 0 layout and should be recaptured against the Phase 1 dashboard and Dockyard workspace. When replacing it, use an empty Dockyard list or clearly fictional local sample data; do not capture host paths, browser tabs, personal information, or authorized-engagement details.
+`dashboard.png` and `workspace.png` are real, scrubbed captures of RedDock running locally against loopback. When replacing them, use an empty Dockyard list or clearly fictional local sample data; do not capture host paths, browser tabs, personal information, or authorized-engagement details.
+
+The current captures use two fictional workspaces, a loopback scope, and a deliberately out-of-scope target so the DockGuard denial is visible.
 
 The README intentionally does not present a mockup as a product screenshot.