Block a user
[Feature] Make route-layer rebuild incremental: update only affected matches/patterns/stops
[Feature] Add source-run history and dataset-version comparison
[Feature] Run the generated 24-source GTFS test set and measure conflicts before scaling to more Europe feeds
[Feature] Add generated stop-to-stop map-path proposals for missing OSM route relations and GTFS detours
[Feature] Add constrained candidate generation for stop matching: concrete OSM stop/platform/bay candidates near each GTFS stop, with explicit transfer links for nearby but dist...
[Feature] Add constrained candidate generation for route matching: OSM route features only, mode/ref/name filters, PostGIS bbox/spatial pruning, and geometry loading only for pl...
[Feature] Add feed/map update diffs so only changed stops, routes, patterns, calendars, and geometry evidence need review
[Feature] Add persistent GTFS/OSM stop and route matching decisions that survive source updates
[Feature] Add first dedup review queues for agencies/operators, stop places, route duplicates, and calendar conflicts
[Feature] Add validation report storage per feed snapshot
[Feature] Add immutable raw feed snapshots and source-run history
[Feature] Store explicit license/publication flags per feed: can import, can derive, can redistribute, attribution required, and commercial restrictions
[Feature] Add the first-class source hierarchy: source directories -> sources/publishers/authorities -> concrete feeds -> immutable feed snapshots/datasets
[Feature] Build the feed review workflow: discovered feed -> license/authority review -> approve -> import
[Feature] Promote GTFS harmonization to the primary data workflow: source discovery, review, import, validation, deduplication, and publication readiness
[Feature] Add proper Alembic migrations for PostgreSQL and keep SQLite test support
[Task] Which future module comes first after platform cleanup: cases, workflow, or connectors?
[Task] Which event transport is the first production target: DB outbox only, Redis/Celery, or pluggable dispatch?
[Task] Should admin be one platform module or split across access/tenancy/policy/audit?
[Task] Should tenants be extracted before policy, or after access but before policy?