feat(admin-frontend): paginação da lista de pessoas atendidas (#155, frontend)

.claude/skills/agenza-frontend-slice/SKILL.md

@@ -56,8 +56,8 @@ enforces it together with the layer direction. It only inspects files inside `ap
 `widgets/` and `shared/` — `src/main.tsx`, `src/test/`, `e2e/` and config files are on review.
 
 Direction is `app → features → widgets → shared`, and inside a slice `ui → model | api`,
-`api → model`. A domain type never lives in `api/`. `widgets/` imports only `shared/`; `shared/`
-imports none of the others.
+`api → model`. A domain type never lives in `api/`. `widgets/` imports `shared/` and, to compose one, another widget (never a cycle);
+`shared/` imports none of the others.
 
 ## 3. Route wiring
 
@@ -70,8 +70,9 @@ page-owned state. Nothing implements this yet; you are writing the first one. Sh
 ## 4. Pages are shells
 
 `<Page>.tsx` holds no `useState`, `useEffect` or `useRef` of its own. All of it lives in that page's
-**own** hook. Hooks are never shared between pages — the single exception is a pure Context accessor
-like `useAuth`. Two pages wanting the same logic means the logic is a pure function for `model/`, not
+**own** hook. Hooks are never shared between pages — the exceptions are a pure Context accessor
+like `useAuth` and a generic hook with no domain in a widget, such as `usePaginatedList` (ADR 0071), which
+a paged list's hook calls with its initial filters and repository `list` (ADR 0072: the hook keeps that state, not the URL). Two pages wanting the same logic means the logic is a pure function for `model/`, not
 a shared hook. Details, sub-component placement and the StrictMode guards:
 [references/pages.md](references/pages.md).
 

.claude/skills/agenza-frontend-slice/references/pages.md

@@ -30,8 +30,11 @@ single-use code) with a terse *why* comment. That guard has to live somewhere it
 without rendering a route tree — the hook. Spread across a component body, it becomes a race you
 rediscover in production.
 
-**Hooks are never shared between pages.** The one exception is a pure Context accessor like
-`useAuth`. If two pages want the same behaviour, extract the *pure* part into `model/` as a plain
+**Hooks are never shared between pages.** The exceptions are a pure Context accessor like
+`useAuth`, and a generic hook with no domain that a widget exports, such as `usePaginatedList` in
+`widgets/paginated-list-section` (ADR 0071): a paged list declares its filters in `model/` as an
+interface, and its page hook passes the initial filters and the repository's `list` to
+`usePaginatedList`, which keeps the filters, the page and the size in its own state (ADR 0072). If two pages want the same behaviour, extract the *pure* part into `model/` as a plain
 function and let each hook call it. A `useSharedThing` imported by two pages is the smell that ends
 with one page's lifecycle quietly driving another's.
 

.claude/skills/agenza-ptbr-copy/SKILL.md

@@ -84,7 +84,7 @@ i18n layer to "prepare" for a language nobody asked for.
 The one exception: a **code → message map is data, not markup**. It belongs in the slice's `model/`,
 where it is pure and testable without React, next to the branch that consumes it.
 
-**Formatters live in `src/shared/format/`** (`date.ts`, `age.ts`) — cross-cutting, no business rule,
+**Formatters live in `src/shared/format/`** (`date.ts`, `age.ts`, `count.ts`) — cross-cutting, no business rule,
 so `shared/` by the dependency direction in
 [`docs/ARCHITECTURE.md` §1](../../../apps/admin-frontend/docs/ARCHITECTURE.md). A value with its own
 validation and limits (CPF, phone, e-mail, birth date) is not a formatter: its mask and parse live with

.claude/skills/agenza-ptbr-copy/references/formatting.md

@@ -130,7 +130,8 @@ whether she has to leave now.
 
 Use `Intl.PluralRules(LOCALE)` rather than `n === 1`. CLDR's rule for `pt` is `i = 0..1 → one`, so
 `select(0)` returns `'one'` — the opposite of the English instinct, and worth confirming in a
-one-liner before you depend on it.
+one-liner before you depend on it. In `admin-frontend` that is `formatCount(count, { singular, plural })`
+in `shared/format/count.ts` ("1 pessoa", "1.234 pessoas"), beside `formatNumber`.
 
 Better still: **never render a zero count.** Zero is an empty state, and "Nenhum serviço ainda" says
 more than "0 serviços". → [`states.md`](states.md)

.claude/skills/agenza-testing/references/patterns.md

@@ -33,6 +33,9 @@ and TypeScript keeps the literal types.
 Fixture builders live in [`src/test/oidcUser.ts`](../../../../apps/admin-frontend/src/test/oidcUser.ts)
 (`makePrincipal`, `makeOidcUser`, `makeAccessToken`). Add to that file rather than hand-rolling a
 principal in a test; a token built by hand tends to be missing exactly the claim under test.
+Beside it, `src/test/pending.ts` gives a promise the test resolves by hand (`pending<T>()`, for an
+answer that arrives after another) and `src/test/footerSkeleton.ts` finds the paged list's footer
+skeleton; import them instead of declaring a copy in the test file.
 
 ---
 
@@ -224,6 +227,9 @@ async function loginAsDemoUser(page: Page) {
 
 Rules that keep these green:
 
+- **Read the demo login from the seed's own config.** `DEMO_EMAIL` and `DEMO_PASSWORD` come from
+  `DemoTenant` in identity-service's `appsettings.Development.json`, the values its seeder creates the
+  user from; never type them again in a spec.
 - **Read seeded ids from the running system.** The demo tenant's id is generated fresh on every
   seed; the live file decodes it out of the issued access token instead of asserting a constant.
 - **Prefer a reload over waiting out a real clock.** Session persistence is proven by reloading and

apps/admin-frontend/AGENTS.md

@@ -38,7 +38,17 @@ ainda. Crie-os quando uma segunda feature precisar da mesma entidade, não antes
 
 **Páginas são cascas.** `<Page>.tsx` não tem `useState`, `useEffect` nem `useRef` próprios; toda a
 lógica mora no hook **daquela** página (`use<Page>.ts`). Hooks não são compartilhados entre páginas —
-a única exceção é um acessor puro de contexto como `useAuth`.
+as exceções são um acessor puro de contexto como `useAuth` e um hook genérico, sem domínio, num widget, como o
+`usePaginatedList` de `widgets/paginated-list-section` ([ADR 0071](../../docs/adr/0071-admin-frontend-paged-list-hook.md)).
+Uma lista paginada declara a interface dos seus filtros em `model/`, e o hook da página só passa os filtros
+iniciais e o repositório ao `usePaginatedList`, que guarda filtros, página e tamanho no próprio estado, fora da URL
+([ADR 0072](../../docs/adr/0072-admin-frontend-paged-list-state-in-the-hook.md)).
+
+**Buscar no backend é uma ação, não uma reação.** O `usePaginatedList` só pede uma página quando uma ação manda
+(`applyFilters`, troca de página ou de tamanho, "Tentar novamente"), na montagem e para corrigir uma página além da
+última. Nenhum efeito depende do estado dele: não acrescente um `useEffect` com dependências que dispare
+`fetchPage`, e uma ação nova passa pelo `request` do hook, conforme a
+[ADR 0073](../../docs/adr/0073-admin-frontend-paged-list-asks-only-when-told.md).
 
 **`loader` e `action` moram em `ui/pages/<Page>/route.ts`** e são reexportados pelo barril, para que
 `app/routes.tsx` os importe via `@/features/<slice>` e a direção continue `app → features`.