Test 074

Anna's new evidence table is finally more useful than the scattered screenshots were. Mercury dogfood evidence — invited-member and retry states, July 24 Owner: Anna Martinez Audience: internal Mercury operating group Cutoff: 2023-07-24 09:40 PT Rule used for this cut - Activated = real_source_connected OR first_live_sync_completed within 7 days. - sample_import_completed is excluded from activation. - invite_sent is supporting activity only. - This document is for internal operating evidence, not board/external use. Evidence rows ID | Account | Scenario | Evidence source | Observed state | Activation treatment | Notes IM-01 | DF-17 | Invited member, no real source on workspace | Screenshot 2023-07-22 10:14 PT + event log | "View setup guide" rendered; no owner CTA shown | Not activated; invite_sent only | Server role=member and source_state=none matched expected branch. IM-02 | DF-22 | Invited member, admin connected first real source before member's first visit | Screenshot 2023-07-22 16:41 PT + session trace | Member still rendered on invited-member guide path, not "Connect a data source" | Admin account counted from real_source_connected; invited member not separately activated | Good evidence that role + source state are not collapsing into the owner path, but still single-account coverage. IM-03 | DF-29 | Invited member with preview/sample data present from prior setup demo | Screenshot 2023-07-23 09:08 PT + event log | Sample area stayed visually separate/preview-only; member state still "View setup guide" | sample_import_completed present but excluded; not activated | Best current proof that sample data is not creating an activated-looking path. IM-04 | DF-31 | Invited member opens while admin has started setup but first live sync is not complete | Screenshot 2023-07-23 17:26 PT + worker log | Member remained on guide path while sync was pending; no false activated state | Not activated on member record; admin activation still tied to real_source_connected / later first_live_sync_completed | Helpful for the waiting-state edge, but we still do not have every invited-member role/source combination. QR-01 | DF-35 | Queued first sync, source unavailable on first attempt, then retry | Screen capture 2023-07-24 08:12 PT + job log | Queued state showed no fake percent/ETA; retry returned cleanly to queued and then completed | Activation already counted from real_source_connected within 7 days; retry did not create a second activation event | Real dogfood proof that retry can re-enter queued cleanly. QR-02 | DF-37 | Queued first sync, manual retry after timeout-class failure | Screen capture 2023-07-24 09:03 PT + job log | Retry action was idempotent; no duplicate jobs visible; state returned to queued without odd copy changes | real_source_connected already present; first_live_sync_completed still pending at cutoff | Better than last week because this is a second real retry attempt, but evidence is still light. FS-UR-01 | DF-41 | Failed sync normalized into unknown/retry bucket | Clean screenshot 2023-07-24 09:34 PT + UI capture | Neutral warning-circle state, "Try again" CTA, no raw vendor string exposed | Activation unchanged; sample import absent | First clean proof for the unknown/retry bucket. Useful, but still only one captured case. Coverage notes as of cutoff - Invited-member evidence is better organized, but four real accounts is still too small to call low-risk across all role/source-state combinations. - Queued-sync retry now has two real dogfood attempts instead of one; that supports using the path operationally, not calling it closed. - Unknown/retry failed-sync now has a clean screenshot. That closes the "no clean proof" gap, but not the broader confidence question. - Any rows with sample_import_completed were checked against the activation rule above and excluded from activation counts. Give me a concise reasoning pass, not a reply: what this supports operationally, what is still too thin to treat as closed, and what must stay out of board or external material.

The latest Figma comments are enough to close the design part and push the evidence gap back where it belongs. Figma comment thread — Mercury activation surface v0.2 File area: failed-sync + small-width states 2023-07-26 [09:12] Priya: Keeping the neutral warning-circle on failed sync. The broken-link direction is still too vendor-specific, and the retry arrow should stay an action affordance, not the main state icon. [09:19] Marcus: From the release-readiness side, the 320px source-unavailable clipping issue looks fixed in the latest frames. The body copy wraps cleanly now and the CTA/help text no longer collide at that width. [09:27] Leo Park: Visual direction seems fine. The one unknown/retry screenshot helps on failed-sync, but queued-sync retry proof is still thin even after Anna's July 24 evidence pass. Better than last week, but I would keep that row live in the ledger until we have another clean retry run tied to logs/screens or equivalent proof. [09:34] Priya: Agree. Also marking setup-guide copy polish and icon polish as follow-up, not dogfood gate, unless either one creates clipping/overlap, points to the wrong action, or makes the state meaning less clear again. Draft a pasteable Figma reply. Lock the neutral warning-circle and the settled CTA direction, say the 320px source-unavailable clipping looks fixed in the latest frames, keep setup-guide copy and icon polish as nonblocking follow-up unless they create clipping, wrong action, or state confusion, and send queued-sync retry proof back to the Linear ledger until another clean log/screen run closes that evidence gap.