Release v0.8.0 — Portainer-first install, in-app guide

- Install from Portainer with no command line: paste the compose, set a
  folder and a password, deploy. Inspector creates its own config and
  detects Docker socket permissions by itself.
- Illustrated how-to guide inside the app (Help tab) and in the repo.
- Containers added in the UI are watched right away, no restart.
- maintenance_window switch on the container form.
- README with logo and screenshots; INSTALL rewritten for Portainer.

CHANGELOG.md

@@ -7,6 +7,47 @@ Version numbers follow [Semantic Versioning](https://semver.org/spec/v2.0.0.html
 
 ---
 
+## [0.8.0] — 2026-10-27
+
+### Added
+
+- **Install from Portainer with no command line.** Mount one folder per purpose
+  (`/app/config`, `/app/logs`, `/app/data`) and deploy. If there's no config yet,
+  Inspector writes a starter `config.yml` (dashboard on, event history on, no
+  containers). Dashboard login comes from `INSPECTOR_USERNAME` / `INSPECTOR_PASSWORD`;
+  without a password, one is generated and printed once in the container logs.
+- **Docker socket access is automatic.** A new entrypoint starts as root only long
+  enough to read the socket's group and fix ownership of the mounted folders, then
+  runs Inspector as `PUID:PGID` (default `1000:1000`) with that group added.
+  `DOCKER_GID` / `group_add` are no longer needed.
+- **In-app guide** at `/guide/` with screenshots, linked from a new **Help** tab
+  in the header. Also in the repo at `src/inspector/assets/guide/guide.html`.
+- **`maintenance_window` switch** on the container form, so containers can opt in
+  to the daily maintenance window without editing YAML.
+
+### Fixed
+
+- Containers added from the UI are now watched on the next check. Before, the
+  loop only logged that a restart was needed, despite what the UI said.
+  Containers removed or disabled from the UI are dropped the same way.
+- Status page could fail to render while a container was being added or removed
+  (it iterated the live state dict and assumed every entry was still in config).
+
+### Changed
+
+- Config path: `--config`, then `$INSPECTOR_CONFIG`, then `/app/config.yml` if
+  present (existing single-file setups keep working unchanged), then
+  `/app/config/config.yml`.
+- Public `compose.yml`, `INSTALL.md`, and `README.md` rewritten for Portainer
+  stacks; README gains the logo and screenshots.
+
+### Upgrade notes
+
+- Existing deployments need no changes. To adopt the simpler layout, move
+  `config.yml` into the new config folder and switch to the new compose file.
+
+---
+
 ## [0.7.4] — 2026-10-27
 
 ### Changed