hsiegeln 0632f1c6a8 fix: agent token refresh returns 404 after server restart ...

The refresh endpoint required the agent to exist in the in-memory
registry. After server restart the registry is empty, so all refresh
attempts got 404. The refresh token itself is self-contained with
subject, application, and roles — the registry lookup is optional.

Now uses application from the JWT, falling back to registry only
if the agent happens to be registered.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

2026-04-03 10:37:57 +02:00

..

main

fix: agent token refresh returns 404 after server restart

2026-04-03 10:37:57 +02:00

test

feat: add Logs tab with cursor-paginated search, level filters, and live tail

2026-04-02 08:47:16 +02:00