feat(controller-status): render per-controller connection status in ctrlstatus command (task 8.3)
Adds ctrlstatus_peer_status_str (mirrors ctrlstatus_role_str's convention: 0=unknown/1=ok/2=catching-up/3=dead, safe default fallback for any other code) and extends cmd_ctrlstatus's per-controller print line to render it alongside each configured controller's existing name:address, completing the CtrlPeer.status wire field added in task 8.1 and sourced in task 8.2. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01RLSNJhNoULvVcUhXEFafQC
This commit is contained in:
parent
ab5dd91537
commit
64b18d5c34
2 changed files with 25 additions and 3 deletions
|
|
@ -180,7 +180,7 @@
|
|||
- _Boundary: ctrlstatus_fill_
|
||||
- _Depends: 8.1_
|
||||
|
||||
- [ ] 8.3 Render each configured controller's connection status in the `ctrlstatus` client command
|
||||
- [x] 8.3 Render each configured controller's connection status in the `ctrlstatus` client command
|
||||
- Add a status-code-to-string renderer covering all four values plus a safe fallback for an unrecognized code (mirroring the existing responder-role renderer's convention), and extend the client command's existing per-controller line to print the rendered status alongside that controller's name and address.
|
||||
- Observable: piping `ctrlstatus` through the client prints each configured controller's connection status alongside its existing name:address line.
|
||||
- _Requirements: 13.1, 13.6_
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue