Repository navigation
Conversation
feat(research): support nationwide DE/DK operator imports without dotenv
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Research operator commands now use exported environment variables without reading the local runtime
.env, and municipality imports cover all 16 German states plus all 98 Danish municipalities. This promotes the changes merged intodevvia #141; the current comparison contains four commits and 16 changed files.The BKG input contains 10,747 German municipalities. Strict AGS matching, catalog-pinned Danish relation IDs, own-Nominatim-only boundaries, deterministic resume and idempotent persistence remain enforced. The 107 German city exceptions were individually verified. Live plans covered 112 German municipalities and all 98 Danish entries; Thisted and Aabenraa remain visible rejections because their relations are absent from the own provider. No production import was performed.
Migration 0017 follows unchanged 0016 and only expands the region constraint. The downgrade refuses to proceed while areas outside the previous scope remain. Metadata and the deployment upgrade contract are aligned; no additional grants are needed. Deploy the migration before the compatible backend and coordinate imports for the table lock. Start at offset 0 when switching from the old geographic scope.
Validation on #141: backend lint, typecheck and tests passed; all three deployment safety matrix jobs passed; database documentation generation, dependency review and Python CodeQL passed. Frontend and JavaScript CodeQL were skipped by path filters. Local research/SQL-console/migration rerun: 372 passed; the optional Qdrant integration was skipped in the full local suite because TEST_QDRANT_URL was unset. Checks on the current dev merge commit are still running; this PR receives its own checks.
Branch direction:
dev→main. No merge or deployment is requested by this PR creation.