Кандидат v1.74.0 после починки свидетеля

Первый кандидат держал не дефект продукта, а мигающий свидетель ресайза: он
фиксировал экранные координаты заранее, а карточка переводит их обратно в момент
события. Свидетель починен (#533), содержание релиза не изменилось.

Трейлер `Release:` просит CI прогнать тяжёлые гейты — смоки, golden и полное
сравнение производительности — на этом SHA.

Issue: #533
User-Visible: no
Release: v1.74.0

docs/STATUS.md

@@ -22,7 +22,7 @@ metadata). Only an explicit owner-approved emergency hotfix may skip this gate.
 | Item | State |
 |---|---|
 | Version | **v1.74.0** everywhere (manifest, const.py, package.json, CARD_VERSION in the card and the editor runtime) |
-| Current local cycle | **Stable v1.74.0** — `main` is fast-forwarded to the tested `dev` SHA and the GitHub Release is public. The line aggregates from the stable v1.73.0: the plan is noticeably smoother and in Firefox dramatically so — a pan frame now moves what is already drawn by a composited transform with the scene re-rasterizing on a budget (#531), and a marker shadow sized in container units no longer restarts a non-composited animation on every marker at once (#524); the printed plan is about a third larger because the in-plan dimension labels shrank and the separate column of external dimensions is gone (#530); a plan left over from the era of rooms without walls can be edited again, the leftover cleaned up on the first save (#529, reported in #527); plus alignment guides that follow the gesture (#521), a summary panel that neither freezes the first frame nor claims an unavailable source (#509) and whose settings dialog scrolls again (#508), no replayed door leaf on a space switch (#525), and 12.8 KB less on a cold start (#526). Internal in the line: #528, #518, #517, #512, #511, #510. The speed verdict for #531 is deliberately NOT claimed by the sandbox — headless Firefox and Chromium hold 60 fps on both the old and the new path; it is owed by a Firefox profile from the owner's machine on the same pan. |
+| Current local cycle | **Stable v1.74.0** — `main` is fast-forwarded to the tested `dev` SHA and the GitHub Release is public. The line aggregates from the stable v1.73.0: the plan is noticeably smoother and in Firefox dramatically so — a pan frame now moves what is already drawn by a composited transform with the scene re-rasterizing on a budget (#531), and a marker shadow sized in container units no longer restarts a non-composited animation on every marker at once (#524); the printed plan is about a third larger because the in-plan dimension labels shrank and the separate column of external dimensions is gone (#530); a plan left over from the era of rooms without walls can be edited again, the leftover cleaned up on the first save (#529, reported in #527); plus alignment guides that follow the gesture (#521), a summary panel that neither freezes the first frame nor claims an unavailable source (#509) and whose settings dialog scrolls again (#508), no replayed door leaf on a space switch (#525), and 12.8 KB less on a cold start (#526). Internal in the line: #528, #518, #517, #512, #511, #510. The speed verdict for #531 is deliberately NOT claimed by the sandbox — headless Firefox and Chromium hold 60 fps on both the old and the new path; it is owed by a Firefox profile from the owner's machine on the same pan. The first release candidate was held back by a flaky witness, not by a product defect: `demo/smoke_room_resize.mjs` fixed its screen coordinates once, up front, while the card converts them back at event time, so a late layout made the gesture commit the wrong amount — red on the runner, green locally. The witness now converts inside the same frame as the dispatch, checks that every event was delivered and pins the mapping itself (#533). |
 | 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) |