chore: articles localization groundwork

docs/design/routes.md

@@ -81,3 +81,9 @@ Needs backend:
 | /account/email/confirm?c=CODE | Verify new email (AuthCard). States in screens/account.md | Session required; without one, inline log in (as /register/validate) | POST /v1/auth/email/confirm |
 | /profile | Gains change email, Your data, Danger zone | Any verified user | POST /v1/auth/email/change, POST /v1/auth/email/resend, DELETE /v1/auth/email/change, GET /v1/user/me/export, DELETE /v1/user/me |
 | /login?reason=account-deleted | One-time message after deletion | Public | none |
+
+## Localization target routes
+
+See [localization.md](localization.md) for authoritative API and compatibility decisions. SPA: `/settings/sites/:key/languages`, `/articles?site=&lang=&tab=all|missing|review&q=&status=&author=&seo=&page=&size=`, `/article/:id/edit?ref=:sourceId`, and `?dialog=add-translation&lang=fr`. Existing `/article/new` entry remains; do not introduce `/articles/new`. Existing guards and per-version permissions remain binding. Language settings are owner-managed; readable language metadata for editors uses the permitted site metadata surface. `author` filtering is a proposed extension, not an existing API capability.
+
+Use only `lang` and `tab` for localization list selection; no `mode` or `needs_review` synonym. No language means grouped story mode for authenticated editorial lists; `lang` selects versions; `tab=missing` selects stories without a readable selected-language version; `tab=review` selects needs-review results in the active mode. Public listing compatibility is preserved separately.