kylon-cli 0.3.0-next.471 → 0.3.0-next.472

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/README.md CHANGED
@@ -83,6 +83,22 @@ runtime service on the old build. The update notice the CLI prints for local
83
83
  runtimes uses exactly this command; `kylon gateway service repair` is the same
84
84
  reconciliation under its recovery-oriented name.
85
85
 
86
+ `repair` goes one step further than `upgrade`: after reconciling the Kylon
87
+ side it installs any provider CLI this machine's placements need but do not
88
+ have, so the commonest broken placement — a Codex agent on a host with no
89
+ `codex` — is fixed by the command whose name says it fixes things. The
90
+ boundary is deliberate. It installs the npm globals this product already tells
91
+ people to install (`@openai/codex`, `@anthropic-ai/claude-code`), echoing each
92
+ command before it runs, and it does nothing else on the operator's behalf: it
93
+ never runs a preset's third-party installer script, never removes a `kylon`
94
+ install this product did not create, and never re-registers an agent. Those
95
+ stay reported findings with a command to run deliberately. Pass
96
+ `--no-provider-install` to reconcile Kylon only.
97
+
98
+ Nothing installs a provider CLI in the background. A daemon that finds its
99
+ provider missing reports it and waits — installing software on someone's
100
+ machine is something they ask for, not something a health check decides.
101
+
86
102
  The drain waits up to five minutes for in-flight agent work, and a drain that
87
103
  exhausts its window rolls the upgrade back — so a persistently busy host would
88
104
  never upgrade without an operator interrupt. Two are available: