Knowledge requests — From onboarding (fill blanks only, part 1)

A live company answers onboarding questions that never got an answer, once; before go-live this tab points to Onboarding

23 Oct 2026 · branch feat/knowledge-requests-live-leftovers · captured against propflow-stage · at e1b6466c2ff+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 · Not live yet (the TEST company): the tab points to Onboarding

The third tab and its rail row. Before go-live the onboarding pages are where these questions are answered, so the tab sends the customer there and asks nothing itself.

Asserted in the captured DOM — From onboarding · These are on your Onboarding pages · Answer them there until you go live. · Open Onboarding. The tab, its pointer and the action are on screen.

Not live yet (the TEST company): the tab points to Onboarding
Sections 2–2 and notes

2 · Phone width

Nothing scrolls sideways.

Asserted in the captured DOM — Open Onboarding

Phone width

What is not in the picture

The live state is not captured: stage's TEST company is not live, and making it live would change how Clara treats it. The live list (never-answered phone-system questions asked through the hub's own card, the rest listed for Propflow) and the server's fill-blank rule (live + empty saves; live + answered or clearing refuses; not live unchanged) are pinned by the DOM and route tests.

PropFlow Docs