# 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 are `docs/DEVELOPMENT.md` › Release, > and task scope and status live in GitHub Issues and their labels. Update 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-09-27 — rerun `node scripts/status-snapshot.mjs` for the current tree | | Version | **1.78.0-beta.6** in all 7 version sources (`scripts/release-contract.mjs`) | | Latest stable tag | `v1.77.0` | | Latest prerelease tag | `v1.78.0-beta.5` | | Tests | Node unit 3140 · pure backend 393 · HA-harness backend 302 · browser smokes 278 (`npm run inventory`) | ## Current cycle and standing decisions | Item | State | |---|---| | Current local cycle | **Beta v1.78.0-beta.6 candidate** — refreshed on the exact integrated `dev` tree after seven S8 items landed. It makes stair drawing, selection, resizing, rotation and snapping follow the decor box contract (#676), and flushes deferred virtual-light and vacuum-trail state during Home Assistant shutdown (#655). The candidate also synchronizes the English user guide (#668), tightens CI scheduling and runner hygiene (#658), reduces browser mutation guards and records their policy (#659), removes private infrastructure details from public documentation (#677), and archives obsolete scripts and documents (#678). `main` remains on stable v1.77.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. | | 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`](../legacy/docs/STATUS-FEATURES.md). ## Where the rest lives - Scope and personas — `docs/SCOPE.md`; process, statuses and gates — `PROCESS.md` (role digests in `docs/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 1. Read by role, as `AGENTS.md` › Read this first lists it. 2. Clone `https://github.com/Matysh/houseplan-card` and run `npm ci` — it installs the hooks (`git config core.hooksPath` → `.githooks`). 3. Start a task from its packet: `node scripts/task-packet.mjs --issue NN`. 4. The task's local gate is `npm run gate:small`; nothing is copied to a Home Assistant instance by hand (`PROCESS.md` §12).