Repository navigation
tech-debt(memory): the lifecycle proxy's failure causes are bare strings about to become a frontend contract #14888
Description
Activity
Remaining scope, measured 2026-10-03 against
origin/main: blocked on #12632Done already: the failure causes are named constants in
autobot_shared/node_proxy.py(REASON_KEY_NOT_CONFIGURED,REASON_URL_NOT_CONFIGURED,REASON_TIMEOUT,REASON_UNREACHABLE), andmemory_lifecycle_proxy.pyemits them.node_status_<code>is still composed inline (memory_lifecycle_proxy.py:108).Not done, and cannot be done yet: there is no frontend consumer. No component, composable or API helper in
autobot-slm-frontend/srccalls/api/memory/lifecycle. The only references are the generatedapi.tstypes. Searched by API path, by operation id (get_memory_lifecycle) and by/memory/route strings, with no hits outside generated types. The tab that would consume these causes is #12632'sMemoryLifecycleTab, still open.So the work items split:
- Named enum on the SLM side: doable now, but it is only useful with the consumer it constrains. It belongs with the tab.
- Frontend mirror and consumer guard ("every cause the proxy emits is one the consumer handles"): need the consumer to exist. Blocked by P1b — SLM: memory-lifecycle aggregator + MemoryLifecycleTab monitoring tab #12632.
Recorded as
blocked_by #12632. When the tab lands, enum + mirror + guard ship together, so the strings never become a hand-typed contract.
Summary
autobot-slm-backend/api/memory_lifecycle_proxy.pyreports why a node could not be read using bare string literals:These are deliberately distinct — 403 means the key is wrong, 404 means the node predates #12631, a timeout means alive but slow, and an operator acts differently on each. That design is right; the representation is weak.
Why now rather than later
#12632's frontend half has to switch on these values to show a useful cause instead of a generic error, and the handoff comment on that issue lists them as the contract. The moment that lands, a typo in either place produces a UI that silently falls through to a default branch — the failure mode being a monitoring surface that tells an operator less than it knows, which is what this whole area exists to fix.
Right now the strings exist in exactly one place and nothing consumes them, so this is the cheapest it will ever be to make explicit.
Work
node_status_<code>composable — the status code is data, not a separate causeAcceptance
A cause the proxy can return and the tab cannot render fails a test rather than rendering as "unknown error".
Related: #12632, #14653.