Skip to content

Beginner UX: lead resilience page with plain-language reassurance - #11215

Merged
diegosouzapw merged 6 commits into
diegosouzapw:release/v3.8.50from
ignamiranda:contributor/feat/beginner-ux-resilience
Aug 23, 2026
Merged

Beginner UX: lead resilience page with plain-language reassurance#11215
diegosouzapw merged 6 commits into
diegosouzapw:release/v3.8.50from
ignamiranda:contributor/feat/beginner-ux-resilience

Conversation

@ignamiranda

Copy link
Copy Markdown
Contributor

What

Lead the connection resilience page with plain-language reassurance before breaker mechanics:

  • Reassurance heading + one-line explanation under the existing title: "Your connections recover automatically. Usually no action is needed. OmniRoute temporarily rests a connection after failures, then safely tries it again."
  • Three-state plain-language legend above the table:
    • Healthy — Requests can be sent
    • Cooling down — Trying again soon
    • Locked out — Needs your attention

No behavior changes. The technical table, timeline, and detail panel are untouched and remain available as advanced detail.

Why

The page currently opens with mechanics ("Backoff," "Circuit Open," HALF_OPEN probes) before saying what resilience protects or whether action is needed (source evidence: connections/page.tsx, ResilienceConnectionsClient.tsx, en.json resilienceConnections). Beginners cannot tell whether a cooling-down connection is broken or fine.

Validation

  • node --import tsx/esm --test tests/unit/resilience-connections-page-static.test.ts — 16/16 pass (incl. 2 new assertions: reassurance renders before the table; en.json carries the plain-language copy)
  • npm run lint
  • npm run typecheck:core
  • npm run i18n:check-ui-coverage

Closes #11212.

⚠️ base-red inherited: #9985

ignamiranda and others added 5 commits August 23, 2026 06:35
…zapw#11204)

Validated on the combined batch board: gates clean (changelog, file-size 159 frozen, complexity 2620<=2774, cognitive 1180<=1223, dead-code 409<=416), typecheck:core clean, i18n suites 16/16 after the vi translation pass. Two-string reframe that stops Embedded Services reading as required infrastructure. Thank you @ignamiranda!
…#11195)

Validated on the combined batch board: gates + typecheck clean, i18n suites 16/16. Pre-merge: the vi.json request-flow strings arrived in English — translated to Vietnamese on the branch (vi is the locale that requires real translations, not markers). Purpose-first API-key orientation with the request-path visual, controls unchanged. Part of diegosouzapw#11167. Thank you @ignamiranda!
…1206)

Validated on the combined batch board (CliConceptCard vitest 9/9 — the ACP warning never leaks onto Code/Agent cards) + this branch: i18n suites 16/16 with the Vietnamese translation of the new acp warning added here. ACP now reads as optional/advanced before its mechanics. Thank you @ignamiranda!
@diegosouzapw
diegosouzapw merged commit dfe73f4 into diegosouzapw:release/v3.8.50 Aug 23, 2026
4 of 7 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Beginner UX: translate resilience states into plain language

3 participants