The inbox step — both connect buttons, and the quiet PropFlow-outbound option
Lane M, part 1b-2: Continue with Google connects the inbox again, and a link under the buttons offers to keep Clara reading this inbox while she writes from a PropFlow address.
18 Sept 2026 · branch onboarding/m1b2-propflow-outbound-option · captured against propflow-stage · at 1cbbae0da8
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 · State 1 — the default: their own inbox, both buttons, the quiet option
Flow map ch.4, state 1. Continue with Google is back and above Microsoft — since #9373 its consent asks for Gmail read + send and stores a mailbox, so it connects the inbox rather than the calendar that Gera pressed into on 2026-09-18.
Under the buttons, the quiet option as a plain link — Prefer Clara to write from a PropFlow address? We'll still read this inbox.
Not a card, not a picker: Gera asked for hidden-but-available. The sentence under the title says both halves of what the connection is for, and the card's after-line offers Skip because the footer is actually offering one.
Asserted in the captured DOM — Connect the inbox Clara works from · Clara reads new leads here and replies from this address · Continue with Google · Continue with Microsoft · Prefer Clara to write from a PropFlow address? We'll still read this inbox. · Skip for now. The title, both halves of the sentence, BOTH connect buttons, the quiet option's exact copy, and Skip. The link is the new control this PR exists for.
2 · The same screen at phone width — one viewport
Title, sentence, card, both buttons, the quiet-option link, and the footer with Skip for now — all inside one phone viewport.
Asserted in the captured DOM — Connect the inbox Clara works from · Continue with Google · Prefer Clara to write from a PropFlow address? · Skip for now
3 · Connected — and the after-line stops naming a button that is not there
The same h1 becomes Leasing inbox connected
. The card's after-line now follows whether a Skip is actually offered (#9367's round-2 finding): on this screen there is no Skip, so it points at Settings instead of naming a button that is not on the frame.
Asserted in the captured DOM — Leasing inbox connected · Clara now answers from this inbox. · Continue
State 2 is on its own page, and why
The PropFlow-outbound state is captured separately (pr-9443-propflow-evidence): the toggle's route is centralized-only and refuses once Clara is live, and neither stage organization this capture tool can sign in as satisfies both — the staff sentinel org has no operatingModel and the customer-admin identity's org is already live. Photographing the click itself would mean changing a shared fixture's operating model, so the second page reaches the same state the other way the ruling allows (staff choosing the PropFlow address on the customer page), which renders through the identical code path. The click itself — one POST, the server's answer driving the sentence, the card and the link, and the buttons staying — is pinned in company-step.test.tsx.