Skip to content

Lock server to canonical research-node schema - #78

Merged
lost-rob0t merged 3 commits into
masterfrom
agent/research-node-schema-lock
Jul 28, 2026
Merged

lost-rob0t merged 3 commits into
masterfrom
agent/research-node-schema-lock

Conversation

@lost-rob0t

Copy link
Copy Markdown
Owner

What changed

  • adds an explicit StarIntel schema lock pointing at merged Auto Dig PR [P1-08] Add structured metrics, tracing, audit events, and operational diagnostics #46 / commit ff814ff63868286d68e21502122832802cd5e361
  • records the canonical schema, expansion, and manifest paths
  • verifies that research-node exists in the canonical v0.9 schema
  • verifies strict data fields, required objective and status, expansion coverage, dtype count, and expansion hash
  • runs the lock check in pull requests, agent branches, dev, and master

Why

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.py against the exact canonical merge commit.

@lost-rob0t
lost-rob0t marked this pull request as ready for review July 28, 2026 06:49
@lost-rob0t
lost-rob0t merged commit 4afd19a into master Jul 28, 2026
5 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant