[shashikanth-gs]

What changed and why

A docs pass after the console redesign (#64–#67) and the embedded-database lock (#64, #65). #68 already pointed grants, credentials and people at Administration; this covers what was left.

• Stale references fixed: the audit trail is now Administration → Audit trail (quickstart, teams and grants, README, console guide permissions table); Browse tasks also opens the Find tasks page, which the quickstart and the find-and-steer guide now name; the quickstart troubleshooting row for a second process on the same .data now shows the new "already open in another process" message; --offline-pglite and the configuration recipe mention the lock.
• Threat model: two rows. People management (admin-only actions, exact subject with the configured issuer, no self-change so an administrator always remains, sessions deleted on deactivation, audited) and the embedded-database lock (what it prevents, and the reused-process-number caveat). This closes the unticked box from Claude/UI workflow redesign #64.
• Compatibility: the operating-systems row now says the full suite runs on Linux and an informational platforms job runs a subset on macOS and Windows, so those stay unverified until it has been green.
• Glossary: an Identifier (ID) entry linking to the Identifiers section of the console guide.
• Screenshots: regenerated all eight images in docs/images/ (home, agents, approval, approval-delivered, audit, chat, flows, tasks) at their original sizes. They showed the old nine-item sidebar and version 0.1.1. They were rebuilt from a production build of current main with the demo agents: the showcase agent's approved "please approve the deploy" task plus a "need form" task in one context. The audit image now shows Administration → Audit trail.

Docs and images only; no code change.

How it was verified

• Every relative link and anchor in the changed Markdown files resolves (script check; one reported anchor in the glossary is on an underscore heading I did not touch and is a limitation of my slug check).
• Looked at each regenerated screenshot: new sidebar grouping, ID labels and copy icons, Administration tabs, version v0.2.0.
• Rebuilt .next from the current checkout first, because the build in the working directory was older than the source and produced a database error when seeding.

Not verified: screenshots were taken in Chromium at 1280px light only. The informational macOS and Windows job has not yet run on main, so the compatibility wording is deliberately cautious.

Checklist

• Focused change, with tests in the same change (docs and images only; no behavior change)
• npm run check passes (or the part you could run is listed above) — not run; no code changed
• Docs updated for the behavior you changed, per docs/contributing/documentation.md (or say why none apply)
• Security-relevant changes update docs/security/threat-model.md
• User-visible changes are in CHANGELOG.md (not applicable: docs only)

---

Generated by Claude Code