Skip to content

feat(doctor): simlock doctor says why agent-device is not available - #496

Merged
V3RON merged 5 commits into
mainfrom
task/471
Oct 12, 2026
Merged

V3RON merged 5 commits into
mainfrom
task/471

Conversation

@V3RON

@V3RON V3RON commented Oct 12, 2026 •

Copy link
Copy Markdown
Contributor

Closes #471

Status

Implement: done (17/17 green) Review: round 1 + claims-only passed Hardware: n/a Gate: running
Next: gate

Done when

  • The tests in the spec pass.
  • Removing the kind from isDrift's exclusions makes the doctor.reconciled test fail (run: "leaves the finding out of doctor.reconciled's driftFindings and emits no other event for it" fails).

Assumptions

  • Assumption: the red commit holds the type-only part of the change (the agent-device-unavailable finding type, OptionalModuleFinding, the optionalModules option) and an agentDeviceFindings stub returning no findings — the pre-commit typecheck needs them, and the stub makes its test fail on an assertion rather than a missing module. No behaviour is built.
  • Assumption: the "Could not read optional module findings" warning logs { error: errorMessage(error) }, not the raw { error } — an Error serializes to {}, so the message is the conservative way to name it.
  • Assumption: protocol bumped 30 -> 31 (PROTOCOL_VERSION_RANGE) with the pins in daemon-protocol, daemon/server and gateway/service tests moved — the spec says "protocol +1 at merge".

Review

Spec review: 1 blocking, 0 fixed, 0 notes. Code review: 2 blocking, 2 fixed, 0 notes. Claims review: 1 blocking, 1 fixed, 1 notes.
Rounds: 1. Tokens: 12.0M.

Rejected:

  • spec: src/core/doctor.test.ts:463 optionalModules order unproven — duplicate of the code finding, fixed there

Fixed unreviewed: claims: docs/CLI.md:2141 restart applies to every cause except a failed start, which retries every 30 s.

Written by an agent.

V3RON added 5 commits October 13, 2026 00:14
6 failing -> 0 failing. Doctor reads optional-module findings from a port the
daemon fills with the agent-device supervisor's availability; the CLI prints
one stderr line per finding; protocol 30 -> 31.
1 failing -> 0 failing.
@V3RON

V3RON commented Oct 12, 2026

Copy link
Copy Markdown
Contributor Author

Review notes

Not blocking, not verified. Each is one reviewer's claim.

  • claims: docs/CLI.md:2131 the cause list omits a Node version too old for agent-device, which also gives agent-device-unavailable through the "node" remedy.

Written by an agent.

@V3RON
V3RON marked this pull request as ready for review October 12, 2026 22:30
@V3RON
V3RON merged commit 90af700 into main Oct 12, 2026
37 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

simlock doctor says why agent-device is not available

1 participant