Knowledge requests — Vendors
Which job types each active vendor does, pre-filled from the company's own work orders; a save appends them to the preferred-vendor list after everyone already on it
23 Oct 2026 · branch feat/knowledge-requests-vendors · captured against propflow-stage · at 196e8d93a7a+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 · Desktop: the Vendors tab (TEST company: no vendor work yet)
The third tab, with its rail row. Stage's TEST company has no work orders assigned to a vendor, so the tab shows its two-sentence empty state. The populated card (rows, pre-picked job types with counts, the plain-words line about what saving does) is pinned by the DOM test, not captured.
Asserted in the captured DOM — Vendors · No vendor work orders yet · Vendors show here once they have had one of your work orders. · Back: Buildings. The tab, the empty state and Back/Next are on screen.
Sections 2–2 and notes
2 · Phone width
The chips wrap; nothing scrolls sideways.
Asserted in the captured DOM — No vendor work orders yet
What is not in the picture
No save was run. The TEST company on stage has no vendor work orders, so the populated rows could not be photographed; seeding work orders was not done. The rows, the pre-pick, the plain-words line and the merge (appended after existing entries, every other entry kept) are pinned by tests.