# Matching-result count localisation

4 November 2026. Source `9bfc51b067c4da4164b84578f5dacf452125ba62`, after published discovery workflow receipted4ce4cc. V22 was reproduced in a real tracked-row capture and confirmed at the shared JobTable table/board count caller.

Add paired literal `jobsMatchingSingle` text (`{count} matching job` / `{count} jobb samsvarer`) for exactly1. Preserve the plural key and count0/2+, active view's actual count, hidden loading/refresh/error count and Trash behavior. Both translator calls are literal; no new dynamic translation key. Query, pagination, filtering, membership, revisions, status writes, provider acquisition and UI/generated-content language ownership remain unchanged.

RED: four singular cases failed and eight zero/plural cases passed; six older cases filtered. The initial test also assumed locale switching never re-fetches, but both existing resource owners explicitly depend on `t`. Preserve that existing behavior; correct the test scope to verify live text/membership and no reads of the inactive view. Initial assumption failure retained separately. Three older tests encoded the wrong English singular and were corrected. The first combined native command used a nonexistent catalogue test path (45 cases passed, command failed); the corrected full targeted run below supersedes it.

PASSED:48 native cases/four suites (18 table/board integration including12 new EN/NB×table/board×0/1/2 live-locale cases; remaining table-density, grouped-board and catalogue cases), type-check, full lint, export build and scoped verifier lint. No overlapping failed/focused run is added to48.

PASSED:36 configurations/72 actual table/board count states at all nine widths/EN/NB/themes. One-record labels are visible in both views; zero status/mutation requests, unexpected writes, page exceptions or axe violations. The count-only scope explicitly leaves detail, alias and mutation workflows NOT RUN. The prior36/144 discovery-to-tracker journey remains bound to the unchanged callback sourcea84/ed4 rather than being repeated for a text-only correction. All API results are synthetic; no backend/provider/native-language/human/device/European/security/release qualification is inferred.

Rollback reverts the paired catalogue entry/shared count selection and associated expected labels; no data, dependency or migration rollback. Final A3/Phase10 and remaining route/error/journey/security/recovery/release/owner gates remain OPEN.