# Duplicate Record

## Objective

Start from something that already works instead of rebuilding it.

A duplicate action on records that copies the content worth keeping and deliberately drops everything that must not be shared.

## 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. Define the copy rules per record type explicitly. A blanket field copy will carry over ids, timestamps, audit trails, ownership, and secrets — all of which must be reset or excluded.
2. Never copy API keys, tokens, credentials, or anything encrypted at rest. A copy is a new secret or no secret; it is never the same secret.
3. Generate a non-conflicting name and slug, and show the user what it will be before they confirm.
4. State clearly in the confirmation what is and is not included — child records, attachments, comments, permissions, schedules. Ambiguity here produces support tickets.
5. Run the duplication in a single transaction. A half-copied record is worse than a failed copy.
6. Do not silently re-activate anything: a copy of a live, scheduled, or published record must start inactive and draft.

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

- Deep hierarchies must have a documented depth limit, or one duplicate can clone half the database.
- Copying counters, view counts, analytics, and history is almost never wanted — reset them.
- Attachments should be referenced or re-uploaded by an explicit rule; deleting the original must not break the copy.
- The duplicate must respect quotas — if the plan limit is reached, refuse before writing anything.
- Cross-workspace duplication must re-map or drop references to users and objects that do not exist in the destination.
- A record the user may view but not create in that container must not be duplicable.

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

- [ ] Ids, audit fields, ownership, and secrets are never carried into the copy.
- [ ] The generated name and slug do not collide with an existing record.
- [ ] The confirmation states exactly what is included and excluded.
- [ ] Duplication is atomic — a failure leaves nothing behind.
- [ ] Copies start in a draft or inactive state.
- [ ] Plan and permission limits are enforced before any write.
- [ ] 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.