dsh-home-hosted 0.7.7 → 0.8.1

package/README.md

@@ -179,7 +179,7 @@ Topic docs, one per area — written for whoever has to touch it next:
 
 One entry (`dsh`), one toggle: the panel keeps it alive, restarts it and reclaims its port. A
 detached restart is recognised on macOS and Linux (`follow`); Windows cannot prove identity through
-a `.cmd` shim, so it uses `onPortConflict: kill`. The plugin pins home-hosted 0.7+, so every key it
+a `.cmd` shim, so it uses `onPortConflict: kill`. The plugin pins home-hosted 0.8+, so every key it
 writes is one that panel parses.
 <sub>Web only — see **dsh Desktop** above.</sub>
 

package/docs/BOOT.md

@@ -232,7 +232,7 @@ would be: `BootStatus.recommended` is the host's own `recommend()` answer, and `
 to it when nothing is installed (`pickOf(mechanism ?? before.mechanism ?? before.recommended)`). So
 "Automatic" says which mechanism the next install would use, instead of leaving a person to install it
 and read the result. The sentence is only shown while nothing is installed under that mechanism, and it
-is absent — never "undefined" — when an older panel does not send the field.
+is absent — never "undefined" — when a response omits the field.
 
 The `Details` block describes the mechanism that is actually **installed**, which is a different one
 while a switch is pending, so both it and the picker read one shared lookup rather than each formatting

package/docs/DESIGN.md

@@ -35,12 +35,14 @@ its page.
 
 ## Config compatibility was dropped, deliberately
 
-`onPortConflict: kill` arrived in home-hosted 0.6.0 and `persistent` in 0.6.3, and an older panel
-handed either key can refuse to *boot* from the config. The plugin used to consult the answering
-panel's version and refuse or drop them (`KILL_UNSUPPORTED`). That is gone on purpose: it pins
-`home-hosted@^0.7.21` and autostarts its own copy, so a panel older than those keys is only reachable by
-deliberately preferring an old global install — and this is pre-1.0. Supporting older panels again means
-bringing that check back from history, not re-deriving it.
+`onPortConflict: kill` (0.6.0), `persistent` (0.6.3), `restart <id>` (0.7.13) and the nullable-`label`
+patch (0.7.21) all predate the release this plugin pins. The plugin used to consult the answering
+panel's version and refuse or drop those keys (`KILL_UNSUPPORTED`), and later to retry a `restart` as a
+stop-then-start pair. Both are gone: it pins `home-hosted@^0.8.0`, which refuses an older panel
+outright, so neither check could ever fire again.
+
+An old state root is upgraded by running the latest 0.7.x **once, before installing 0.8** — its first
+run moves the state into `.hh/`.
 
 ## Tests
 

package/docs/PANEL.md

@@ -51,9 +51,15 @@ Verified against a real 0.7.20 panel and its own CLI: `PATCH {port:null}` delete
 and `bootstrap` have a schema that admits `null`; `_hh` is still exactly four routes; and every route,
 subcommand and flag this plugin drives is unchanged. The console **file** — `.hh/.logs/home-hosted.log`
 plus its `.1`, and the 5 MB rotation — is unchanged too, and this plugin's reader still matches
-`home-hosted logs` line for line. A capability that needs a *newer* 0.7.x degrades rather than raising
-the floor: `logs` (0.7.12) is a file read either way, and `restart <id>` (0.7.13) falls back to the
-stop/start pair it replaced.
+`home-hosted logs` line for line.
+
+**0.8.0 stopped relocating an old state root, and this plugin follows it.** A 0.6.x root used to be
+moved into `.hh/` on 0.7's first run; 0.8 refuses it instead, before any command resolves a path into
+it, so a config at the old paths is never read as an empty panel. **Upgrading from 0.7 or earlier? Run
+the latest 0.7.x once first — that release moves the state — then install 0.8.** The plugin's floor is
+`0.8.0` for the same reason, so a 0.7.x panel is reported as unsupported rather than driven. That
+removed the last version-conditional code here: a stop-then-start fallback for a panel without
+`restart <id>`, and `panel.migrate`, whose CLI no longer performs the move.
 
 **0.7.21 widens that nullable set by one field, and it closed a bug here.** Clearing a server's label
 sent an empty string, which the panel accepts and saves — so the entry kept a blank label instead of

package/docs/WORKSPACES.md

@@ -42,8 +42,8 @@ machines. The RPC endpoint still defaults an absent value (the page always sends
 call should not break), but a model is never left to guess.
 
 A pre-0.7 root is not read or written at all. It is recognised (`legacyRoot` on the status), refused on
-every write, and fixed through one action that runs `home-hosted migrate --yes` — the same relocation a
-first 0.7 start does on its own.
+every write, and the refusal names the one remedy: run the latest 0.7.x once — its first run moves the
+state into `.hh/` — before installing 0.8. Nothing is changed or deleted by the refusal.
 
 ## Several panels on one machine
 
@@ -76,12 +76,8 @@ that endpoint has, least invasive first:
   credential, but no live status either, and a running panel applies a changed definition at that
   entry's next start;
 - `cli` runs the CLI against its state root — the only runtime path the panel itself offers.
-  `start`/`stop` act on one entry; a restart is now the CLI's own `restart <id>` (home-hosted
-  0.7.13), which is what the panel's UI does and leaves no window in which the entry is down. A
-  local panel older than that refused the command before touching anything, so the plugin falls
-  back to the stop-then-start pair and reports `downgraded` in the result — the refusal is
-  detected from the CLI's own text, including the `Unexpected argument` a 0.7.12 CLI prints for
-  the positional id;
+  `start`/`stop` act on one entry, and a restart is the CLI's own `restart <id>`, which is what the
+  panel's UI does and leaves no window in which the entry is down;
 - `api` mints a token for that panel, enrols it and uses its HTTP API — the only way to get live
   status, and it replaces any token that panel had, which the question says outright.