{# Executive — Scan plan panel (Overview only). Mirrors the CLI's Phase-0 scan-plan board (``ui/scan_plan.py``) so the first thing an operator reads on the dashboard is the same plan they confirmed in the terminal. Replaced the framework-internal "Scan identity" fingerprint card (SCAN_ID / SEED / GUARDIAN / AIVSS / PROBES / TARGET / EVIDENCE) — those internal version pins were noise for end users. Grouped into the same six sections as the CLI: TARGET — URL, Mode, Reachable, Multi-agent MODELS — Attacker, Evaluator, Commander (+ validated indicator) BUDGET — Mode, Wall-clock cap, USD cap, Estimated cost OUTPUTS — --output DASHBOARD — URL, Server status SAFETY GUARDS — RoE blocklist, Authorization, Egress policy Payload (``scan_plan``) is assembled in ``dashboard_view._build_scan_plan``; any field the persisted scan record cannot supply renders as "—" rather than being fabricated. #}

Scan plan

{# Target URL gets its own full-width row — it's the longest value and would wrap character-by-character if squeezed into one of the side-by-side columns below. #}
URL
{{ scan_plan.target.url }}
{# TARGET #}

TARGET

Mode
{{ scan_plan.target.mode }}
Reachable
{{ scan_plan.target.reachable }}
Multi-agent
{{ scan_plan.target.multi_agent }}
{# MODELS — each role carries a validated indicator. #}

MODELS

Attacker
{{ scan_plan.models.attacker }} {{ scan_plan.models.validated }}
Evaluator
{{ scan_plan.models.evaluator }} {{ scan_plan.models.validated }}
Commander
{{ scan_plan.models.commander }} {{ scan_plan.models.validated }}
{# BUDGET #}

BUDGET

Mode
{{ scan_plan.budget.mode }}
Wall-clock cap
{{ scan_plan.budget.wall_cap }}
USD cap
{{ scan_plan.budget.usd_cap }}
Estimated cost
{{ scan_plan.budget.estimated_cost }}
{# OUTPUTS #}

OUTPUTS

--output
{{ scan_plan.outputs.output }}
{# DASHBOARD #}

DASHBOARD

URL
{{ scan_plan.dashboard.url }}
Server status
{{ scan_plan.dashboard.server_status }}
{# SAFETY GUARDS #}

SAFETY GUARDS

RoE blocklist
{{ scan_plan.safety.roe_blocklist }}
Authorization
{{ scan_plan.safety.authorization }}
Egress policy
{{ scan_plan.safety.egress_policy }}