canvas-frontend

6 Commits

Author	SHA1	Message	Date
canvas-bot	9cbee11756	fix: studio createDraft split, llm fallback offers tools, topbar a11y pass build-and-publish / test (push) Has been cancelled Details build-and-publish / image (push) Has been cancelled Details Three Oracle-flagged gaps: 1. Studio createDraft 500 (was masked by retries). Empirical curl reproducer proved POST /api/ea2/flow returns 201 with the minimal shape but intermittently 500s when config.wizard.* is in the initial body. Split: POST creates the draft minimally, then a follow-up PUT attaches the wizard config best-effort. Draft creation now lands reliably. 2. LLM 'temporarily unavailable' was a dead end for the user. Now the assistant returns ok:true with a concrete menu of tools the user CAN use right now ('list processes', 'start <name>', 'open <hub>', 'tell <name> that ...', 'remember ...', 'recall ...'). The reply renders as a normal assistant message, not a red error. 3. Topbar UI/UX Pro Max pass: - Added aria-label to the ⌘K and avatar buttons (icon-only a11y) - Removed the duplicate topbar-mid chips on Mission (Mission scene already shows family/defName/version inline). Cleaner topbar. - Added focus-visible outlines (2px amber, 2px offset) on all topbar action buttons + user-menu items - Hover/active scale on the avatar (1.04 / 0.97) with 160ms ease - Tabular numerals for the ⌘K kbd and notification badge - prefers-reduced-motion respected 30/30 vitest pass. tsc + vite build green.	2026-06-15 20:04:59 +04:00
canvas-bot	5abb3595fc	fix(wizard): retry createDraft on 500/502/503/504 + human error message build-and-publish / test (push) Has been cancelled Details build-and-publish / image (push) Has been cancelled Details POST /api/ea2/flow currently returns 500 after 19s on demo upstream. Retry once with backoff, then surface a clear 'EA2 backend temporarily unable to create new processes' message naming the status. The user gets actionable info instead of a raw 500.	2026-06-15 19:42:32 +04:00
canvas-bot	3a72b74371	fix(chat): tolerate 500 on empty inbox edges; fix(agent): clear LLM-unavailable msg build-and-publish / test (push) Has been cancelled Details build-and-publish / image (push) Has been cancelled Details - chatApi.listThreads: catch on the edges query so a fresh empty inbox doesn't bubble a 500 to the UI. New users see 'No conversations yet' instead of the error banner. - agentTools.llmFallback: when the LLM gateway returns 503/500, show a clear 'plain-language replies temporarily unavailable' message naming the reason, listing the deterministic capabilities that still work. No more silent null returns.	2026-06-15 19:27:37 +04:00
canvas-bot	8d85a4c3ea	fix(login): do not block login completion on EA2 scenario fetch build-and-publish / test (push) Has been cancelled Details build-and-publish / image (push) Has been cancelled Details If buildLiveScenariosFromApi hangs or errors on any EA2 read, loginAs would await it forever, leaving the user stuck on 'VERIFYING...' even after auth+identity succeed. Make refreshLive fire-and-forget after the toast; the Mission scene re-fetches on mount and surfaces failures via liveError.	2026-06-15 19:13:13 +04:00
canvas-bot	722b0ba3a2	fix(nginx): drop CoreDNS from resolver, use public DNS only build-and-publish / test (push) Has been cancelled Details build-and-publish / image (push) Has been cancelled Details CoreDNS at 10.43.0.10 returns SERVFAIL for demo.flow-master.ai in this environment. Including it in the resolver list caused nginx to query it first, get SERVFAIL, and return 502 before falling back to 1.1.1.1. Pinning to public resolvers eliminates the cold miss. 300s TTL caches the result. Restored $variable form for proxy_pass because the static-hostname form failed pod readiness (DNS query at config-load time hits the same SERVFAIL).	2026-06-15 18:56:29 +04:00
canvas-bot	db32934100	fix(nginx): static proxy_pass hostname so DNS resolves once at config-load build-and-publish / test (push) Has been cancelled Details build-and-publish / image (push) Has been cancelled Details The previous $variable form forced lazy per-request DNS resolution. Per-request lookups against 10.43.0.10 → SERVFAIL → cold-cache 502 even when downstream was healthy. Switching to a literal hostname makes nginx resolve once at startup and reuse the cached upstream IP for the lifetime of the worker. Cloudflare anycast is stable so this is safe.	2026-06-15 18:39:26 +04:00