rays 1698cf8d1e Answer status on the socket instead of queuing it behind the worker ...

The worker runs one job at a time, and status was one of its jobs, so the
Docker healthcheck waited behind the startup scan (54 seconds of it after
the last deploy) and timed out at 5. Any scan or download longer than
three probes would have had a working daemon marked unhealthy. The socket
now answers status straight away; everything else still queues. A test
fills the queue and checks status comes back anyway.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01TAC7sLVqfKmY6rsTLXzNgk

2026-09-12 14:19:00 +00:00

..

architecture.md

Answer status on the socket instead of queuing it behind the worker

2026-09-12 14:19:00 +00:00

cli.md

Design pass on the web UI: amber for new, EQ bars, keyboard feed list

2026-09-11 22:24:41 +00:00

configuration.md

Sign out through the proxy when the proxy signed you in

2026-09-12 14:10:30 +00:00

history.md

Answer status on the socket instead of queuing it behind the worker

2026-09-12 14:19:00 +00:00

sso.md

Sign out through the proxy when the proxy signed you in

2026-09-12 14:10:30 +00:00

users.md

Trim the state database; Popular lists feeds the way Directory does

2026-09-12 13:15:55 +00:00