How Tugport's API serves service status from memory instead of asking Docker every time
Since v0.1.28 Tugport's API reads container state from the proxy's snapshot and serves Docker disk usage and update checks from a background-refreshed cache. What changed in the code, and what I measured on the live panel.