Implement Plan 02 agent control channel and Limentinus enrollment - #18
Merged
Conversation
PianoNic
added
feature
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.
Scaffolds the agent WebSocket control channel on the manager side and wires the matching client in the Limentinus repo. Admin generates a provisioning key, Limentinus enrolls with it (one-shot burn), opens a persistent JSON-over-WS connection, and heartbeats every 30s. Nodes UI polls every 5s to show status transitions (Pending to Active to Disconnected). End-to-end verified locally: key inserted, agent enrolled, DB shows Active with LastSeenAt updating, kill agent, DB flips to Disconnected. No WireGuard yet, Plan 03 covers that. Closes #15