# Print-Friendly View

## Objective

Make the pages people actually print come out clean.

Print styles for the screens users send to paper or PDF: invoices, reports, orders, summaries.

## 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. Identify the handful of screens people genuinely print. Do not attempt to style the whole app.
2. Hide navigation, sidebars, sticky headers, toolbars, and anything that only works when clicked.
3. Set page breaks so tables do not split a row, and headings do not land alone at the foot of a page.
4. Expand collapsed sections that carry meaning in print, and leave out the ones that are only screen conveniences.
5. Do not build a separate print page or a second template. A duplicate view drifts out of sync with the real one.

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

- Link text is useless on paper. Print the destination URL for links that matter and suppress it for navigation.
- Dark backgrounds and inverted panels waste ink. Print on white regardless of the active theme.
- Long tables need their header row repeated on each page.
- Include the generation date and the record identifier, so a printed copy can be traced back.
- Do not print internal admin controls, draft warnings, or debug information on a customer-facing document.
- Charts and images must fit the page width rather than being clipped at the margin.

## 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 key screens print with no navigation, controls, or sticky elements.
- [ ] Nothing is clipped at the page edge in A4 and Letter.
- [ ] Table headers repeat and rows do not split across pages.
- [ ] Printed output is legible in both light and dark themes.
- [ ] Each printed page carries a date and identifier.
- [ ] 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.