Bridge 1b: the ASR worker wait in the console, quiet in notifications

[KodeStar]

Server side of Bridge Phase 1b (KodeStar/audiosilo-bridge#3): the Bridge gained native ASR workers. The worker protocol is Bridge-internal; what reaches the server is the heartbeat's workers (already accepted since Phase 0) and one new park code.

• asr_worker_waiting (no ASR worker is connected and the Bridge's asr.worker_fallback is wait, or it has no ASR of its own) joins transientParks: it resumes by itself when a worker connects, and a sleeping laptop worker would otherwise announce each book that reaches its transcription. Test: the notification sequence in sidecars_test.go.
• The console words it (KNOWN_PARKS, bridge.park.asr_worker_waiting in 6 locales), and also library_not_writable, which had no sentence. The Workers card's empty state points at the Bridge's Workers tab instead of "a later version".
• es/fr/it/pt: the Bridge's grammatical gender and the word for a job as in the rest of each locale.

Real stack: with the fallback at wait and the worker stopped, the job parked asr_worker_waiting and a configured webhook received nothing; it went back to running when the worker reconnected.

Quality passes: /simplify (paired reviewers for this small, data-only diff: clean; the hand-kept park lists in console and player are a known pattern, a hint fallback for unknown codes is a follow-up) then /code-review xhigh --fix (8 findings: 5 fixed, the notification one decided as above; left: a pre-1b Bridge's empty state, a direct #workers link).

Gates: scripts/build-admin.sh (825 tests), go build/vet, golangci-lint run (0), go test -race ./... (a load flake in internal/backup passed on rerun).