feat(feishu): route direct channel through agent engine - #506
Open
GatewayJ wants to merge 1 commit into
Open
Conversation
GatewayJ
force-pushed
the
feishu_chanael
branch
3 times, most recently
from
August 21, 2026 10:00
948211c to
7e13c95
Compare
Add binding-owned ingress, execution, delivery, and durable channel state.\nRemove the legacy Feishu codexbridge execution path without adding fallback behavior.
GatewayJ
force-pushed
the
feishu_chanael
branch
from
August 21, 2026 10:08
7e13c95 to
daf02ee
Compare
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.
Summary
Validation
go test -race ./internal/channel/feishu/...go vet ./internal/channel/feishu/...git diff --checkImpact
Hosted Feishu workers now use process-local best-effort delivery state without WAL or restart recovery. Legacy Feishu codexbridge execution is removed.
Notes
A full
go test ./...run was not clean locally because port 127.0.0.1:18080 was already occupied and two API tests depended on local configuration/runtime state.