> For the complete documentation index, see [llms.txt](https://klassdocs.gitbook.io/klassapp-documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://klassdocs.gitbook.io/klassapp-documentation/design/system/klassapp-handoff-2026-09-28.md).

# KlassApp handoff — 2026-09-28 (base dbe68419)

Read in this order:

1. `A-handoff-app-resync.md`: Task A. App component library resync in 5 phases, each with acceptance checks. It includes the `<x-empty-state>` recommendation and the table and badge tokens.
2. `B-handoff-emails-public.md`: Task B. Email shell and public pages.
3. `B-copy-corrections-production.md`: proposed production copy fixes (C1–C3 required, O1–O5 optional). **Not applied. Nothing in this bundle writes data.**

Code and previews:

* `B-emails-code/`: drop-in files that mirror repo paths (mail theme CSS, `vendor/mail/html` components, email views, `App\Support\MailContent`, logo PNGs).
* `concepts/emails/index.html`: every email at 600 and 375, the plain-text versions, and dark-mode and images-off toggles. `contrast.md` has the computed ratios.
* `concepts/public-pages/index.html`: proposed public pages at 1280 and 375. `screens/*.html` open standalone, and `pp.css` mirrors `auth-preview.css` with the contrast fixes marked `FIX`.

**Open these over a local server** (for example `npx serve .`). The review pages load their data with `fetch`, and that doesn't work from `file://`.

`concepts/public-pages/index.html` also shows the staging screenshots in its "Now" column. They weren't copied into this bundle, so those images appear broken here.

Contrast values are computed from hex values. Pixel sizes are specified geometry, so measure them in the rendered output before merging.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://klassdocs.gitbook.io/klassapp-documentation/design/system/klassapp-handoff-2026-09-28.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.