Lock server to canonical research-node schema - #78
Merged
Merged
Conversation
lost-rob0t
marked this pull request as ready for review
July 28, 2026 06:49
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.
What changed
ff814ff63868286d68e21502122832802cd5e361research-nodeexists in the canonical v0.9 schemadatafields, requiredobjectiveandstatus, expansion coverage, dtype count, and expansion hashdev, andmasterWhy
The server must not silently validate or document a different StarIntel contract than the Python, JavaScript, Common Lisp, Nim, browser, and Auto Dig repositories.
Scope
This is a schema persistence and drift gate only. It does not revive the stale server-wide v0.9 migration PR #54 or mix unrelated ingestion/runtime changes into this PR.
Validation
GitHub Actions runs
python scripts/check-starintel-schema-lock.pyagainst the exact canonical merge commit.