Complete ObjectType kernel migration - #18
Merged
Merged
Conversation
Standardize authenticated domain dispatch through metadata-driven Records and actions while preserving authoritative services behind adapters.
Make the deployed contracts, migration boundaries, plugin lifecycle, security limits, and verification workflow explicit for users, contributors, and agents.
|
Bugbot is not enabled for your account, so this pull request was not reviewed. Enable Bugbot in the Cursor dashboard to get automatic reviews on future PRs. |
Close the final audit gaps around plugin authoring, compatibility classifications, security enforcement, deployment checks, and agent guidance.
ReBoticsAI
marked this pull request as draft
July 15, 2026 01:23
This was referenced Jul 15, 2026
Route all durable domain mutations through enforced kernel contracts, add recovery and security guarantees, and establish zero-debt completion gates so the architecture is safe to deploy and extend.
Add missing columns before creating claim indexes so upgraded tenant databases can execute kernel actions after deployment.
Run test files serially because migration suites intentionally exercise the singleton core database and must not race schema upgrades across workers.
Prevent declarative lifecycle reconciliation from erasing adapter-backed definitions registered by executable plugins.
Replace the obsolete hybrid architecture narrative with the enforced durable-through-kernel contract, production verification evidence, and coordinated plugin migration boundaries.
Generalize private domain references while retaining the reviewed external transport exception and coordinated ecosystem guidance.
ReBoticsAI
marked this pull request as ready for review
July 15, 2026 03:33
Support the migrated marketplace bundle format with a constrained, validated Record importer that dispatches safe portable ObjectTypes through kernel seeding.
Align core documentation with the now-merged plugin and marketplace migrations.
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.
Summary
Completion gates
Verification
npm run audit:kernel:strict: 15 mutation routes (3 Record, 2 action, 5 kernel-delegated, 5 protocol exceptions); 0 legacy routes/callers, unmatched callers, direct writes, or tool collisions; 72 audited core ObjectTypes, 75 static tools, 335 generated candidates662378dc3020397bb7eda8343ac4bf59d05ac94a; health returned 200If-Matchcorrectly returned 412; cleanup passedCoordinated ecosystem PRs
The core PR is merge-ready. Ecosystem-wide rollout still requires merging the coordinated external PRs in the planned order.