feat!: remove flow package — extracted to link#38
Merged
Conversation
The flow DAG engine was domain-specific to link's conversation routing. Cross-repo recon (asteby-hq/link, asteby-hq/ops, asteby-hq/visor, asteby-hq/hub, asteby/metacore-starter, asteby-hq/operador360, asteby-hq/p2p) confirmed link was the only importer. The engine is now part of link/backend/internal/flow (asteby-hq/link#129). BREAKING CHANGE: any consumer importing github.com/asteby/metacore-kernel/flow must remove the import. The kernel no longer ships a workflow engine — hosts that need one should fork from link or implement their own. Build / test: - GOWORK=off go build ./... — passes - GOWORK=off go test ./... — all 30+ packages green
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.
Why
The flow DAG engine was domain-specific to link's conversation routing. Cross-repo recon (link, ops, visor, hub, starter, operador360, p2p) confirmed link was the only importer. The engine doesn't belong in a generic kernel.
See decision in metacore-kernel#36 (bridge stable contract — flagged flow as the opposite case: extract).
What
Build / test
Breaking change
Any consumer importing `github.com/asteby/metacore-kernel/flow` must remove the import. The kernel no longer ships a workflow engine — hosts that need one should fork from link or implement their own.
Order with link PR
Merge link first: asteby-hq/link#129 absorbs the engine into `backend/internal/flow` while keeping kernel v0.8.0 (which still ships flow). Once link is on its local copy, this PR can land.