Repository navigation
feat: replace Coordinator runtime with Go - #22
Merged
Merged
Conversation
|
Important
This repository does not receive automatic reviews because it has fewer than 10 stars.
|
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.
Change
Replace the Node/Effect runtime with one Go executable for inspector, connector, CLI, MCP and native hooks. Keep only required Pi/OMP host-language adapters, centralize strict Go contracts, and remove token/context/cost telemetry.
Organize commands under cmd, implementation and embedded assets under internal, and keep the README concise. Release version: 0.3.0-beta.12. Preserve the deleted THIRD_PARTY_NOTICES.md; bundled dependency licenses are included in LICENSE.
Verification
Normal exact-head CI must pass before merge; current-main CI must produce the signed release image and native/chart/package evidence before GitOps promotion.
Deployment
Owner authorized deployment via the existing signed-artifact promotion path and accepted the existing Recreate readiness gap. Existing credentials, namespace, services, storage decisions and native work remain preserved. Native plugin rollout must follow verified contract compatibility; no direct cluster image patch or trust/admission bypass.