hydromind-cli-maintainer

Diagnose HydroMind CLI queue readiness problems and stuck runs by escalating from public CLI facts to internal read-only evidence. This process determines root causes for queue start readiness issues and runtime anomalies, then translates findings back to product semantics for remediation.

Contradictory HydroMind queue status occurs when public CLI facts lack sufficient evidence to explain the anomaly. Escalate to internal read-only evidence from the source checkout and control layer internals to identify the root cause, then map the findings back to public CLI surface semantics.

Troubleshoot HydroMind CLI anomalies by enforcing strict evidence boundaries during escalation. Consult internal read-only evidence to determine root causes, but preserve public CLI surface semantics by translating findings back into user-facing remediation guidance for queue, run, and maintenance workflows.

Diagnosing HydroMind queue stop inconsistencies and runtime anomalies requires access to the HydroMind source checkout and knowledge of control layer internals. These prerequisites enable the structured escalation from public CLI facts to internal read-only evidence for root cause analysis.

Escalate HydroMind CLI diagnostics to internal evidence when public CLI facts cannot explain queue or runtime anomalies, such as contradictory queue status, stuck running runs, or readiness problems. Start with public facts, then consult internal read-only evidence as needed to resolve the issue.

Resolve repo-maintenance work on HydroMind CLI and queue diagnostics by escalating from public CLI facts to internal read-only evidence. Analyze control layer internals to determine root causes, then translate the findings back into public CLI semantics for user-facing remediation across maintenance workflows.