Publish the 58 integrated S8 issues since beta.1. Synchronize versions, rebuild committed frontend assets, refresh ratchets to measured facts, and update release metadata. All 11 documentation screenshots were accepted as pixel-identical in WSL, without replacing PNG bytes. Owner-authorized manual ship review covers all 13 ship issues; High 0. Local checks: build/typecheck, 3510 unit tests passed (30 skipped), 20 selected browser smokes, Stage 3 dense observable contract. Full exact-SHA Validate remains mandatory before publication. Release: v1.79.0-beta.2 Issue: #694 Issue: #703 Issue: #704 Issue: #705 Issue: #707 Issue: #708 Issue: #712 Issue: #714 Issue: #715 Issue: #716 Issue: #717 Issue: #718 Issue: #719 Issue: #720 Issue: #721 Issue: #722 Issue: #723 Issue: #724 Issue: #725 Issue: #726 Issue: #727 Issue: #728 Issue: #729 Issue: #730 Issue: #731 Issue: #732 Issue: #733 Issue: #734 Issue: #735 Issue: #736 Issue: #737 Issue: #738 Issue: #739 Issue: #740 Issue: #741 Issue: #742 Issue: #743 Issue: #744 Issue: #745 Issue: #746 Issue: #747 Issue: #748 Issue: #749 Issue: #750 Issue: #751 Issue: #752 Issue: #753 Issue: #754 Issue: #755 Issue: #756 Issue: #757 Issue: #758 Issue: #759 Issue: #760 Issue: #761 Issue: #762 Issue: #772 Issue: #775 User-Visible: yes
5.2 KiB
Project status
The current state for a resuming session: a generated snapshot, the current cycle and the standing decisions that explain it. Rules are not here — the process is
PROCESS.md, release mechanics aredocs/DEVELOPMENT.md› Release, and task scope and status live in GitHub Issues and their labels. The snapshot below is generated — never edit it by hand; the prose sections after it are edited by hand, a row in the same commit as the change it describes (PROCESS.md§2.6).
Snapshot
Everything computable from the tree and git; regenerate, never edit by hand (#634). Workflow status is not here — it lives only in issue labels.
| Item | State |
|---|---|
| Generated | 2026-10-02 — rerun node scripts/status-snapshot.mjs for the current tree |
| Version | 1.79.0-beta.2 in all 7 version sources (scripts/release-contract.mjs) |
| Latest stable tag | v1.78.0 |
| Latest prerelease tag | v1.79.0-beta.1 |
| Tests | Node unit 3470 · pure backend 397 · HA-harness backend 303 · browser smokes 289 (npm run inventory) |
Current cycle and standing decisions
| Item | State |
|---|---|
| Current local cycle | Beta v1.79.0-beta.2 candidate — 58 integrated S8 issues since beta.1. The moon works on any background and explains its visibility (#718, #731); room/floor changes no longer flash (#742, #745, #746); delayed warm restoration keeps the editor camera and dialog while respecting newer navigation (#756, #762); editor-load retries are explicit (#757), and plan edits invalidate only the affected floor cache (#744). main remains on stable v1.78.0. |
| Branches | main carries stable releases only; pre-release tags point at dev. Work lands on dev, which is equal to or ahead of main, never behind. |
| Warm remount | Delayed editor restoration preserves the original View camera, reserves pending chrome space, and yields synchronously to mode/space navigation (#762). Header/stage dimensions are published as one settled pair. Canonical: docs/WARM-REMOUNT.md. |
| 2.5D View | Public since #649: the installation-wide General settings switch settings.volumetric_view (Display). Flat stays the default and byte-for-byte unchanged; editors and houseplan-space-card stay Flat. Canonical: docs/ISOMETRIC.md. |
| Input support | Owner's rule since 2026-08-08: View and kiosk are fully supported and release-blocking on touch; the three editors are desktop-first, touch editing is best effort. Canonical: docs/TOUCH-SUPPORT.md. |
| Localization | UI in en/ru/de/fr (src/i18n/*.json); German and French load lazily through the registry introduced by #62. |
| HACS and community | In the HACS default catalog since 2026-08-25 (hacs/default#9004): install is a plain HACS search, houseplan.zip is attached to stable tags. Support channel — Telegram chat https://t.me/ha_houseplan; GitHub Issues stay for bugs and features. |
| Furniture | Top-view category/variant palette (#159, #593) from the MIT pack assets/furniture/houseplan-0.4.1 (#606); plan art is lazy (#474), saved geometry and default dimensions never change with the pack. |
| Vacuums | Live puck, server-side trails and fit calibration are shipped; Roomba is not covered. Canonical: docs/VACUUM.md. |
| Demo stand | https://demo.houseplan.tech — public, login demo/demo, resets to a synthetic home every hour. https://dev.houseplan.tech — closed, auto-deploys the head of dev. The demo home and what the stand cannot show: demo/stand/README.md. |
| Privacy | Real-house plan sources and screenshots are gone from the tree; public images are generated from synthetic fixtures (docs/images/screenshots.json). Old images persist in git history and release archives — history is deliberately not rewritten, because that would break release tags and HACS installs. |
The feature surface and early milestones are described by the changelog and the
user guide; the former parallel list is archived in
legacy/docs/STATUS-FEATURES.md.
Where the rest lives
- Scope and personas —
docs/SCOPE.md; process, statuses and gates —PROCESS.md(role digests indocs/process/). - Release mechanics, CI proof semantics and publication —
docs/DEVELOPMENT.md› Release. - Local toolchain (Windows, WSL, the five-minute contour) —
docs/DEVELOPMENT.md. - Tests —
docs/TESTING.md: Node unit, pure backend, HA-harness backend (CI or WSL only; it uses repository-pinned Python plus pytest-homeassistant-custom-component) and browser smokes. Counts and runtime pins are never copied into prose:npm run inventory,npm run toolchain:check.
How to resume work in a fresh session
- Read by role, as
AGENTS.md› Read this first lists it. - Clone
https://github.com/Matysh/houseplan-cardand runnpm ci— it installs the hooks (git config core.hooksPath→.githooks). - Start a task from its packet:
node scripts/task-packet.mjs --issue NN. - The task's local gate is
npm run gate:small; nothing is copied to a Home Assistant instance by hand (PROCESS.md§12).