# Frontend Page → Screen Doc Parity Check (reverse direction)

## Context

App: {{APP_NAME}}
Frontend pages: {{FRONTEND_PAGES}}
Screen docs: {{SCREEN_DOCS}}

Check whether each implemented frontend page has a corresponding screen doc, and
report pages that have none.

## Instructions

1. List the `page.tsx` files at the paths above and their directory structure.
   Filenames/paths are enough to detect a missing doc; read page bodies only when
   disambiguating a borderline name match.
2. Read the screen doc filenames (basenames) at the paths above.
3. For each page, check whether a corresponding screen doc exists.
4. Return results as JSON per the Output Format section.

## Parity Check

| Check ID   | Question                                            |
| ---------- | --------------------------------------------------- |
| doc_exists | Does a screen doc exist for each implemented page?  |

For each `page.tsx`, derive the screen identity from its route relative to
`frontend/src/pages/` — directory segments form the route, and `[id]/page.tsx`
is the detail view of its parent segment (see the **Screen Type → File Pattern**
table in [screen-doc-code-parity.md](screen-doc-code-parity.md) for the
mapping). Look for a screen doc whose basename corresponds.
If one is found → `pass`; if none → `fail` (`source` = page path, `target` =
`"missing"`).

## Output Format

Return a JSON object with `check_type: "page-screen-doc-parity"` plus the
standard `gaps`, `inconsistencies`, and `summary` fields. Each gap sets `source`
to the page path, `target` to `"missing"`, and `check` to `doc_exists`. See
[impl-parity-report-format.md](impl-parity-report-format.md) for the full schema
and field definitions.
