Fact 129
Morgan Chen requested a pasteable Figma reply for Mercury activation surface v0.2 that retains the settled failed-sync icon and CTA directions, reports the latest 320px source-unavailable clipping result, preserves the clipping, wrong-action, and state-clarity exceptions for nonblocking copy and icon polish, and routes queued-sync retry proof back to the Linear ledger until another clean logged or captured run closes the evidence gap.
Source evidence (1)
000657Jul 26, 2023 / 09:49 UTC-07:00
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.
Message 000657 in history