home-hosted 0.7.20 → 0.8.0

package/AGENTS.md

@@ -14,8 +14,9 @@ nanny state), and `run.json` (the live daemon's pid/url/token, 0600). Every work
 `servers.config.json`, `.secrets.json` (0600: Telegram token, plus DDNS credentials sealed with
 AES-256-GCM under `HHOSTED_DDNS_SECRET` — only DDNS is sealed, because it is the one thing replayed
 to a third party), `.logs/` (per server, `<id>.log` plus `<id>.log.1` when it rotates), and
-`.state/` (nanny state, its 0600 spawn spec until read, `ddns.json`). A pre-`.hh` instance is
-relocated automatically by `ensureLayout()`. **The package ships no servers**: never commit a config,
+`.state/` (nanny state, its 0600 spawn spec until read, `ddns.json`). A home still on the 0.6.x layout
+is **refused** by `ensureLayout()`, which names the file and tells the person to install the latest
+0.7.x; 0.8.0 does not relocate it. **The package ships no servers**: never commit a config,
 a seed entry, or a path that names one.
 
 ## Docs
@@ -191,7 +192,9 @@ nobody reads is worse than a long file.
   commit*. A stale doc is a bug like stale code.
 - **UIs move together.** `uis/stock` is not the only client: a change to it — or to a shared contract
   it reads — lands in every other UI under `uis/`, and each altered UI bumps its `ui.json` (see
-  [`.agentDocs/ARCHITECTURE.md`](.agentDocs/ARCHITECTURE.md)).
+  [`.agentDocs/ARCHITECTURE.md`](.agentDocs/ARCHITECTURE.md)). `src/shared/**` is a UI build input, so
+  a contract a UI *calls* at runtime ships in its bundle and needs the bump — the pre-commit hook only
+  inspects `uis/` paths and stays silent on that commit.
 
 ## Releasing
 

package/README.md

@@ -348,7 +348,7 @@ restarts itself), and how hand-edits are validated: [SERVERS.md](./docs/SERVERS.
 | `home-hosted logs` | read the panel's own console output — the file `up` redirects it into (`--lines`, `--follow`, `--json`) |
 | `home-hosted set-password` | set the panel password without opening a browser |
 | `home-hosted set-token` | set the API token scripts and agents use (`--generate`, `--clear`) |
-| `home-hosted migrate` | relocate a pre-workspaces state directory and stamp every config for this release (`--dry-run`, `--yes`) |
+| `home-hosted migrate` | bring every config up to the schema this release understands (`--dry-run`, `--yes`) |
 | `home-hosted init` | scaffold a self-contained project, whose scripts keep state in the repo (`--home ./state`) |
 | `home-hosted ui-switch` | install a UI from a release asset, a zip file or a URL (interactive) |
 | `home-hosted ui-update` | bring an installed UI up to date automatically (official UI) or pick a release (`--old`, `--check`) |
@@ -413,6 +413,17 @@ or a config whose schema is newer than the running release stops `up` with the e
 than starting with defaults that quietly differ from your file. Fix the file, or install the release
 that wrote it.
 
+### Coming from 0.6.x
+
+**Install the latest 0.7.x first, and run it once.** 0.7.0 moved all state from `$HHOSTED_HOME` itself
+into `$HHOSTED_HOME/.hh`, splitting the old all-in-one `servers.config.json` into global settings, a
+`default` workspace, and that workspace's servers — and it did the move automatically on its first
+run. 0.8.0 dropped that relocation.
+
+So a home that is still on the 0.6.x layout is not read: `up` stops and names the file it found,
+rather than starting against an empty state directory beside a config it never opened. 0.7.x does
+the move on its first run; 0.8.0 then starts against the result.
+
 </details>
 
 ---