# Subscription Cancellation Flow

## Objective

Let people cancel without hiding what happens to their access and data.

A cancellation path that states the effective date, remaining access, data retention and any money involved, and can be undone before it takes effect.

## 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. Offer the choice between cancelling at the end of the paid period and cancelling immediately, and say what each one costs. Default to end-of-period.
2. Disclose, on the confirmation screen, what happens to the account's data, how long it is retained, what access remains until the effective date, and whether anything is refundable.
3. Let the user reverse the cancellation at any point before the effective date, and show the pending state everywhere the plan is displayed.
4. Keep any reason survey optional and place it after the cancellation is already recorded. Do NOT gate the action behind a survey, a retention offer, or a support conversation — that converts churn into chargebacks.
5. Subscription state, webhooks and payment methods are owned by Billing Portal; drive this flow from that state rather than tracking your own. Its rule that cancelled users keep access until the paid period ends still applies here.

## 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 cancellation that is scheduled but not yet effective is a distinct state. The UI must not describe the account as already cancelled or as fully active.
- Immediate cancellation mid-period may generate a credit or may forfeit the remainder. Which one it is must be shown before confirming, not discovered afterwards.
- An account already in a failed-payment grace period is cancelling from a different position. Do not promise access it does not have.
- Cancellation by one admin affects every member of the workspace. Notify the owner, and refuse it from members who lack the permission.
- The user may resubscribe before the effective date. Treat that as reversing the cancellation, not as a new subscription with a fresh trial.
- If the provider call fails, the subscription is not cancelled. Report the failure — a confirmation screen shown over a failed request is the worst outcome here.

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

- [ ] The user can choose between immediate and end-of-period cancellation, with the consequence of each stated.
- [ ] The confirmation screen names the effective date, remaining access, data retention and any refund or credit.
- [ ] A scheduled cancellation can be reversed by the user until its effective date.
- [ ] No step of the flow requires answering a survey or contacting a human.
- [ ] Pending cancellation is shown as its own state wherever plan status appears.
- [ ] A failed provider call leaves the subscription unchanged and says so.
- [ ] 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.