feat: add the House Plan sidebar panel

Issue: #486
User-Visible: yes

docs/STATUS.md

@@ -22,7 +22,7 @@ metadata). Only an explicit owner-approved emergency hotfix may skip this gate.
 | Item | State |
 |---|---|
 | Version | **v1.73.0-beta.4** everywhere (manifest, const.py, package.json, CARD_VERSION) |
-| Current local cycle | On top of v1.73.0-beta.4, the pending #484 fix preserves a complete reconstructable external dimension chain around rectangular facade steps while retaining strict post-exit wall-collision rejection. PDF unit, browser-download, mutation and dedicated Linux golden/semantic witnesses cover the regression. The interaction performance smoke aggregate keeps hosted-runner headroom while retaining the unchanged per-series, Long Task, heap, cache and structural gates (#483). Publish from `dev` only after exact-SHA Validate is green; `main` remains at v1.72.0. |
+| Current local cycle | On top of v1.73.0-beta.4, #484 preserves a complete reconstructable PDF exterior-dimension chain around rectangular facade steps. #486 adds the primary `/houseplan` sidebar panel around the same full-card model, with fail-soft owned backend registration, a separate bounded panel entry, read-only empty-state safety and full-width Sections default for the optional dashboard card. The card graph and saved plan/config/layout models remain unchanged. Publish from `dev` only after exact-SHA Validate is green; `main` remains at v1.72.0. |
 | Hidden Alpha Stage | #89 Stage 1 ships in v1.63.0-beta.1, #122 Stage 2 in v1.64.0 and #160 Stage 3 in v1.73.0-beta.1. The same hidden `iso` view uses the fixed 4° camera, raised/tethered device-room-lock overlays, deeper openings and bounded theme materials; #471 removes the overlay plates from paint while retaining their safety geometry. Since #448 the experiment is enabled only through the single indefinite browser-local `hp_alpha` gate; it is not expiring and has no per-stage key. Flat remains default; editors, `houseplan-space-card`, floor effects, stored coordinates and HA actions remain unchanged. Stage 3 stays internal and is absent from public changelog/user documentation. |
 | Workflow | Superseded 2026-08-12: the pre-1.62 rule of "local edits without tests or commits" is **dead** — since release 1.62 every product change follows `PROCESS.md` (issue in `S5-ready`+, branch `issue/<NN>-slug`, trailers on every commit, review pipeline; `AGENTS.md` is the summary). Release mechanics below remain current. A requested pre-release gets a production build plus the smallest targeted unit/smoke set covering the changed surfaces, one tested `dev` commit/tag and a GitHub Release with `prerelease=true`; `main` stays untouched. The complete local frontend/backend/smoke gate runs only before a stable release, after which `main` is fast-forwarded to the exact tested `dev` SHA and the GitHub Release uses `prerelease=false`. Release bodies are short and bilingual (Russian first); every bullet links its GitHub issue (#NN) so the #328 rules stay machine-checkable. A STABLE body aggregates the changelog since the PREVIOUS STABLE release (never since the last beta): features/fixes described across the line's beta changelogs must appear, while bugs that were introduced and fixed strictly inside the beta line (never shipped in any stable) are excluded — draft with `npm run release:notes -- <tag>`, curate by hand, then `npm run release:notes -- <tag> --verify` must pass. `Мелкие исправления и улучшения` / `Small fixes and improvements` is allowed only when the range really contains user-visible work not itemised in the body; a single-issue hotfix ships without it (the verifier enforces this). Every body ends with separate links to the Russian and English changelogs. Open or partially delivered issues are never presented as shipped. Telegram announcements are sent only for stable releases; beta and RC publication is silent. `docs/RELEASE-NOTES.md` is the current canonical body instance; `npm run release:prerelease -- <tag> --issues=… --yes` is the primary local publication path and the manual `Publish prerelease` workflow is its GitHub-only equivalent once present on `main`. Nothing is copied to the home instance by hand |
 | GitHub | https://github.com/Matysh/houseplan-card — [Issues](https://github.com/Matysh/houseplan-card/issues) are the canonical task records; their labels carry priority and workflow status (`PROCESS.md` §9). GitHub Projects is no longer used. `main` carries stable releases; pre-release tags may point directly at `dev`. Work lands on `dev` and is merged into `main` for a stable release, so `dev` is normally equal to or ahead of `main`, never behind. Push via SSH key `ha_jb` (remote git@github.com:…); API releases via the fine-grained PAT in `~/.git-credentials` (Contents R/W, issued 2026-07-23) |
@@ -40,6 +40,13 @@ metadata). Only an explicit owner-approved emergency hotfix may skip this gate.
 
 ## Current feature surface (since the 2026-07-17 snapshot)
 
+- **Primary sidebar panel + optional cards** (#486): the integration registers
+  `/houseplan` for every signed-in user after backend initialization. Its own HA
+  app bar wraps the same `houseplan-card`, so spaces, permissions, actions and
+  editor lifecycle stay shared; only the duplicated product title and outer
+  dashboard-card chrome are removed. Failure to register the panel is isolated
+  and reported in System Health. The optional full dashboard card requests full
+  width in Sections by default; explicit HA sizing remains authoritative.
 - **Three editors + View**: Plan / Devices / Background (decor layer v1.33) as
   tabs with an X to close; View is the default; only the last space persists,
   while reload/return from another HA route always starts in View (#93).