## Goal Remove the legacy `Geo::UploadReplicator`, its `file_registry` and `upload_states` tables, and the dual-run plumbing that let it coexist with the 23 per-partition upload replicators. ## Context Phase 6a (&23525) switches replication to the partition replicators and keeps every user-visible "Uploads" surface intact: the `uploads_*` status fields and `geo_uploads_*` gauges report as aggregates of the partitions, and the two legacy admin URLs render overview pages linking to the partition pages. After Event B in 19.6 the legacy code only serves checksum adoption on the primary and a stale `file_registry` on secondaries. The one surface that cannot be kept cheaply is GraphQL. `GeoNode.uploadRegistries` returns registry rows, and presenting 23 registry tables as one would need the first database view on the Geo tracking database, a hand-written resolver and finder, and fan-out for the bulk update mutation. No GitLab frontend code uses the field. It is deprecated instead. ## Scope - 19.6: deprecate `GeoNode.uploadRegistries` and the `UPLOAD_REGISTRY` enum value in favour of the per-partition fields, with a deprecation entry and a breaking change exception request. - 19.8, after two milestones of soak: remove the legacy replicator, registry, state model, dual-run plumbing, checksum adoption, and the two legacy feature flags. Rework the two Geo cleanup tools that still read `upload_states`. Update documentation and publish an upgrade note. - 19.9: drop `upload_states` and `file_registry`. - 20.0: remove the deprecated GraphQL field, type, and enum value. ## Exit criteria - No code references `Geo::UploadReplicator`, `Geo::UploadRegistry`, or `Geo::UploadState`. - `upload_states` and `file_registry` are dropped. - The `uploads_*` aggregate fields, `geo_uploads_*` gauges, and both Uploads overview pages from Phase 6a still work. - GraphQL removal shipped in 20.0 with an approved exception. - Administrator documentation no longer names the legacy classes.