# Integration Connection Health

## Objective

Show at a glance whether each connected service actually still works.

A health state per integration connection that separates expired credentials, missing permissions, and provider outages.

## Before You Begin

This feature is being added to an application that already exists and already
works. Do not scaffold a new project, and do not assume a blank slate.

Inspect the codebase first and establish:

- The existing application structure and where code of this kind already lives.
- The framework and version in use.
- The existing design system — colours, spacing, typography, and component conventions.
- Existing UI components you can reuse instead of writing new ones.
- The existing database structure, if this feature needs to persist anything.
- The existing authentication and authorization system, if this feature is user-scoped.
- Dependencies already installed, so you don't add a library that duplicates one.
- The existing test setup and conventions.

Only start writing code once you understand the above. If the application
already implements part of this feature, extend it rather than replacing it.

## Implementation Instructions

1. Give every connection an explicit health state: healthy, needs reconnection, missing permission, provider unavailable, or never used.
2. Derive health from the last successful call, not from whether a token row exists. A stored token proves nothing — providers revoke without telling you.
3. Record the classified reason whenever a call fails, so the state has an explanation attached rather than being recomputed from guesswork.
4. Offer a reconnect action that repairs the existing connection in place, keeping its ID, settings, and mappings. Do NOT create a second connection on reconnect — that orphans everything attached to the first one.
5. Show the user a plain sentence about what to do. Never surface the provider's raw error body, which routinely contains tokens, internal URLs, and account identifiers.
6. Per-run sync freshness, record counts, and the manual sync button are owned by External Sync Status; link to it rather than duplicating it. Refresh-token mechanics are owned by OAuth Token Refresh Recovery.

## UI and UX Requirements

Match the application's existing design system exactly. Reuse its components,
spacing, and typography. This feature should look like it was always there.

## Responsive Requirements

Works on mobile, tablet, and desktop. Touch targets are large enough to hit on a
phone, and nothing overflows horizontally at 320px.

## Accessibility Requirements

- Fully keyboard navigable.
- Correct semantic elements and ARIA roles.
- Visible focus states.
- Meets WCAG AA contrast.
- Dynamic changes are announced to screen readers.
- Respects prefers-reduced-motion.

## Edge Cases

- A provider outage is not a broken connection. Do not tell the user to reconnect when the fix is to wait.
- A scope added to the app after a user connected leaves old connections technically valid but functionally incomplete. Detect the missing scope and ask for incremental consent, not a full teardown.
- A connection that has never been used has no last-success timestamp. Show 'not yet used' rather than an alarming red state.
- Rate limiting looks like failure. Treat it as a distinct, temporary state and do not degrade health for it.
- Health checks must not hammer the provider. Judge from real traffic, and probe on a schedule slow enough not to consume the user's quota.
- The person who sees the broken connection may not be the one who can fix it. Say who owns the connection and notify them.

## Testing

Exercise the feature end to end in the running application. Cover every edge case
above, then run the existing test suite and confirm nothing regressed.

## Acceptance Criteria

- [ ] Every connection displays one of the defined health states.
- [ ] Expired credentials, missing scopes, and provider outages are distinguishable in the UI.
- [ ] Health is computed from the last successful call, not token presence.
- [ ] Reconnecting preserves the connection's ID and configuration.
- [ ] No provider error body, token, or internal URL is shown to the user.
- [ ] Health checking does not measurably consume the user's provider rate limit.
- [ ] The feature matches the existing design system.
- [ ] No existing functionality is broken.

## Adaptation Rules

- Match the existing design system. Do not introduce a new colour palette,
  spacing scale, or component library.
- Reuse existing components and utilities wherever they fit.
- Follow the naming, file layout, and code style already present.
- Do not upgrade, replace, or remove existing dependencies to make this
  feature fit. Adapt the feature to the app, not the app to the feature.
- Do not break existing functionality. If a change is genuinely required in
  existing code, make the smallest one that works and say so.
- If something in these instructions conflicts with how the application is
  built, follow the application and explain the deviation.

## Final Verification

Before you report the work as done:

1. Re-read the acceptance criteria above and check each one against what you
   actually built.
2. Run the application and exercise the feature end to end.
3. Run the existing test suite and confirm you have broken nothing.
4. Check the feature on mobile, tablet, and desktop widths.
5. Check keyboard navigation and focus handling.
6. Summarize what changed: files added, files modified, and anything you
   deliberately did differently because of how this application is built.

If any acceptance criterion is unmet, fix it before reporting completion.