Description
The entire RUNNER BRAIN section is confusing and provides unclear information:
- RUNNER BRAIN — what does this even mean? The name is not self-explanatory.
- Status label (e.g., "ALERT / SPINNING UP / PROCESSING / BUSY") — unclear what state machine this represents, and what each state means for the user.
- "preparing new runners" / "jobs in execution" — vague descriptions that don't tell the user what's actually happening.
- UPTIME 00h:09m:30s — uptime of what? The controller process? The longest-running runner? Not clear.
- IDLE TIMEOUT 15M — timeout for what? Scaling down idle runners? The brain itself? No context given.
Overall the section feels like internal debugging info exposed to the user without explanation.
Expected
Either:
- Redesign with clear, actionable information (e.g., "Auto-scaling: 2 runners spinning up", "Controller uptime: 9m30s")
- Remove it entirely if the information is not useful to end users
- At minimum, add tooltips or better labels so users understand what each field means
Description
The entire RUNNER BRAIN section is confusing and provides unclear information:
Overall the section feels like internal debugging info exposed to the user without explanation.
Expected
Either: