frontend-handofflisted

# Frontend handoff (docs for the frontend developer) Run this **after the full, final implementation** is done and the gates are green (after `final-check`). It produces the documentation a frontend developer reads, then hands to their own AI to build the UI against this backend and the design. ## Audience & language - The reader is a **human frontend developer** who studies the doc, then passes it to their AI to compose the backend contract + design into a frontend. - **Write these docs in Russian** — they are a human handoff, an explicit exception to the English-artifact rule. Keep endpoint paths, field names, enum values, and HTTP details in English (that is the contract). - **No frontend code.** No JS/TS, no components, no fetch snippets — the developer knows how to build. Describe *what / when / how / why / where* and the **contract**. JSON request/response **data** examples and field tables are encouraged (they are the contract, not code). - **Ground everything in the real implementation** — derive endpoints, request rules, response shape, auth, states, and visibility from the actual routes, `FormRequest`s, `JsonResource`s, enums, policies, and migrations you just built. Mark anything uncertain as an assumption; never invent a field or rule. See `${CLAUDE_SKILL_DIR}/../../guidelines/grounding-protocol.md`. ## When it applies Only when the change touches the **frontend-facing surface**: endpoints, request/validation rules, response shape, authorizati