GitHub Issue: Polish Dashboard Captures & Demo UX for Release Readiness

A recent GitHub issue details a focused push to polish the dashboard and command-line interface (CLI) media assets for a more professional release presentation. The core change is the addition of a screenshot-only `capture=1` mode, which allows dashboard captures to display all navigation groups fully expanded without altering the default runtime behavior for users. This directly addresses a key weakness: previous screenshots and terminal demos were flattening important sections, hiding the full navigation structure, and appearing too much like internal development artifacts rather than polished release materials.

The changes are comprehensive and user-facing. The Risk Overview layout has been strengthened with clearer collapsible headers for sections like 'Top Attack Paths' and 'Exposure KPIs,' alongside improved affordances for drilling down into attack paths. For the CLI demo, the terminal output GIF has been slowed down, better sectioned, and now shows the actual package-check CVE table instead of a quiet, less informative output. Documentation has also been tightened, with updates to the self-hosted README and capture instructions focusing on the promoted EKS rollout components: scan, fleet/runtime, proxy, gateway, and the operator plane.

This work signals a transition from internal development to external presentation, aiming to ensure that promotional screenshots, demo videos, and documentation reflect a complete and professional product. The fixes, including a grammar correction for local DB status messages to prevent release media from showing `vulnerability/vulnerabilities`, are minor but indicative of a broader scrutiny on detail. The effort underscores the pressure to present a cohesive and mature front for what appears to be a significant rollout, likely tied to a Kubernetes (EKS) deployment strategy.