I2707 — majordomus doctor reports a stale server, or says plainly that it checks governance only
Make the top-level majordomus doctor either report the runtime of the checkout (server, lease, mesh) or say in its help, usage and reference that it checks governance alone.
DONE wave 1 · p1 · implementation profile · runs alone
Objective
Make the top-level majordomus doctor either report the runtime of the checkout (server, lease, mesh) or say in its help, usage and reference that it checks governance alone.
Why
Split from I2157 on 2026-10-14. I2157 made /api/v1/ready refuse a lost lease and name a degraded layer, and gave health.report a mesh check, and its desired_state said 'Not done here' of majordomus doctor, which still checks governance alone while its help does not say so; the shell usage, share/commands.yaml and docs/CLI.md that would change together were left to their own change. Its acceptance criteria still required it, so it could never close. Baseline audit of 2026-10-09 at master 1fb8d6be44, failure gap 10 and premise 4.
Current state
majordomus doctor is the governance doctor of lib/doctor.sh; it checks nothing about the server, the lease or the mesh, which its name suggests it does. Runtime health is read through health.report, GET /api/v1/ready, serve status and mesh doctor.
Desired state
majordomus doctor in a checkout whose server is stale reports it, or its help, the shell usage, share/commands.yaml and docs/CLI.md say together that it checks governance only and name where runtime health is read.
Scope
- lib/doctor.sh
- bin/majordomus
- share/commands.yaml
- docs/CLI.md
- test/cases
Out of scope
- Readiness and the health.report mesh check, which I2157 delivered
Dependencies
Acceptance criteria
- majordomus doctor in a checkout whose server is stale reports it, or its help states that it checks governance only
Validation
- bin/majordomus plan validate
Evidence required
- doctor_states_its_reach_case
Evidence
| covers | type | command | result | at commit |
|---|---|---|---|---|
| doctor_states_its_reach_case | test | bash test/run.sh 3050_doctor_says_it_checks_governance_only | ok 3050: doctor --help, bin/majordomus usage, share/commands.yaml (summary + note) and docs/CLI.md say doctor checks governance only and name majordomus serve status, majordomus mesh doctor, GET /api/v1/health and GET /api/v1/ready; the case failed on master c0e3585dc8 (no 'governance only' in doctor --help) (run 2026-10-15 01:2xZ) | c0e3585 |
Timeline
- started
- 2026-10-15T01:27:13Z
- verified
- 2026-10-15T01:27:25Z
- completed
- 2026-10-15T01:27:40Z
Those three fields, the evidence above and the state of the dependencies are all the status is made of. There is no status field to disagree with them.
Canonical record: .ai/repo/project/issues/I2707.yaml. Read it back with majordomus plan show I2707.