Three endpoints fail on the live instance and none of them tells the operator:
/api/chat/update 501, fired on load, console only.
/api/version 501, console only. The UI simply never shows a version.
/api/logs/stream 503. This one does surface, but as a permanent amber "reconnecting"
pill sat next to the text "Durable history unavailable; live daemon logs continue",
which are opposite claims.
A 501 means the feature is not configured on this deployment, which is a legitimate state
and should read as "not configured", not as silence.
Expected
An unconfigured capability is stated in the UI where its control lives, and the control is
disabled rather than failing on click.
A stream that cannot reconnect stops claiming logs are continuing.
Related: archie-core-1786637500953-422-01075562 (closed) removed a raw 501 banner from chat;
the swing went too far, from a raw error to nothing at all.
Close reason
Closed
Imported from beads archie-core-c5bz · GitHub #967 · type bug · priority P1 · created 2026-09-20 · closed 2026-09-20
Three endpoints fail on the live instance and none of them tells the operator:
- `/api/chat/update` 501, fired on load, console only.
- `/api/version` 501, console only. The UI simply never shows a version.
- `/api/logs/stream` 503. This one does surface, but as a permanent amber "reconnecting"
pill sat next to the text "Durable history unavailable; live daemon logs continue",
which are opposite claims.
A 501 means the feature is not configured on this deployment, which is a legitimate state
and should read as "not configured", not as silence.
### Expected
- An unconfigured capability is stated in the UI where its control lives, and the control is
disabled rather than failing on click.
- A stream that cannot reconnect stops claiming logs are continuing.
Related: archie-core-1786637500953-422-01075562 (closed) removed a raw 501 banner from chat;
the swing went too far, from a raw error to nothing at all.
### Close reason
Closed
---
_Imported from beads `archie-core-c5bz` · GitHub #967 · type bug · priority P1 · created 2026-09-20 · closed 2026-09-20_
sam
added the highbug labels 2026-10-27 13:39:40 +00:00
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Three endpoints fail on the live instance and none of them tells the operator:
/api/chat/update501, fired on load, console only./api/version501, console only. The UI simply never shows a version./api/logs/stream503. This one does surface, but as a permanent amber "reconnecting"pill sat next to the text "Durable history unavailable; live daemon logs continue",
which are opposite claims.
A 501 means the feature is not configured on this deployment, which is a legitimate state
and should read as "not configured", not as silence.
Expected
disabled rather than failing on click.
Related: archie-core-1786637500953-422-01075562 (closed) removed a raw 501 banner from chat;
the swing went too far, from a raw error to nothing at all.
Close reason
Closed
Imported from beads
archie-core-c5bz· GitHub #967 · type bug · priority P1 · created 2026-09-20 · closed 2026-09-20