german/houseplan-card
1
0
Fork 0
mirror of https://github.com/Matysh/houseplan-card synced 2026-09-29 03:09:36 +00:00
Code Issues Actions 6 Packages Projects Releases Wiki Activity

docs: record the parallel v1.68.0 performance gate

Browse Source 
Issue: #322
User-Visible: no
This commit is contained in:
Matysh
2026-08-27 12:13:46 +03:00
parent 8210af6472
commit de7554e9e0
1 changed files with 1 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/STATUS.md
+1 -1
View File
@@ -22,7 +22,7 @@ metadata). Only an explicit owner-approved emergency hotfix may skip this gate.
| Item | State |
|---|---|
| Version | **v1.68.0** everywhere (manifest, const.py, package.json, CARD_VERSION) — stable promotion of the published v1.68.0-beta.4 product line |
| Current local cycle | v1.68.0 promotes the exact product behaviour already published through beta.4: stable wall-segment identity and atomic model-v9 migration, unified zero-thickness walls, repaired junction rendering and reliable plan editing. The complete local suite and exact-tree Validate are green. The first `main` Full Performance attempt exposed only a release-infrastructure compatibility gap with the older v1.66.0 baseline; the backward-compatible baseline materialization fix changes no shipped bundle or product behaviour, and the repaired exact-SHA Validate plus Full Performance remain the publication gates. |
| Current local cycle | v1.68.0 promotes the exact product behaviour already published through beta.4: stable wall-segment identity and atomic model-v9 migration, unified zero-thickness walls, repaired junction rendering and reliable plan editing. The complete local suite and exact-tree Validate are green. Stable-gate diagnostics exposed two infrastructure-only defects: legacy v1.66.0 lacked the current bundle materializer, and five full 7-sample profile pairs could not fit a 60-minute serial job. Old baselines now use an equivalent fresh-bundle fallback, while independent profile pairs run in parallel and retain same-runner sequential base/candidate comparison. These repairs change no shipped bundle or product behaviour; their exact-SHA Validate and Full Performance remain the publication gates. |
| Hidden Labs Stage | #89 Stage 1 ships in v1.63.0-beta.1. #122 Stage 2 ships in v1.64.0 and evolves the same hidden, expiring `iso` experiment with matte walls, a low exterior floor edge, restrained shared shadows and live vertical door/window/gate panels. Flat remains default; editors and `houseplan-space-card` remain flat; live floor effects and HA actions remain unchanged. Public activation remains a separate task. |
| 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): only significant user changes get individual bullets, while minor/code-only work is grouped as `Мелкие исправления и улучшения` / `Small fixes and improvements`; every body ends with separate links to the Russian and English changelogs. Detailed RU/EN changelog bullets may link the corresponding closed GitHub Issues; 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) |