initialize Electron desktop app and remove unused files
This commit is contained in:
@@ -0,0 +1,26 @@
|
||||
---
|
||||
date: 2026-10-22
|
||||
feature: HTTP startup and session reload after backend restart
|
||||
impact: Keep session APIs available during bridge startup and recover failed initial loads
|
||||
---
|
||||
|
||||
PR/commit: pending.
|
||||
|
||||
The HTTP listener, Web UI stores, routes and Socket.IO handlers are initialized
|
||||
before starting the managed Agent Bridge in the background. Bridge readiness
|
||||
continues to be checked by the existing chat handlers; the chat-run protocol is
|
||||
unchanged. The bridge manager is registered with shutdown before starting it.
|
||||
|
||||
A failed session-list request no longer marks the list loaded or discards a
|
||||
route-selected session. Offline health polling retries after two seconds;
|
||||
reconnection reloads profiles, models and sessions. An already loaded session
|
||||
list retains its state on request failure. Chat, global-agent and history views
|
||||
handle reconnection. Batch-delete confirmation text uses Popconfirm content
|
||||
rather than becoming part of the sidebar trigger.
|
||||
|
||||
Validation: app-store and session-order Vitest coverage; Playwright startup
|
||||
recovery (base route and direct session route), deletion confirmation and history
|
||||
deep links; build and harness checks. A real isolated built-server smoke check
|
||||
used a fake Python executable sleeping for 60 seconds and confirmed /health
|
||||
responded with status=ok before the bridge became ready. State, uploads and
|
||||
bridge endpoint were isolated under a temporary directory.
|
||||
Reference in New Issue
Block a user