mirror of https://github.com/Matysh/houseplan-card synced 2026-10-05 06:08:59 +00:00

Files

T

Matysh 181b61ae8e fix(led): colour the active core from its resolved light

Keep off and unavailable presentation unchanged. Extend the rendered colour
and surface matrix and retain the independent white-source geometry oracle.

Issue: #790
User-Visible: yes

2026-10-03 23:54:21 +03:00

5.6 KiB

Raw Blame History

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. 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-03 — rerun `node scripts/status-snapshot.mjs` for the current tree
Version	1.79.0 in all 7 version sources (`scripts/release-contract.mjs`)
Latest stable tag	`v1.78.0`
Latest prerelease tag	`v1.79.0-beta.7`
Tests	Node unit 3538 · pure backend 423 · HA-harness backend 311 · browser smokes 294 (`npm run inventory`)

Current cycle and standing decisions

Item	State
Current local cycle	Stable v1.79.0 candidate — promotion of published beta.7, with no new feature source. The line adds LED strips and the moon on any background, stabilizes 2.5D layout, and improves room-fill transitions and warm remount. Exact-SHA full gates precede publication; `main` is promoted only to the tested candidate.
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.
LED regression acceptance	#788 covers mixed face/free and fractional-coordinate joins, winding-safe field unions, retained endpoints/acute vertices and circle–wall transition events. The actual owner export is exercised locally; public fixtures are synthetic. Pixel oracles, not just SVG counts, protect the visible falloff.
LED core colour	#790 makes the on core follow the resolved light colour with or without Glow. Off, unavailable and non-live static strips keep their neutral presentation; geometry and field brightness are unchanged.
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 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

Read by role, as AGENTS.md › Read this first lists it.
Clone https://github.com/Matysh/houseplan-card and run npm 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).

5.6 KiB Raw Blame History Unescape Escape