alknet/tasks/server/control-channel.md at 596c89ce24ac5974512a57ccd0380bde81818af8

Files

glm-5.1 596c89ce24 refactor!: rebrand wraith to alknet

Rename all crates, CLI commands, constants, type names, doc comments,
and documentation from wraith to alknet. Includes wire-protocol changes:
ALPN wraith-ssh -> alknet-ssh, reserved destination prefix wraith- ->
alknet-, SSH auth username wraith -> alknet.

2026-06-05 10:04:32 +00:00

2.3 KiB

Raw Blame History

id, name, status, depends_on, scope, risk, impact, level

name

status

depends_on

scope

risk

impact

level

server/control-channel

Implement alknet-control reserved channel for pubsub event bus bridging (ADR-018)

pending

server/handler

auth/error-types

narrow

medium

component

implementation

Description

Implement the control channel routing per ADR-018. When the server receives a channel_open_direct_tcpip request for alknet-control:0:

The handler detects the reserved alknet- prefix destination
Instead of making a TCP connection, it bridges the SSH channel to an internal event bus handle
EventEnvelope JSON flows bidirectionally over the SSH channel

The entire alknet- prefix is reserved — no TCP connections should be attempted for alknet-* destinations. The control channel is optional; servers without pubsub configured should accept the channel and provide a configurable behavior (reject or provide a loopback pipe).

At this stage, implement the routing logic and a ControlChannel trait that consumers can implement. The actual pubsub bridge implementation would be in a separate crate or behind a feature flag.

Acceptance Criteria

crates/alknet-core/src/server/control_channel.rs exports ControlChannelHandler trait and routing logic
ALKNET_CONTROL_DESTINATION constant defined as "alknet-control" (ADR-018)
ALKNET_PREFIX constant defined as "alknet-" for namespace reservation
ControlChannelHandler trait: async fn handle_channel(stream: Box<dyn AsyncRead + AsyncWrite + Unpin + Send>)
Server handler detects alknet-* prefix and routes to ControlChannelHandler instead of TCP proxy
If no ControlChannelHandler configured, reject the channel open request (SSH channel open failure)
Non-reserved destinations continue through normal TCP proxy path
Server constraint enforced: no TCP connections to alknet-* destinations
Unit tests: reserved destination detected, non-reserved passes through, prefix matching works

References

docs/architecture/server.md — Channel Handling section (reserved destinations), Constraints section
docs/architecture/decisions/018-control-channel-for-pubsub.md — control channel rationale
docs/architecture/napi-and-pubsub.md — server-side control channel behavior

Notes

To be filled by implementation agent

Summary

To be filled on completion

2.3 KiB Raw Blame History