Settings: Renewals on the unified topic page
Renewals uses the shared header and the topic page. TEST company only.
2 Oct 2026 · branch settings-renewals-topic-pr · captured against propflow-stage · at fb263e63e0c
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 · Company scope: Company first, on the topic page's fixed tracks
The settings header's tabs sit above the grid; the grid's own in-table tabs are gone. Company is the first column on fixed tracks (no lone caption row once Split view ships, #15887).
Asserted in the captured DOM — Company · Open renewal · Renewals
Sections 2–3
2 · Building scope: the page still names itself "Renewals"
A TEST building picked and focused (scope=property). The top bar's title reads Renewals (the old building page said "Renewals & collections"), Company stays first, and the building's box sits beside it.
Asserted in the captured DOM — Renewals · Company · Open renewal
3 · Company and three TEST buildings: columns on fixed tracks
Three buildings side by side, each its own column on fixed tracks; a building whose Renewals is off would show the module-off sentence in its column instead of a box (pinned by renewals-scoped-page.test.tsx — no TEST building has Renewals off, and this capture does not change data to fake one).
Asserted in the captured DOM — Company · Open renewal
