# Certificate Generator

## Objective

Issue a personalised certificate people can download, print, or share on completion.

A certificate record and rendered document tied to a completed achievement, with a public verification page.

## 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. Trigger issuance from the achievement the app already tracks, so a certificate exists because something was completed rather than because someone visited a page.
2. Store the recipient name, achievement title, issue date, and issuer details on the certificate record itself. Reading them from live accounts means a name change would rewrite certificates already in circulation.
3. Render through the app's existing PDF Export path and reuse the app's brand assets rather than introducing a second set of fonts and logos.
4. Give every certificate a stable public verification URL that shows what was issued, to whom, when, and whether it is still valid.
5. Do not put personal data beyond the recipient's name and the achievement on the public verification page. It is a link people paste into profiles and it will be crawled.

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

- Long names, long course titles, and names in scripts with tall glyphs will overrun a fixed-width line and collide with the border. Shrink or wrap within a defined box and test with a name of sixty characters before shipping.
- A certificate with no way to check it is worth nothing to the person reading it. Give each one a verification page reachable from an identifier printed on the document, and keep that page working even after the recipient's account is closed.
- When the underlying achievement is revoked, corrected, or retaken, the old certificate must be marked revoked or superseded on the verification page rather than silently deleted, because copies are already downloaded and circulating.
- A document rendered at screen resolution prints blurry and looks cheap. Render at print resolution with vector text and embedded fonts, and size the page to a standard sheet.
- Editing the template must not alter certificates already issued. Version the design and keep each certificate bound to the version it was issued under, so a redesign does not rewrite history.
- The verification identifier must not be sequential or guessable, or anyone can enumerate every certificate the app has ever issued.
- Recipients will share the certificate on social platforms, so the verification page needs a title and preview image that render sensibly when unfurled.
- A recipient who downloads twice should get the same document, not a freshly dated one.

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

- [ ] Completing the tracked achievement issues a certificate with the recipient and date recorded on it.
- [ ] Names and titles up to a defined length render inside the layout without overlap or clipping.
- [ ] Every certificate carries an identifier that resolves to a public verification page.
- [ ] Revoking or superseding an achievement is reflected on the verification page.
- [ ] Documents render at print resolution on a standard page size with embedded fonts.
- [ ] Template changes are versioned and do not alter previously issued certificates.
- [ ] Verification identifiers cannot be enumerated.
- [ ] 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.