Repository navigation
Fix live Slack agent discovery registration - #198
Merged
Merged
Conversation
Signed-off-by: Tiberiu Socaci <tsocaci@makeitfuture.com>
…lack-connection Signed-off-by: Tiberiu Socaci <tsocaci@makeitfuture.com> # Conflicts: # CHANGELOG.md
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.
The live agent directory returned an empty list because Slack's existing lifecycle manager was not registered with the connector lookup used by discovery. Register that manager during daemon transport boot, resolving the current client after reconnect and failing closed while disconnected.
Keep automationTarget on its existing raw Slack WebClient path so scheduled/background results retain image uploads, menus, trusted prefixes and reminder permalinks.
Validation: real boot integration covers default discovery and reconciliation across connect/disconnect/reconnect without an injected verifier; all 3,903 tests passed with 34 optional/live skips, including coverage floors. Static, secret scan, security coverage and DCO passed. Independent review found no blockers. Feature/test/changelog records and the private boot acceptance gate were updated. Deployment verification follows the safe restart.