migrations: add NUC-only 106/107 as 108/109 (resolve number collision) - #45
Open
DarrenZal wants to merge 1 commit into
Open
migrations: add NUC-only 106/107 as 108/109 (resolve number collision)#45DarrenZal wants to merge 1 commit into
DarrenZal wants to merge 1 commit into
Conversation
Recovered from the NUC runtime snapshot (nuc-runtime@316f2e2). These files existed ONLY in the NUC's .git — no MacBook clone had them, and the newest tarball backup predated them by 2.5 months. Additive: no existing file is modified.
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
1 participant
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.
Recovered from the NUC runtime snapshot (
nuc-runtime@316f2e2).These files existed only inside the NUC's
.git. No MacBook clone had them (koi-processor-service,RegenAI/koi-processor,koi-processor-runtimeall checked), and the newest tarball backup predated them by 2.5 months. Provenance: they were MacBook working-tree scratch, rsynced to the NUC bydobby/scripts/deploy.sh, then lost locally — see~/.claude/plans/koi-infra-entity-type-hints-handoff.md:36, which lists several as "untracked scratch in the working tree (operator to triage — NOT committed)".Purely additive: no existing file is modified, nothing is imported or wired up, no migration is applied. Merging changes no runtime behaviour.
The collision
The NUC carried
106_entity_notion_mappings.sqland107_entity_visibility_scope.sql;regen-prodindependently used those same numbers for different migrations (106_ingest_idempotency,107_entity_closure). Renumbered to 108/109, verified free across all remote branches.Apply nothing
108_entity_notion_mappingsentity_notion_mappings,projection_checkpoints+ 2 indexes)109_entity_visibility_scopeAll applied/not-applied verdicts come from
pg_tables/pg_indexes/information_schemaprobes, not the tracker tables — this repo has three of them (schema_migrations,koi_migrations,koi_schema_migrations) and they disagree with each other.