Skip to content

Treat the transition companion absence as healthy - #171

Merged
myobie merged 1 commit into
mainfrom
fix/transition-companion-doctor
Sep 5, 2026
Merged

Treat the transition companion absence as healthy#171
myobie merged 1 commit into
mainfrom
fix/transition-companion-doctor

Conversation

@myobie

@myobie myobie commented Sep 5, 2026

Copy link
Copy Markdown
Collaborator

Release A intentionally installs no fabric-sync binary or service. Doctor currently reports both absences as problems and tells the operator to run fabric service install.

This change recognizes the exact healthy transition: the main daemon answers, embedded sync owns the engine, and both the companion binary and service are absent. It reports the service and runtime as healthy and offers no action.

The paired states stay strict. A present companion binary without its service still requests service installation. An enabled service without its binary requests a matched pair. An unknown binary state stays unknown and offers no action.

The red test reproduced the deployed Release A report before the fix. Local proof passed 513 library tests, with five measurements ignored. The doctor integration target passed two tests. A read-only doctor run against the live Silber state reports both transition checks as healthy.

@myobie
myobie merged commit 475807e into main Sep 5, 2026
3 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.

1 participant