feat(resource): admin UI for resources, types, skills and pools, plus real API docs

Four pages on the existing design system: a resources list whose branch/type/skill/
status filters live in the URL and go straight to the server, and three supporting
pages for types, skills and pools. Filtering client-side over a list the server had
already filtered would have been a second source of truth, so the page does neither.

The pool members dialog only offers resources from the pool's own branch and type —
the same rule the server enforces with 422, applied early so the user never reaches
the error. Skill assignment and pool membership are both full replacements, and both
say so in the dialog, because a partial-looking save that silently drops rows is
worse than an explicit one.

Wiring that was missing: deactivating a staff member through
PATCH /api/v1/staff/{uuid}/toggle now closes their resource too. Without it an
inactive operator would still have shown up in availability search. It is an explicit
call rather than a Doctrine lifecycle callback, since callbacks do not fire for
getArrayResult() — which is how every admin list is built — and that asymmetry is
its own bug. The reverse does not hold: closing a resource does not deactivate the
person, who may be purely administrative.

docs/api/resource.md documents all sixteen endpoints with responses captured from
real curl runs against ddev, including the 422 bodies for person-capacity and
non-scalar attributes. staff.md gains a "relationship to resources" section stating
that job_title is not a skill. tenancy.md contrasts these aggregate children —
whose roots do carry a tenant pair — with the branch_working_hours case from task 01,
where the root was global and the classification was wrong.

Also fixed a pre-existing flaky test: NumericFieldNormalizerTest guarded its random
mobile against collision on the never-reset db_test but not its random national code,
so a full-suite run could fail with 422 and close the EntityManager, taking an
unrelated test down with it. Both are now guarded, and the assertion prints the
server's response instead of a bare "422 is not 201".

Verified: phpunit 1119 tests / 3113 assertions green; slot-mode frozen contract green;
phpstan 14 errors before and after, none in touched files; tsc clean; vitest 88 files
/ 617 tests green.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

docs/api/staff.md

@@ -178,3 +178,20 @@
 |------|------|-------|
 | ERR_STAFF_NOT_FOUND | 404 | پرسنل یافت نشد |
 | ERR_FORBIDDEN_001 | 403 | دسترسی ندارید |
+
+---
+
+## رابطه با منبع
+
+پرسنل به‌تنهایی تقویم، ظرفیت و مهارت ندارد؛ آن‌ها روی **منبع** می‌نشینند
+([resource.md](resource.md)). هر پرسنل می‌تواند یک منبع از نوع `staff` در هر شعبه
+داشته باشد و `app:resource:backfill` این پل را برای پرسنلِ موجود می‌سازد.
+
+| نکته | چرا |
+|---|---|
+| `job_title` **مهارت نیست** | متن آزاد و فقط برای نمایش است؛ هیچ‌جا برای تصمیم‌گیری parse نمی‌شود. مهارت یک موجودیت با هویت است که در انتخاب منبع و شرط قوانین استفاده می‌شود |
+| غیرفعال کردن پرسنل | باید منبعش را هم ببندد، وگرنه در جستجوی وقت ظاهر می‌شود. `ResourceLinker::syncActive()` این کار را می‌کند — **فراخوانی صریح**، نه Doctrine lifecycle callback (که در `getArrayResult()` اجرا نمی‌شود و رفتار نامتقارن می‌سازد) |
+| غیرفعال کردن منبع | پرسنل را غیرفعال **نمی‌کند** — پرسنل ممکن است فقط نقش اداری داشته باشد |
+| پرسنلِ محیط چندشعبه‌ای | backfill پلش را نمی‌سازد و **گزارش** می‌دهد: هیچ ستونی نمی‌گوید در کدام شعبه کار می‌کند و حدس زدن او را در ساختمان اشتباه می‌نشاند |
+
+ظرفیت منبعِ پرسنل همیشه ۱ است — یک شخص هم‌زمان دو بیمار ندارد.