Agent evals: Leasing and Renewals are a filter, not two tabs
Admin → developer tools → Agent evals: one Scenario runs tab with a Domain filter in its toolbar.
2 Oct 2026 · branch fix/admin-dev-tabs-as-filters · captured against propflow-stage · at 7469116eb66+local
Data note. Every name and balance below comes from propflow-stage, which is anonymized by construction (ADR-0097/0110 — phones in the impossible +1000 NPA, emails @example.test). The identical capture against prod would carry real tenants' names and balances and is not safe to attach anywhere, which is why the generator refuses to run against one.
1 · 1 · The tab row: one Scenario runs tab, and a Domain filter on it
Before, the tab row carried Leasing · x/y and Renewals · x/y as two tabs over the same scenario table. Screen rule 8 (brand-and-design.md) refuses tabs that are really filters, so they are one Scenario runs tab, and the domain is picked in the table's toolbar with the same FilterDropdown the run picker beside it already uses. An old ?tab=leasing link still lands here with Leasing picked. The other tabs are separate panels with their own data, which rule 8 keeps.
Asserted in the captured DOM — Overview · Scenario runs · Acceptance · Domain
Sections 2–3
2 · 2 · The Domain filter open
The two domains, each with its latest run's pass count when one exists — the counts the tab labels used to carry. Picking Renewals rewrites the link to ?tab=renewals, so a copied URL still opens the table on screen.
Asserted in the captured DOM — Leasing · Renewals
3 · 3 · Email templates: unchanged, by ruling
The audit said this page used tabs to pick a template. It does not: the template is picked in a dropdown, and the two tabs switch between a live email preview and the written design guide — two different kinds of content, which screen rule 8 keeps (decision fac32e16a). No code change here.
Asserted in the captured DOM — Templates · Design guide
