Connectors: a failed connector's error text is only reachable by hand-selecting it #2027

Implementation: FlyBot (ours) — PR follows within 24h. Do not pick up without a pickup-ok comment on this issue.

Written-by: FlyBot Lead
Claimed-by: FlyBot Lead
Claim-Id: db3db67d2c824345bf5577b2fd3de232
Branch: dev/1-connector-error-copy
Base: e807b26
At: 2026-11-01T11:06:25Z

Implementation: FlyBot (ours) — PR follows within 24h. Do not pick up without a pickup-ok comment.

Written-by: FlyBot Lead

What

Since #2022 a connector row in the error state can carry up to 2,000 characters of the host's own failure text (REASON_MAX, host/connectors.js), but the row's only actions are Try again and Disconnect. The text is drawn as one wrapping status span (client/connectors.js:43 → bt-connector-status, white-space: normal), so a person who wants to hand that sentence to someone — paste it in a chat, send it to whoever runs the gateway — has to select it by hand, which on a phone is close to impossible.

Proposal

Add a Copy error button to the row while connector.state === 'error', next to Try again:

• copy the exact stored text the row displays (connector.error), not a re-worded summary;
• use copiedToClipboard() from core/src/shared/remote-label.js:252, which returns true/false and never reports a quiet success (UI: a click-through found a wrapping settings drawer, protocol text in previews, blank first-paint chats and a cut-off failure #1347);
• on true the button reads Copied (key already exists in client/i18n.js), on false it reads Could not copy the error and stays readable — no silent success, no exception escaping into the row.

Acceptance (red first, on the live base)

1. With a connector in error state carrying the 2,000-character stored text, clicking Copy error hands the full stored text to navigator.clipboard.writeText, and the button then reads Copied.
2. With no clipboard (no navigator.clipboard, or writeText not a function) or with writeText rejecting, the button reads Could not copy the error and never Copied.
3. A connector that is ready or off renders no Copy error button; a row in error still renders Try again and Disconnect unchanged.

Each of 1–3 must be red on the base commit with only the new test file added, and green at the tip. Put the red-first output and one mutation per assertion in the PR body.

Scope

• core/src/client/connectors.js — the button and its state.
• core/src/client/i18n.js — ZH entries for Copy error and Could not copy the error (Copied already exists).
• core/test/connectors-page.test.js — new file; follow the esbuild + stub rendering pattern of core/test/schedules-client.test.js.
• core/client.js and patches/ds-bot/0008-client-bundle.patch — generate output only.
• changelog.d/<issue>-connector-error-copy.fixed.md.
• Do not create patches/ds-bot/files/src/client/connectors.js: checked on e807b261, that mirror does not exist (35 mirrors under files/src/client/, connectors.js is not one of them); it ships inside the 0008 bundle.

Dedup (live main e807b2616cf91a3546ebd460cffbb7325d2dc279, 2026-11-01)

• grep -n "Copy error" core/src/client/connectors.js core/src/client/i18n.js → 0 hits; copiedToClipboard is not imported by connectors.js.
• GitHub issue search repo:ThinkFlowLab/FlyBot connector error clipboard → 1 hit, #504 (invite/friend-chat polish, closed, unrelated).

Notes

• Base is e807b261; if main moves before the PR opens, rebase and re-run the red-first on the new base.
• Do not touch the 2,000-character window itself: this issue is only about making the text reachable.