Кандидат v1.76.0-beta.5 после починки перфоманса

Трейлер `Release:` просит CI прогнать тяжёлые гейты — смоки, golden и полное
сравнение производительности — на этом SHA: кандидат 1734b077 был задержан
собственным гейтом производительности изометрии, регрессия из #583 починена
коммитом выше по §11.4 (та же задача, без повторного ревью, команда и её
результат записаны в issue).

Issue: #583
User-Visible: no
Release: v1.76.0-beta.5

docs/STATUS.md

@@ -22,7 +22,7 @@ metadata). Only an explicit owner-approved emergency hotfix may skip this gate.
 | Item | State |
 |---|---|
 | Version | **v1.76.0-beta.5** everywhere (manifest, const.py, package.json, package-lock in both places, CARD_VERSION in the card and the editor runtime) |
-| Current local cycle | **Beta v1.76.0-beta.5 candidate** — prepared from the exact integrated `dev` tree; `main` remains on v1.75.0. It fixes fixed white gaps during pinch-zoom on large “Follows the Sun” plans in the HA app (#582), outer-corner sun rays shining through thick walls (#580) and a room keeping its own colour after “As the space” — orphan room colours now heal on read (#581); the hidden 2.5D presentation is refined internally (#583). First beta whose bookkeeping closes issues from the immutable `RELEASE-MEMBERSHIP.json` of the candidate (#547). |
+| Current local cycle | **Beta v1.76.0-beta.5 candidate** — prepared from the exact integrated `dev` tree; `main` remains on v1.75.0. It fixes fixed white gaps during pinch-zoom on large “Follows the Sun” plans in the HA app (#582), outer-corner sun rays shining through thick walls (#580) and a room keeping its own colour after “As the space” — orphan room colours now heal on read (#581); the hidden 2.5D presentation is refined internally (#583). First beta whose bookkeeping closes issues from the immutable `RELEASE-MEMBERSHIP.json` of the candidate (#547). The first candidate was held by its own performance gate: the #583 refinement made the 2.5D overlay collision resolver scan a 1 px disc of offsets and ask every wall about every candidate — resize 344 → 3635 ms, pan/zoom 37 → 1244 ms against the tree before it. Measurement, not guesswork, named the cost (98 % of positions rejected by walls); the search now walks a 4 px lattice and refines to 1 px around the winner, group pass 9584 → 839 ms with identical resolution quality, and this commit re-marks the candidate so the heavy gates re-run on the fixed SHA (§11.4). |
 | 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; #570 adds the Stage 4 designer handoff and #583 refines it on `dev`: only the building ambient shadow remains, door/gate volumes pivot on the selected host face without strokes, and devices/lock badges receive deterministic mutual collision correction while room labels remain passive below them. The same hidden `iso` view uses a fixed 0°/20° camera and scale-aware wall height 84, low screen-facing device/room/lock overlays without tethers or ground dots, neutral full-height window frames with blue glass, and bounded theme materials. 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 4 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 stable release is produced by `release.yml` (`workflow_dispatch` on `main` with the tag) — the only publisher of installable assets since #540: gates on the exact SHA (Validate, Full Performance, E2E on the candidate commit), one build, `houseplan.zip` archived from the committed tree, `SHA256SUMS`, draft → publish → read-back verification; a release published by hand in the GitHub form is turned back into a draft and walked through the same path, and a re-dispatch on a public tag is a repair that adds only missing assets. 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) |