 glm-5.3-flash
|
ea5ac83b57
|
feat(gateway): the 5 core gateway routes wired into the router
- src/gateway/routes.rs: /search /schema /call /batch /subscribe
- SSE projection: data frames per event, error event terminates,
internal/unknown ops -> NOT_FOUND, query-op -> INVALID_OPERATION_TYPE
- /search + /schema ACL-filtered via services/list + services/schema
discovery handlers; /batch ordered per-item envelope JSON
- gateway_router() merged into HttpAdapter's router under the shared
bearer-auth route layer; decoy remains the fallback
- adapted to alkcall 0.1.1: OperationType::Sub, envelope error by value
Verified: cargo test (71 lib tests), clippy -D warnings, fmt.
|
2026-08-28 08:31:43 +00:00 |
|
|
glm-5.3-flash
|
d070e548ad
|
feat: server foundation (phase 1 core) — state, auth, healthz/decoy, gateway dispatch, HttpAdapter
Tasks completed: server-core-types, server-auth, server-healthz-decoy,
gateway-dispatch, server-adapter (5 of 17).
- src/server/state.rs: DecoyConfig + RouterState (alkcall type paths,
6-endpoint reserved-path docs)
- src/server/auth.rs: bearer middleware + ResolvedIdentity extractor
(10 tests: missing/malformed/basic/failed-resolution matrix)
- src/server/healthz.rs + decoy.rs: raw healthz; nginx-style 404,
static site (path-traversal guarded), redirect decoys
- src/gateway/dispatch.rs: GatewayDispatch invoke/invoke_streaming
(internal:false, forwarded_for:None, bounded deadline) +
src/gateway/error.rs: CallError→HTTP status mapping (HTTP_<status>
passthrough, retryable→Retry-After)
- src/server/adapter.rs: HttpAdapter ProtocolHandler — accept_bi →
BiStream → TokioIo → hyper auto builder (h2 CONNECT enabled);
integration tests over DuplexStream (request/response cycle, healthz,
decoy 404)
Verified: cargo test (46 lib tests), clippy -D warnings, fmt,
test --all-features.
|
2026-08-28 07:35:02 +00:00 |
|
|
glm-5.3-flash
|
a85500d3d9
|
docs: ws-byte-adapter POC complete (GO) — resolve OQ-01, update framing facts
POC at /workspace/ws-byte-adapter-poc/ (not on main), all tests green:
- call round-trip over axum WS ↔ adapter ↔ ChannelsAdapter ↔ channel-0
Dispatcher (published alkcall API only, no forks)
- 3 MiB payload splits across 1 MiB WS messages, byte-intact reassembly
- 20 interleaved calls reassemble without corruption/cross-correlation
Findings merged:
- OQ-01 resolved: byte-stream both directions, bounded mpsc (64 slots)
inbound, outbound chunk-header parsing (frame-as-two-chunks
live-confirmed), 1 MiB message cap with split, flush no-op, close →
EOF → REQ-CH-02
- websocket.md: chunk ≠ frame on channel 0 (frame reassembly required);
operationId is the request payload key
- task ws-byte-adapter → completed with full Summary; ws-upgrade-session
unblocks
|
2026-08-28 07:14:32 +00:00 |
|
|
glm-5.3-flash
|
63dc4b6d06
|
docs: implementation plan (TTY precedents folded in); task decomposition (17 tasks)
Plan updated with the alknet-tty findings: the drainer pattern
(single ordered writer) makes outbound chunk-boundary parsing sound;
TestStdinSink's try_send→Full→Pending is the inbound backpressure
precedent; OQ-01(a) now cites the reference.
Task graph (taskgraph-validated, 17 tasks, 6 generations, no cycles):
- tasks/server/: core-types, auth, healthz-decoy, adapter
- tasks/gateway/: dispatch, routes, publish
- tasks/websocket/: byte-adapter (research POC), upgrade-session, overlay-ops
- tasks/adapters/: from-openapi, from-jsonschema, to-openapi, from-wss, mcp
- tasks/client/: http-host
- tasks/infra/: integration-suite (phase 4)
Critical path runs through server core → adapter → WS session →
overlay tests → integration suite. High-risk tasks are the three WS
tasks, de-risked by the ws-byte-adapter POC blocking upgrade-session.
|
2026-08-28 06:05:45 +00:00 |
|