# External Sync Status

## Objective

Tell users how current their synced data is instead of making them guess.

Per-connection sync run state showing what was last attempted, what last succeeded, and what failed.

## 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. Track last attempted and last successful sync as separate values. Collapsing them into one timestamp hides exactly the failure you need to see.
2. Record per-run counts: records created, updated, skipped, and failed. A run that half-worked is the common case, not the exception.
3. Give the sync run explicit states — queued, running, completed, completed with errors, failed — and show the current one.
4. Provide a manual re-sync that is disabled while a run is in progress, so repeated clicks cannot start overlapping runs against the same connection.
5. Describe freshness honestly. If you poll every fifteen minutes, say 'updated 12 minutes ago', not 'live'. Do NOT imply real-time when the data is polled.
6. Credential validity, missing scopes, and the reconnect flow are owned by Integration Connection Health. When a sync fails for auth reasons, hand off to that state rather than restating it.

## 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 run that dies without reporting leaves the state stuck on 'running'. Give runs a heartbeat or a maximum duration and mark stalled ones as failed.
- Partial failures need the failing records named or downloadable. 'Completed with 43 errors' is not actionable on its own.
- Timestamps must render in the viewer's time zone, and relative times must keep updating on a page that stays open.
- The first sync has no previous run. Show a first-run state, not 'never synced' in red.
- A long-running initial import will make freshness look terrible for hours. Distinguish an initial backfill from routine incremental syncs.
- Manual re-sync must be rate-limited per connection. Users will click it repeatedly during an outage and exhaust the provider quota.

## 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

- [ ] Last attempted and last successful sync are stored and displayed separately.
- [ ] Each run reports created, updated, skipped, and failed record counts.
- [ ] Failed records are inspectable, not just counted.
- [ ] Manual re-sync cannot start while a run is active and is rate-limited.
- [ ] Freshness wording matches the actual polling interval and never claims real-time.
- [ ] A stalled run transitions to a failed state within a bounded time.
- [ ] 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.