3 Commits

Include renames

Author	SHA1	Message	Date
Admin Bot	509cb39521	feat: Gotify CRUD + internal handler dispatch for notification service ... - Add internal handler support to ServiceAdapter (Handler field) - Dispatcher routes to internal handler when set (no reverse proxy) - GotifyClient: full CRUD (send/list/delete messages, CRUD applications) - Refactor notification handler: route by X-Resource header, not body format - Register notification as ServiceAdapter with auth required - Resources: send-email, send-message, list-messages, delete-message, delete-all-messages, list-applications, create-application, delete-application - Update examples: sendmsg-email.sh, gotify-crud.sh - Env vars: GOTIFY_URL, GOTIFY_APP_TOKEN, GOTIFY_CLIENT_TOKEN	2026-09-15 08:51:19 +09:00
Admin Bot	d5c7440655	feat: add Gotify support to sendMsg handler ... - Add sendGotify method to send notifications to Gotify server - Support format: 'gotify' in SendMsgRequest - Extract message ID from Gotify response - Configurable via GOTIFY_URL and GOTIFY_TOKEN env vars - Fallback graceful error if Gotify not configured	2026-09-15 02:36:02 +09:00
Admin Bot	cc9a32f53a	feat(network): SSE optimization for local LLM streaming (#31 #32 #33) ... Addresses three critical network issues for LLM streaming performance: **#33 Disable proxy buffering for SSE** - Add X-Accel-Buffering: no header to response - Tells nginx/Ingress to stream events immediately instead of buffering - Paired with ResponseController.Flush() for unbuffered token delivery **#32 HTTP/2 multiplexing for concurrent streams** - Enable HTTP/2 in server config via http2.ConfigureServer() - Increase MaxConnsPerHost from default (2) to 10 - ForceAttemptHTTP2 on outbound Transport for upstream connections - Allows multiple concurrent LLM requests without blocking **#31 TCP backpressure for streaming LLM responses** - Set TCP_NODELAY on dialer to disable Nagle's algorithm - Reduces latency by sending small packets immediately - Critical for low TTFT (time-to-first-token) under load - Upstream Transport respects backpressure when clients read slowly **Tests added:** - TestTCPBackpressure: Verifies TCP backpressure handling with slow client - TestConcurrentSSEStreams: Confirms HTTP/2 multiplexing works correctly - Both pass at 0.11s and 0.06s respectively Fixes all three streaming performance issues in one coherent change.	2026-09-14 08:14:04 +09:00