[translator] A run carries fields, not a strategy — the server half #208

The server half of #48. Out of scope: the field-picker tree and the admin forms, which #48 keeps.

TranslationStrategy disappears as a port, with both implementations, from the pipeline, the enqueue input, the stored row, the host-facing task and the status response. A run carries, per target locale, an optional list of leaf addresses and an optional list of criterion names; the pipeline receives one input, the list of leaves to translate.

Also here, because the selection forces each one: the module chain is assembled per locale rather than once at boot; the receipt stops re-basing leaves a run did not translate; the staleness route reports which leaves drifted, not only that a locale did.

Auto-translate loses strategy and nothing replaces it — its runs cover the whole document until its own rework. Breaking; docs/DEPRECATIONS.md carries the entry.

Design: docs/plans/2026-10-18-the-rewiring.md §4 (S1–S6), superseding D21's run kind.