docs: review document for #226

Issue: #226
User-Visible: no

.githooks/pre-push

@@ -30,14 +30,10 @@ else
 fi
 
 status=0
-gate_status=0
-
-# Строки git читаются один раз: их нужно и локальному набору, и процессному гейту.
-refs=$(cat)
 
 while read -r local_ref local_sha remote_ref remote_sha; do
-  # An empty line (nothing on stdin) and deleting a remote branch push nothing to examine.
-  if [ -z "$local_sha" ] || [ "$local_sha" = "$zero" ]; then
+  # Deleting a remote branch pushes nothing to examine.
+  if [ "$local_sha" = "$zero" ]; then
     continue
   fi
 
@@ -65,25 +61,10 @@ while read -r local_ref local_sha remote_ref remote_sha; do
   if ! node "$gate" --range "${base}..${local_sha}" --target-ref "$remote_ref" $issues_flag >&2; then
     status=1
   fi
-done <<EOF
-$refs
-EOF
-
-# Локальный набор gate:small (#633, прежде opt-in #343) — после процессного
-# гейта: тот отвечает за секунды, а набор идёт минуты; прогоняются оба, чтобы
-# автор узнал обо всех провалах одним кругом. По умолчанию включён для
-# веток issue/* с исполняемым диффом; дифф только класса C/D (документы ревью,
-# changelog, бандл) и ветки вне issue/* его не запускают. Выключение — явное:
-# HP_PREPUSH_GATE=0; HP_PREPUSH_GATE=1 — прогнать для любой ветки. Документация:
-# docs/TESTING.md, docs/DEVELOPMENT.md «Локальный контур за 5 минут».
-if [ -f "$repo_root/scripts/pre-push-gate.mjs" ]; then
-  if ! printf '%s\n' "$refs" | node "$repo_root/scripts/pre-push-gate.mjs" --hook >&2; then
-    gate_status=1
-  fi
-fi
+done
 
 if [ "$status" -ne 0 ]; then
-  cat >&2 <<'MSG'
+  cat >&2 <<'EOF'
 
 Push остановлен: нарушен процесс (PROCESS.md §10.2).
 
@@ -93,12 +74,7 @@ Push остановлен: нарушен процесс (PROCESS.md §10.2).
 
 Обойти проверку можно через `git push --no-verify`, и тогда то же самое найдёт
 job `process-gate` в Validate — уже после того, как код окажется в dev.
-MSG
-fi
-
-if [ "$gate_status" -ne 0 ]; then
-  echo "Push остановлен: красный локальный набор gate:small (см. вывод выше)." >&2
-  exit 1
+EOF
 fi
 
 exit "$status"

.github/workflows/_mutation-gate.yml

@@ -1,357 +0,0 @@
-name: "Мутационный гейт · тело (#623)"
-
-# Реестр известных поломок (issue #85): каждый мутант ломает продуктовый код
-# известным способом, и объявленный тест ОБЯЗАН на этом покраснеть. Тест,
-# оставшийся зелёным на сломанном коде, ничего не защищает — он лишь выглядит
-# защитой, и это хуже его отсутствия.
-#
-# Прогон дорогой и проверяет не продукт, а тесты, поэтому он не входит ни в
-# Validate, ни в цикл разработки, ни в релизный гейт (#513, решение владельца
-# 09.09): каждую ночь по расписанию, отказ — issue с отчётом (#472).
-# Мутанты, задетые диффом, конвейер ревью и слияние гоняют отдельно на своём
-# кандидате (#510); кандидат беты, `full=true` и ночной Validate их не
-# запрашивают (#601) — ночью достаточно этого полного реестра.
-# Дешёвая половина — «якоря патчей живы, guard-файлы существуют» — идёт с
-# обычными юнитами: test/mutation-gate.test.mjs.
-#
-# #332: бандл собирается только мутантам с браузерным гвардом (guardNeedsBundle),
-# компиляция тестов в worktree стартует с тёплого test-build (инкрементальный
-# tsc), а реестр режется на четыре чересполосных шарда — полный прогон
-# укладывается в десятки минут вместо часов. Локальный дифф-режим:
-# node scripts/mutation-gate.mjs --changed origin/dev..HEAD
-#
-# #620: ночь по расписанию на дереве, уже доказанном зелёным полным прогоном
-# (тот же tree материала, тот же SHA workflow, маркер не старше недели), шарды не
-# гоняет — в сводке «reused from run N». Маркер пишет только зелёный агрегатор,
-# поэтому красный не переносится: следующая ночь гонит реестр заново и снова
-# заводит issue (#472). Ручной dispatch гонит полный реестр всегда. Решение —
-# чистая функция scripts/mutation-nightly-reuse.mjs.
-#
-# #623: «SHA workflow» — `job.workflow_sha`, SHA этого файла-тела. В вызываемом
-# workflow `github.workflow_sha` принадлежит вызывающему `mutation-gate.yml` из
-# main и не меняется вместе с телом, поэтому здесь он не используется.
-
-on:
-  # #623: тело вызывается тонким файлом `mutation-gate.yml` из ветки по умолчанию
-  # по ссылке `@dev`; триггеры, run-name и concurrency живут там.
-  workflow_call:
-    inputs:
-      ref:
-        description: "Git ref whose mutation guards must be proved"
-        required: false
-        type: string
-        default: dev
-
-permissions:
-  contents: read
-
-# Concurrency уровня workflow — у вызывающего `mutation-gate.yml` (#623).
-
-jobs:
-  # #549: moving ref разрешается ровно один раз. Все шарды ниже получают один
-  # commit/tree, а не самостоятельно читают dev в разное время.
-  material:
-    name: "Зафиксировать неизменяемый материал"
-    runs-on: ubuntu-24.04
-    timeout-minutes: 10
-    outputs:
-      sha: ${{ steps.identity.outputs.sha }}
-      tree: ${{ steps.identity.outputs.tree }}
-      ref: ${{ steps.identity.outputs.ref }}
-      reuse: ${{ steps.reuse.outputs.reuse }}
-      reused_run: ${{ steps.reuse.outputs.reused_run }}
-    steps:
-      - uses: actions/checkout@3d3c42e5aac5ba805825da76410c181273ba90b1 # v7
-        with:
-          ref: ${{ github.event_name == 'workflow_dispatch' && inputs.ref || 'dev' }}
-          fetch-depth: 0
-      - name: Зафиксировать commit и tree
-        id: identity
-        run: |
-          echo "sha=$(git rev-parse HEAD)" >> "$GITHUB_OUTPUT"
-          echo "tree=$(git rev-parse 'HEAD^{tree}')" >> "$GITHUB_OUTPUT"
-          echo "ref=${{ github.event_name == 'workflow_dispatch' && inputs.ref || 'dev' }}" >> "$GITHUB_OUTPUT"
-      # #620: самый свежий маркер зелёного прогона этого tree и этого workflow.
-      # Ключ уникален на прогон (кэш неизменяем), восстанавливается по префиксу —
-      # иначе перепроверка после недели не смогла бы освежить маркер.
-      - name: Маркер зелёного прогона этого дерева
-        if: github.event_name == 'schedule'
-        uses: actions/cache/restore@55cc8345863c7cc4c66a329aec7e433d2d1c52a9 # v6
-        with:
-          path: artifacts/mutation-green
-          key: mutation-green-v1-${{ steps.identity.outputs.tree }}-${{ job.workflow_sha }}-${{ github.run_id }}
-          restore-keys: |
-            mutation-green-v1-${{ steps.identity.outputs.tree }}-${{ job.workflow_sha }}-
-      - uses: actions/setup-node@820762786026740c76f36085b0efc47a31fe5020 # v7
-        with:
-          node-version: 22
-      # Любой сбой решения — полный прогон: пропуск должен быть доказан, а не
-      # выведен из ошибки. Материал без скрипта (dispatch старого ref) — тоже.
-      - name: Нужен ли прогон
-        id: reuse
-        env:
-          EVENT_NAME: ${{ github.event_name }}
-          TREE: ${{ steps.identity.outputs.tree }}
-          WORKFLOW_SHA: ${{ job.workflow_sha }}
-          RUN_URL_BASE: ${{ github.server_url }}/${{ github.repository }}/actions/runs
-        run: |
-          decision="$RUNNER_TEMP/mutation-reuse.txt"
-          if [ -f scripts/mutation-nightly-reuse.mjs ] && node scripts/mutation-nightly-reuse.mjs --decide \
-               --event="$EVENT_NAME" --tree="$TREE" --workflow-sha="$WORKFLOW_SHA" \
-               --marker=artifacts/mutation-green/marker.json \
-               --summary="$GITHUB_STEP_SUMMARY" --run-url-base="$RUN_URL_BASE" > "$decision"; then
-            cat "$decision" >> "$GITHUB_OUTPUT"
-            if grep -qx 'reuse=true' "$decision"; then
-              echo "::notice::reused from run $(sed -n 's/^reused_run=//p' "$decision")"
-            fi
-          else
-            echo "::warning::решение о повторном использовании не получено — полный прогон"
-            echo "reuse=false" >> "$GITHUB_OUTPUT"
-          fi
-
-  mutants:
-    name: "Мутанты: каждый обязан красить тесты (шард ${{ matrix.shard }} из 6)"
-    needs: material
-    if: needs.material.outputs.reuse != 'true'
-    runs-on: ubuntu-24.04
-    strategy:
-      fail-fast: false
-      matrix:
-        shard: [1, 2, 3, 4, 5, 6]
-    # Шесть чересполосных шардов (#604): при четырёх шард нёс ~203 мутанта из
-    # 810 и рос с реестром — 42 мин 10.09, 57 мин 20.09, 61 мин 21.09, и шард
-    # 2/4 был снят по потолку без единого FAIL. Делитель тот же, что у
-    # `changed_mutants` в Validate; число шардов повторяется в `--shard=i/6`,
-    # `--shards=6` и имени job — тест `mutation-gate.test.mjs` держит их
-    # равными. Бандл собирают только браузерные гварды. Час — потолок против
-    # зависшего Chromium, а не бюджет шарда: шард, упёршийся в него, — сигнал
-    # снова делить, и отчёт (#472) называет такой шард прерванным, не «ok».
-    timeout-minutes: 60
-    steps:
-      - uses: actions/checkout@3d3c42e5aac5ba805825da76410c181273ba90b1 # v7
-        with:
-          ref: ${{ needs.material.outputs.sha }}
-          fetch-depth: 0
-
-      - uses: actions/setup-node@820762786026740c76f36085b0efc47a31fe5020 # v7
-        with:
-          node-version: 22
-          cache: npm
-
-      - run: npm ci
-
-      - uses: actions/setup-python@5fda3b95a4ea91299a34e894583c3862153e4b97 # v7
-        with:
-          python-version: '3.14'
-
-      - name: Установить backend test dependencies
-        run: |
-          # Точные версии — в tests_backend/requirements.txt (#392): без них
-          # резолвер выбирает набор сам, и «зелёный backend» значит разное
-          # в разные дни.
-          pip install -r tests_backend/requirements.txt
-          pip list --format=columns | grep -Ei 'homeassistant|voluptuous|^pytest '
-
-      - name: Кэш браузеров Playwright
-        id: pw
-        uses: actions/cache@55cc8345863c7cc4c66a329aec7e433d2d1c52a9 # v6
-        with:
-          path: ~/.cache/ms-playwright
-          key: playwright-${{ runner.os }}-${{ hashFiles('package-lock.json') }}
-
-      - name: Установить Chromium
-        if: steps.pw.outputs.cache-hit != 'true'
-        run: npx playwright install --with-deps chromium
-
-      - name: Реестр применим к текущему коду
-        run: node scripts/mutation-gate.mjs --check
-
-      - name: Тёплый test-build для инкрементальной компиляции мутантов
-        run: npx tsc -p tsconfig.test.json && node scripts/fix-test-build.mjs
-
-      # Вывод шарда сохраняется артефактом (#472): строки
-      # `FAIL <id>: тест остался зелёным…` — единственное место, где названо,
-      # ЧТО сбежало. Без артефакта отказ безымянный. `PIPESTATUS` — чтобы
-      # `tee` не съел код выхода раннера.
-      - name: Каждый тест ловит свою поломку
-        id: gate
-        run: |
-          mkdir -p artifacts/mutation-shard-${{ matrix.shard }}
-          set -o pipefail
-          node scripts/mutation-gate.mjs --shard=${{ matrix.shard }}/6 2>&1 | tee artifacts/mutation-shard-${{ matrix.shard }}/mutation-shard-${{ matrix.shard }}.log
-      # Исход шага едет в evidence (#604): снятый по timeout-minutes шаг даёт
-      # `cancelled`, и агрегатор отвергает такой шард как неполный — лог без
-      # строк FAIL сам по себе зелёным не считается.
-      - name: Записать identity шарда
-        if: always()
-        run: |
-          node scripts/mutation-gate-report.mjs \
-            --write-evidence=artifacts/mutation-shard-${{ matrix.shard }}/evidence.json \
-            --sha=${{ needs.material.outputs.sha }} \
-            --tree=${{ needs.material.outputs.tree }} \
-            --workflow-sha=${{ job.workflow_sha }} \
-            --run-id=${{ github.run_id }} --run-attempt=${{ github.run_attempt }} \
-            --shard=${{ matrix.shard }} --shards=6 \
-            --outcome=${{ steps.gate.outcome }}
-      - name: Сохранить лог и identity шарда
-        if: always()
-        uses: actions/upload-artifact@043fb46d1a93c77aae656e7c1c64a875d1fc6a0a # v7
-        with:
-          name: mutation-shard-${{ matrix.shard }}-attempt-${{ github.run_attempt }}
-          path: artifacts/mutation-shard-${{ matrix.shard }}
-          if-no-files-found: warn
-          retention-days: 30
-
-  # Результат нельзя приписывать material, пока не доказаны все шесть шардов —
-  # каждый с identity и с дошедшим до конца прогоном (#549, #604).
-  # always() нужен при красном мутанте: лог красного шарда всё равно evidence.
-  evidence:
-    name: "Доказать единый material всех шардов"
-    needs: [material, mutants]
-    if: always() && needs.material.outputs.reuse != 'true'
-    runs-on: ubuntu-24.04
-    timeout-minutes: 10
-    steps:
-      - uses: actions/checkout@3d3c42e5aac5ba805825da76410c181273ba90b1 # v7
-        with:
-          # CLI отчётчика принадлежит зафиксированному material. В main лежит
-          # только workflow и может не быть dev-версии scripts/**.
-          ref: ${{ needs.material.outputs.sha }}
-      - uses: actions/setup-node@820762786026740c76f36085b0efc47a31fe5020 # v7
-        with:
-          node-version: 22
-      - name: Забрать evidence всех попыток
-        uses: actions/download-artifact@37930b1c2abaa49bbe596cd826c3c89aef350131 # v7
-        with:
-          pattern: mutation-shard-*
-          path: artifacts/mutation-logs
-      - name: Проверить полноту и identity
-        run: |
-          node scripts/mutation-gate-report.mjs --verify-only \
-            --logs=artifacts/mutation-logs --shards=6 \
-            --sha=${{ needs.material.outputs.sha }} \
-            --tree=${{ needs.material.outputs.tree }} \
-            --workflow-sha=${{ job.workflow_sha }} \
-            --run-id=${{ github.run_id }} --run-attempt=${{ github.run_attempt }}
-
-  # #620: маркер пишется ТОЛЬКО после зелёного агрегатора — все шесть шардов
-  # доказаны на одном material. Красный или неполный прогон маркера не оставляет,
-  # и следующая ночь гонит реестр заново.
-  green_marker:
-    name: "Записать маркер зелёного прогона"
-    needs: [material, mutants, evidence]
-    if: needs.material.outputs.reuse != 'true' && needs.mutants.result == 'success' && needs.evidence.result == 'success'
-    runs-on: ubuntu-24.04
-    timeout-minutes: 10
-    steps:
-      - uses: actions/checkout@3d3c42e5aac5ba805825da76410c181273ba90b1 # v7
-        with:
-          ref: ${{ needs.material.outputs.sha }}
-      - uses: actions/setup-node@820762786026740c76f36085b0efc47a31fe5020 # v7
-        with:
-          node-version: 22
-      - name: Маркер
-        run: |
-          node scripts/mutation-nightly-reuse.mjs \
-            --write-marker=artifacts/mutation-green/marker.json \
-            --tree=${{ needs.material.outputs.tree }} \
-            --sha=${{ needs.material.outputs.sha }} \
-            --workflow-sha=${{ job.workflow_sha }} \
-            --run-id=${{ github.run_id }} --run-attempt=${{ github.run_attempt }} \
-            --event=${{ github.event_name }}
-      - name: Сохранить маркер
-        uses: actions/cache/save@55cc8345863c7cc4c66a329aec7e433d2d1c52a9 # v6
-        with:
-          path: artifacts/mutation-green
-          key: mutation-green-v1-${{ needs.material.outputs.tree }}-${{ job.workflow_sha }}-${{ github.run_id }}
-
-  # Адресат у отказа (#472). Только по расписанию: ручной dispatch остаётся
-  # для отладки самого гейта, его результат смотрят в прогоне — issue на
-  # каждый такой отказ был бы шумом, который снова перестанут читать.
-  #
-  # Права job-уровня ЗАМЕНЯЮТ права workflow, а не дополняют (прецедент —
-  # validate.yml, job с actions: read): перечислены все три.
-  report:
-    name: "Отказ расписания: issue и Telegram"
-    needs: [material, mutants, evidence]
-    # #620: ночь, принявшая доказательство прошлого зелёного прогона, отказом не
-    # является — её шарды пропущены намеренно. Любой другой пропуск шардов
-    # (упал material) по-прежнему заводит issue.
-    if: always() && github.event_name == 'schedule' && needs.material.outputs.reuse != 'true' && (needs.mutants.result != 'success' || needs.evidence.result != 'success')
-    runs-on: ubuntu-24.04
-    timeout-minutes: 10
-    permissions:
-      contents: read
-      actions: read
-      issues: write
-    steps:
-      - uses: actions/checkout@3d3c42e5aac5ba805825da76410c181273ba90b1 # v7
-        with:
-          # Не перечитываем moving dev: код отчётчика берётся из уже
-          # зафиксированного material. В стабильном main dev-скриптов нет.
-          ref: ${{ needs.material.outputs.sha }}
-      - uses: actions/setup-node@820762786026740c76f36085b0efc47a31fe5020 # v7
-        with:
-          node-version: 22
-      - name: Забрать логи шардов
-        continue-on-error: true
-        uses: actions/download-artifact@37930b1c2abaa49bbe596cd826c3c89aef350131 # v7
-        with:
-          pattern: mutation-shard-*
-          path: artifacts/mutation-logs
-      - name: Собрать отчёт
-        id: report
-        env:
-          RUN_URL: ${{ github.server_url }}/${{ github.repository }}/actions/runs/${{ github.run_id }}
-        run: |
-          mkdir -p artifacts
-          node scripts/mutation-gate-report.mjs \
-            --require-evidence --logs=artifacts/mutation-logs --shards=6 \
-            --sha=${{ needs.material.outputs.sha }} \
-            --tree=${{ needs.material.outputs.tree }} \
-            --workflow-sha=${{ job.workflow_sha }} \
-            --run-id=${{ github.run_id }} --run-attempt=${{ github.run_attempt }} \
-            --run-url="$RUN_URL" --ref=${{ needs.material.outputs.ref }} \
-            --body-out=artifacts/mutation-report.md \
-            --telegram-out=artifacts/mutation-telegram.txt >> "$GITHUB_OUTPUT"
-      # Одно issue, а не одно на неделю: открытое с тем же маркером в заголовке
-      # получает комментарий, новое заводится только если открытого нет.
-      - name: Issue — создать или дописать
-        id: issue
-        env:
-          GH_TOKEN: ${{ github.token }}
-          REPO: ${{ github.repository }}
-          MARKER: ${{ steps.report.outputs.marker }}
-          TITLE: ${{ steps.report.outputs.title }}
-        run: |
-          existing=$(gh issue list --repo "$REPO" --state open --search "\"$MARKER\" in:title" \
-            --json number,title --jq '[.[] | select(.title | startswith(env.MARKER))][0].number // empty')
-          if [ -n "$existing" ]; then
-            gh issue comment "$existing" --repo "$REPO" --body-file artifacts/mutation-report.md
-            url="${{ github.server_url }}/$REPO/issues/$existing"
-          else
-            url=$(gh issue create --repo "$REPO" --title "$TITLE" \
-              --label infra --label process --label tests \
-              --body-file artifacts/mutation-report.md)
-          fi
-          echo "url=$url" >> "$GITHUB_OUTPUT"
-          echo "issue: $url"
-      # Тот же канал, что у релизов (announce.yml). Нет секретов — не отказ:
-      # issue уже заведено, а Telegram — второй адресат, не единственный.
-      - name: Telegram
-        if: always() && steps.issue.outcome == 'success'
-        env:
-          TOKEN: ${{ secrets.TELEGRAM_BOT_TOKEN }}
-          CHAT: ${{ secrets.TELEGRAM_CHAT_ID }}
-          ISSUE_URL: ${{ steps.issue.outputs.url }}
-        run: |
-          if [ -z "$TOKEN" ] || [ -z "$CHAT" ]; then
-            echo "::warning::TELEGRAM_BOT_TOKEN/TELEGRAM_CHAT_ID не заданы — оповещение пропущено, issue заведено"
-            exit 0
-          fi
-          TEXT=$(sed "s|(issue)|$ISSUE_URL|" artifacts/mutation-telegram.txt)
-          curl -sS --fail-with-body -X POST \
-            "https://api.telegram.org/bot$TOKEN/sendMessage" \
-            --data-urlencode "chat_id=$CHAT" \
-            --data-urlencode "text=$TEXT" \
-            -d disable_web_page_preview=true

.github/workflows/_nightly.yml

@@ -1,84 +0,0 @@
-# Ночной полный прогон (#479).
-#
-# Тяжёлые job Validate — смоки, golden, performance_smoke — на обычном пуше не
-# идут: они ни разу не ловили дефект в момент ревью и стоили ~6 минут
-# критического пути на каждую итерацию. Полный набор идёт на кандидате беты
-# (трейлер `Release:`), по кнопке и здесь — каждую ночь на голове `dev`.
-#
-# Почему не `schedule` прямо в validate.yml: расписание исполняется на ветке
-# по умолчанию (`main`), а проверять надо `dev`. Один dispatch с `--ref dev`
-# делает это без переписывания checkout во всех job. Reuse (#208) сохраняется:
-# при неизменённом дереве ночной прогон обойдётся маркерами.
-#
-# Красный ночной прогон — сигнал автору последних коммитов на dev, не гейт:
-# гейт беты по-прежнему требует зелёный Validate на точном SHA кандидата, и
-# там полный набор идёт заново.
-#
-# Сигнал обязан быть настоящим (#492 §7): до этой задачи job завершалась
-# успехом в момент постановки Validate в очередь, и красный полный прогон не
-# делал ночной workflow красным. Теперь job находит запущенный прогон и ждёт
-# его: успешный dispatch — не успешная проверка.
-name: "Ночной полный прогон dev · тело (#623)"
-
-on:
-  # #623: тело вызывается тонким файлом `nightly.yml` из ветки по умолчанию
-  # по ссылке `@dev`; триггеры, run-name и concurrency живут там.
-  workflow_call:
-
-permissions:
-  actions: write
-  contents: read
-
-jobs:
-  dispatch:
-    name: "Запустить Validate на dev с полным набором и дождаться результата"
-    runs-on: ubuntu-24.04
-    timeout-minutes: 90
-    steps:
-      # #658: при плане 02:30 UTC ночь фактически стартовала в 07:42–08:05 и
-      # кончалась в рабочее время владельца. Сдвиг старта больше часа — видимое
-      # предупреждение, а не молча съеденная ночь. `github.event.schedule` —
-      # строка cron вызывающего `nightly.yml`; NOW_EPOCH подставляет только тест.
-      - name: "Сдвиг старта ночи против расписания"
-        if: github.event_name == 'schedule'
-        env:
-          SCHEDULE: ${{ github.event.schedule }}
-        run: |
-          set -euo pipefail
-          read -r minute hour _ <<< "$SCHEDULE"
-          now=${NOW_EPOCH:-$(date -u +%s)}
-          planned=$(date -u -d "@$now" +%F)
-          planned=$(date -u -d "$planned $hour:$minute" +%s)
-          [ "$planned" -le "$now" ] || planned=$((planned - 86400))
-          lag=$(( (now - planned) / 60 ))
-          echo "- Старт по расписанию \`$SCHEDULE\` (UTC): сдвиг $lag мин" >> "$GITHUB_STEP_SUMMARY"
-          if [ "$lag" -gt 60 ]; then
-            echo "::warning::ночной прогон стартовал на $lag мин позже расписания ($SCHEDULE UTC) — очередь расписаний GitHub (#658)"
-          fi
-      - env:
-          GH_TOKEN: ${{ github.token }}
-          REPO: ${{ github.repository }}
-        run: |
-          set -euo pipefail
-          since=$(date -u +%FT%TZ)
-          gh workflow run validate.yml --repo "$REPO" --ref dev -f full=true
-          echo "Validate(dev, full=true) поставлен в очередь: $since"
-          # Найти именно этот прогон: workflow_dispatch на dev, созданный не
-          # раньше момента запуска. До трёх минут на появление в списке.
-          run_id=""
-          for _ in $(seq 1 18); do
-            sleep 10
-            run_id=$(gh run list --repo "$REPO" --workflow validate.yml --branch dev \
-              --event workflow_dispatch --json databaseId,createdAt --limit 5 \
-              --jq "[.[] | select(.createdAt >= \"$since\")] | sort_by(.createdAt) | last | .databaseId // empty")
-            [ -n "$run_id" ] && break
-          done
-          if [ -z "$run_id" ]; then
-            echo "::error::прогон Validate не появился за 3 минуты — dispatch не равен проверке"
-            exit 1
-          fi
-          url="${{ github.server_url }}/$REPO/actions/runs/$run_id"
-          echo "дочерний прогон: $url"
-          echo "- Validate(dev, full=true): $url" >> "$GITHUB_STEP_SUMMARY"
-          # Ждём завершения; красный дочерний прогон — красный ночной.
-          gh run watch "$run_id" --repo "$REPO" --exit-status --interval 30

.github/workflows/_process-metrics.yml

@@ -1,59 +0,0 @@
-name: "Метрики процесса · тело (#623)"
-
-# #637: еженедельный замер вместо ощущений — lead time S→S7→S8, раунды ревью,
-# прогоны Validate по исходам, минуты конвейера в S4/S7. Только чтение: отчёт
-# идёт в step summary и артефакт; в issue и репозиторий ничего не пишется.
-# Цифры аудита 22.09 (1,57 раунда код-ревью, S7 ≈ 36 мин/раунд, 226 Validate
-# за неделю) были собраны руками за час — теперь они стоят один запуск.
-
-on:
-  # #623: тело вызывается тонким файлом `process-metrics.yml` из ветки по умолчанию
-  # по ссылке `@dev`; триггеры, run-name и concurrency живут там.
-  workflow_call:
-    inputs:
-      days:
-        description: "Окно в днях"
-        required: false
-        type: string
-        default: "7"
-
-permissions:
-  contents: read
-  actions: read
-  issues: read
-
-jobs:
-  metrics:
-    name: "Снимок недели: issue, раунды, прогоны"
-    runs-on: ubuntu-24.04
-    timeout-minutes: 15
-    steps:
-      # Код — из dev, как у reconcile: расписание читается из main, а исполняется
-      # версия, которую проверил CI.
-      - uses: actions/checkout@3d3c42e5aac5ba805825da76410c181273ba90b1 # v7
-        with:
-          ref: dev
-          fetch-depth: 1
-          persist-credentials: false
-      - uses: actions/setup-node@820762786026740c76f36085b0efc47a31fe5020 # v7
-        with:
-          node-version: 22
-      - name: Собрать отчёт
-        env:
-          GH_TOKEN: ${{ secrets.HP_PROCESS_TOKEN }}
-          REPO: ${{ github.repository }}
-          DAYS: ${{ inputs.days || '7' }}
-        run: |
-          mkdir -p artifacts/process-metrics
-          node scripts/process-metrics.mjs --repo="$REPO" --days="$DAYS" \
-            --output=artifacts/process-metrics/report.md \
-            --json=artifacts/process-metrics/report.json > /dev/null
-          cat artifacts/process-metrics/report.md >> "$GITHUB_STEP_SUMMARY"
-      - name: Сохранить отчёт
-        if: always()
-        uses: actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02 # v4
-        with:
-          name: process-metrics-${{ github.run_id }}
-          path: artifacts/process-metrics
-          if-no-files-found: error
-          retention-days: 90

.github/workflows/_process-reconcile.yml

@@ -1,57 +0,0 @@
-name: "Сверка очереди ревью · тело (#623)"
-
-on:
-  # #623: тело вызывается тонким файлом `process-reconcile.yml` из ветки по умолчанию
-  # по ссылке `@dev`; триггеры, run-name и concurrency живут там.
-  workflow_call:
-    inputs:
-      apply:
-        description: "Повторно будить потерянные запросы и публиковать диагностику"
-        required: false
-        type: boolean
-        default: true
-
-permissions:
-  actions: read
-  contents: read
-  issues: read
-
-jobs:
-  reconcile:
-    name: "Один снимок S4/S7 без polling модели"
-    runs-on: ubuntu-24.04
-    timeout-minutes: 10
-    concurrency:
-      group: process-reconcile
-      cancel-in-progress: false
-    steps:
-      # Расписание читается из main, а исполняемый reconciler — из dev: так
-      # после штатного merge действует та же версия кода, которую проверил CI.
-      - uses: actions/checkout@3d3c42e5aac5ba805825da76410c181273ba90b1 # v7
-        with:
-          ref: dev
-          fetch-depth: 1
-          persist-credentials: false
-      - uses: actions/setup-node@820762786026740c76f36085b0efc47a31fe5020 # v7
-        with:
-          node-version: 22
-      - name: Сопоставить labels, requests, runs и sealed evidence
-        env:
-          GH_TOKEN: ${{ secrets.HP_PROCESS_TOKEN }}
-          REPO: ${{ github.repository }}
-          APPLY: ${{ github.event_name == 'schedule' || inputs.apply == true }}
-        run: |
-          mkdir -p artifacts/process-reconcile
-          node scripts/process-reconcile.mjs \
-            --repo "$REPO" \
-            --apply="$APPLY" \
-            --max-actions=5 \
-            --output=artifacts/process-reconcile/summary.json
-      - name: Опубликовать компактный machine-readable итог
-        if: always()
-        uses: actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02 # v4
-        with:
-          name: process-reconcile-${{ github.run_id }}-${{ github.run_attempt }}
-          path: artifacts/process-reconcile/summary.json
-          if-no-files-found: error
-          retention-days: 14

.github/workflows/_process-resume.yml

@@ -1,60 +0,0 @@
-name: "Продолжение ревью после Validate · тело (#623)"
-
-# #636. Стадия `prepare` конвейера (process.yml) больше не ждёт Validate с
-# мутантами на материале внутри job — раннер спал ≈ 28 минут на раунд при
-# 10–12 минутах работы модели. Она диспатчит прогон, кладёт запечатанный
-# маркер `review-pending-…` и выходит. Этот workflow просыпается на завершение
-# любого Validate и, если раунд ждал именно этот прогон (маркер на материале,
-# метка S7 стоит, активного прогона конвейера нет), переставляет метку S7 —
-# новый прогон `prepare` находит завершённый dispatch и продолжает раунд.
-# Ничего не оценивает: зелёный/красный разбирает сам конвейер. Страховка на
-# потерянное событие — process-reconcile.yml с тем же маркером.
-#
-# Для события `workflow_run` GitHub берёт workflow только из ветки по
-# умолчанию (main). Там лежит тонкий `process-resume.yml`, который вызывает
-# этот файл по ссылке `@dev` (#623); сверка тонких копий — в preflight
-# validate.yml.
-
-on:
-  # #623: тело вызывается тонким файлом `process-resume.yml` из ветки по умолчанию
-  # по ссылке `@dev`; триггеры, run-name и concurrency живут там.
-  workflow_call:
-
-permissions:
-  contents: read
-  actions: read
-
-jobs:
-  resume:
-    name: "Разбудить раунд, ждавший этот Validate"
-    if: github.event.workflow_run.event == 'workflow_dispatch' && startsWith(github.event.workflow_run.head_branch, 'issue/')
-    runs-on: ubuntu-24.04
-    timeout-minutes: 10
-    concurrency:
-      group: process-resume-${{ github.event.workflow_run.head_branch }}
-      cancel-in-progress: false
-    steps:
-      # Код берётся из dev, как у reconcile: после штатного слияния действует
-      # версия, которую проверил CI, а не копия из main.
-      - uses: actions/checkout@3d3c42e5aac5ba805825da76410c181273ba90b1 # v7
-        with:
-          ref: dev
-          fetch-depth: 1
-          persist-credentials: false
-      - uses: actions/setup-node@820762786026740c76f36085b0efc47a31fe5020 # v7
-        with:
-          node-version: 22
-      # Метка переставляется HP_PROCESS_TOKEN: событие от GITHUB_TOKEN не
-      # запустило бы process.yml (см. шапку process.yml, п. 1).
-      - name: Решить по маркеру ожидания и переставить S7
-        env:
-          GH_TOKEN: ${{ secrets.HP_PROCESS_TOKEN }}
-          REPO: ${{ github.repository }}
-          BRANCH: ${{ github.event.workflow_run.head_branch }}
-          SHA: ${{ github.event.workflow_run.head_sha }}
-          EVENT: ${{ github.event.workflow_run.event }}
-          STATUS: ${{ github.event.workflow_run.status }}
-        run: |
-          node scripts/process-resume.mjs \
-            --repo="$REPO" --branch="$BRANCH" --sha="$SHA" \
-            --event="$EVENT" --status="$STATUS" --apply=true | tee -a "$GITHUB_STEP_SUMMARY"

.github/workflows/announce.yml

@@ -1,16 +1,11 @@
-name: Анонс релиза
+name: Announce release
 # Telegram notifications for t.me/ha_houseplan (owner request, 2026-08-07).
 # Stable releases are announced; prereleases are deliberately silent.
 # workflow_dispatch exists purely as a connectivity test button and therefore
 # remains allowed to send a test message.
-# #538: НЕТ триггера `release: published`. Три воркфлоу висели на одном событии
-# и бежали параллельно, а анонсу нечего было проверять — он выигрывал гонку
-# всегда. 12.09 v1.75.0 объявили в канале в ту же минуту, когда гейт ассетов
-# отказал: релиз остался без `houseplan-card.js`, E2E не выполнялся вовсе, а
-# подписчики получили сообщение. Анонс вызывается только после того, как работа
-# сделана: `release.yml` зовёт его после выкладки ассетов,
-# `publish-prerelease.yml` — после публикации беты.
 on:
+  release:
+    types: [published]
   workflow_dispatch: {}
   workflow_call:
     inputs:
@@ -41,14 +36,12 @@ permissions:
   contents: read
 jobs:
   telegram:
-    name: Оповещение в Telegram (только стабильные)
-    if: ${{ github.event_name == 'workflow_dispatch' || (github.event_name == 'workflow_call' && inputs.prerelease == false) }}
-    runs-on: ubuntu-24.04
-    timeout-minutes: 10
+    if: ${{ github.event_name == 'workflow_dispatch' || (github.event_name == 'release' && github.event.release.prerelease == false) || (github.event_name == 'workflow_call' && inputs.prerelease == false) }}
+    runs-on: ubuntu-latest
     steps:
       - name: Check out release notes for a reusable call
         if: ${{ inputs.reusable == true }}
-        uses: actions/checkout@3d3c42e5aac5ba805825da76410c181273ba90b1 # v7
+        uses: actions/checkout@v7
         with:
           ref: ${{ inputs.ref }}
       - name: Send to Telegram
@@ -60,20 +53,32 @@ jobs:
           INPUT_NAME: ${{ inputs.release_name }}
           INPUT_URL: ${{ inputs.url }}
           INPUT_PRE: ${{ inputs.prerelease }}
+          RELEASE_TAG: ${{ github.event.release.tag_name }}
+          RELEASE_NAME: ${{ github.event.release.name }}
+          RELEASE_URL: ${{ github.event.release.html_url }}
+          RELEASE_PRE: ${{ github.event.release.prerelease }}
+          # The body goes through env, never through shell interpolation —
+          # release notes are arbitrary text.
+          RELEASE_BODY: ${{ github.event.release.body }}
           EVENT: ${{ github.event_name }}
         run: |
           set -euo pipefail
           if [ "$EVENT" = "workflow_dispatch" ] && [ "$CALLED" != "true" ]; then
             TEXT="✅ Тест: оповещения о релизах houseplan-card подключены."
           else
-            # Единственный путь к сообщению о релизе — вызов из воркфлоу, который
-            # уже закончил работу (#538). Тело берётся из файла заметок ветки
-            # тега, а не из события: события здесь больше нет.
-            TAG=$INPUT_TAG
-            NAME=$INPUT_NAME
-            URL=$INPUT_URL
-            PRE=$INPUT_PRE
-            BODY=$(cat docs/RELEASE-NOTES.md)
+            if [ "$CALLED" = "true" ]; then
+              TAG=$INPUT_TAG
+              NAME=$INPUT_NAME
+              URL=$INPUT_URL
+              PRE=$INPUT_PRE
+              BODY=$(cat docs/RELEASE-NOTES.md)
+            else
+              TAG=$RELEASE_TAG
+              NAME=$RELEASE_NAME
+              URL=$RELEASE_URL
+              PRE=$RELEASE_PRE
+              BODY=$RELEASE_BODY
+            fi
             if [ "$PRE" = "true" ]; then
               echo "Prerelease Telegram announcement is disabled"
               exit 0

.github/workflows/docs-screenshots.yml

@@ -1,155 +0,0 @@
-# Скриншоты документации снимаются здесь и только здесь (#246).
-#
-# Съёмка на машине исполнителя даёт байтово разный PNG при одинаковом кадре:
-# сглаживание и хинтинг зависят от окружения. Измерено на истории — пересъёмка
-# в #231 изменила два файла из девяти на 7–8 байт, набор с беты все девять
-# целиком. Одно окружение убирает этот шум насовсем.
-#
-# Джоба ничего не коммитит: она публикует артефакт, который человек принимает
-# локально через `npm run docs:accept -- --reviewed --from=<распакованный>`.
-# Та же конструкция, что у golden-эталонов, и по той же причине: картинки
-# попадают в репозиторий через явное решение, а не через бота.
-#
-# Снимать здесь больше не обязанность, а удобство (#401). Приёмка проверяет не
-# место съёмки, а её воспроизводимость: каждый кадр, не объявленный изменённым,
-# должен совпасть с закоммиченным байт-в-байт. Эта джоба потому и удобна, что
-# среда у неё та же, в которой снят закоммиченный набор, — но принять получится
-# из любой, где кадры воспроизводятся, и не получится ни из одной, где нет.
-name: Скриншоты документации
-
-on:
-  workflow_dispatch:
-    inputs:
-      ref:
-        description: Ветка или SHA, с которого снимать
-        required: false
-        default: dev
-
-permissions:
-  contents: read
-
-jobs:
-  capture:
-    name: Съёмка и сверка скриншот-индекса
-    runs-on: ubuntu-24.04
-    timeout-minutes: 20
-    steps:
-      - uses: actions/checkout@3d3c42e5aac5ba805825da76410c181273ba90b1 # v7
-        with:
-          ref: ${{ inputs.ref }}
-      - uses: actions/setup-node@820762786026740c76f36085b0efc47a31fe5020 # v7
-        with:
-          node-version: 22
-          cache: npm
-      - run: npm ci
-      # Тот же кэш и тот же отказ от --with-deps, что в smoke/golden (#175, #206):
-      # системные библиотеки Chromium уже в образе раннера.
-      - name: Кэш браузеров Playwright
-        id: pw
-        uses: actions/cache@55cc8345863c7cc4c66a329aec7e433d2d1c52a9 # v6
-        with:
-          path: ~/.cache/ms-playwright
-          key: playwright-${{ runner.os }}-${{ hashFiles('package-lock.json') }}
-      - name: Install pinned Chromium
-        if: steps.pw.outputs.cache-hit != 'true'
-        run: npx playwright install chromium
-      - name: Build the bundle the screenshots must come from
-        run: npm run build
-      # oxipng без потерь снимает с набора ~19% (замер в #345 на pyoxipng 9.1.1;
-      # у 10.2.0 пресеты уровней перебалансированы, точная доля может отличаться,
-      # но кадры остаются пиксельно идентичными в любой версии — это перепаковка).
-      #
-      # Пин версии и контрольной суммы намеренно, а не `apt-get install oxipng`:
-      # пакет из образа раннера может пропасть или переехать, а падение шага
-      # съёмки стоит целого цикла приёмки. Тот же урок, что с azure-зеркалом
-      # Playwright (#175, #206).
-      - name: Установить oxipng
-        env:
-          OXIPNG_VERSION: 10.2.0
-          OXIPNG_SHA256: b33f84c73d42cb592bea5d84c431030b1e97784817693380dfcec7d9575f871e
-        run: |
-          set -euo pipefail
-          asset="oxipng-${OXIPNG_VERSION}-x86_64-unknown-linux-gnu.tar.gz"
-          curl -fsSL -o "$asset" \
-            "https://github.com/oxipng/oxipng/releases/download/v${OXIPNG_VERSION}/${asset}"
-          echo "${OXIPNG_SHA256}  ${asset}" | sha256sum -c -
-          mkdir -p "$HOME/.local/bin"
-          tar -xzf "$asset" --strip-components=1 -C "$HOME/.local/bin" \
-            "oxipng-${OXIPNG_VERSION}-x86_64-unknown-linux-gnu/oxipng"
-          echo "$HOME/.local/bin" >> "$GITHUB_PATH"
-          "$HOME/.local/bin/oxipng" --version
-      # Съёмка идёт дважды и сравнивается по хешам (#422). Прежний замер
-      # (`--stability`) отвечает на вопрос «плавает ли кадр от времени внутри
-      # страницы» и остаётся ниже; дефект #410 был по другой оси — обрезка
-      # плавала МЕЖДУ прогонами, и три снимка внутри одного процесса совпали бы
-      # всегда. Проверка, объявленная гарантией воспроизводимости, на
-      # собственном инциденте промолчала бы.
-      #
-      # Второй прогон заодно оставляет в `docs/images` кадры, которые и уедут в
-      # артефакт: сравнивать хеши и публиковать разные файлы было бы странно.
-      - name: "Съёмка воспроизводима между прогонами (#410, #422)"
-        run: node scripts/capture-determinism.mjs
-      # Вердикт до всякой приёмки. Само число изменившихся файлов ничего не
-      # говорит: набор, снятый другим браузером, меняет их все, и это нормально
-      # ровно один раз — при переходе на канонический прогон. Сравнивать надо
-      # браузер: тот же Chromium и десять изменившихся картинок означают, что
-      # изменился продукт (или что-то не так), другой Chromium — ожидаемую
-      # разницу рендеринга.
-      # Хеши печатаются в лог, а не только уезжают в артефакт (#410): чтобы
-      # сравнить два прогона одного и того же SHA, нужен текст, который видно с
-      # экрана. Именно так измеряется недетерминированность съёмки — и её
-      # отсутствие после починки.
-      # Съёмка обязана быть воспроизводимой, и это проверяется, а не
-      # предполагается (#410): три снимка на сценарий в одном процессе, без
-      # правки состояния между ними, обязаны совпасть побайтово. Шаг падает,
-      # если кадр снова начнёт зависеть от времени.
-      #
-      # Шаг стоит ПОСЛЕ съёмки и до вердикта: публикацию артефакта он всё равно
-      # блокирует падением job'а, а снимать набор третий раз ради порядка строк
-      # в логе незачем.
-      - name: "Кадр не плавает внутри одного состояния (#410)"
-        run: node demo/docs/capture.mjs --stability=3
-      - name: Хеши кадров
-        run: |
-          for f in docs/images/*.png; do sha256sum "$f"; done
-      - name: Вердикт
-        run: |
-          # Поле манифеста «до» — из закоммиченного состояния, «после» — из
-          # свежего. Читается одинаково для браузера и для упаковщика: оба
-          # переписывают все кадры сразу, и различить их причины обязан вердикт,
-          # а не человек по памяти (#345).
-          field() {
-            node -e "let s='';process.stdin.on('data',d=>s+=d).on('end',()=>{try{console.log(JSON.parse(s).$1||'')}catch{console.log('')}})"
-          }
-          git status --porcelain docs/images
-          changed=$(git diff --name-only docs/images | grep -c png || true)
-          before=$(git show HEAD:docs/images/screenshots.json | field chromium)
-          after=$(node -e "console.log(require('./docs/images/screenshots.json').chromium)")
-          packer_before=$(git show HEAD:docs/images/screenshots.json | field oxipng)
-          packer_after=$(node -e "console.log(require('./docs/images/screenshots.json').oxipng || '')")
-          echo "--- изменившихся PNG: $changed"
-          echo "--- Chromium: было «${before:-не записан}», стало «$after»"
-          echo "--- oxipng: было «${packer_before:-не записан}», стало «${packer_after:-нет}»"
-          if [ "$packer_before" != "$packer_after" ] && [ "$changed" -gt 0 ]; then
-            echo "ВЕРДИКТ: изменился упаковщик, поэтому переписаны все кадры сразу."
-            echo "Это перепаковка без потерь: пиксели те же, размер меньше на ~19%."
-            echo "Ожидаемо один раз — при включении oxipng либо при смене его версии."
-            echo "Проверить можно сравнением декодированных кадров, а не байтов."
-          elif [ "$before" = "$after" ] && [ "$changed" -gt 0 ]; then
-            echo "ВЕРДИКТ: тот же браузер и тот же упаковщик, а картинки изменились —"
-            echo "изменился продукт. Смотрите на кадры: если изменение ожидаемое, принимайте."
-          elif [ "$before" != "$after" ]; then
-            echo "ВЕРДИКТ: браузер другой, поэтому переписаны все кадры сразу."
-            echo "Это ожидаемо один раз — при переходе на канонический прогон."
-            echo "Если Chromium сменился неожиданно, сверьте закреплённую версию в package-lock."
-          else
-            echo "ВЕРДИКТ: ничего не изменилось, принимать нечего."
-          fi
-      - name: Upload candidate
-        uses: actions/upload-artifact@043fb46d1a93c77aae656e7c1c64a875d1fc6a0a # v7
-        with:
-          name: docs-screenshots
-          path: |
-            docs/images/*.png
-            docs/images/screenshots.json
-          if-no-files-found: error

.github/workflows/mutation-gate.yml

@@ -1,12 +1,15 @@
-name: Мутационный гейт
+name: Mutation gate
 
-# Тонкий вызывающий файл (#623). Для этого события GitHub берёт workflow из
-# ветки по умолчанию (`main`), поэтому здесь только то, что обязано жить там:
-# триггеры, run-name, права и concurrency. Тело — `_mutation-gate.yml` по ссылке
-# `@dev`: правка конвейера — один коммит в `dev`, зеркало в `main` не нужно.
-# Этот файл меняется, только когда меняются сами триггеры или потолок прав;
-# тогда он зеркалится в `main`, и preflight `workflow_sync` (validate.yml)
-# держит копии равными.
+# Реестр известных поломок (issue #85): каждый мутант ломает продуктовый код
+# известным способом, и объявленный тест ОБЯЗАН на этом покраснеть. Тест,
+# оставшийся зелёным на сломанном коде, ничего не защищает — он лишь выглядит
+# защитой, и это хуже его отсутствия.
+#
+# Прогон дорогой: пересборка бандла на каждого мутанта. Поэтому он не входит в
+# Validate и не идёт на каждый push. Его место — перед стабильным релизом
+# (PROCESS.md §8) и раз в неделю по расписанию, чтобы дрейф тестов не копился
+# до релиза. Дешёвая половина — «якоря патчей живы, guard-файлы существуют» —
+# идёт с обычными юнитами: test/mutation-gate.test.mjs.
 
 on:
   workflow_dispatch:
@@ -16,33 +19,55 @@ on:
         required: false
         default: dev
   schedule:
-    # Каждую ночь, 00:43 UTC (03:43 MSK) — после суток правок и до ночного
-    # полного Validate (nightly.yml, 02:17 UTC), чтобы не делить раннеры (#513).
-    # Минута не круглая: такие старты GitHub сдвигает меньше (#658).
-    - cron: '43 0 * * *'
+    # Понедельник, 05:20 UTC — до начала рабочего дня владельца.
+    - cron: '20 5 * * 1'
 
 permissions:
   contents: read
 
-# Группа зависит от события (#472). Прежде она была одна на всё, и ручной
-# запуск (отладка гейта) отменял идущий по расписанию — так 24.08 погиб
-# еженедельный прогон, а отменённый в списке выглядит «не красным». Поймать
-# отмену изнутри нельзя: вместе с прогоном отменяются и не начавшиеся job,
-# включая любой репортёр. Значит отмену надо не ловить, а не допускать.
 concurrency:
-  group: mutation-gate-${{ github.event_name }}
+  group: mutation-gate
   cancel-in-progress: true
 
 jobs:
-  # Потолок прав тела: объединение job-level прав `_mutation-gate.yml`. Вызываемый
-  # workflow может права только сузить, поэтому каждая его job по-прежнему
-  # получает свой прежний минимум (#556), а шире этого набора не получит никто.
-  dev:
-    permissions:
-      contents: read
-      actions: read
-      issues: write
-    uses: Matysh/houseplan-card/.github/workflows/_mutation-gate.yml@dev # #623: тело конвейера из dev
-    with:
-      ref: ${{ inputs.ref }}
-    secrets: inherit
+  mutants:
+    runs-on: ubuntu-latest
+    # Все мутанты × (сборка + свой guard) — это десятки минут, и это нормально:
+    # гейт предрелизный. Час — потолок против зависшего Chromium.
+    timeout-minutes: 60
+    steps:
+      - uses: actions/checkout@v7
+        with:
+          ref: ${{ github.event_name == 'workflow_dispatch' && inputs.ref || 'dev' }}
+          fetch-depth: 0
+
+      - uses: actions/setup-node@v7
+        with:
+          node-version: 22
+          cache: npm
+
+      - run: npm ci
+
+      - uses: actions/setup-python@v7
+        with:
+          python-version: '3.13'
+
+      - name: Установить backend test dependencies
+        run: pip install pytest voluptuous pytest-homeassistant-custom-component home-assistant-frontend
+
+      - name: Кэш браузеров Playwright
+        id: pw
+        uses: actions/cache@v6
+        with:
+          path: ~/.cache/ms-playwright
+          key: playwright-${{ runner.os }}-${{ hashFiles('package-lock.json') }}
+
+      - name: Установить Chromium
+        if: steps.pw.outputs.cache-hit != 'true'
+        run: npx playwright install --with-deps chromium
+
+      - name: Реестр применим к текущему коду
+        run: node scripts/mutation-gate.mjs --check
+
+      - name: Каждый тест ловит свою поломку
+        run: node scripts/mutation-gate.mjs

.github/workflows/nightly.yml

@@ -1,31 +0,0 @@
-name: Ночной полный прогон dev
-
-# Тонкий вызывающий файл (#623). Для этого события GitHub берёт workflow из
-# ветки по умолчанию (`main`), поэтому здесь только то, что обязано жить там:
-# триггеры, run-name, права и concurrency. Тело — `_nightly.yml` по ссылке
-# `@dev`: правка конвейера — один коммит в `dev`, зеркало в `main` не нужно.
-# Этот файл меняется, только когда меняются сами триггеры или потолок прав;
-# тогда он зеркалится в `main`, и preflight `workflow_sync` (validate.yml)
-# держит копии равными.
-
-on:
-  # 02:17 UTC, не на круглой минуте: старты «ровно в час/полчаса» GitHub
-  # откладывает на часы (факт — 07:42–08:05 при плане 02:30, #658).
-  schedule:
-    - cron: '17 2 * * *'
-  workflow_dispatch: {}
-
-permissions:
-  actions: write
-  contents: read
-
-jobs:
-  # Потолок прав тела: объединение job-level прав `_nightly.yml`. Вызываемый
-  # workflow может права только сузить, поэтому каждая его job по-прежнему
-  # получает свой прежний минимум (#556), а шире этого набора не получит никто.
-  dev:
-    permissions:
-      actions: write
-      contents: read
-    uses: Matysh/houseplan-card/.github/workflows/_nightly.yml@dev # #623: тело конвейера из dev
-    secrets: inherit

.github/workflows/performance.yml

@@ -1,4 +1,4 @@
-name: Полные бенчмарки производительности
+name: Full Performance
 
 on:
   # Every main promotion is a stable-release candidate and must have an
@@ -6,12 +6,8 @@ on:
   push:
     branches:
       - main
-    paths-ignore:
-      - ".github/workflows/**"
-      - "docs/**"
   schedule:
-    # Минута не круглая (#658): доходит до main вместе со стабильным релизом.
-    - cron: "11 4 * * 1"
+    - cron: "0 4 * * 1"
   workflow_dispatch:
     inputs:
       comparison_ref:
@@ -28,28 +24,13 @@ concurrency:
 
 jobs:
   performance:
-    name: Бенчмарки рендера и геометрии
-    # Every profile keeps base and candidate sequential on one hosted runner.
-    # Independent profile pairs run in parallel: cross-profile timing is never
-    # compared, while serialising all profile pairs cannot fit the job timeout.
-    runs-on: ubuntu-24.04
+    # Base and candidate stay sequential on one hosted runner. Splitting them
+    # across runners would turn machine variance into a false regression.
+    runs-on: ubuntu-latest
     timeout-minutes: 60
-    strategy:
-      fail-fast: false
-      matrix:
-        profile:
-          - large-house
-          - isometric
-          - isometric-stage3
-          - plan-snap
-          - interaction
-          - blend
-          - overlay
-          - space-default
-          - space-glow
     steps:
       - name: Check out candidate
-        uses: actions/checkout@3d3c42e5aac5ba805825da76410c181273ba90b1 # v7
+        uses: actions/checkout@v7
         with:
           path: candidate
           fetch-depth: 2
@@ -61,10 +42,6 @@ jobs:
           EVENT_NAME: ${{ github.event_name }}
           PUSH_BEFORE_SHA: ${{ github.event.before }}
           MANUAL_BASE: ${{ inputs.comparison_ref }}
-          # #587: кандидат стабильного релиза судится о предыдущий стабильный
-          # тег, а не о прошлую вершину main. Признак кандидата — трейлер
-          # `Release:` в сообщении head-коммита, поэтому оно едет в скрипт.
-          HEAD_MESSAGE: ${{ github.event.head_commit.message }}
         run: |
           set -euo pipefail
           if [ "$(git rev-parse --is-shallow-repository)" = "true" ]; then
@@ -72,17 +49,79 @@ jobs:
           else
             git fetch --force --tags --prune origin
           fi
-          # Решение целиком в скрипте: его отрицательные случаи проверяются
-          # фикстурами, а shell-развилку прогнать тестом нельзя (#556, #587).
-          node scripts/performance-baseline.mjs
+
+          if [ "$EVENT_NAME" = "workflow_dispatch" ] && [ -n "$MANUAL_BASE" ]; then
+            sha="$(git rev-parse "${MANUAL_BASE}^{commit}" 2>/dev/null || true)"
+            source="manual comparison ref $MANUAL_BASE"
+          elif [ "$EVENT_NAME" = "push" ] && [ -n "$PUSH_BEFORE_SHA" ] && ! printf '%s' "$PUSH_BEFORE_SHA" | grep -Eq '^0+$'; then
+            sha="$PUSH_BEFORE_SHA"
+            source="push before"
+          else
+            sha="$(git rev-parse HEAD^ 2>/dev/null || true)"
+            source="candidate parent"
+          fi
+          requested_sha="$sha"
+
+          usable=true
+          reason=""
+          if [ -z "$sha" ] || ! git cat-file -e "${sha}^{commit}" 2>/dev/null; then
+            usable=false
+            reason="commit is not present after fetching all remote refs"
+          elif [ "$source" = "push before" ] && ! git merge-base --is-ancestor "$sha" HEAD; then
+            usable=false
+            reason="commit is no longer an ancestor of the pushed revision"
+          fi
+
+          if [ "$usable" != true ]; then
+            parent_sha="$(git rev-parse HEAD^ 2>/dev/null || true)"
+            if [ -n "$parent_sha" ] && [ "$parent_sha" != "$(git rev-parse HEAD)" ]; then
+              sha="$parent_sha"
+              source="candidate parent (unusable requested-base fallback)"
+              echo "::warning::Comparison SHA ${requested_sha:-none} is unusable ($reason); using candidate parent $sha."
+              usable=true
+            fi
+          fi
+
+          if [ "$usable" != true ]; then
+            fallback_tag=""
+            fallback_sha=""
+            head_sha="$(git rev-parse HEAD)"
+            while IFS= read -r tag; do
+              case "$tag" in
+                v[0-9]*.[0-9]*.[0-9]*) ;;
+                *) continue ;;
+              esac
+              tag_sha="$(git rev-list -n 1 "$tag")"
+              if [ "$tag_sha" != "$head_sha" ]; then
+                fallback_tag="$tag"
+                fallback_sha="$tag_sha"
+                break
+              fi
+            done < <(git tag --merged HEAD --sort=-version:refname)
+            if [ -z "$fallback_sha" ]; then
+              echo "::error::No usable comparison commit or previous release tag is reachable from HEAD."
+              exit 1
+            fi
+            sha="$fallback_sha"
+            source="release tag $fallback_tag"
+            echo "::warning::Using $fallback_tag ($sha) as the comparison base."
+          fi
+
+          if ! git cat-file -e "${sha}:demo/bundle-freshness.mjs" 2>/dev/null; then
+            echo "::warning::Comparison $sha predates HP-PERF-01; using candidate parent HEAD^."
+            sha="$(git rev-parse HEAD^)"
+            source="candidate parent (HP-PERF-01 compatibility)"
+          fi
+          echo "sha=$sha" >> "$GITHUB_OUTPUT"
+          echo "Comparison base: $sha ($source)" >> "$GITHUB_STEP_SUMMARY"
 
       - name: Check out base SHA
-        uses: actions/checkout@3d3c42e5aac5ba805825da76410c181273ba90b1 # v7
+        uses: actions/checkout@v7
         with:
           ref: ${{ steps.base.outputs.sha }}
           path: baseline
 
-      - uses: actions/setup-node@820762786026740c76f36085b0efc47a31fe5020 # v7
+      - uses: actions/setup-node@v7
         with:
           node-version: 22
           cache: npm
@@ -96,7 +135,7 @@ jobs:
       # То же, что в validate.yml: кэш браузеров, apt не трогаем (#206).
       - name: Кэш браузеров Playwright
         id: pw
-        uses: actions/cache@55cc8345863c7cc4c66a329aec7e433d2d1c52a9 # v6
+        uses: actions/cache@v6
         with:
           path: ~/.cache/ms-playwright
           key: playwright-${{ runner.os }}-${{ hashFiles('candidate/package-lock.json') }}
@@ -108,112 +147,40 @@ jobs:
       - name: Build both exact source trees
         run: |
           npm --prefix candidate run build
-          (cd candidate && node scripts/bundle-sync.mjs)
+          cp candidate/dist/houseplan-card.js candidate/demo/srv/assets/houseplan-card.js
           npm --prefix baseline run build
-          if [ -f baseline/scripts/bundle-sync.mjs ]; then
-            (cd baseline && node scripts/bundle-sync.mjs)
-          else
-            echo "::notice::The comparison base predates bundle-sync.mjs; materializing its freshly built bundle with the legacy copy path."
-            mkdir -p baseline/custom_components/houseplan/frontend baseline/demo/srv/assets
-            cp baseline/dist/houseplan-card.js baseline/custom_components/houseplan/frontend/houseplan-card.js
-            cp baseline/dist/houseplan-card.js baseline/demo/srv/assets/houseplan-card.js
+          cp baseline/dist/houseplan-card.js baseline/demo/srv/assets/houseplan-card.js
+
+      - name: Capture base and candidate profiles
+        working-directory: candidate
+        run: |
+          npm run benchmark:large-house -- --target-root=../baseline --samples=7 --warmups=1 --output=../artifacts/performance/baseline.json
+          npm run benchmark:large-house -- --target-root=. --samples=7 --warmups=1 --output=../artifacts/performance/candidate.json
+          npm run benchmark:large-house-isometric -- --target-root=../baseline --samples=7 --warmups=1 --output=../artifacts/performance/isometric-baseline.json
+          npm run benchmark:large-house-isometric -- --target-root=. --samples=7 --warmups=1 --output=../artifacts/performance/isometric-candidate.json
+          npm run benchmark:large-house-plan-snap -- --target-root=../baseline --samples=7 --warmups=1 --output=../artifacts/performance/plan-snap-baseline.json
+          npm run benchmark:large-house-plan-snap -- --target-root=. --samples=7 --warmups=1 --output=../artifacts/performance/plan-snap-candidate.json
+          npm run benchmark:glow -- --profile=large-light-blend-v1 --target-root=../baseline --samples=7 --warmups=1 --output=../artifacts/performance/blend-baseline.json
+          npm run benchmark:glow -- --profile=large-light-blend-v1 --target-root=. --samples=7 --warmups=1 --output=../artifacts/performance/blend-candidate.json
+          npm run benchmark:glow -- --profile=large-house-glow-overlay-v1 --target-root=../baseline --samples=7 --warmups=1 --output=../artifacts/performance/overlay-baseline.json
+          npm run benchmark:glow -- --profile=large-house-glow-overlay-v1 --target-root=. --samples=7 --warmups=1 --output=../artifacts/performance/overlay-candidate.json
+          if ! grep -q "glow_enabled" ../baseline/src/logic.ts; then
+            echo "Base predates independent Glow; bootstrap relative overlay baseline, keep absolute gate"
+            cp ../artifacts/performance/overlay-candidate.json ../artifacts/performance/overlay-baseline.json
           fi
 
-      - name: Capture base and candidate profile
+      - name: Enforce relative and absolute performance budgets
         working-directory: candidate
-        env:
-          PROFILE: ${{ matrix.profile }}
         run: |
-          mkdir -p ../artifacts/performance
-          case "$PROFILE" in
-            large-house)
-              npm run benchmark:large-house -- --target-root=../baseline --samples=7 --warmups=1 --output=../artifacts/performance/baseline.json
-              npm run benchmark:large-house -- --target-root=. --samples=7 --warmups=1 --output=../artifacts/performance/candidate.json
-              ;;
-            isometric)
-              npm run benchmark:large-house-isometric -- --target-root=../baseline --samples=7 --warmups=1 --output=../artifacts/performance/isometric-baseline.json
-              npm run benchmark:large-house-isometric -- --target-root=. --samples=7 --warmups=1 --output=../artifacts/performance/isometric-candidate.json
-              ;;
-            isometric-stage3)
-              npm run benchmark:isometric-stage3-dense -- --allow-stage2-base --target-root=../baseline --samples=7 --warmups=1 --output=../artifacts/performance/isometric-stage3-baseline.json
-              npm run benchmark:isometric-stage3-dense -- --target-root=. --samples=7 --warmups=1 --output=../artifacts/performance/isometric-stage3-candidate.json
-              ;;
-            plan-snap)
-              npm run benchmark:large-house-plan-snap -- --target-root=../baseline --samples=7 --warmups=1 --output=../artifacts/performance/plan-snap-baseline.json
-              npm run benchmark:large-house-plan-snap -- --target-root=. --samples=7 --warmups=1 --output=../artifacts/performance/plan-snap-candidate.json
-              ;;
-            interaction)
-              npm run benchmark:large-house-interaction -- --target-root=../baseline --samples=7 --warmups=1 --output=../artifacts/performance/interaction-baseline.json
-              npm run benchmark:large-house-interaction -- --target-root=. --samples=7 --warmups=1 --output=../artifacts/performance/interaction-candidate.json
-              ;;
-            blend)
-              npm run benchmark:glow -- --profile=large-light-blend-v1 --target-root=../baseline --samples=7 --warmups=1 --output=../artifacts/performance/blend-baseline.json
-              npm run benchmark:glow -- --profile=large-light-blend-v1 --target-root=. --samples=7 --warmups=1 --output=../artifacts/performance/blend-candidate.json
-              ;;
-            overlay)
-              npm run benchmark:glow -- --profile=large-house-glow-overlay-v1 --target-root=../baseline --samples=7 --warmups=1 --output=../artifacts/performance/overlay-baseline.json
-              npm run benchmark:glow -- --profile=large-house-glow-overlay-v1 --target-root=. --samples=7 --warmups=1 --output=../artifacts/performance/overlay-candidate.json
-              if ! grep -q "glow_enabled" ../baseline/src/logic.ts; then
-                echo "Base predates independent Glow; bootstrap relative overlay baseline, keep absolute gate"
-                cp ../artifacts/performance/overlay-candidate.json ../artifacts/performance/overlay-baseline.json
-              fi
-              ;;
-            space-default)
-              npm run benchmark:glow -- --profile=large-space-card-default-v1 --target-root=../baseline --samples=7 --warmups=1 --output=../artifacts/performance/space-default-baseline.json
-              npm run benchmark:glow -- --profile=large-space-card-default-v1 --target-root=. --samples=7 --warmups=1 --output=../artifacts/performance/space-default-candidate.json
-              ;;
-            space-glow)
-              npm run benchmark:glow -- --profile=large-space-card-glow-v1 --target-root=../baseline --samples=7 --warmups=1 --output=../artifacts/performance/space-glow-baseline.json
-              npm run benchmark:glow -- --profile=large-space-card-glow-v1 --target-root=. --samples=7 --warmups=1 --output=../artifacts/performance/space-glow-candidate.json
-              if ! grep -q "light_pools" ../baseline/src/space-card.ts; then
-                echo "Base predates opt-in static Glow; bootstrap relative baseline, keep absolute gate"
-                cp ../artifacts/performance/space-glow-candidate.json ../artifacts/performance/space-glow-baseline.json
-              fi
-              ;;
-            *)
-              echo "::error::Unknown performance profile: $PROFILE"
-              exit 1
-              ;;
-          esac
+          npm run benchmark:compare -- --baseline=../artifacts/performance/baseline.json --candidate=../artifacts/performance/candidate.json --output=../artifacts/performance/comparison.json
+          npm run benchmark:compare -- --budgets=demo/performance/budgets-large-house-isometric.json --baseline=../artifacts/performance/isometric-baseline.json --candidate=../artifacts/performance/isometric-candidate.json --output=../artifacts/performance/isometric-comparison.json
+          npm run benchmark:compare -- --budgets=demo/performance/budgets-large-house-plan-snap.json --baseline=../artifacts/performance/plan-snap-baseline.json --candidate=../artifacts/performance/plan-snap-candidate.json --output=../artifacts/performance/plan-snap-comparison.json
+          npm run benchmark:compare -- --budgets=demo/performance/budgets-large-light-blend.json --baseline=../artifacts/performance/blend-baseline.json --candidate=../artifacts/performance/blend-candidate.json --output=../artifacts/performance/blend-comparison.json
+          npm run benchmark:compare -- --budgets=demo/performance/budgets-large-house-glow-overlay.json --baseline=../artifacts/performance/overlay-baseline.json --candidate=../artifacts/performance/overlay-candidate.json --output=../artifacts/performance/overlay-comparison.json
 
-      - name: Enforce relative and absolute performance budget
-        working-directory: candidate
-        env:
-          PROFILE: ${{ matrix.profile }}
-        run: |
-          case "$PROFILE" in
-            large-house)
-              npm run benchmark:compare -- --baseline=../artifacts/performance/baseline.json --candidate=../artifacts/performance/candidate.json --output=../artifacts/performance/comparison.json
-              ;;
-            isometric)
-              npm run benchmark:compare -- --budgets=demo/performance/budgets-large-house-isometric.json --baseline=../artifacts/performance/isometric-baseline.json --candidate=../artifacts/performance/isometric-candidate.json --baseline-sha="$(git -C ../baseline rev-parse HEAD)" --candidate-sha="$(git rev-parse HEAD)" --output=../artifacts/performance/isometric-comparison.json
-              ;;
-            isometric-stage3)
-              npm run benchmark:compare -- --budgets=demo/performance/budgets-isometric-stage3-dense.json --baseline=../artifacts/performance/isometric-stage3-baseline.json --candidate=../artifacts/performance/isometric-stage3-candidate.json --baseline-sha="$(git -C ../baseline rev-parse HEAD)" --candidate-sha="$(git rev-parse HEAD)" --output=../artifacts/performance/isometric-stage3-comparison.json
-              ;;
-            plan-snap)
-              npm run benchmark:compare -- --budgets=demo/performance/budgets-large-house-plan-snap.json --baseline=../artifacts/performance/plan-snap-baseline.json --candidate=../artifacts/performance/plan-snap-candidate.json --output=../artifacts/performance/plan-snap-comparison.json
-              ;;
-            interaction)
-              npm run benchmark:compare -- --budgets=demo/performance/budgets-large-house-interaction.json --baseline=../artifacts/performance/interaction-baseline.json --candidate=../artifacts/performance/interaction-candidate.json --output=../artifacts/performance/interaction-comparison.json
-              ;;
-            blend)
-              npm run benchmark:compare -- --budgets=demo/performance/budgets-large-light-blend.json --baseline=../artifacts/performance/blend-baseline.json --candidate=../artifacts/performance/blend-candidate.json --output=../artifacts/performance/blend-comparison.json
-              ;;
-            overlay)
-              npm run benchmark:compare -- --budgets=demo/performance/budgets-large-house-glow-overlay.json --baseline=../artifacts/performance/overlay-baseline.json --candidate=../artifacts/performance/overlay-candidate.json --output=../artifacts/performance/overlay-comparison.json
-              ;;
-            space-default)
-              npm run benchmark:compare -- --budgets=demo/performance/budgets-large-space-card-default.json --baseline=../artifacts/performance/space-default-baseline.json --candidate=../artifacts/performance/space-default-candidate.json --output=../artifacts/performance/space-default-comparison.json
-              ;;
-            space-glow)
-              npm run benchmark:compare -- --budgets=demo/performance/budgets-large-space-card-glow.json --baseline=../artifacts/performance/space-glow-baseline.json --candidate=../artifacts/performance/space-glow-candidate.json --output=../artifacts/performance/space-glow-comparison.json
-              ;;
-          esac
-
-      - name: Upload full performance report
+      - name: Upload full performance reports
         if: always()
-        uses: actions/upload-artifact@043fb46d1a93c77aae656e7c1c64a875d1fc6a0a # v7
+        uses: actions/upload-artifact@v7
         with:
-          name: full-performance-${{ matrix.profile }}
+          name: full-performance
           path: artifacts/performance

.github/workflows/process-metrics.yml

@@ -1,41 +0,0 @@
-name: Метрики процесса
-
-# Тонкий вызывающий файл (#623). Для этого события GitHub берёт workflow из
-# ветки по умолчанию (`main`), поэтому здесь только то, что обязано жить там:
-# триггеры, run-name, права и concurrency. Тело — `_process-metrics.yml` по ссылке
-# `@dev`: правка конвейера — один коммит в `dev`, зеркало в `main` не нужно.
-# Этот файл меняется, только когда меняются сами триггеры или потолок прав;
-# тогда он зеркалится в `main`, и preflight `workflow_sync` (validate.yml)
-# держит копии равными.
-
-on:
-  schedule:
-    # Понедельник 05:23 UTC — после ночных прогонов, до рабочего дня; минута
-    # не круглая, чтобы не стоять в очереди «ровных» расписаний (#658).
-    - cron: '23 5 * * 1'
-  workflow_dispatch:
-    inputs:
-      days:
-        description: "Окно в днях"
-        required: false
-        default: "7"
-        type: string
-
-permissions:
-  contents: read
-  actions: read
-  issues: read
-
-jobs:
-  # Потолок прав тела: объединение job-level прав `_process-metrics.yml`. Вызываемый
-  # workflow может права только сузить, поэтому каждая его job по-прежнему
-  # получает свой прежний минимум (#556), а шире этого набора не получит никто.
-  dev:
-    permissions:
-      contents: read
-      actions: read
-      issues: read
-    uses: Matysh/houseplan-card/.github/workflows/_process-metrics.yml@dev # #623: тело конвейера из dev
-    with:
-      days: ${{ inputs.days }}
-    secrets: inherit

.github/workflows/process-reconcile.yml

@@ -1,40 +0,0 @@
-name: Сверка очереди ревью
-run-name: "reconcile process queue · ${{ github.event_name }}"
-
-# Тонкий вызывающий файл (#623). Для этого события GitHub берёт workflow из
-# ветки по умолчанию (`main`), поэтому здесь только то, что обязано жить там:
-# триггеры, run-name, права и concurrency. Тело — `_process-reconcile.yml` по ссылке
-# `@dev`: правка конвейера — один коммит в `dev`, зеркало в `main` не нужно.
-# Этот файл меняется, только когда меняются сами триггеры или потолок прав;
-# тогда он зеркалится в `main`, и preflight `workflow_sync` (validate.yml)
-# держит копии равными.
-
-on:
-  schedule:
-    - cron: '7,37 * * * *'
-  workflow_dispatch:
-    inputs:
-      apply:
-        description: "Повторно будить потерянные запросы и публиковать диагностику"
-        required: true
-        type: boolean
-        default: true
-
-permissions:
-  actions: read
-  contents: read
-  issues: read
-
-jobs:
-  # Потолок прав тела: объединение job-level прав `_process-reconcile.yml`. Вызываемый
-  # workflow может права только сузить, поэтому каждая его job по-прежнему
-  # получает свой прежний минимум (#556), а шире этого набора не получит никто.
-  dev:
-    permissions:
-      actions: read
-      contents: read
-      issues: read
-    uses: Matysh/houseplan-card/.github/workflows/_process-reconcile.yml@dev # #623: тело конвейера из dev
-    with:
-      apply: ${{ inputs.apply == true }}
-    secrets: inherit

.github/workflows/process-resume.yml

@@ -1,33 +0,0 @@
-name: Продолжение ревью после Validate
-run-name: "resume · ${{ github.event.workflow_run.head_branch }} · ${{ github.event.workflow_run.conclusion }}"
-
-# Тонкий вызывающий файл (#623). Для этого события GitHub берёт workflow из
-# ветки по умолчанию (`main`), поэтому здесь только то, что обязано жить там:
-# триггеры, run-name, права и concurrency. Тело — `_process-resume.yml` по ссылке
-# `@dev`: правка конвейера — один коммит в `dev`, зеркало в `main` не нужно.
-# Этот файл меняется, только когда меняются сами триггеры или потолок прав;
-# тогда он зеркалится в `main`, и preflight `workflow_sync` (validate.yml)
-# держит копии равными.
-
-on:
-  workflow_run:
-    workflows: ["Проверка (CI)"]
-    types: [completed]
-
-permissions:
-  contents: read
-  actions: read
-
-jobs:
-  # Потолок прав тела: объединение job-level прав `_process-resume.yml`. Вызываемый
-  # workflow может права только сузить, поэтому каждая его job по-прежнему
-  # получает свой прежний минимум (#556), а шире этого набора не получит никто.
-  dev:
-    # Тот же фильтр, что у job `resume` тела: посторонние события не
-    # поднимают вызов, а прогон остаётся skipped, как до #623.
-    if: github.event.workflow_run.event == 'workflow_dispatch' && startsWith(github.event.workflow_run.head_branch, 'issue/')
-    permissions:
-      contents: read
-      actions: read
-    uses: Matysh/houseplan-card/.github/workflows/_process-resume.yml@dev # #623: тело конвейера из dev
-    secrets: inherit

.github/workflows/process.yml

@@ -1,31 +1,556 @@
-name: Ревью-конвейер
-run-name: "process #${{ github.event.issue.number }} · ${{ github.event.label.name }} · ${{ github.event.issue.title }}"
+name: Process
 
-# Тонкий вызывающий файл (#623). Для этого события GitHub берёт workflow из
-# ветки по умолчанию (`main`), поэтому здесь только то, что обязано жить там:
-# триггеры, run-name, права и concurrency. Тело — `_process.yml` по ссылке
-# `@dev`: правка конвейера — один коммит в `dev`, зеркало в `main` не нужно.
-# Этот файл меняется, только когда меняются сами триггеры или потолок прав;
-# тогда он зеркалится в `main`, и preflight `workflow_sync` (validate.yml)
-# держит копии равными.
+# Событийный конвейер процесса (PROCESS.md). Смена статусной метки — это
+# сообщение: она порождает событие, событие запускает следующий шаг.
+#
+# S4-spec-review -> ревью ТЗ    -> S5-ready | S3-spec
+# S7-code-review -> код-ревью   -> слияние в dev -> S8-merged | S6-in-progress
+#
+# Три вещи, без которых конвейер молча не работает:
+#
+# 1. Метки переставляются токеном HP_PROCESS_TOKEN, а не GITHUB_TOKEN. GitHub
+#    намеренно не запускает workflow от событий, вызванных GITHUB_TOKEN, чтобы
+#    не было циклов — цепочка оборвалась бы после первого шага.
+# 2. Этот файл обязан лежать в ветке по умолчанию (main). Для события `issues`
+#    GitHub берёт workflow только оттуда, независимо от того, что в dev.
+# 3. Многострочный текст внутри `run:` — только через heredoc. Строка с нулевым
+#    отступом обрывает блок YAML, и скрипт обрезается без ошибки парсера.
+#    Проверять не только YAML, но и каждый `run` через `bash -n`.
 
 on:
   issues:
     types: [labeled]
 
+concurrency:
+  # Два события по одному issue не должны запускать два прогона.
+  group: process-issue-${{ github.event.issue.number }}
+  cancel-in-progress: false
+
 permissions:
   contents: read
+  issues: write
+  # Обязательно: claude-code-action получает OIDC-токен для авторизации
+  # GitHub App. Без этого прогон падает с «Could not fetch an OIDC token».
+  id-token: write
 
 jobs:
-  # Потолок прав тела: объединение job-level прав `_process.yml`. Вызываемый
-  # workflow может права только сузить, поэтому каждая его job по-прежнему
-  # получает свой прежний минимум (#556), а шире этого набора не получит никто.
-  dev:
-    # Тот же фильтр, что у job `guard` тела: посторонние события не
-    # поднимают вызов, а прогон остаётся skipped, как до #623.
-    if: github.event.label.name == 'S4-spec-review' || github.event.label.name == 'S7-code-review'
-    permissions:
-      contents: read
-      issues: write
-    uses: Matysh/houseplan-card/.github/workflows/_process.yml@dev # #623: тело конвейера из dev
-    secrets: inherit
+  guard:
+    runs-on: ubuntu-latest
+    outputs:
+      stage: ${{ steps.decide.outputs.stage }}
+      cycle: ${{ steps.decide.outputs.cycle }}
+      limit: ${{ steps.decide.outputs.limit }}
+    steps:
+      - id: decide
+        env:
+          GH_TOKEN: ${{ secrets.HP_PROCESS_TOKEN }}
+          LABEL: ${{ github.event.label.name }}
+          BLOCKED: ${{ contains(github.event.issue.labels.*.name, 'blocked') }}
+          EXHAUSTED: ${{ contains(github.event.issue.labels.*.name, 'review-4') }}
+          SMALL: ${{ contains(github.event.issue.labels.*.name, 'small') }}
+          TRIVIAL: ${{ contains(github.event.issue.labels.*.name, 'trivial') }}
+          NUM: ${{ github.event.issue.number }}
+        run: |
+          # Этап определяется первым: от него зависит, какие вердикты считать.
+          stage=""; marker=""
+          case "$LABEL" in
+            S4-spec-review) stage="spec"; marker="SPEC-REVIEW" ;;
+            S7-code-review) stage="code"; marker="CODE-REVIEW" ;;
+            *) echo "метка $LABEL конвейер не запускает" ;;
+          esac
+
+          # Лимит циклов: 4 обычный, 2 на лёгком и коротком треке (PROCESS.md §4).
+          limit=4
+          if [ "$SMALL" = "true" ] || [ "$TRIVIAL" = "true" ]; then limit=2; fi
+
+          # Счётчик считает вердикты ТОЛЬКО своего этапа. Раньше он брал все
+          # подряд, и вердикт по ТЗ съедал цикл из бюджета код-ревью: на #89
+          # первое код-ревью получило r2/4. На задаче с двумя циклами ТЗ второе
+          # код-ревью упиралось бы в review-4 после одной правки.
+          #
+          # Этап опознаётся по имени документа в теле комментария. Если документа
+          # нет, вердикт не посчитается — недосчёт даёт лишний цикл, а перерасчёт
+          # остановил бы работу досрочно; из двух ошибок выбрана обратимая.
+          done_cycles=0
+          if [ -n "$stage" ]; then
+            done_cycles=$(gh issue view "$NUM" --repo "${{ github.repository }}" \
+              --json comments \
+              -q "[.comments[] | select(.body | test(\"Вердикт:\")) | select(.body | test(\"$marker\"))] | length")
+          fi
+
+          # Отказ обязан быть виден в issue, а не только в логе прогона.
+          # Ревьюшная метка обещает работу; если конвейер её не начал и промолчал,
+          # задача стоит в этом статусе бесконечно и никто об этом не узнаёт.
+          # Так и вышло на #123: чужой issue довели до S4-spec-review, guard
+          # отказался за 9 секунд, и в issue не было ни слова.
+          #
+          # Пишем только когда пытались запустить ревью, то есть stage опознан.
+          # Иначе комментарий уходил бы на каждую смену любой метки.
+          refuse() {
+            echo "$1"
+            gh issue comment "$NUM" --repo "${{ github.repository }}" --body \
+              "Конвейер ревью не запущен: $2
+
+          Метка \`$LABEL\` обещает работу, которая не начнётся, поэтому статус лучше вернуть в предыдущий — иначе задача простоит здесь бесконечно. [Прогон](${{ github.server_url }}/${{ github.repository }}/actions/runs/${{ github.run_id }})."
+            stage=""
+          }
+
+          # Автор issue здесь не проверяется (решение владельца 2026-08-13).
+          # Проверка стоит на входе в процесс, а не на каждом шаге: как только
+          # задача получила статусную метку, она в работе, и кто её завёл — не
+          # имеет значения. Само присвоение метки и есть явное подтверждение
+          # владельца, причём проверенное платформой: метки может ставить только
+          # тот, у кого есть право записи в репозиторий. Прежняя проверка здесь
+          # дублировала эту гарантию и заставляла переоформлять чужие отчёты
+          # своими issue — чистая работа впустую, как на #123.
+          if [ -z "$stage" ]; then
+            :
+          elif [ "$BLOCKED" = "true" ]; then
+            refuse "стоит blocked — конвейер не запускается" \
+              "на issue стоит \`blocked\` — задача ждёт внешнего решения. Снять метку, когда решение принято."
+          elif [ "$EXHAUSTED" = "true" ]; then
+            refuse "стоит review-4 — решение за владельцем" \
+              "на issue стоит \`review-4\`: лимит циклов ревью исчерпан, дальше решает владелец — разделить задачу, отклонить или арбитраж (PROCESS.md §4)."
+          elif [ "$done_cycles" -ge "$limit" ]; then
+            echo "циклов этапа $stage пройдено $done_cycles из $limit — лимит исчерпан"
+            gh issue edit "$NUM" --repo "${{ github.repository }}" --add-label review-4
+            gh issue comment "$NUM" --repo "${{ github.repository }}" --body \
+              "Лимит циклов ревью исчерпан ($done_cycles из $limit на этапе \`$stage\`). Пятого захода нет: решение владельца — разделить задачу, отклонить или арбитраж (PROCESS.md §4)."
+            stage=""
+          else
+            echo "этап $stage, цикл $((done_cycles + 1)) из $limit"
+          fi
+          echo "stage=$stage" >> "$GITHUB_OUTPUT"
+          echo "cycle=$((done_cycles + 1))" >> "$GITHUB_OUTPUT"
+          echo "limit=$limit" >> "$GITHUB_OUTPUT"
+
+  review:
+    needs: guard
+    if: needs.guard.outputs.stage != ''
+    runs-on: ubuntu-latest
+    # Время — единственный настоящий ограничитель зациклившегося прогона.
+    timeout-minutes: 45
+    steps:
+      - uses: actions/checkout@v7
+        with:
+          fetch-depth: 0
+          ref: dev
+          # Иначе в конфиге git остаётся креденшел GITHUB_TOKEN, и push с
+          # мёртвым PAT молча уходит от github-actions[bot] — 403 при
+          # contents: read. Отказ обязан быть громким и правильным.
+          persist-credentials: false
+
+      # Живость PAT проверяется ДО ревью. На #150 истёкший токен обнаружился
+      # только на публикации документа — после сорока минут работы ревьюера.
+      - name: Секрет HP_PROCESS_TOKEN жив
+        env:
+          GH_TOKEN: ${{ secrets.HP_PROCESS_TOKEN }}
+        run: |
+          if [ -z "$GH_TOKEN" ]; then
+            echo "::error::HP_PROCESS_TOKEN пуст — секрет удалён или недоступен"
+            exit 1
+          fi
+          if ! login=$(gh api user -q .login 2>/dev/null); then
+            echo "::error::HP_PROCESS_TOKEN не аутентифицируется — истёк или отозван. Обновить: Settings -> Secrets and variables -> Actions -> HP_PROCESS_TOKEN"
+            exit 1
+          fi
+          echo "токен жив, действует от: $login"
+
+      # Окружение готовит workflow, а не модель своими ходами. Раньше промпт
+      # велел ревьюеру самому выполнить `npm ci`: минуты уходили на установку без
+      # кэша, платились из бюджета 45 минут и из лимитов подписки, а ходы модели
+      # тратились на работу инфраструктуры. В validate.yml кэш стоит на всех
+      # тяжёлых job, здесь его не было.
+      - uses: actions/setup-node@v7
+        with:
+          node-version: 22
+          cache: npm
+
+      # Материал ревью живёт в ветке задачи: ТЗ в docs/specs/ и код коммитятся
+      # в issue/<NN>-slug. Если ветка запушена — переключаемся на неё, иначе
+      # ревьюер прочтёт dev и не найдёт того, что должен оценивать.
+      - name: Перейти на ветку задачи
+        id: branch
+        env:
+          NUM: ${{ github.event.issue.number }}
+        run: |
+          # Свежая по последнему коммиту, а не первая по алфавиту: на #150 рядом
+          # жили ветка ТЗ и ветка реализации, и head -1 выбрал устаревшую.
+          git fetch -q origin "+refs/heads/issue/${NUM}-*:refs/remotes/origin/issue/${NUM}-*" || true
+          branches=$(git for-each-ref --sort=-committerdate \
+            --format='%(refname:lstrip=3)' "refs/remotes/origin/issue/${NUM}-*")
+          branch=$(printf '%s\n' "$branches" | head -1)
+          if [ "$(printf '%s\n' "$branches" | grep -c .)" -gt 1 ]; then
+            echo "::warning::веток issue/${NUM}-* несколько ($(echo $branches | tr '\n' ' ')) — выбрана свежая по коммиту: $branch. Устаревшую следует удалить."
+          fi
+          if [ -n "$branch" ]; then
+            git checkout -q "origin/$branch"
+            echo "материал ревью: ветка $branch, $(git rev-parse --short HEAD)"
+            echo "name=$branch" >> "$GITHUB_OUTPUT"
+          else
+            echo "::warning::ветка issue/${NUM}-* не найдена на origin — ревью пойдёт по dev"
+            echo "МАТЕРИАЛ НЕ ЗАПУШЕН" >> "$GITHUB_STEP_SUMMARY"
+          fi
+
+      # Зависимости ставятся ПОСЛЕ переключения на ветку задачи: lockfile мог
+      # измениться именно в ней, и установка по копии из dev дала бы не то дерево.
+      - name: Установить зависимости
+        run: npm ci
+
+      # Браузер нужен не всякому ревью (см. правило выбора гейтов в промпте),
+      # но когда нужен — качать его заново дороже, чем держать в кэше.
+      - name: Кэш браузеров Playwright
+        id: pw
+        uses: actions/cache@v6
+        with:
+          path: ~/.cache/ms-playwright
+          key: playwright-${{ runner.os }}-${{ hashFiles('package-lock.json') }}
+
+      - name: Установить Chromium
+        if: steps.pw.outputs.cache-hit != 'true'
+        # Без --with-deps: системные библиотеки Chromium предустановлены в
+        # образе ubuntu-latest, а apt при промахе кэша съедал минуты из бюджета
+        # ревью и подолгу перебирал недоступное azure-зеркало (#175). Если
+        # библиотека когда-нибудь пропадёт из образа, Chromium не запустится с
+        # внятной ошибкой — тогда флаг вернуть.
+        run: npx playwright install chromium
+
+      - name: Review
+        id: review
+        uses: anthropics/claude-code-action@v1
+        with:
+          # Подписка, а не отдельный счёт API: токен выпускается через
+          # `claude setup-token` (Pro/Max). Действуют лимиты подписки.
+          claude_code_oauth_token: ${{ secrets.CLAUDE_CODE_OAUTH_TOKEN }}
+          prompt: |
+            Ты ревьюер проекта House Plan. Язык ответа — русский.
+
+            Issue: #${{ github.event.issue.number }}
+            Репозиторий: ${{ github.repository }}
+            Этап: ${{ needs.guard.outputs.stage }}
+              spec — ревью ТЗ (PROCESS.md §2.4)
+              code — код-ревью (PROCESS.md §2.7)
+            Цикл: r${{ needs.guard.outputs.cycle }}
+
+            **Если цикл не первый — объём разбора по дельте, а не заново**
+            (PROCESS.md §2.9, issue #214). Раньше промпт был одинаковым для
+            всех раундов, и повторный цикл заново выводил продуктовую рамку и
+            перепроверял AC, которых правка не касалась: r2 по #150 стоил
+            полного прогона ради одной строки в тестовой фикстуре.
+
+            Порядок для r2 и дальше:
+              1. найди вердикт предыдущего раунда в комментариях issue и SHA,
+                 на котором он получен. SHA в вердикте не назван — это находка;
+              2. объяви дельту: `git diff <тот SHA>..HEAD` для кода, дифф файла
+                 ТЗ или тела issue для spec. Дельта — предмет этого раунда;
+              3. по каждой находке предыдущего раунда покажи, чем именно она
+                 закрыта: строка кода или текста, а не заявление автора;
+              4. заново проверяй только те AC, чьё доказательство дельта
+                 задевает. Остальные наследуй;
+              5. в документе обязателен раздел «Унаследовано из r<N-1>»: что
+                 принято без повторной проверки, со ссылкой на документ того
+                 раунда и SHA, на котором вывод получен. Без этого перечня
+                 сокращение — молчаливое доверие, а такой тихий успех уже
+                 дважды стоил дня (#171, #207).
+
+            Разбор остаётся ПОЛНЫМ, если дельта не локальна: ребейз на ушедший
+            вперёд dev (после ребейза это другой код, §7.2), смена контракта
+            поведения, задета новая подсистема, либо объём дельты сопоставим с
+            исходной задачей. Сомневаешься — разбирай полностью и скажи почему.
+
+            Сокращается объём РАЗБОРА, а не строгость: правка по замечанию
+            способна сломать AC, который предыдущий раунд признал выполненным —
+            так появилась регрессия #102. Поэтому граница не «только находки», а
+            «находки плюс всё, до чего дотягивается дельта».
+
+            Прочитай в этом порядке, прежде чем судить:
+              1. docs/SCOPE.md — зачем продукт существует и для кого. Он
+                 ограничитель: «features are built, improved and accepted only
+                 if they serve a job listed here». Первый вопрос к задаче —
+                 какую строку Core user jobs она закрывает.
+              2. AGENTS.md и PROCESS.md — процесс, классы изменений, трейлеры,
+                 лимит циклов, формат вердикта.
+              3. Тело issue #${{ github.event.issue.number }} и все комментарии.
+              4. Если меняется видимое поведение — docs/USER-GUIDE.ru.md:
+                 терминология интерфейса берётся оттуда, а не изобретается.
+              5. Канонический документ затронутой подсистемы: docs/SUN.md,
+                 LIGHT.md, CANVAS.md, WALL-THICKNESS.md, UX-MODES.md,
+                 CONFIG-COMPATIBILITY.md, TOUCH-SUPPORT.md.
+
+            Для этапа spec: если issue помечен small, ТЗ живёт в теле issue и
+            файла в docs/specs/ быть не должно. Иначе ТЗ — docs/specs/<NN>-*.md.
+            Проверь обязательные разделы §7.1, однозначность каждого AC и
+            указание способа доказательства. Отдельно проверь, что автор не
+            выдал догадку за решение: утверждение о поведении, которого нет ни
+            в одном документе и которое не помечено как предположение, —
+            замечание. Не бывает сложной задачи без единого открытого вопроса.
+
+            Владельцу задаются только продуктовые вопросы: что человек видит или
+            делает и каков объём видимых изменений в этом issue. Технический
+            вопрос, вынесенный владельцу, — тоже замечание: ты его снимаешь и
+            решаешь по существу в своём вердикте.
+
+            Для этапа code: материал — диапазон `git log --oneline origin/dev..HEAD`
+            и `git diff origin/dev...HEAD`. Ручного тестирования в цикле нет,
+            поэтому именно ты отвечаешь на вопрос «оно вообще работает».
+            По каждому AC: либо он доказан автотестом и ты убедился, что тест
+            умеет падать, либо разобран по коду с явной записью «проверено
+            чтением, не исполнением». «Verified» без названной команды и её
+            результата доказательством не является. Зависимости уже установлены
+            workflow, Chromium тоже — `npm ci` выполнять не нужно. Проверь
+            трейлеры Issue и User-Visible, при User-Visible: yes — правки в оба
+            changelog в том же коммите.
+
+            **Объём гейтов соразмерен задаче.** Прогонять весь набор на каждой
+            правке — не тщательность, а потеря времени: полные наборы это
+            предрелизный гейт (PROCESS.md §8), а не гейт ревью.
+
+            Всегда, они дешёвые, и в повторном раунде тоже: код изменился,
+            а стоят они минуты:
+              `npx tsc --noEmit`, `npm test`, `npm run build` со сверкой трёх
+              копий бандла.
+
+            По необходимости, и «необходимость» определяется diff'ом и AC:
+              - браузерные смоки `demo/smoke_*.mjs` — названные в AC плюс
+                относящиеся к тронутым поверхностям. Их 127; прогон всех уместен
+                только когда задача действительно задевает всё;
+              - `npm run golden:verify` — если diff может изменить видимый
+                результат: рендер, геометрия, стили, слои;
+              - `python -m pytest tests_backend -q` — если тронут
+                `custom_components/**/*.py`;
+              - performance-профили — если названы в AC либо тронуты
+                чувствительные к перфу пути.
+
+            Дисциплина «тест должен уметь падать» не отменяется, но применяется к
+            тем тестам, которые ты прогонял.
+
+            **В комментарии обязателен перечень: какие гейты прогнал, какие нет и
+            почему.** Это условие честности такого сужения: непрогнанный гейт
+            становится видимым решением, а не молчаливым пропуском. Раздел «чего
+            не проверял» в документе ревью — не формальность, а главный его
+            раздел на коротких задачах.
+
+            Ты НЕ правишь ни ТЗ, ни продуктовый код. Только оцениваешь.
+
+            Серьёзность: High блокирует; Medium В СКОУПЕ задачи чинится в ней
+            же — без High это жёлтый вердикт и возврат автору, отдельный issue
+            НЕ заводится (решение владельца 2026-08-19, #202: заведение и
+            обслуживание issue дороже правки на месте); Low либо правится,
+            либо снимается с записью. Жёлтый вердикт допустим и при полностью
+            выполненных AC, если изменение не решает заявленный сценарий или
+            ухудшает смежный. Продуктовое рассуждение расширяет вопросы, но не
+            отменяет AC и не даёт права менять скоуп.
+
+            Только Medium-находку ВНЕ скоупа задачи (попутный дефект соседнего
+            поведения, который в этой ветке чинить нельзя) заведи отдельным
+            issue со ссылкой на #${{ github.event.issue.number }} и метками:
+            тип, приоритет, S1-new. «Оставили в тексте ревью» закрытием не
+            считается и прямо запрещено §12.
+
+            Напиши полный документ ревью в файл
+            docs/reviews/<SPEC|CODE>-REVIEW-${{ github.event.issue.number }}-r${{ needs.guard.outputs.cycle }}.md
+            (SPEC для этапа spec, CODE для code): скоуп, как проверялось,
+            находки с воспроизведением, что проверено и корректно, чего не
+            проверял. Для r2 и дальше добавь два раздела: «Закрытие раунда
+            r<N-1>» — таблица «находка | чем закрыта | где это видно», и
+            «Унаследовано из r<N-1>» — что принято без повторной проверки, с
+            документом и SHA. Каталог docs/reviews/ создай, если его нет. Больше не
+            пиши ничего: любой файл вне docs/reviews/ опубликован не будет.
+
+            Затем оставь в issue краткий комментарий: вердикт, ключевые находки
+            и ссылка на документ. Первой строкой — вердикт в формате §7.2:
+            `Вердикт: зелёный/жёлтый/красный · цикл r${{ needs.guard.outputs.cycle }}/${{ needs.guard.outputs.limit }} · High: N · Medium: N → в задаче | #…`
+            («→ #…» — только у Medium вне скоупа; находки в скоупе возвращаются автору жёлтым)
+
+            Затем верни JSON по схеме. Это последнее действие и оно обязательно:
+            без него метка не переставится и конвейер встанет.
+          claude_args: |
+            --max-turns 150
+            --allowedTools Read,Write,Grep,Glob,Bash,mcp__github__add_issue_comment,mcp__github__issue_write,mcp__github__issue_read
+            --json-schema '{"type":"object","properties":{"verdict":{"type":"string","enum":["green","yellow","red"]},"high":{"type":"integer"},"medium":{"type":"integer"},"summary":{"type":"string"}},"required":["verdict","high","medium","summary"]}'
+
+      # Ревьюер пишет только в docs/reviews/. Что именно попадёт в коммит,
+      # решает этот шаг, а не модель: всё остальное откатывается.
+      - name: Опубликовать документ ревью
+        env:
+          TOKEN: ${{ secrets.HP_PROCESS_TOKEN }}
+          BRANCH: ${{ steps.branch.outputs.name }}
+          NUM: ${{ github.event.issue.number }}
+          STAGE: ${{ needs.guard.outputs.stage }}
+          CYCLE: ${{ needs.guard.outputs.cycle }}
+        run: |
+          # Ветки задачи может не быть: у задач, размеченных до появления
+          # конвейера, ТЗ лежит прямо в dev. Раньше шаг в этом случае молча
+          # выходил с нулём, и разбор ревью терялся — оставался только вердикт
+          # комментарием. Это тот же тихий отказ: шаг сообщал об успехе тем, что
+          # ничего не сделал. Документ ложится туда же, где лежит само ТЗ.
+          target="${BRANCH:-dev}"
+          if [ -z "$BRANCH" ]; then
+            echo "::warning::ветки задачи нет — документ ревью ляжет в dev"
+          fi
+          marker=CODE-REVIEW
+          if [ "$STAGE" = "spec" ]; then marker=SPEC-REVIEW; fi
+          doc="docs/reviews/${marker}-${NUM}-r${CYCLE}.md"
+          git checkout -- . 2>/dev/null || true
+          git clean -fd -e docs/reviews -e node_modules >/dev/null 2>&1 || true
+          git add docs/reviews 2>/dev/null || true
+          if git diff --cached --quiet; then
+            # Пустая рабочая копия — ещё не провал: ревьюер иногда коммитит
+            # документ сам, своим app-токеном мимо этого шага (CODE-REVIEW-150-r1,
+            # коммиттер GitHub). Провал — когда файла нет и на ветке.
+            git fetch -q origin "$target"
+            if git cat-file -e "origin/$target:$doc" 2>/dev/null; then
+              echo "документ уже опубликован ревьюером: $doc"
+              exit 0
+            fi
+            # Ревью без артефакта запрещено (PROCESS.md §2.4/§10.4/§12). Раньше
+            # здесь стоял warning с exit 0: на #150 оба вердикта ревью ТЗ
+            # остались только комментариями, метки переставились, и пропажу
+            # заметило лишь следующее ревью — issue #171. Падение ДО шага с
+            # меткой сохраняет инвариант «метка не сменилась = прогон упал».
+            echo "::error::вердикт есть, а документа $doc нет ни в рабочей копии, ни в $target — ревью без артефакта (#171)"
+            exit 1
+          fi
+          git -c user.name="claude[bot]" \
+              -c user.email="209825114+claude[bot]@users.noreply.github.com" \
+              commit -q -F - <<EOF
+          docs: review document for #$NUM
+
+          Issue: #$NUM
+          User-Visible: no
+          EOF
+          # Публикация в dev идёт из детачнутого состояния поверх ветки задачи
+          # либо dev, поэтому push нужен с явным перебазированием при гонке:
+          # dev мог уйти вперёд, пока шло ревью — оно длится до 45 минут.
+          if ! git push -q "https://x-access-token:$TOKEN@github.com/${{ github.repository }}" \
+               "HEAD:$target"; then
+            git fetch -q origin "$target"
+            if ! git -c user.name="claude[bot]" \
+                     -c user.email="209825114+claude[bot]@users.noreply.github.com" \
+                     rebase "origin/$target"; then
+              git rebase --abort || true
+              # Тоже вердикт без артефакта: раньше exit 0 переставил бы метку.
+              echo "::error::документ ревью не удалось опубликовать в $target: конфликт (#171)"
+              exit 1
+            fi
+            git push -q "https://x-access-token:$TOKEN@github.com/${{ github.repository }}" \
+              "HEAD:$target"
+          fi
+          # Постусловие: до ветки дошёл именно ожидаемый файл. Коммит с
+          # документом, названным не по формату, — тот же вердикт без
+          # артефакта, только дороже в обнаружении.
+          git fetch -q origin "$target"
+          if ! git cat-file -e "origin/$target:$doc" 2>/dev/null; then
+            echo "::error::коммит в $target опубликован, но ожидаемого $doc в нём нет — файл назван не по формату (#171)"
+            exit 1
+          fi
+          echo "документ опубликован в $target: $doc"
+
+      - name: Решение по вердикту
+        id: decide
+        env:
+          OUT: ${{ steps.review.outputs.structured_output }}
+          STAGE: ${{ needs.guard.outputs.stage }}
+        run: |
+          verdict=$(echo "$OUT" | jq -r '.verdict')
+          high=$(echo "$OUT" | jq -r '.high')
+          echo "вердикт: $verdict, High: $high"
+
+          # Вперёд двигает ТОЛЬКО зелёный. Жёлтый и красный возвращают
+          # автору: на прогоне #111 жёлтый означал, что AC описывает неверное
+          # изменение контракта — реализовать такое ТЗ значит сделать ошибку
+          # по инструкции. Оба считаются циклом.
+          if [ "$verdict" = "green" ] && [ "$high" -eq 0 ]; then
+            green=true
+            case "$STAGE" in
+              spec) from=S4-spec-review; to=S5-ready ;;
+              code) from=S7-code-review; to=S8-merged ;;
+            esac
+          else
+            green=false
+            case "$STAGE" in
+              spec) from=S4-spec-review; to=S3-spec ;;
+              code) from=S7-code-review; to=S6-in-progress ;;
+            esac
+          fi
+          echo "green=$green" >> "$GITHUB_OUTPUT"
+          echo "from=$from"   >> "$GITHUB_OUTPUT"
+          echo "to=$to"       >> "$GITHUB_OUTPUT"
+
+      # S8-merged утверждает, что код в dev. Значит слияние обязано произойти
+      # ДО метки, иначе она врёт в промежутке.
+      #
+      # При конфликте шаг НЕ падает и метку не оставляет на месте. Первая
+      # редакция делала именно так, и это оказалось тупиком: автор ждёт смену
+      # метки, метка не менялась, и он тридцать раз опрашивал впустую, чтобы
+      # затем отчитаться «лимит исчерпан» — при зелёном вердикте. Инвариант
+      # теперь жёстче: ПОСЛЕ ПРОГОНА РЕВЬЮ МЕТКА МЕНЯЕТСЯ ВСЕГДА.
+      - name: Слить ветку в dev
+        id: merge
+        if: needs.guard.outputs.stage == 'code' && steps.decide.outputs.green == 'true'
+        env:
+          TOKEN: ${{ secrets.HP_PROCESS_TOKEN }}
+          GH_TOKEN: ${{ secrets.HP_PROCESS_TOKEN }}
+          BRANCH: ${{ steps.branch.outputs.name }}
+          NUM: ${{ github.event.issue.number }}
+        run: |
+          if [ -z "$BRANCH" ]; then
+            echo "::error::ветки задачи нет — сливать нечего"
+            echo "merged=false" >> "$GITHUB_OUTPUT"
+            exit 0
+          fi
+          git fetch -q origin dev
+          git checkout -q -B merge-into-dev "origin/$BRANCH"
+          if ! git -c user.name="claude[bot]" \
+                   -c user.email="209825114+claude[bot]@users.noreply.github.com" \
+                   rebase origin/dev; then
+            git rebase --abort || true
+            echo "merged=false" >> "$GITHUB_OUTPUT"
+            echo "::warning::ветка $BRANCH не сливается в dev без конфликта"
+            cat > /tmp/conflict.md <<EOF
+          **Код-ревью зелёное — вердикт выше в силе, переделывать работу не нужно.** Не удалось только слияние: ветка \`$BRANCH\` конфликтует с \`dev\`.
+
+          Задача переведена в \`S6-in-progress\`, потому что работа вернулась к автору. Осталась не правка кода, а ребейз:
+
+          1. \`git fetch origin\`, затем \`git rebase origin/dev\` в ветке задачи, разрешить конфликт;
+          2. запушить ветку;
+          3. вернуть метку \`S7-code-review\`.
+
+          Повторный прогон ревью — не формальность: после ребейза на новый \`dev\` это другой код, и принимать его без проверки нельзя. Цикл считается по этапу, лимит на код-ревью тратится отдельно от ревью ТЗ.
+          EOF
+            gh issue comment "$NUM" --repo "${{ github.repository }}" --body-file /tmp/conflict.md
+            exit 0
+          fi
+          git push -q "https://x-access-token:$TOKEN@github.com/${{ github.repository }}" HEAD:dev
+          echo "merged=true" >> "$GITHUB_OUTPUT"
+          echo "слито в dev: $(git rev-parse --short HEAD)"
+
+      - name: Переставить метку
+        env:
+          # Именно PAT: с GITHUB_TOKEN следующий шаг конвейера не запустится.
+          GH_TOKEN: ${{ secrets.HP_PROCESS_TOKEN }}
+          NUM: ${{ github.event.issue.number }}
+          FROM: ${{ steps.decide.outputs.from }}
+          # Зелёное код-ревью без слияния ведёт не в S8-merged, а обратно к
+          # автору: метка утверждала бы, что код в dev, а его там нет.
+          TO: ${{ (needs.guard.outputs.stage == 'code' && steps.decide.outputs.green == 'true' && steps.merge.outputs.merged != 'true') && 'S6-in-progress' || steps.decide.outputs.to }}
+        run: |
+          gh issue edit "$NUM" --repo "${{ github.repository }}" \
+            --add-label "$TO" --remove-label "$FROM"
+          echo "$FROM -> $TO"
+
+      - name: Позвать владельца, если ревью упало
+        if: failure()
+        env:
+          GH_TOKEN: ${{ secrets.HP_PROCESS_TOKEN }}
+          RUN_URL: ${{ github.server_url }}/${{ github.repository }}/actions/runs/${{ github.run_id }}
+        run: |
+          # Тело через heredoc, а не многострочный --body: строка с нулевым
+          # отступом обрывает блок YAML и оставляет незакрытую кавычку.
+          cat > /tmp/failure.md <<EOF
+          Автоматическое ревью не отработало: [прогон]($RUN_URL). Статусная метка не менялась, задача осталась на месте.
+
+          Если вердикт выше всё же опубликован — сбой произошёл после него. Перестановку метки в этом случае выполняет чат обслуживания или владелец, но не автор задачи: автор не толкует вердикт о своей же работе.
+          EOF
+          gh issue comment "${{ github.event.issue.number }}" \
+            --repo "${{ github.repository }}" --body-file /tmp/failure.md

.github/workflows/publish-prerelease.yml

@@ -1,4 +1,4 @@
-name: Публикация пре-релиза (ручная)
+name: Publish prerelease
 run-name: Publish ${{ inputs.tag }}
 
 on:
@@ -12,7 +12,6 @@ on:
 permissions:
   contents: write
   actions: read
-  issues: read
 
 concurrency:
   group: publish-prerelease-${{ inputs.tag }}
@@ -20,21 +19,18 @@ concurrency:
 
 jobs:
   gate:
-    name: "Гейт: зелёная Проверка и релизный контракт"
-    runs-on: ubuntu-24.04
-    # Больше ожидания зелёного Validate в release-gate.mjs (до 60 мин) (#658).
-    timeout-minutes: 75
+    runs-on: ubuntu-latest
     outputs:
       sha: ${{ steps.candidate.outputs.sha }}
       tag: ${{ steps.candidate.outputs.tag }}
     steps:
-      - uses: actions/checkout@3d3c42e5aac5ba805825da76410c181273ba90b1 # v7
+      - uses: actions/checkout@v7
         with:
           ref: ${{ github.sha }}
           fetch-depth: 0
-      - uses: actions/setup-node@820762786026740c76f36085b0efc47a31fe5020 # v7
+      - uses: actions/setup-node@v7
         with: { node-version: 22 }
-      - name: Pin the dev candidate or the existing annotated tag
+      - name: Pin the current dev candidate
         id: candidate
         env:
           TAG: ${{ inputs.tag }}
@@ -45,127 +41,59 @@ jobs:
             echo "::error::Prereleases must be dispatched from the dev branch, got $REF_NAME"
             exit 1
           }
-          DISPATCHED_SHA=$(git rev-parse HEAD)
-          git fetch --force origin dev --tags
-          REMOTE=$(git ls-remote --tags origin "refs/tags/$TAG" "refs/tags/$TAG^{}")
-          if [ -n "$REMOTE" ]; then
-            SHA=$(printf '%s\n' "$REMOTE" | awk -v ref="refs/tags/$TAG^{}" '$2 == ref {print $1}')
-            test -n "$SHA" || {
-              echo "::error::Existing remote tag $TAG is not annotated"
-              exit 1
-            }
-          else
-            SHA=$DISPATCHED_SHA
-            test "$(git rev-parse origin/dev)" = "$SHA" || {
-              echo "::error::The dispatched SHA is no longer the origin/dev tip"
-              exit 1
-            }
-          fi
-          git checkout --detach "$SHA"
+          SHA=$(git rev-parse HEAD)
+          git fetch origin dev
+          test "$(git rev-parse origin/dev)" = "$SHA" || {
+            echo "::error::The dispatched SHA is no longer the origin/dev tip"
+            exit 1
+          }
           echo "sha=$SHA" >> "$GITHUB_OUTPUT"
           echo "tag=$TAG" >> "$GITHUB_OUTPUT"
       - name: Verify version, changelogs and bilingual release notes
         env:
           TAG: ${{ inputs.tag }}
         run: node scripts/release-contract.mjs "$TAG" --repo="$GITHUB_REPOSITORY"
-      # #479: тяжёлые job Validate идут только на коммите с трейлером `Release:`.
-      # Зелёный Validate без трейлера означал бы прогон без смоков и golden —
-      # класс тихого пропуска #171/#207, поэтому трейлер проверяется здесь явно.
-      - name: Require the Release trailer on the candidate commit
-        env:
-          SHA: ${{ steps.candidate.outputs.sha }}
-        run: |
-          set -euo pipefail
-          git log -1 --format=%B "$SHA" > /tmp/head-message.txt
-          if ! grep -Eq '^Release:[[:space:]]*v?[0-9]+\.[0-9]+\.[0-9]+' /tmp/head-message.txt; then
-            echo "::error::Candidate $SHA has no Release: trailer — Validate ran without the heavy gates (#479)"
-            exit 1
-          fi
-      # #479: свежесть скриншотов на обычном пуше — предупреждение; на
-      # кандидате она обязана быть доказана строгим режимом.
-      - name: Documentation screenshots are fresh for the candidate
-        run: node scripts/check-docs.mjs --screenshots=strict
       - name: Require green Validate for this exact SHA
         env:
           GH_TOKEN: ${{ github.token }}
           REPO: ${{ github.repository }}
           SHA: ${{ steps.candidate.outputs.sha }}
         run: node scripts/release-gate.mjs "$SHA"
-      - name: Bind issue membership to the exact candidate
-        env:
-          GH_TOKEN: ${{ github.token }}
-          TAG: ${{ steps.candidate.outputs.tag }}
-          SHA: ${{ steps.candidate.outputs.sha }}
-        run: |
-          set -euo pipefail
-          mkdir -p release-membership
-          if gh release view "$TAG" --repo "$GITHUB_REPOSITORY" >/dev/null 2>&1; then
-            gh release download "$TAG" --repo "$GITHUB_REPOSITORY" \
-              --dir release-membership --pattern RELEASE-MEMBERSHIP.json --clobber || true
-          fi
-          if [ -s release-membership/RELEASE-MEMBERSHIP.json ]; then
-            node scripts/release-membership.mjs verify --tag="$TAG" --candidate="$SHA" \
-              --input=release-membership/RELEASE-MEMBERSHIP.json
-          else
-            ISSUES=$(gh issue list --repo "$GITHUB_REPOSITORY" --state open \
-              --label S8-merged --limit 1000 --json number --jq 'map(.number)|join(",")')
-            node scripts/release-membership.mjs create --tag="$TAG" --candidate="$SHA" \
-              --issues="$ISSUES" --allow-unmatched \
-              --output=release-membership/RELEASE-MEMBERSHIP.json
-          fi
-      - name: Preserve candidate membership for publication
-        uses: actions/upload-artifact@043fb46d1a93c77aae656e7c1c64a875d1fc6a0a # v7
-        with:
-          name: release-membership
-          path: release-membership/RELEASE-MEMBERSHIP.json
-          if-no-files-found: error
-          retention-days: 7
 
   publish:
-    name: Публикация тега и релиза
     needs: gate
-    runs-on: ubuntu-24.04
-    timeout-minutes: 20
+    runs-on: ubuntu-latest
     outputs:
       url: ${{ steps.verify.outputs.url }}
       newly_published: ${{ steps.release.outputs.newly_published }}
     steps:
-      - uses: actions/checkout@3d3c42e5aac5ba805825da76410c181273ba90b1 # v7
+      - uses: actions/checkout@v7
         with:
           ref: ${{ needs.gate.outputs.sha }}
           fetch-depth: 0
-      - uses: actions/setup-node@820762786026740c76f36085b0efc47a31fe5020 # v7
+      - uses: actions/setup-node@v7
         with: { node-version: 22 }
-      - uses: actions/download-artifact@37930b1c2abaa49bbe596cd826c3c89aef350131 # v7
-        with:
-          name: release-membership
-          path: release-assets
       - name: Build and verify both release assets before publication
         env:
           TAG: ${{ needs.gate.outputs.tag }}
-          SHA: ${{ needs.gate.outputs.sha }}
         run: |
           set -euo pipefail
           npm ci
           npm run build
-          node scripts/bundle-tree.mjs dist custom_components/houseplan/frontend
-          npm run bundle:budget
+          cmp dist/houseplan-card.js custom_components/houseplan/frontend/houseplan-card.js
+          cmp dist/houseplan-card.js demo/srv/assets/houseplan-card.js
           VERSION=${TAG#v}
-          grep -RFq "$VERSION" dist
-          # #540: тот же способ, что у release.yml и release-prerelease.mjs —
-          # архив закоммиченного дерева точного коммита, детерминированный.
-          git -c core.autocrlf=false archive --format=zip --output=houseplan.zip \
-            "$SHA:custom_components/houseplan"
-          node scripts/verify-houseplan-zip.mjs houseplan.zip \
-            custom_components/houseplan/frontend "$VERSION"
+          grep -Fq "$VERSION" dist/houseplan-card.js
+          (cd custom_components/houseplan && zip -qr ../../houseplan.zip .)
+          unzip -l houseplan.zip | grep -q "manifest.json"
+          ZIP_VERSION=$(unzip -p houseplan.zip manifest.json | node -e \
+            "let s='';process.stdin.on('data',d=>s+=d).on('end',()=>process.stdout.write(JSON.parse(s).version))")
+          test "$ZIP_VERSION" = "$VERSION" || {
+            echo "::error::houseplan.zip manifest version $ZIP_VERSION != $VERSION"
+            exit 1
+          }
           test -s dist/houseplan-card.js
-          test -s dist/houseplan-panel.js
           test -s houseplan.zip
-          mkdir -p release-assets
-          cp dist/houseplan-card.js houseplan.zip release-assets/
-          node scripts/release-membership.mjs verify --tag="$TAG" --candidate="$SHA" \
-            --input=release-assets/RELEASE-MEMBERSHIP.json
-          node scripts/release-assets.mjs sums release-assets --include-membership
       - name: Create or verify the annotated tag
         env:
           TAG: ${{ needs.gate.outputs.tag }}
@@ -204,22 +132,7 @@ jobs:
           fi
           WAS_DRAFT=$(gh release view "$TAG" --repo "$GITHUB_REPOSITORY" --json isDraft --jq .isDraft)
           echo "newly_published=$WAS_DRAFT" >> "$GITHUB_OUTPUT"
-          if [ "$WAS_DRAFT" = "false" ]; then
-            mkdir -p existing-public
-            if gh release download "$TAG" --repo "$GITHUB_REPOSITORY" --dir existing-public \
-                --pattern houseplan-card.js --pattern houseplan.zip \
-                --pattern RELEASE-MEMBERSHIP.json --pattern SHA256SUMS --clobber \
-              && diff -u release-assets/SHA256SUMS existing-public/SHA256SUMS \
-              && node scripts/release-assets.mjs check existing-public release-assets/SHA256SUMS \
-              && node scripts/release-membership.mjs verify --tag="$TAG" --candidate="${{ needs.gate.outputs.sha }}" \
-                --input=existing-public/RELEASE-MEMBERSHIP.json; then
-              echo "release is already public and byte-identical; publication skipped"
-              exit 0
-            fi
-            echo "existing public assets need recovery; verified files will be uploaded again"
-          fi
-          gh release upload "$TAG" release-assets/houseplan-card.js release-assets/houseplan.zip \
-            release-assets/RELEASE-MEMBERSHIP.json release-assets/SHA256SUMS \
+          gh release upload "$TAG" dist/houseplan-card.js houseplan.zip \
             --repo "$GITHUB_REPOSITORY" --clobber
           RELEASE_JSON=$(gh release view "$TAG" --repo "$GITHUB_REPOSITORY" \
             --json tagName,isDraft,isPrerelease,assets,url)
@@ -228,7 +141,7 @@ jobs:
           const release = JSON.parse(process.env.RELEASE_JSON);
           if (release.tagName !== process.env.TAG) throw new Error('release tag mismatch');
           const assets = new Map(release.assets.map((asset) => [asset.name, asset]));
-          for (const name of ['houseplan-card.js', 'houseplan.zip', 'RELEASE-MEMBERSHIP.json', 'SHA256SUMS']) {
+          for (const name of ['houseplan-card.js', 'houseplan.zip']) {
             if (!(Number(assets.get(name)?.size) > 0)) throw new Error(`${name} is missing or empty`);
           }
           NODE
@@ -250,26 +163,17 @@ jobs:
           if (release.tagName !== process.env.TAG || release.isDraft || !release.isPrerelease)
             throw new Error('release is not a public prerelease for the requested tag');
           const assets = new Map(release.assets.map((asset) => [asset.name, asset]));
-          for (const name of ['houseplan-card.js', 'houseplan.zip', 'RELEASE-MEMBERSHIP.json', 'SHA256SUMS']) {
+          for (const name of ['houseplan-card.js', 'houseplan.zip']) {
             if (!(Number(assets.get(name)?.size) > 0)) throw new Error(`${name} is missing or empty`);
           }
           NODE
-          # #540: публичные байты — ровно те, что собраны и проверены выше.
-          mkdir -p public
-          gh release download "$TAG" --repo "$GITHUB_REPOSITORY" --dir public \
-            --pattern houseplan-card.js --pattern houseplan.zip \
-            --pattern RELEASE-MEMBERSHIP.json --pattern SHA256SUMS --clobber
-          diff -u release-assets/SHA256SUMS public/SHA256SUMS
-          node scripts/release-assets.mjs check public release-assets/SHA256SUMS
-          node scripts/release-membership.mjs verify --tag="$TAG" --candidate="$SHA" \
-            --input=public/RELEASE-MEMBERSHIP.json
           test "$(git rev-list -n 1 "$TAG")" = "$SHA"
           URL=$(node -p "JSON.parse(process.env.RELEASE_JSON).url")
           echo "url=$URL" >> "$GITHUB_OUTPUT"
-          printf '### Published %s\n\n- exact SHA: `%s`\n- [GitHub prerelease](%s)\n\n```\n%s```\n' \
-            "$TAG" "$SHA" "$URL" "$(cat public/SHA256SUMS)" >> "$GITHUB_STEP_SUMMARY"
+          printf '### Published %s\n\n- exact SHA: `%s`\n- [GitHub prerelease](%s)\n- assets: `houseplan-card.js`, `houseplan.zip`\n' \
+            "$TAG" "$SHA" "$URL" >> "$GITHUB_STEP_SUMMARY"
       - name: Verify HACS prerelease discovery order
-        uses: actions/github-script@3a2844b7e9c422d3c10d287c895573f7108da1b3 # v9
+        uses: actions/github-script@v9
         env:
           EXPECTED_TAG: ${{ needs.gate.outputs.tag }}
         with:
@@ -287,32 +191,25 @@ jobs:
               );
             }
 
-  # #547: bookkeeping is driven by the immutable candidate manifest, not by the
-  # mutable S8 queue. It also runs on a verified retry of an already-public beta.
+  # PROCESS.md 10.2 item 10: closing issues and stripping status labels happens
+  # because a beta was published, not because someone remembered to do it. The
+  # manual step was skipped twice, and both times it broke the invariant that a
+  # closed issue carries no status label — the one thing `verify` relies on.
+  #
+  # A manual step after a successful release is the worst kind: by the time it is
+  # due, the work already looks finished, which is exactly why it gets forgotten.
   close-merged:
-    name: Закрытие вошедших issue
     needs: [gate, publish]
-    runs-on: ubuntu-24.04
-    timeout-minutes: 15
+    if: ${{ needs.publish.outputs.newly_published == 'true' }}
+    runs-on: ubuntu-latest
     permissions:
       contents: read
-      actions: read
       # Deliberately the stock token, not a PAT: events caused by GITHUB_TOKEN do
       # not start workflows, so removing the label cannot wake the review
       # pipeline. A PAT here would build a cascade out of a bookkeeping step.
       issues: write
     steps:
-      - uses: actions/checkout@3d3c42e5aac5ba805825da76410c181273ba90b1 # v7
-        with:
-          ref: ${{ needs.gate.outputs.sha }}
-          fetch-depth: 0
-      - uses: actions/setup-node@820762786026740c76f36085b0efc47a31fe5020 # v7
-        with: { node-version: 22 }
-      - uses: actions/download-artifact@37930b1c2abaa49bbe596cd826c3c89aef350131 # v7
-        with:
-          name: release-membership
-          path: release-membership
-      - name: Finish only the issues proven in the candidate manifest
+      - name: Close the S8-merged queue and strip status labels
         env:
           GH_TOKEN: ${{ github.token }}
           REPO: ${{ github.repository }}
@@ -320,12 +217,35 @@ jobs:
           URL: ${{ needs.publish.outputs.url }}
         run: |
           set -euo pipefail
-          node scripts/release-bookkeeping.mjs --repo="$REPO" --tag="$TAG" \
-            --candidate="${{ needs.gate.outputs.sha }}" --url="$URL" \
-            --membership=release-membership/RELEASE-MEMBERSHIP.json
+          # Only the owner's issues take part in the process; issues filed by
+          # anyone else never carry status labels and are not ours to close.
+          numbers=$(gh issue list --repo "$REPO" --state open --label S8-merged \
+            --author Matysh --limit 100 --json number --jq '.[].number')
+          if [ -z "$numbers" ]; then
+            echo "the S8-merged queue is empty, nothing to close"
+          else
+            for n in $numbers; do
+              gh issue comment "$n" --repo "$REPO" \
+                --body "Выпущено в \`$TAG\` · [релиз]($URL)"
+              # Label first, then close. If the run dies between the two steps an
+              # open issue without a status is visible and fixable in the flow;
+              # the reverse order would recreate the exact breakage this job is
+              # here to prevent.
+              gh issue edit "$n" --repo "$REPO" --remove-label S8-merged
+              gh issue close "$n" --repo "$REPO" --reason completed
+              echo "closed #$n"
+            done
+          fi
+          # Targeted at the defect that actually recurs, not at the invariant in
+          # general: no closed issue may still carry S8-merged.
+          leftover=$(gh issue list --repo "$REPO" --state closed --label S8-merged \
+            --limit 100 --json number --jq 'length')
+          test "$leftover" = "0" || {
+            echo "::error::$leftover closed issues still carry S8-merged"
+            exit 1
+          }
 
   announce:
-    name: Комментарий о публикации
     needs: [gate, publish]
     if: ${{ needs.publish.outputs.newly_published == 'true' }}
     uses: ./.github/workflows/announce.yml

.github/workflows/release-review.yml

@@ -1,335 +0,0 @@
-name: "Релиз: независимое ревью линии"
-run-name: "Release review ${{ inputs.tag }}"
-
-# #638, PROCESS.md §11.5: перед стабильным релизом — одно независимое ревью
-# поверхностей, изменённых всей линией бет, «с нуля»: без ТЗ и документов
-# раундов, по SCOPE и USER-GUIDE. Инкрементальное ревью судит дифф задачи
-# против её ТЗ; четыре дефекта линии 1.77 (#607, #608, #611, #619) не входили
-# ни в один AC и нашлись только так.
-#
-# Решение владельца 2026-09-25: ревью НЕ блокирует выпуск. `release.yml`
-# запускает этот workflow параллельно гейтам из job, от которого не зависит ни
-# один job выпуска; документ — рекомендация, в работу его берёт владелец.
-#
-# Только `workflow_dispatch`: GitHub исполняет файл с той ветки, на которой
-# запущен прогон (`release.yml` зовёт `--ref dev`), поэтому зеркало в `main`
-# не нужно, а правка — один коммит в `dev`.
-#
-# Три job, как у конвейера (#551, #556): детерминированная подготовка,
-# недоверенная модель без единого права на запись, детерминированная
-# публикация документа в `dev`.
-on:
-  workflow_dispatch:
-    inputs:
-      tag:
-        description: "Stable release tag, for example v1.78.0"
-        required: true
-        type: string
-      candidate:
-        description: "Exact candidate SHA; empty = the commit of the tag"
-        required: false
-        type: string
-        default: ""
-      force:
-        description: "Review again even when the document already exists in dev"
-        required: false
-        type: boolean
-        default: false
-
-permissions:
-  contents: read
-
-concurrency:
-  group: release-review-${{ inputs.tag }}
-  cancel-in-progress: false
-
-jobs:
-  prepare:
-    name: "Ревью релиза: вход линии"
-    runs-on: ubuntu-24.04
-    timeout-minutes: 10
-    permissions:
-      contents: read
-    outputs:
-      proceed: ${{ steps.line.outputs.proceed }}
-      candidate: ${{ steps.line.outputs.candidate }}
-      base: ${{ steps.line.outputs.base }}
-      doc: ${{ steps.line.outputs.doc }}
-      issues: ${{ steps.line.outputs.issues }}
-    steps:
-      - uses: actions/checkout@3d3c42e5aac5ba805825da76410c181273ba90b1 # v7
-        with:
-          fetch-depth: 0
-          ref: dev
-          persist-credentials: false
-
-      - uses: actions/setup-node@820762786026740c76f36085b0efc47a31fe5020 # v7
-        with:
-          node-version: 22
-
-      - name: Кандидат, база и issue линии
-        id: line
-        env:
-          TAG: ${{ inputs.tag }}
-          CANDIDATE: ${{ inputs.candidate }}
-          FORCE: ${{ inputs.force }}
-          RUN_URL: ${{ github.server_url }}/${{ github.repository }}/actions/runs/${{ github.run_id }}
-        run: |
-          doc=$(node scripts/release-review.mjs doc --tag="$TAG")
-          git fetch -q --tags origin
-          if [ -z "$CANDIDATE" ]; then
-            CANDIDATE=$(git rev-parse --verify -q "refs/tags/$TAG^{commit}") || {
-              echo "::error::тега $TAG нет, а кандидат не передан"; exit 1; }
-          fi
-          git cat-file -e "$CANDIDATE^{commit}"
-          CANDIDATE=$(git rev-parse "$CANDIDATE^{commit}")
-          # Повтор на тот же тег не тратит модель: документ уже есть (§11.5).
-          if [ "$FORCE" != "true" ] && git cat-file -e "origin/dev:$doc" 2>/dev/null; then
-            echo "::notice::$doc уже есть в dev — повторное ревью не запускается (force=true, чтобы переснять)"
-            echo "proceed=false" >> "$GITHUB_OUTPUT"
-            exit 0
-          fi
-          out="$RUNNER_TEMP/release-review-input"
-          node scripts/release-review.mjs prepare --tag="$TAG" --candidate="$CANDIDATE" \
-            --out="$out" --run-url="$RUN_URL" | tee -a "$GITHUB_OUTPUT"
-          echo "candidate=$CANDIDATE" >> "$GITHUB_OUTPUT"
-          echo "proceed=true" >> "$GITHUB_OUTPUT"
-          (cd "$out" && sha256sum brief.md line-membership.json > manifest.sha256)
-          cat "$out/brief.md" >> "$GITHUB_STEP_SUMMARY"
-
-      - name: Передать вход модели
-        if: steps.line.outputs.proceed == 'true'
-        uses: actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02 # v4
-        with:
-          name: release-review-input-${{ github.run_id }}-${{ github.run_attempt }}
-          path: ${{ runner.temp }}/release-review-input
-          if-no-files-found: error
-          retention-days: 3
-
-  model_review:
-    name: "Ревью релиза: работа модели"
-    needs: prepare
-    if: needs.prepare.outputs.proceed == 'true'
-    runs-on: ubuntu-24.04
-    timeout-minutes: 60
-    # Недоверенная стадия. Прав на запись нет никаких: ни в репозиторий, ни в
-    # issue. Документ публикует `publish`; находки в issue превращает владелец.
-    # `github_token` у шага Review обязателен (#556): без него action меняет
-    # OIDC на собственный App-токен с правом записи.
-    permissions:
-      contents: read
-    steps:
-      - uses: actions/checkout@3d3c42e5aac5ba805825da76410c181273ba90b1 # v7
-        with:
-          fetch-depth: 0
-          ref: ${{ needs.prepare.outputs.candidate }}
-          persist-credentials: false
-
-      - uses: actions/setup-node@820762786026740c76f36085b0efc47a31fe5020 # v7
-        with:
-          node-version: 22
-          cache: npm
-
-      - name: Получить вход линии
-        uses: actions/download-artifact@d3f86a106a0bac45b974a628896c90dbdf5c8093 # v4
-        with:
-          name: release-review-input-${{ github.run_id }}-${{ github.run_attempt }}
-          path: ${{ runner.temp }}/release-review-input
-
-      - name: Проверить вход и кандидата
-        env:
-          CANDIDATE: ${{ needs.prepare.outputs.candidate }}
-        run: |
-          (cd "$RUNNER_TEMP/release-review-input" && sha256sum -c manifest.sha256)
-          test "$(git rev-parse HEAD)" = "$CANDIDATE"
-
-      - name: Установить зависимости
-        run: npm ci
-
-      - name: Кэш браузеров Playwright
-        id: pw
-        uses: actions/cache@55cc8345863c7cc4c66a329aec7e433d2d1c52a9 # v6
-        with:
-          path: ~/.cache/ms-playwright
-          key: playwright-${{ runner.os }}-${{ hashFiles('package-lock.json') }}
-
-      - name: Установить Chromium
-        if: steps.pw.outputs.cache-hit != 'true'
-        run: npx playwright install chromium
-
-      # Тот же обход, что у конвейера (_process.yml, anthropics issue 1817).
-      - name: Установить Claude Code детерминированно
-        id: claude_bin
-        run: |
-          src=$(ls "$RUNNER_WORKSPACE"/../_actions/anthropics/claude-code-*/v1/src/entrypoints/run.ts 2>/dev/null | head -1)
-          ver=$(grep -oE 'claudeCodeVersion = "[0-9]+\.[0-9]+\.[0-9]+"' "$src" 2>/dev/null | grep -oE '[0-9]+\.[0-9]+\.[0-9]+' || true)
-          ver="${ver:-2.1.265}"
-          base=https://downloads.claude.ai/claude-code-releases
-          bin="$HOME/.local/bin/claude"
-          mkdir -p "$(dirname "$bin")"
-          curl -fsSL --retry 3 "$base/$ver/linux-x64/claude" -o "$bin"
-          sum=$(curl -fsSL --retry 3 "$base/$ver/manifest.json" | jq -r '.platforms["linux-x64"].checksum')
-          echo "$sum  $bin" | sha256sum -c -
-          chmod +x "$bin"
-          "$bin" --version
-          echo "path=$bin" >> "$GITHUB_OUTPUT"
-
-      - name: Review
-        id: review
-        uses: anthropics/claude-code-action@9cdae7f0d995e3ba7c33f226087fdf82a59cd520 # v1
-        env:
-          REVIEW_DOC: ${{ runner.temp }}/release-review.md
-          REVIEW_INPUT: ${{ runner.temp }}/release-review-input
-        with:
-          claude_code_oauth_token: ${{ secrets.CLAUDE_CODE_OAUTH_TOKEN }}
-          github_token: ${{ secrets.GITHUB_TOKEN }}
-          path_to_claude_code_executable: ${{ steps.claude_bin.outputs.path }}
-          prompt: |
-            Ты независимый ревьюер релиза House Plan. Язык ответа — русский.
-
-            Релиз: ${{ inputs.tag }} · кандидат ${{ needs.prepare.outputs.candidate }}
-            (рабочая копия уже на нём) · база линии: ${{ needs.prepare.outputs.base || 'нет' }}.
-            Вход линии — файл $REVIEW_INPUT/brief.md (issue линии, доказанные
-            трейлерами, и изменённые продуктовые файлы) и
-            $REVIEW_INPUT/line-membership.json.
-
-            Правила этого ревью — docs/process/REVIEWER.md, раздел «Независимое
-            ревью линии», канон — PROCESS.md §11.5. Прочитай их первыми.
-
-            Главное, что нельзя пропустить:
-            - Ты судишь ПОВЕРХНОСТИ, изменённые линией, против ПОЛЬЗОВАТЕЛЯ, а
-              не дифф против ТЗ. Не читай ТЗ задач (раздел «## ТЗ» в issue,
-              docs/specs/**) и документы раундов (docs/reviews/**): независимость
-              и есть смысл шага. Основа суждения — docs/SCOPE.md (персоны и
-              работы) и docs/USER-GUIDE.ru.md (что обещано пользователю).
-            - Проверяй исполнением, а не чтением: собери бандл
-              (`npm run bundle:sync`), открой затронутые поверхности в браузере
-              (стенд `demo/`, смоки `demo/smoke_*.mjs`), вводи текст
-              посимвольно, закрывай диалоги настоящим Escape и крестиком. Где
-              есть диалоги HA — пиннутая фикстура `ha-dialog` (#505,
-              demo/helpers/README-ha-dialog.md,
-              `node demo/verify_ha_dialog_discard_recovery.mjs`).
-            - Для каждой поверхности: обычный сценарий и самый рискованный
-              соседний, шесть классов риска (async, данные/права, геометрия,
-              визуал, объём/perf, host/input) — PROCESS.md §2.6.
-            - Ты ничего не правишь и не публикуешь: ни код, ни issue, ни
-              комментарии. Права на запись у тебя нет. Любые изменения рабочей
-              копии будут отброшены — после проверок восстанови её сам
-              (`git checkout -- . && git clean -fd`), если что-то менял.
-
-            Находки: High / Medium / Low, у каждой — поверхность, воспроизведение
-            (команда или шаги), что увидит пользователь, какая персона задета.
-            Выпуск это ревью не останавливает: документ — рекомендация владельцу.
-
-            Напиши полный документ в файл по пути из переменной REVIEW_DOC
-            (абсолютный, вне репозитория). Разделы: что входило в линию,
-            поверхности и как каждая проверялась (команда → результат),
-            находки, что проверено и корректно, чего не проверял и почему.
-            Первой строкой после заголовка — `Итог: High N · Medium N · Low N`.
-
-            Затем верни JSON по схеме — последнее обязательное действие.
-          claude_args: |
-            --max-turns 200
-            --allowedTools Read,Write,Grep,Glob,Bash
-            --json-schema '{"type":"object","properties":{"high":{"type":"integer"},"medium":{"type":"integer"},"low":{"type":"integer"},"summary":{"type":"string"}},"required":["high","medium","low","summary"]}'
-
-      - name: Запечатать результат модели
-        env:
-          SOURCE: ${{ runner.temp }}/release-review.md
-          OUT: ${{ steps.review.outputs.structured_output }}
-        run: |
-          test -s "$SOURCE" || { echo "::error::модель не оставила документ ревью"; exit 1; }
-          dir="$RUNNER_TEMP/release-review-result"
-          mkdir -p "$dir"
-          printf '%s' "$OUT" > "$dir/result.json"
-          jq -e '(.high|type=="number") and (.medium|type=="number") and (.low|type=="number") and (.summary|type=="string")' \
-            "$dir/result.json" >/dev/null
-          cp "$SOURCE" "$dir/release-review.md"
-          (cd "$dir" && sha256sum release-review.md result.json > manifest.sha256)
-
-      - name: Передать результат публикации
-        uses: actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02 # v4
-        with:
-          name: release-review-result-${{ github.run_id }}-${{ github.run_attempt }}
-          path: ${{ runner.temp }}/release-review-result
-          if-no-files-found: error
-          retention-days: 3
-
-  publish:
-    name: "Ревью релиза: документ в dev"
-    needs: [prepare, model_review]
-    runs-on: ubuntu-24.04
-    timeout-minutes: 10
-    permissions:
-      contents: read
-    steps:
-      - uses: actions/checkout@3d3c42e5aac5ba805825da76410c181273ba90b1 # v7
-        with:
-          fetch-depth: 0
-          ref: dev
-          persist-credentials: false
-
-      - uses: actions/setup-node@820762786026740c76f36085b0efc47a31fe5020 # v7
-        with:
-          node-version: 22
-
-      - name: Получить результат модели
-        uses: actions/download-artifact@d3f86a106a0bac45b974a628896c90dbdf5c8093 # v4
-        with:
-          name: release-review-result-${{ github.run_id }}-${{ github.run_attempt }}
-          path: ${{ runner.temp }}/release-review-result
-
-      # Модель пишет только текст документа. Путь, машинный блок, индекс и
-      # коммит решает этот шаг; всё остальное в рабочей копии не существует.
-      - name: Опубликовать документ
-        env:
-          TOKEN: ${{ secrets.HP_PROCESS_TOKEN }}
-          TAG: ${{ inputs.tag }}
-          DOC: ${{ needs.prepare.outputs.doc }}
-          CANDIDATE: ${{ needs.prepare.outputs.candidate }}
-          BASE: ${{ needs.prepare.outputs.base }}
-          ISSUES: ${{ needs.prepare.outputs.issues }}
-          RUN_URL: ${{ github.server_url }}/${{ github.repository }}/actions/runs/${{ github.run_id }}
-        run: |
-          dir="$RUNNER_TEMP/release-review-result"
-          (cd "$dir" && sha256sum -c manifest.sha256)
-          test "$DOC" = "$(node scripts/release-review.mjs doc --tag="$TAG")"
-          counts=$(jq -r '"High \(.high) · Medium \(.medium) · Low \(.low)"' "$dir/result.json")
-          for attempt in 1 2 3; do
-            git fetch -q origin dev
-            git reset -q --hard origin/dev
-            git clean -fdq
-            mkdir -p docs/reviews
-            {
-              cat "$dir/release-review.md"
-              printf '\n\n<!-- hp-release-review-anchors -->\n### Материал ревью\n\n```\n'
-              printf 'tag %s\ncandidate %s\nbase %s\nissues %s\nrun %s\n' \
-                "$TAG" "$CANDIDATE" "${BASE:-—}" "${ISSUES:-—}" "$RUN_URL"
-              printf '```\n'
-            } > "$DOC"
-            node scripts/reviews-index.mjs --dir=docs/reviews --strict
-            git add -- "$DOC" docs/reviews/INDEX.md
-            git diff --cached --name-only | node scripts/review-doc-guard.mjs
-            git -c user.name="claude[bot]" \
-                -c user.email="209825114+claude[bot]@users.noreply.github.com" \
-                commit -q -F - <<MSG
-          docs: release review for $TAG
-
-          Независимое ревью линии перед стабильным релизом (PROCESS.md §11.5).
-          Итог: $counts. Выпуск не блокирует; решение по находкам — за владельцем.
-
-          Issue: #638
-          User-Visible: no
-          MSG
-            git diff --name-only "origin/dev...HEAD" | node scripts/review-doc-guard.mjs
-            if git push -q "https://x-access-token:$TOKEN@github.com/${{ github.repository }}" HEAD:dev; then
-              echo "### Независимое ревью $TAG" >> "$GITHUB_STEP_SUMMARY"
-              echo "Итог: $counts — \`$DOC\` в dev. Выпуск не блокируется." >> "$GITHUB_STEP_SUMMARY"
-              echo "::notice::$DOC опубликован: $counts"
-              exit 0
-            fi
-            echo "::warning::dev ушёл вперёд — попытка $attempt из 3, документ собирается заново"
-            sleep $((attempt * 10))
-          done
-          echo "::error::документ ревью не опубликован в dev за три попытки"
-          exit 1

.github/workflows/release-zip.yml

@@ -0,0 +1,40 @@
+name: Attach HACS zip to release
+# hacs.json declares zip_release + filename=houseplan.zip, so every release
+# (prereleases included) must carry the asset — HACS installs from it and
+# GitHub's public download counter becomes a free per-version install metric
+# (owner request, 2026-08-08). Like announce.yml, the workflow file lives at
+# the TAGGED commit: betas cut from dev pick it up as soon as this file is on
+# dev, stable tags once it reaches main.
+# workflow_dispatch lets us attach the zip to an EXISTING release (needed
+# once for the latest stable after the hacs.json change reaches main).
+on:
+  release:
+    types: [published]
+  workflow_dispatch:
+    inputs:
+      tag:
+        description: "Existing release tag to attach the zip to"
+        required: true
+permissions:
+  contents: write
+jobs:
+  zip:
+    runs-on: ubuntu-latest
+    steps:
+      - name: Resolve tag
+        id: tag
+        env:
+          EVENT_TAG: ${{ github.event.release.tag_name }}
+          INPUT_TAG: ${{ github.event.inputs.tag }}
+        run: echo "tag=${EVENT_TAG:-$INPUT_TAG}" >> "$GITHUB_OUTPUT"
+      - uses: actions/checkout@v7
+        with:
+          ref: ${{ steps.tag.outputs.tag }}
+      - name: Build houseplan.zip (contents of custom_components/houseplan at zip root)
+        run: cd custom_components/houseplan && zip -qr ../../houseplan.zip .
+      - name: Sanity check
+        run: unzip -l houseplan.zip | grep -q "manifest.json"
+      - name: Upload asset
+        env:
+          GH_TOKEN: ${{ secrets.GITHUB_TOKEN }}
+        run: gh release upload "${{ steps.tag.outputs.tag }}" houseplan.zip --clobber --repo "$GITHUB_REPOSITORY"

.github/workflows/release.yml

@@ -1,492 +1,86 @@
-name: "Релиз: проверка, сборка и публикация ассетов"
-run-name: "Release ${{ inputs.tag || github.event.release.tag_name }}"
-
-# #540: единственный путь, по которому установочные ассеты стабильного релиза
-# (`houseplan.zip` для HACS и `houseplan-card.js` для ручной установки) попадают
-# наружу. До этого публикаторов было четыре, и `release-zip.yml` выкладывал ZIP
-# в ту же секунду, когда релиз становился публичным, — до Validate, Full
-# Performance и E2E. Порядок теперь один: закрепить SHA → релиз в черновике →
-# гейты на этом SHA → одна сборка и `SHA256SUMS` → загрузка в черновик →
-# публикация → сверка публичных байтов с паспортом → анонс.
-#
-# Два входа, один порядок:
-#   • `workflow_dispatch(tag)` — штатный выпуск и ремонт. Тега ещё нет — он
-#     ставится на вершину ветки, с которой запущен workflow (main для
-#     стабильного, dev для беты). Тег есть — берётся его коммит.
-#   • `release: published` — человек опубликовал стабильный релиз руками.
-#     Fail-closed: релиз немедленно возвращается в черновик и проходит тот же
-#     путь; снаружи ничего установочного не остаётся, пока идут проверки.
-#     Беты это событие пропускают — у них свой staged-путь
-#     (`publish-prerelease.yml`, `release-prerelease.mjs`).
-#
-# Ремонт публичного релиза (dispatch на существующий тег): недостающие ассеты
-# догружаются только при зелёных гейтах; присутствующий ассет с другим хешем —
-# отказ без правок, публичные байты не подменяются молча.
-#
-# Событие `release` исполняет workflow с коммита тега: новая редакция файла
-# действует для стабильных тегов только после того, как она есть на main.
+name: Release
 on:
   release:
     types: [published]
-  workflow_dispatch:
-    inputs:
-      tag:
-        description: "Exact release tag, for example v1.75.1; created on the dispatched branch tip when missing"
-        required: true
-        type: string
-
 permissions:
   contents: write
   actions: read
-
-concurrency:
-  group: release-${{ inputs.tag || github.event.release.tag_name }}
-  cancel-in-progress: false
-
 jobs:
-  candidate:
-    name: "Кандидат: точный SHA, режим и черновик"
-    # Публикация беты руками — не наш случай: у бет свой staged-путь.
-    if: ${{ github.event_name == 'workflow_dispatch' || !github.event.release.prerelease }}
-    runs-on: ubuntu-24.04
-    timeout-minutes: 10
-    outputs:
-      sha: ${{ steps.resolve.outputs.sha }}
-      tag: ${{ steps.resolve.outputs.tag }}
-      version: ${{ steps.resolve.outputs.version }}
-      prerelease: ${{ steps.resolve.outputs.prerelease }}
-      mode: ${{ steps.release.outputs.mode }}
-    steps:
-      - uses: actions/checkout@3d3c42e5aac5ba805825da76410c181273ba90b1 # v7
-        with:
-          fetch-depth: 0
-      - name: Resolve the tag to its exact commit
-        id: resolve
-        env:
-          EVENT: ${{ github.event_name }}
-          TAG: ${{ inputs.tag || github.event.release.tag_name }}
-        run: |
-          set -euo pipefail
-          [[ "$TAG" =~ ^v[0-9]+\.[0-9]+\.[0-9]+(-[0-9A-Za-z.]+)?$ ]] || {
-            echo "::error::$TAG is not a release tag (vX.Y.Z or vX.Y.Z-pre)"
-            exit 1
-          }
-          VERSION=${TAG#v}
-          case "$TAG" in *-*) PRERELEASE=true ;; *) PRERELEASE=false ;; esac
-          if git ls-remote --exit-code --tags origin "refs/tags/$TAG" >/dev/null; then
-            git fetch --force origin "refs/tags/$TAG:refs/tags/$TAG"
-            # Peeled commit both for annotated and lightweight tags (a release
-            # form makes lightweight ones). Neither target_commitish nor the
-            # event SHA is trusted: the former may be a branch name.
-            SHA=$(git rev-list -n 1 "refs/tags/$TAG")
-            echo "tag $TAG exists → $SHA"
-          else
-            test "$EVENT" = "workflow_dispatch" || {
-              echo "::error::release event for a tag that does not exist: $TAG"
-              exit 1
-            }
-            SHA=$(git rev-parse HEAD)
-            echo "tag $TAG is new → dispatched branch tip $SHA"
-          fi
-          if [ "$PRERELEASE" = "false" ]; then
-            git fetch origin main
-            git merge-base --is-ancestor "$SHA" origin/main || {
-              echo "::error::stable candidate $SHA is not on main"
-              exit 1
-            }
-          else
-            git fetch origin dev
-            git merge-base --is-ancestor "$SHA" origin/dev || {
-              echo "::error::prerelease candidate $SHA is not on dev"
-              exit 1
-            }
-          fi
-          {
-            echo "sha=$SHA"
-            echo "tag=$TAG"
-            echo "version=$VERSION"
-            echo "prerelease=$PRERELEASE"
-          } >> "$GITHUB_OUTPUT"
-      - name: Take the release off the public surface until it is verified
-        id: release
-        env:
-          GH_TOKEN: ${{ github.token }}
-          EVENT: ${{ github.event_name }}
-          TAG: ${{ steps.resolve.outputs.tag }}
-        run: |
-          set -euo pipefail
-          if ! gh release view "$TAG" --repo "$GITHUB_REPOSITORY" --json isDraft --jq .isDraft > /tmp/is-draft 2>/dev/null; then
-            echo "mode=fresh" >> "$GITHUB_OUTPUT"
-            echo "no release for $TAG yet: it will be created as a draft after the gates"
-          elif [ "$(cat /tmp/is-draft)" = "true" ]; then
-            echo "mode=staged" >> "$GITHUB_OUTPUT"
-            echo "release $TAG is a draft: staging into it"
-          elif [ "$EVENT" = "release" ]; then
-            # Published by hand: nothing here has been verified. Back to draft
-            # first, gates second — the order is the whole point (#540).
-            gh release edit "$TAG" --repo "$GITHUB_REPOSITORY" --draft
-            echo "mode=event" >> "$GITHUB_OUTPUT"
-            echo "::notice::$TAG was published by hand and is a draft again until the gates pass"
-          else
-            echo "mode=repair" >> "$GITHUB_OUTPUT"
-            echo "release $TAG is public: repair mode — only missing assets may be added"
-          fi
-
-  independent-review:
-    name: "Независимое ревью линии (не блокирует выпуск)"
-    # #638, PROCESS.md §11.5. Решение владельца 2026-09-25: ревью идёт
-    # параллельно гейтам и выпуск не ждёт и не останавливает. Поэтому этот job
-    # только ставит в очередь `release-review.yml` на `dev` и ни один job
-    # выпуска от него не зависит (`needs` на него запрещён тестом
-    # release-workflow); его отказ — предупреждение, а не красный релиз.
-    # Беты пропускаются: ревью линии — перед стабильным.
-    needs: candidate
-    if: ${{ needs.candidate.outputs.prerelease != 'true' }}
-    continue-on-error: true
-    runs-on: ubuntu-24.04
-    timeout-minutes: 5
-    permissions:
-      actions: write
-    steps:
-      - name: Поставить в очередь ревью линии
-        env:
-          GH_TOKEN: ${{ github.token }}
-          TAG: ${{ needs.candidate.outputs.tag }}
-          SHA: ${{ needs.candidate.outputs.sha }}
-        run: |
-          if gh workflow run release-review.yml --repo "${{ github.repository }}" --ref dev \
-               -f tag="$TAG" -f candidate="$SHA"; then
-            echo "Независимое ревью $TAG поставлено в очередь: release-review.yml на dev" >> "$GITHUB_STEP_SUMMARY"
-          else
-            echo "::warning::ревью линии $TAG не запущено — выпуск продолжается; запустить руками: gh workflow run release-review.yml --ref dev -f tag=$TAG -f candidate=$SHA"
-            exit 1
-          fi
-
+  # AUD-159B7-02: publishing a GitHub Release used to BE the gate — this
+  # workflow only built and uploaded, so an asset shipped while both Validate
+  # runs for the very same commit were red. The asset now waits for a green
+  # Validate of the EXACT commit the tag points at, and is withheld otherwise.
+  #
+  # Needs a push with a token that has the `workflow` scope (the ordinary
+  # Personal Access Token used for `git push` refuses workflow file updates).
   gate:
-    name: "Гейт: контракт, Validate, Full Performance и E2E на точном SHA"
-    needs: candidate
-    runs-on: ubuntu-24.04
-    # Больше суммы собственных ожиданий job: Validate и Full Performance ждутся
-    # до 60 мин каждый (release-gate.mjs), E2E — до 45 (e2e-gate.mjs): 165 < 180 (#658).
-    timeout-minutes: 180
+    runs-on: ubuntu-latest
     steps:
-      - uses: actions/checkout@3d3c42e5aac5ba805825da76410c181273ba90b1 # v7
+      - uses: actions/checkout@v7
         with:
-          ref: ${{ needs.candidate.outputs.sha }}
+          ref: ${{ github.event.release.tag_name }}
           fetch-depth: 0
-      - uses: actions/setup-node@820762786026740c76f36085b0efc47a31fe5020 # v7
+      - uses: actions/setup-node@v7
         with: { node-version: 22 }
-      # #479: тяжёлые job Validate идут только на коммите с трейлером `Release:`;
-      # без него зелёный Validate — прогон без смоков и golden. Трейлер обязан
-      # называть ровно этот тег: кандидат сам объявляет, чем он выпускается.
-      - name: Require the Release trailer naming this exact tag
-        env:
-          SHA: ${{ needs.candidate.outputs.sha }}
-          TAG: ${{ needs.candidate.outputs.tag }}
-        run: |
-          set -euo pipefail
-          git log -1 --format=%B "$SHA" > /tmp/head-message.txt
-          if ! grep -Eq '^Release:[[:space:]]*v?[0-9]+\.[0-9]+\.[0-9]+' /tmp/head-message.txt; then
-            echo "::error::$SHA has no Release: trailer — Validate ran without the heavy gates (#479)"
-            exit 1
-          fi
-          if ! grep -Fxq "Release: $TAG" /tmp/head-message.txt; then
-            echo "::error::$SHA declares $(grep -E '^Release:' /tmp/head-message.txt | head -1), not $TAG"
-            exit 1
-          fi
-      - name: Verify version, changelogs and bilingual release notes
-        env:
-          TAG: ${{ needs.candidate.outputs.tag }}
-          PRERELEASE: ${{ needs.candidate.outputs.prerelease }}
-        run: |
-          set -euo pipefail
-          if [ "$PRERELEASE" = "true" ]; then
-            node scripts/release-contract.mjs "$TAG" --repo="$GITHUB_REPOSITORY"
-          else
-            node scripts/release-contract.mjs "$TAG" --repo="$GITHUB_REPOSITORY" --stable
-          fi
       - name: Require a green Validate for this exact commit
         env:
           GH_TOKEN: ${{ github.token }}
           REPO: ${{ github.repository }}
-          SHA: ${{ needs.candidate.outputs.sha }}
-        run: node scripts/release-gate.mjs "$SHA"
+          TAG: ${{ github.event.release.tag_name }}
+        run: |
+          set -euo pipefail
+          # HEAD is the peeled commit even when TAG is annotated. Do not trust
+          # target_commitish (it may be a branch name) or an event-context SHA.
+          SHA=$(git rev-parse HEAD)
+          echo "release tag: $TAG; exact commit: $SHA"
+          node scripts/release-gate.mjs "$SHA"
       - name: Require full performance for a stable release
-        if: ${{ needs.candidate.outputs.prerelease != 'true' }}
+        if: ${{ !github.event.release.prerelease }}
         env:
           GH_TOKEN: ${{ github.token }}
           REPO: ${{ github.repository }}
-          SHA: ${{ needs.candidate.outputs.sha }}
-        run: node scripts/release-gate.mjs "$SHA" --workflow=performance.yml --label="Полные бенчмарки производительности"
-      # #514/#540: единственная проверка на настоящем Home Assistant. Раньше
-      # houseplan-e2e ставил `houseplan.zip` из публичного релиза — то есть
-      # релиз должен был быть публичным ДО проверки. Теперь он ставит дерево
-      # `custom_components/houseplan` коммита-кандидата (tarball codeload),
-      # а ZIP строится `git archive` из того же дерева: тождество «что
-      # тестировали = что публикуем» — хеш дерева, он печатается на сборке.
-      # Cross-repository dispatch needs a token with Actions: write on
-      # houseplan-e2e; HP_PROCESS_TOKEN (classic, repo scope) has it,
-      # E2E_DISPATCH_TOKEN is the fallback for a fine-grained token.
-      - name: Require green E2E on a real Home Assistant for a stable release
-        if: ${{ needs.candidate.outputs.prerelease != 'true' }}
-        env:
-          GH_TOKEN: ${{ secrets.E2E_DISPATCH_TOKEN || secrets.HP_PROCESS_TOKEN }}
-          SHA: ${{ needs.candidate.outputs.sha }}
-          TAG: ${{ needs.candidate.outputs.tag }}
-        run: node scripts/e2e-gate.mjs --ref="$SHA" --tag="$TAG"
-
-  stage:
-    name: "Сборка: ассеты, SHA256SUMS и загрузка в черновик"
-    needs: [candidate, gate]
-    runs-on: ubuntu-24.04
-    timeout-minutes: 30
-    steps:
-      - uses: actions/checkout@3d3c42e5aac5ba805825da76410c181273ba90b1 # v7
-        with:
-          ref: ${{ needs.candidate.outputs.sha }}
-          fetch-depth: 0
-      - uses: actions/setup-node@820762786026740c76f36085b0efc47a31fe5020 # v7
-        with: { node-version: 22 }
-      - name: Build once and verify both installable assets
-        id: build
-        env:
-          SHA: ${{ needs.candidate.outputs.sha }}
-          VERSION: ${{ needs.candidate.outputs.version }}
         run: |
           set -euo pipefail
-          npm ci
-          npm run build
-          node scripts/bundle-tree.mjs dist custom_components/houseplan/frontend
-          npm run bundle:budget
-          grep -RFq "$VERSION" dist
-          test -s dist/houseplan-card.js
-          test -s dist/houseplan-panel.js
-          # The ZIP is the committed integration tree of the exact commit —
-          # the same tree E2E installed from the codeload tarball. `git archive`
-          # is deterministic for a commit, so a repair rebuilds identical bytes.
-          git -c core.autocrlf=false archive --format=zip --output=houseplan.zip \
-            "$SHA:custom_components/houseplan"
-          node scripts/verify-houseplan-zip.mjs houseplan.zip \
-            custom_components/houseplan/frontend "$VERSION"
-          mkdir -p release-assets
-          cp dist/houseplan-card.js houseplan.zip release-assets/
-          node scripts/release-assets.mjs sums release-assets
-          TREE=$(git rev-parse "$SHA:custom_components/houseplan")
-          echo "tree=$TREE" >> "$GITHUB_OUTPUT"
-          printf '### Staged assets for %s\n\n- exact commit: `%s`\n- `custom_components/houseplan` tree (what E2E installed): `%s`\n\n```\n%s```\n' \
-            "$VERSION" "$SHA" "$TREE" "$(cat release-assets/SHA256SUMS)" >> "$GITHUB_STEP_SUMMARY"
+          SHA=$(git rev-parse HEAD)
+          node scripts/release-gate.mjs "$SHA" --workflow=performance.yml --label="Full Performance"
+  build:
+    needs: gate
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v7
+        with:
+          ref: ${{ github.event.release.tag_name }}
+      - uses: actions/setup-node@v7
+        with: { node-version: 22 }
+      - run: npm ci && npm run build
       - name: Verify compositor frame continuity for a stable release
-        if: ${{ needs.candidate.outputs.prerelease != 'true' }}
+        if: ${{ !github.event.release.prerelease }}
         run: |
           npx playwright install --with-deps chromium
-          node scripts/bundle-sync.mjs
+          cp dist/houseplan-card.js demo/srv/assets/houseplan-card.js
           npm run continuity:screencast
       - name: Upload failed continuity frames
-        if: ${{ failure() && needs.candidate.outputs.prerelease != 'true' }}
-        uses: actions/upload-artifact@043fb46d1a93c77aae656e7c1c64a875d1fc6a0a # v7
+        if: ${{ failure() && !github.event.release.prerelease }}
+        uses: actions/upload-artifact@v7
         with:
           name: continuity-screencast
           path: artifacts/continuity-screencast
-      - name: Keep the passport for the publication step
-        uses: actions/upload-artifact@043fb46d1a93c77aae656e7c1c64a875d1fc6a0a # v7
+      - run: cp dist/houseplan-card.js custom_components/houseplan/frontend/
+      - name: Attach card to release
+        uses: softprops/action-gh-release@v3
         with:
-          name: release-assets-${{ needs.candidate.outputs.tag }}
-          path: release-assets/SHA256SUMS
-          if-no-files-found: error
-      # Also for a draft made in the release form: its tag may not exist yet,
-      # and publishing such a draft would let GitHub tag target_commitish —
-      # not necessarily the verified commit. The tag is pinned here, first.
-      - name: Create or verify the tag at the exact commit
-        env:
-          TAG: ${{ needs.candidate.outputs.tag }}
-          SHA: ${{ needs.candidate.outputs.sha }}
-        run: |
-          set -euo pipefail
-          REMOTE=$(git ls-remote --tags origin "refs/tags/$TAG" "refs/tags/$TAG^{}")
-          if [ -n "$REMOTE" ]; then
-            PEELED=$(printf '%s\n' "$REMOTE" | awk -v ref="refs/tags/$TAG^{}" '$2 == ref {print $1}')
-            test -n "$PEELED" || PEELED=$(printf '%s\n' "$REMOTE" | awk -v ref="refs/tags/$TAG" '$2 == ref {print $1}')
-            test "$PEELED" = "$SHA" || {
-              echo "::error::Existing tag $TAG points to $PEELED, expected $SHA"
-              exit 1
-            }
-          else
-            git config user.name "github-actions[bot]"
-            git config user.email "41898282+github-actions[bot]@users.noreply.github.com"
-            git tag -a "$TAG" "$SHA" -m "$TAG"
-            git push origin "$TAG"
-          fi
-      - name: Stage the verified assets into the release
-        env:
-          GH_TOKEN: ${{ github.token }}
-          TAG: ${{ needs.candidate.outputs.tag }}
-          MODE: ${{ needs.candidate.outputs.mode }}
-          PRERELEASE: ${{ needs.candidate.outputs.prerelease }}
-        run: |
-          set -euo pipefail
-          if [ "$MODE" = "fresh" ]; then
-            FLAG="--prerelease=false"
-            if [ "$PRERELEASE" = "true" ]; then FLAG="--prerelease"; fi
-            gh release create "$TAG" --repo "$GITHUB_REPOSITORY" --verify-tag --draft "$FLAG" \
-              --title "$TAG" --notes-file docs/RELEASE-NOTES.md
-          fi
-          if [ "$MODE" = "repair" ]; then
-            # Public release: what is already outside must be the bytes we just
-            # rebuilt; anything else is a finding, not a --clobber. Only missing
-            # assets are added, and only now — after the gates.
-            mkdir -p public
-            for name in $(gh release view "$TAG" --repo "$GITHUB_REPOSITORY" --json assets --jq '.assets[].name'); do
-              case "$name" in
-                houseplan-card.js|houseplan.zip|SHA256SUMS)
-                  gh release download "$TAG" --repo "$GITHUB_REPOSITORY" --dir public --pattern "$name" --clobber ;;
-              esac
-            done
-            if [ -f public/SHA256SUMS ]; then
-              diff -u public/SHA256SUMS release-assets/SHA256SUMS || {
-                echo "::error::public SHA256SUMS of $TAG differ from the rebuilt assets"
-                exit 1
-              }
-            fi
-            node scripts/release-assets.mjs check public release-assets/SHA256SUMS --allow-missing
-            missing=""
-            for name in houseplan-card.js houseplan.zip SHA256SUMS; do
-              [ -f "public/$name" ] || missing="$missing release-assets/$name"
-            done
-            if [ -z "$missing" ]; then
-              echo "nothing to repair: every asset of $TAG is present and matches"
-            else
-              echo "adding missing assets:$missing"
-              # shellcheck disable=SC2086
-              gh release upload "$TAG" $missing --repo "$GITHUB_REPOSITORY"
-            fi
-          else
-            # Draft: whatever a hand-made publication put here was never
-            # verified, so the verified bytes replace it.
-            gh release upload "$TAG" release-assets/houseplan-card.js release-assets/houseplan.zip \
-              release-assets/SHA256SUMS --repo "$GITHUB_REPOSITORY" --clobber
-          fi
-          RELEASE_JSON=$(gh release view "$TAG" --repo "$GITHUB_REPOSITORY" --json tagName,isDraft,assets)
-          export RELEASE_JSON TAG
-          node <<'NODE'
-          const release = JSON.parse(process.env.RELEASE_JSON);
-          if (release.tagName !== process.env.TAG) throw new Error('release tag mismatch');
-          const assets = new Map(release.assets.map((asset) => [asset.name, asset]));
-          for (const name of ['houseplan-card.js', 'houseplan.zip', 'SHA256SUMS']) {
-            if (!(Number(assets.get(name)?.size) > 0)) throw new Error(`${name} is missing or empty`);
-          }
-          NODE
-
-  publish:
-    name: "Публикация и сверка публичных байтов"
-    needs: [candidate, gate, stage]
-    runs-on: ubuntu-24.04
-    timeout-minutes: 15
-    outputs:
-      url: ${{ steps.verify.outputs.url }}
-      name: ${{ steps.verify.outputs.name }}
-      newly_published: ${{ steps.flip.outputs.newly_published }}
-    steps:
-      - uses: actions/checkout@3d3c42e5aac5ba805825da76410c181273ba90b1 # v7
-        with:
-          ref: ${{ needs.candidate.outputs.sha }}
-          fetch-depth: 0
-      - uses: actions/setup-node@820762786026740c76f36085b0efc47a31fe5020 # v7
-        with: { node-version: 22 }
-      - uses: actions/download-artifact@37930b1c2abaa49bbe596cd826c3c89aef350131 # v7
-        with:
-          name: release-assets-${{ needs.candidate.outputs.tag }}
-          path: passport
-      - name: Publish the verified draft
-        id: flip
-        env:
-          GH_TOKEN: ${{ github.token }}
-          TAG: ${{ needs.candidate.outputs.tag }}
-          MODE: ${{ needs.candidate.outputs.mode }}
-          PRERELEASE: ${{ needs.candidate.outputs.prerelease }}
-        run: |
-          set -euo pipefail
-          if [ "$MODE" = "repair" ]; then
-            echo "newly_published=false" >> "$GITHUB_OUTPUT"
-            echo "repair of a public release: nothing to publish"
-            exit 0
-          fi
-          FLAG="--prerelease=false"
-          if [ "$PRERELEASE" = "true" ]; then FLAG="--prerelease"; fi
-          gh release edit "$TAG" --repo "$GITHUB_REPOSITORY" --draft=false "$FLAG" \
-            --title "$TAG" --notes-file docs/RELEASE-NOTES.md
-          echo "newly_published=true" >> "$GITHUB_OUTPUT"
-      - name: Verify the public release against the passport
-        id: verify
-        env:
-          GH_TOKEN: ${{ github.token }}
-          TAG: ${{ needs.candidate.outputs.tag }}
-          SHA: ${{ needs.candidate.outputs.sha }}
-          PRERELEASE: ${{ needs.candidate.outputs.prerelease }}
-        run: |
-          set -euo pipefail
-          RELEASE_JSON=$(gh release view "$TAG" --repo "$GITHUB_REPOSITORY" \
-            --json tagName,name,isDraft,isPrerelease,assets,url)
-          export RELEASE_JSON TAG PRERELEASE
-          node <<'NODE'
-          const release = JSON.parse(process.env.RELEASE_JSON);
-          if (release.tagName !== process.env.TAG || release.isDraft) throw new Error('release is not public for the requested tag');
-          if (String(release.isPrerelease) !== process.env.PRERELEASE) throw new Error('release prerelease flag does not match the tag');
-          const assets = new Map(release.assets.map((asset) => [asset.name, asset]));
-          for (const name of ['houseplan-card.js', 'houseplan.zip', 'SHA256SUMS']) {
-            if (!(Number(assets.get(name)?.size) > 0)) throw new Error(`${name} is missing or empty`);
-          }
-          NODE
-          # The bytes anyone downloads now are the bytes the gates saw.
-          mkdir -p public
-          gh release download "$TAG" --repo "$GITHUB_REPOSITORY" --dir public \
-            --pattern houseplan-card.js --pattern houseplan.zip --pattern SHA256SUMS --clobber
-          diff -u passport/SHA256SUMS public/SHA256SUMS
-          node scripts/release-assets.mjs check public passport/SHA256SUMS
-          git fetch --force origin "refs/tags/$TAG:refs/tags/$TAG"
-          test "$(git rev-list -n 1 "refs/tags/$TAG")" = "$SHA"
-          URL=$(node -p "JSON.parse(process.env.RELEASE_JSON).url")
-          NAME=$(node -p "JSON.parse(process.env.RELEASE_JSON).name || process.env.TAG")
-          {
-            echo "url=$URL"
-            echo "name=$NAME"
-          } >> "$GITHUB_OUTPUT"
-          printf '### Published %s\n\n- exact SHA: `%s`\n- [GitHub release](%s)\n\n```\n%s```\n' \
-            "$TAG" "$SHA" "$URL" "$(cat public/SHA256SUMS)" >> "$GITHUB_STEP_SUMMARY"
-
-  announce:
-    # #538: анонс — последнее звено, а не параллельное. Пока он висел на самом
-    # событии `release: published`, он обгонял гейт: 12.09 v1.75.0 объявили в
-    # канале в ту же минуту, когда проверка отказала выкладывать ассеты.
-    # `needs: publish` означает, что молчание — это тоже ответ: красный гейт или
-    # несостоявшаяся выкладка сообщения не рождают. Ремонт не анонсируется.
-    name: Оповещение о релизе после выкладки
-    needs: [candidate, publish]
-    if: ${{ needs.publish.outputs.newly_published == 'true' }}
-    uses: ./.github/workflows/announce.yml
-    with:
-      reusable: true
-      tag: ${{ needs.candidate.outputs.tag }}
-      release_name: ${{ needs.publish.outputs.name }}
-      url: ${{ needs.publish.outputs.url }}
-      prerelease: ${{ needs.candidate.outputs.prerelease == 'true' }}
-      ref: ${{ needs.candidate.outputs.tag }}
-    secrets: inherit
-
+          files: dist/houseplan-card.js
   hacs-discovery:
-    name: HACS-видимость пре-релиза (порядок бет)
     # HACS 2.0.x takes the first prerelease in GitHub's response instead of
     # sorting SemVer. A valid asset can therefore be invisible to beta users
     # (beta.10 appeared after beta.9). Keep the release asset, but
     # make that distribution failure impossible to miss in the release run.
-    if: ${{ needs.candidate.outputs.prerelease == 'true' }}
-    needs: [candidate, publish]
-    runs-on: ubuntu-24.04
-    timeout-minutes: 10
+    if: ${{ github.event.release.prerelease }}
+    needs: build
+    runs-on: ubuntu-latest
     steps:
       - name: Verify the published tag is the prerelease HACS will discover
-        uses: actions/github-script@3a2844b7e9c422d3c10d287c895573f7108da1b3 # v9
-        env:
-          EXPECTED_TAG: ${{ needs.candidate.outputs.tag }}
+        uses: actions/github-script@v9
         with:
           script: |
             const releases = await github.paginate(github.rest.repos.listReleases, {
@@ -495,7 +89,7 @@ jobs:
               per_page: 100,
             });
             const first = releases.find((r) => r.prerelease && !r.draft);
-            const expected = process.env.EXPECTED_TAG;
+            const expected = context.payload.release.tag_name;
             if (first?.tag_name !== expected) {
               core.setFailed(
                 `HACS prerelease discovery is stale: GitHub returns ${first?.tag_name ?? 'none'} before ${expected}. ` +

.gitignore

@@ -1,6 +1,4 @@
-# Без слэша: с ним шаблон не покрывает СИМВОЛИЧЕСКУЮ ССЫЛКУ с этим именем,
-# и `git add -A` в чужом worktree затягивает её в коммит (#520, прежде #429).
-node_modules
+node_modules/
 tsout/
 test-build/
 *.log
@@ -9,11 +7,3 @@ __pycache__/
 .venv-backend/
 artifacts/
 .agents/
-
-# Копия бандла для стенда: её собирает `npm run bundle:sync`, а в репозитории
-# она только росла — 364 версии по 1.16 МБ за семь недель (#255). Обязательных
-# копий две: `dist/` (артефакт сборки) и `custom_components/` (её ставит HACS).
-demo/srv/assets/houseplan-card.js
-demo/srv/assets/houseplan-panel.js
-demo/srv/assets/houseplan-assets.json
-demo/srv/assets/houseplan-assets/

.nvmrc

@@ -1 +0,0 @@
-22

.python-version

@@ -1 +0,0 @@
-3.14

AGENTS.md

@@ -2,51 +2,68 @@
 
 House Plan is one HACS package with two parts plus a demo harness:
 
-- **Lovelace card** (`src/`, TypeScript + Lit) — the primary product, bundled to
-  the entry, manifest and hashed chunks under `dist/`.
-- **Storage integration** (`custom_components/houseplan/`, Python) — the Home
-  Assistant backend.
-- **Demo harness** (`demo/`) — a Playwright page (`demo/srv/demo.html`) that
-  renders the card against a fake `hass` for screenshots and the `smoke_*.mjs`
-  suite. The home is fully synthetic. Launcher `demo/serve.mjs`; golden scenes
-  `demo/golden/`, performance `demo/performance/`, guard suite `demo/guard/`,
-  live stand seed `demo/stand/` — each with its own README.
-
-This file is the map and the few rules every session needs before its first
-command. `PROCESS.md` is the only complete canon and wins any disagreement;
-the sections below link to it instead of retelling it.
+- **Lovelace card** (`src/`, TypeScript + Lit) — the primary product, bundled to `dist/houseplan-card.js`.
+- **Storage integration** (`custom_components/houseplan/`, Python) — the Home Assistant backend.
+- **Demo harness** (`demo/`) — a self-contained Playwright page (`demo/srv/demo.html`) that renders the card against a fake `hass`, used for screenshots and the `smoke_*.mjs` end-to-end suite.
 
 ## Read this first
 
 **`docs/SCOPE.md` before anything else.** It was fixed with the owner and states
 its own authority: features are built, improved and accepted **only** if they
-serve a job listed there. Its central consequence: **View mode is the product
-for two of the three personas.** Editors are admin-only tools and must never
-leak interactions into View. For work that changes visible behaviour, also read
-`docs/USER-GUIDE.ru.md` — interface wording comes from there and is not invented.
+serve a job listed there. It carries the mission, the three personas, the core
+user jobs and the out-of-scope list.
 
-**Reading order by role** (#634). `node scripts/entry-cost.mjs` measures each
-route and `test/entry-cost.test.mjs` keeps this list equal to its routes:
+Its central consequence: **View mode is the product for two of the three
+personas.** Editors are admin-only tools and must never leak interactions into
+View.
 
-- author (analysis, spec, implementation, infrastructure): `docs/SCOPE.md` →
-  `AGENTS.md` → `docs/process/AUTHOR.md` → `docs/STATUS.md`;
-- reviewer (spec or code): `docs/SCOPE.md` → `AGENTS.md` →
-  `docs/process/REVIEWER.md`, then the issue body and its comments;
-- changing the pipeline, the gates or the process itself: `docs/SCOPE.md` →
-  `AGENTS.md` → `PROCESS.md` → `docs/STATUS.md`.
+For work that changes visible behaviour, also read `docs/USER-GUIDE.ru.md` —
+interface wording comes from there and is not invented, or the UI starts speaking
+developer.
 
-The two digests quote and link `PROCESS.md` section by section; open the linked
-section whenever a digest line governs your current step. For non-trivial
-changes add `docs/ARCHITECTURE.md` plus the canonical document of the subsystem
-you touch (one list, the same one the reviewer prompt in `_process.yml` reads):
-`SUN.md`, `LIGHT.md`, `CANVAS.md`, `WALL-THICKNESS.md`, `UX-MODES.md`,
-`CONFIG-COMPATIBILITY.md`, `TOUCH-SUPPORT.md`, `ISOMETRIC.md`, `VACUUM.md`,
-`DECOR-EDITOR.md`, `DEVICE-PRESENTATION.md`, `FILTERING.md`, `STAIRS.md`,
-`RADAR.md`, `PDF-EXPORT.md`, `STYLING-HOOKS.md`.
+Then `PROCESS.md` (the full process), `docs/STATUS.md` (where the release line
+is), and for non-trivial changes `docs/ARCHITECTURE.md` plus the canonical
+document of the subsystem you touch: `SUN.md`, `LIGHT.md`, `CANVAS.md`,
+`WALL-THICKNESS.md`, `UX-MODES.md`, `CONFIG-COMPATIBILITY.md`,
+`TOUCH-SUPPORT.md`.
 
-Where the rest lives: commands — `package.json` scripts, `CONTRIBUTING.md`,
-`docs/DEVELOPMENT.md` (toolchain, build, release — its Release section is the
-only home of release mechanics); tests and gates — `docs/TESTING.md`.
+Standard commands live in `package.json` scripts, `CONTRIBUTING.md` and
+`docs/DEVELOPMENT.md`.
+
+## Canonical backlog and status
+
+[GitHub Issues](https://github.com/Matysh/houseplan-card/issues) are the canonical
+task records: problem, scope, acceptance criteria and discussion.
+
+**Status lives in labels:** `S1-new`, `S2-analysis`, `S3-spec`, `S4-spec-review`,
+`S5-ready`, `S6-in-progress`, `S7-code-review`, `S8-merged`, plus `blocked` on top
+of a status and `rejected` on a closed issue. Exactly one `S*` label per open
+issue. Labels are the whole of it: GitHub Projects is no longer used.
+
+Two shortcuts exist for small work. `small` — the light track: the spec lives in
+the issue body and its review is a comment. `trivial` — the short track: no spec
+stage at all, `S2-analysis` straight to `S5-ready`, with the AC written into the
+issue body first. `trivial` requires a bug confined to one surface with no new UX
+contract, no migration, no i18n, no perf or touch impact, at most three checkable
+AC, **and expected behaviour already on record** — nothing left to decide. Code
+review is never skipped on either track; it is what stands in for testing.
+`PROCESS.md` §5 and §5.1 hold the criteria.
+
+An issue filed by an outsider is worked exactly like one of the owner's own, once
+the owner has decided to take it. The check sits **at the entrance**, not on every
+step: while an issue carries no status label it is outside the process and the
+invariants do not apply to it; once a label is on, the task is in flight and **who
+filed it stops mattering**.
+
+Applying that first label *is* the owner's explicit decision, and the platform
+already guarantees it — only someone with write access can label. The earlier rule
+made outside reports be refiled as the owner's own issues, which turned out to be
+work for nothing: on #123 the spec was already written by the time the guard
+refused.
+
+Specs, audits and ADRs may live under `docs/`, but must link to their issue and
+must not become a parallel task list. When repository documentation disagrees with
+Issues, the issue wins.
 
 ## Rule #1
 
@@ -63,100 +80,142 @@ The label must be one of `S5-ready`, `S6-in-progress`, `S7-code-review`. Anythin
 else — refuse and say why. "Issue #83 is in `S2-analysis`, code is off limits.
 Start with the spec?" is the correct answer, not a smaller patch.
 
-GitHub Issues are the canonical task records and the **labels** are the status
-(`PROCESS.md` §9); when repository documentation disagrees with an issue, the
-issue wins. Change classes (`PROCESS.md` §1): **A** product (`src/**`,
-integration Python, manifests, i18n), **B** gates and tooling (tests, `demo/**`,
-`scripts/**`, `.github/**`, build and package configuration), **C**
-documentation, **D** generated (bundle, golden baselines) — D beats A where paths
-overlap. The committed bundle changes only in a commit with a `Release:` trailer
-(#657); an ordinary task restores it with `npm run bundle:clean` before
-committing.
+## Change classes
 
-**Tracks** (`PROCESS.md` §5, §5.1): `small` is the default — the spec lives in the
-issue body and its review is a comment; taking the full track means naming the
-`small` criterion the task fails. `trivial` skips the spec stage for a bug whose
-expected behaviour is already on record. An **infrastructure** task — not a single
-class A file — skips analysis and spec and enters at `S7-code-review`
-(`PROCESS.md` §1). Code review is never skipped on any track: it checks scope,
-risks and the evidence from executed tests, but does not replace executing them.
+| Class | Paths | Issue required |
+|---|---|---|
+| **A — product** | `src/**`, `custom_components/houseplan/**/*.py`, `manifest.json`, `hacs.json`, i18n, `custom_components/**/translations/**` | yes |
+| **B — gates and tooling** | `test/**`, `tests_backend/**`, `demo/**`, `scripts/**`, `.github/workflows/**`, `rollup.config.mjs`, `tsconfig*.json` | yes; may reuse the issue it covers |
+| **C — documentation** | `docs/**`, `README*`, `CHANGELOG*`, `AGENTS.md` | not if it is part of its issue's DoD |
+| **D — generated** | `dist/**`, `custom_components/houseplan/frontend/**`, `demo/srv/assets/houseplan-card.js`, `demo/golden/baselines/**` | never changes on its own |
 
-## Specs
+The table above is a summary; `PROCESS.md` §1 is the authority and now covers the
+configuration files this one omits — `package.json`, `package-lock.json`,
+`pytest.ini`, `.gitignore`, `.gitattributes`, `.githooks/**` and the rest of
+`.github/**` are class B. Where paths overlap, **D beats A**: the built bundle
+lives inside `custom_components/houseplan/frontend/` and would otherwise read as
+product source.
 
-The spec lives in the **issue body**, under a `## ТЗ` heading (owner decision
-2026-09-10, #517); `docs/specs/` is an archive of specs written before that date
-and takes no new files. Required sections and the rule for questions are
-`PROCESS.md` §7.1: only **product** ambiguity goes to the owner — what a person
-sees or does, and how much user-visible change belongs in this issue — in one
-batched comment with a proposed default for each question and `blocked` on top of
-`S3-spec`. Everything a user cannot observe is yours to decide and record.
+## Commits
 
-## Commits and branches
+Hooks install themselves: `package.json` runs `"prepare": "node
+scripts/install-hooks.mjs"`, so `npm ci` sets `core.hooksPath` in every fresh
+clone. Verify with `git config core.hooksPath` — expect `.githooks`.
 
-Hooks install themselves on `npm ci` (`prepare` → `scripts/install-hooks.mjs`);
-`git config core.hooksPath` must print `.githooks`. Every non-merge commit
-carries **terminal** trailers:
+Every non-merge commit carries **terminal** trailers:
 
 ```text
 Issue: #123
 User-Visible: yes
 ```
 
-One `Issue:` line per issue. `User-Visible: yes` requires edits to **both**
-`docs/CHANGELOG.md` and `docs/CHANGELOG.ru.md` in the same commit. A commit
-touching `demo/golden/baselines/**` also needs `Release:` plus exactly one of
-`Baseline-Reviewed: <GitHub run URL>` or `Baseline-Reviewed-Local: sha256:<WSL
-attestation>` (`PROCESS.md` §10.1). Never invent a review link and never rewrite
-published history to satisfy trailers.
+One `Issue:` line per issue if a commit closes several. `User-Visible: no` for
+tests, refactors, tooling and documentation that does not change the product.
+`User-Visible: yes` requires edits to **both** changelogs — `docs/CHANGELOG.md`
+and `docs/CHANGELOG.ru.md` — in the same commit.
 
-Branch `issue/<NN>-slug`; direct commits to `dev`, no PR (owner's decision); a
-violation is fixed with a follow-up commit, never a force-push.
+A commit touching `demo/golden/baselines/**` additionally requires:
 
-- **Push after every task, not before a beta** — while work sits unpushed there
-  is nothing to review.
-- **Standing permission: push `issue/<NN>-slug` without asking.** The reviewer
-  runs in CI and reads only the remote; a task branch publishes nothing to users.
-  Push the material **before** applying the review label.
-- **Do not merge into `dev` by hand.** On a green review the pipeline rebases,
-  pushes and only then sets `S8-merged`. A conflicting rebase returns the task to
-  `S6-in-progress` with the verdict intact; `node scripts/rebase-on-dev.mjs`
-  resolves conflicts in generated files only (`PROCESS.md` §2.10), then push and
-  re-apply `S7-code-review`.
-- Everything else needs the owner's explicit command: pushing `main`, tags,
-  publishing betas and releases, closing issues.
+```text
+Release: v1.62.0-beta.9
+Baseline-Reviewed: https://github.com/Matysh/houseplan-card/actions/runs/<run-id>
+```
+
+Never invent a review link and never rewrite published history to satisfy
+trailers. `.githooks/commit-msg` and the `provenance` CI job both run
+`scripts/validate-commit-provenance.mjs`.
+
+Branch: `issue/<NN>-slug`. Direct commits to `dev`, no PR — the owner's decision;
+CI checks after the fact, and a violation is fixed with a follow-up commit, never
+a force-push.
+
+**Push after every task, not before a beta.** While work sits unpushed there is
+nothing to review, and reviewing twenty tasks at once is not review. `dev` may hold
+unreviewed code while a task is in flight; what matters is its state when the
+reviewer says it is accepted.
+
+**Standing permission: push `issue/<NN>-slug` without asking.** The reviewer runs
+in CI and can only read what is on the remote — an unpushed spec or commit means
+the review either stalls or judges the wrong tree. Pushing a task branch publishes
+nothing to users and does not touch the integration branch, so it needs no command.
+
+**Do not merge into `dev` by hand.** On a green code review the pipeline rebases
+the task branch onto `dev`, pushes it, and only then sets `S8-merged` — the label
+asserts the code is in `dev`, so the merge has to happen first or the label lies
+in between.
+
+If the rebase conflicts the pipeline says so in the issue and sends the task back
+to `S6-in-progress`. The verdict still stands: nothing needs reviewing again, the
+remaining work is the rebase. Resolve it, push the branch, re-apply
+`S7-code-review`. The second review run is not a formality — after a rebase onto a
+moved `dev` this is different code, and accepting it unchecked is how regressions
+arrive. Cycles are counted per stage, so a code review spends its own budget.
+
+Everything else still requires the owner's explicit command: pushing `main`,
+creating tags, publishing betas and releases, closing issues.
 
 ## Working trees (#115)
 
 One checkout, one `HEAD`: two agents sharing a directory inherit each other's
-branch. `houseplan-card-src/houseplan-card` is the author's tree — task branches
-live there, and unfamiliar local changes belong to the author or the owner,
-never reset or clean them away. `houseplan-card-src/hp-dev` is the owner's
-worktree, permanently on `dev`. The reviewer owns no tree: it runs in CI on a
-fresh checkout. A worktree works only on the machine that created it — its
-`.git` file records an absolute path in that machine's format.
+branch, and twice in one hour a commit landed on someone else's task branch that
+way. The layout is therefore fixed:
 
-## Handoff and the verdict
+- **`houseplan-card-src/houseplan-card`** — the author's tree. Task branches live
+  here; nobody else commits in it. Unfamiliar local changes belong to the author
+  or the owner — never reset or clean them away.
+- **`houseplan-card-src/hp-dev`** — the owner's worktree, permanently on `dev`. For owner-side operations that must not disturb the
+  author's tree: pushing `dev`, restoring a hook's executable bit, emergencies.
+- **The reviewer and the infrastructure agent own no local tree.** The reviewer
+  runs in CI on a fresh checkout. The infrastructure agent reads via `git show`
+  and publishes through the GitHub API; it makes no local commits at all, so it
+  needs no `HEAD` of its own. Its scratch worktrees live outside the repo and are
+  pruned after use.
 
-Start a task from its packet: `node scripts/task-packet.mjs --issue NN` (status,
-track, what the status permits, the branch against `dev`, the previous verdict
-and the unwitnessed AC; it writes nothing). The local gate is
-`npm run gate:small` (`docs/TESTING.md` › Локальный набор перед пушем); run the
-smokes named in the AC before `S7-code-review`. **"Verified" without a named
-command and its result is not evidence.** Comment formats — claim, handoff,
-verdict — are `PROCESS.md` §7.2.
+A worktree is only usable on the machine that created it: the `.git` file records
+an absolute path in that machine's format. One created from a Linux sandbox is
+dead on Windows and vice versa — create worktrees on the machine that will use
+them, which for `hp-dev` means the owner's.
 
-**One handoff, one push** (`PROCESS.md` §10.4). Run
-`node scripts/process-gate.mjs --issues` before pushing; after
-`S7-code-review` do not push to the branch until the verdict or the return
-arrives — a push on top of a running review cancels it.
+## Two-agent workflow
 
-**Having applied `S4-spec-review` or `S7-code-review`, wait for the result
-instead of ending the session.** The label starts the pipeline by itself. Poll
-with `node scripts/wait-verdict.mjs --issue NN [--sha <tip>]` (#496): it watches
-the label and the pipeline's comments every 90 s, at most 110 times, prints only
-on a change and exits 0 on a new label, 3 on an event that needs a hand, 4 on
-timeout. Watch the **label**, not the comment. Do not wait while `blocked` is
-set.
+**Codex** writes analysis, specs and all product code. **Claude** reviews specs and
+code and owns infrastructure and distribution. The owner rules on disputes, closes
+issues and commands releases.
+
+Author and reviewer are different models, which is what "a fresh session without
+implementation context" means in practice. The reviewer never edits product code;
+the author never grades their own work.
+
+**Infrastructure-only work runs outside this flow.** CI, scripts, labels, demo
+stands, the landing page and distribution are Claude's alone, and running them
+through spec-writing and review buys nothing: the spec would restate what is
+already unambiguous, and author and reviewer would be the same role. So no spec
+file, no spec review, no code review, no walk through `S1`…`S8`.
+
+The test for "infrastructure only" is mechanical: **not a single class A file** —
+nothing under `src/**`, no `custom_components/**/*.py`, no manifests, no i18n. A
+task that touches class A even once is not infrastructure and takes the full flow;
+there is no such thing as "mostly infrastructure". The strictness is deliberate:
+a loose reading would turn this into the route by which product changes skip
+review.
+
+What stays mandatory either way: an issue exists, both trailers are on every
+commit, `typecheck`, `test` and `build` are green, and any non-obvious decision is
+written down in the code or the issue rather than kept in someone's head.
+
+**Review starts by itself.** Applying `S4-spec-review` or `S7-code-review` fires the
+pipeline, which reviews without anyone asking and takes ten to forty-five minutes.
+
+**Having applied one of those labels, wait for the result instead of ending the
+session.** Reporting "handed over for review" stops a conveyor that could have kept
+moving on its own. An agent has no clock — it exists only during its own turn — so
+waiting means polling: every 90 seconds, at most 30 times. A single long sleep hits
+the command timeout. Watch the **label**, not the comment: the label is the state,
+the comment only explains it. Do not wait at all while `blocked` is set — the task
+is waiting on the owner, not on the reviewer. On exhausting the attempts, stop and
+tell the owner: a failed run leaves the label where it was, forever.
+
+What the new label means:
 
 | Now reads | What happened | What you do |
 |---|---|---|
@@ -167,21 +226,200 @@ set.
 | `review-4` | the cycle limit is spent | stop, the owner decides |
 
 **After a review run the label always changes.** If it did not, the run itself
-failed rather than the work — say so to the owner instead of polling on. The
-bounded queue reconciler (#555) re-wakes a review whose event was lost; it is a
-safety net, not permission to stop waiting for the review you started.
+failed rather than the work — say so to the owner instead of polling on.
 
-A failed pre-release gate (golden, full smokes, performance, HA harness) does not
-send the issue back to review: fix, re-run what failed, record the exact command
-and result in the issue (`PROCESS.md` §11.4 — and its limits).
+**A failed pre-release gate does not send the issue back to review.** The
+implementation loop runs only typecheck, unit and build; golden, browser smokes,
+performance and the full HA harness run before a beta, which is after the code
+review has passed and the issue sits in `S8-merged`. Some defects cannot surface
+any earlier.
+
+Fix it, re-run what failed, and a green run is enough for the release to continue.
+The issue stays in `S8-merged`. Record the **exact command and its result** in the
+issue — "verified" without a command proves nothing. Trailers as usual, and
+`User-Visible: yes` still means both changelogs in the same commit.
+
+The exception covers repairing the defect the gate named, not carrying on
+development under the name of a repair. It goes through the normal flow — a new
+issue, or back to `S6-in-progress` — if the fix changes a behaviour contract, gives
+the user something new, reaches a subsystem the task never touched, or is
+comparable in size to the task itself. And editing the gate so it stops failing is
+concealment, not repair; the exception is a defect proven to be **in the fixture**,
+as on #89, where the sun sat at azimuth 180° and the only window faced north, so no
+ray was ever built.
+
+Baselines are still accepted only via `npm run golden:accept -- --reviewed` on a
+complete Linux CI artefact. "So the gate goes green" is not a reason.
+
+The exchange happens in **issue comments** — there is no local message bus. Verdict
+format:
+
+```text
+Verdict: green/yellow/red · cycle r<N>/4 · High: N · Medium: N → in-task | #… · Document: …
+```
+
+High blocks. A Medium finding INSIDE the task's scope is fixed within the task:
+with no High findings the verdict is yellow, the author fixes it and the fix
+passes another review cycle — no separate issue (owner's decision 2026-08-19,
+#202: filing and servicing an issue costs far more than fixing in place). Only
+a Medium finding OUTSIDE the scope becomes its own issue — foreign scope is
+never patched from this branch. Low is fixed or waived with a note
+in the review document. A yellow verdict is legitimate even when every acceptance
+criterion passes, if the change does not solve the stated scenario or degrades a
+neighbouring one.
+
+**Four review cycles** (two on the light track). The counter lives in the document
+name, `-r1`…`-r4`; the fourth adds the `review-4` label. There is no fifth attempt:
+the owner splits the task, rejects it, or arbitrates.
+
+On the light track (`small`: complexity ≤3, one surface, no config migration, no
+new UX contract, no perf or touch impact — all at once) the spec lives in the issue
+body and the spec review is a comment. Code review is never skipped.
+
+## Specs
+
+`docs/specs/<NN>-<slug>.md`, linked to its issue in both directions. Required
+sections are in `PROCESS.md` §7.1, plus two product ones: which persona meets this,
+on which surface, at what moment; and what the person sees before and after, in one
+sentence without implementation terms.
+
+**Ambiguity is asked, not guessed — but only product ambiguity.** A guess written as
+fact is the worst kind of defect: it passes review because it looks like a decision.
+
+The owner answers exactly two kinds of question: **what a person sees or does**, and
+**how much user-visible change belongs in this issue**. Behaviour in a boundary case,
+which persona wins when two conflict, what counts as acceptable degradation, whether
+a neighbouring behaviour is in scope here or becomes its own issue.
+
+Everything a user cannot observe is yours to settle: where state is stored, which
+module carries the guard, naming, file layout, test strategy, migration mechanics,
+development policy. Decide it, record it in an explicit "assumed, change freely"
+block, and let the reviewer challenge it. A technical disagreement between author and
+reviewer is settled by the verdict, not by the owner; it reaches him only when the
+cycle limit is exhausted.
+
+Split a mixed question instead of escalating all of it. "Where does this state live"
+is technical. "Does it survive a page reload and follow the plan across screens" is
+product. Ask the second, decide the first.
+
+Ask in one batched issue comment, each question carrying a proposed default, and put
+`blocked` on top of `S3-spec` while waiting. A question with a default costs the
+owner seconds; one without costs him minutes.
+
+## Gates
+
+```
+npm run typecheck
+npm test
+npm run build
+npm run inventory        # the only correct way to get test counts
+```
+
+Never copy test counts into documents by hand; they go stale in days.
+
+After building, keep all three bundle snapshots in sync — CI compares them
+byte-for-byte:
+
+```
+cp dist/houseplan-card.js custom_components/houseplan/frontend/houseplan-card.js
+cp dist/houseplan-card.js demo/srv/assets/houseplan-card.js
+```
+
+During the implementation cycle the fast gates always run. Since 2026-08-14 the
+owner's machine also carries Playwright with Chromium (Windows) and a full WSL
+environment, which changes one thing (#151): **before moving an issue to
+`S7-code-review`, run the smokes named in its AC locally** — `node
+demo/smoke_<name>.mjs`. A red smoke that reaches the review costs a cycle; run
+locally it costs a minute. Precedent: on #89 a fixture error lived through a
+whole review round that a local run would have caught immediately.
+
+The full smoke set, `golden` and `performance_smoke` still belong to the
+pre-beta run — which is then mandatory and complete. WSL runs of the full HA
+harness (`~/houseplan-card`, venv) and `golden:verify` are advisory; **the canon
+does not move**: the beta gate is CI at the exact SHA, and baselines are accepted
+only via `npm run golden:accept -- --reviewed` on a complete Linux CI artefact.
+
+**Backend.** A full Home Assistant harness cannot run on native Windows at all:
+Home Assistant imports the Unix-only `fcntl` module. Its canon is Linux CI or WSL.
+Locally only the pure subset runs; `python -m pytest tests_backend/ -q` without
+Home Assistant **silently skips** `test_ha_*.py` (`conftest.py` ignores them when
+`homeassistant` is not importable), so a green result proves nothing. Say so in the
+report instead of claiming the backend was verified. Cloud agents have the harness
+at `.venv-backend/bin/python`.
+
+**Running the app / smoke suite**: build a fresh bundle and copy it into the demo
+assets first, then run `node demo/smoke_*.mjs`. No real Home Assistant server is
+required: `demo/srv/demo.html` stubs `hass`, registries and `callService`.
+
+**Golden images**: `npm run golden:capture` and `npm run golden:verify` refuse a
+stale demo bundle. Build and copy first, then review `artifacts/golden/actual/` and
+`diff/`. Update baselines only with `npm run golden:accept -- --reviewed`, using the
+complete Linux CI artifact; never accept a partial scenario or images merely to make
+CI green. See `demo/golden/README.md`.
+
+**Freshness contract**: the embedded fingerprint covers `src/` plus Rollup,
+TypeScript and package-lock build inputs. Benchmark and golden tooling must call
+`assertFreshDemoBundle` before recording any result; a missing or mismatched
+fingerprint is a hard failure, not a warning.
+
+**CI is pinned to an exact SHA.** The release gate accepts only a `completed
+success` run for the candidate's SHA, not "the last green one"; a new push cancels
+an unfinished Validate for the same branch. Gate jobs, matching the actual
+`validate.yml` (#191): `docs`, `provenance`, `process-gate`, `hacs`, `hassfest`,
+`frontend`, `smoke`, `golden`, `performance_smoke`, `backend`. The `changes` job
+is a service path-filter, not a gate. `docs` is a real blocker: it checks the
+screenshots `sourceFingerprint` against current `src/**`, which is exactly what
+went red after the #113 merge.
+
+**"Verified" without a named command and its result is not evidence.**
 
 ## Environments
 
-The owner's Windows machine: `.\scripts\windows-toolchain.ps1 setup|check` owns
-the pinned Node and Python; WSL works from an ext4 clone with
-`bash scripts/wsl-setup.sh --verify` (`docs/DEVELOPMENT.md` › Local Windows
-workstation). `npm run toolchain:check` compares any machine with the pins CI
-uses. The full Home Assistant harness cannot run on native Windows; without an
-importable `homeassistant` pytest does not collect `test_ha_*.py` at all, so a
-green pure run proves nothing about the harness (`docs/TESTING.md`). Cloud
-agents have the harness at `.venv-backend/bin/python`.
+**Local Windows checkout** is the day-to-day environment: Node 22 as in CI, Python
+3.13 in a venv, `gh` authenticated. `.venv-backend` does **not** exist there — it is
+provisioned only by cloud agent startup scripts, which also run `npm ci` and install
+Playwright Chromium.
+
+Known environment-sensitive smoke: `demo/smoke_opening_measure.mjs` fails two
+sub-checks (`place_dialog_x_magnetised`, `place_committed_x_center`) under the pinned
+Chromium — a `1e-6`-tolerance magnet-snap on the opening-*placement* path. It
+reproduces against the pristine committed bundle, so treat it as
+pre-existing/pixel-precision, not a regression you introduced.
+
+## Labs flags
+
+`src/labs.ts` is the single registry and resolver for hidden presentation
+experiments. Activate a live flag through `?hp-labs=<id>` or the shared hash
+grammar, remove it with `-<id>`, and use `off` to clear the set. Do not add a
+YAML/config switch for a Labs-only experiment. A new entry needs a unique
+lowercase id, issue, numeric-core `since`, numeric-core `expires`, summary and
+unit/browser coverage. Invalid or duplicate registry entries fail closed.
+
+Expiry is exclusive and ignores prerelease suffixes: an entry expiring at
+`1.65.0` is unavailable in `1.65.0-beta.1`. Before that cycle, either remove the
+experiment or graduate it through its own reviewed issue; never extend expiry as
+an incidental change. Labs may alter presentation only and must not gate data,
+migrations, stores, HA actions or network calls. Current renderer details are in
+`docs/ISOMETRIC.md`.
+
+Demo harness render quirk: the fake `hass` in `demo.html` is set once, so opening the
+page directly in a browser renders the floor plan but **device icons only appear
+after a re-render** (an F5 refresh, or nudging `card.hass = {...card.hass}`). The
+smoke launcher `demo/serve.mjs` already does this nudge; a plain browser session does
+not. This is a harness limitation, not a card bug.
+
+## Promotion rule
+
+Every new feature or material behaviour change must be published as a beta/RC
+before it can enter a stable release, even when its local audit is clean. The
+stable release commit is promotion-only: version fields, generated bundle
+snapshots and changelog/release metadata. Do not add feature source code in
+that commit. An explicit owner-requested emergency hotfix is the only exception
+and must be called out in the release handoff.
+
+A `Release vX.Y.Z-beta.N candidate` commit is **not** promotion-only: it carries
+the work itself and follows the ordinary rules, trailers included.
+
+Issues are closed in a batch when a beta ships, not when implementation ends: that
+way a bug found in the beta returns to the same task, and the beta announcement can
+list what went in. Status labels are stripped as the issues close.

CONTRIBUTING.md

@@ -9,68 +9,6 @@ User-visible changes go into **both** changelogs in the same commit:
 `docs/CHANGELOG.md` (English) and `docs/CHANGELOG.ru.md` (Russian). Entries
 older than v1.42.0 exist only in the English file — no need to backfill them.
 
-## Translations
-
-A shipped UI language has three matching parts:
-
-1. `src/i18n/<code>.json` for the card;
-2. `custom_components/houseplan/translations/<code>.json` for the Home Assistant
-   integration;
-3. one registry entry (code, native label and eager dictionary or lazy loader)
-   in `src/i18n/registry.ts`.
-
-Use the canonical Home Assistant/BCP 47 language tag as `<code>` (for example,
-`fr` or `pt-BR`) and use that exact spelling for both JSON filenames. Lookup is
-case-insensitive and also accepts `_` from legacy locale sources.
-
-The registry drives language resolution, the visual-editor selector and parity
-tests. The tests reject missing or extra locale files; frontend dictionaries
-also fail on mismatched keys, empty values and changed placeholders.
-Placeholders such as `{name}` and `{n}` are a contract: do not translate, add
-or remove them.
-
-English and Russian are synchronous fallback/legacy locales. German is the
-reference lazy third-locale implementation: its module carries the same build
-fingerprint as the entry bundle, has one content-hashed retry URL and is listed
-under `lazyLocaleFiles` in `houseplan-assets.json`. New sizeable locales should
-follow that path unless a measured initial-bundle budget explicitly justifies
-an eager import. Extend the runtime, manifest, file/key/placeholder parity and
-regional-locale tests together; never bypass the registry by importing a locale
-directly in a component.
-
-Administrator-only copy lives in three lazy namespace dictionaries —
-`src/i18n/settings/`, `src/i18n/support/` and `src/i18n/topology/` (#627). Their
-English file is static (the synchronous fallback); every other language is one
-lazy chunk per namespace × language: a two-line loader module
-`src/i18n/<namespace>/<namespace>-<code>.ts`, one `import()` with a
-content-hashed retry token in `src/i18n/<namespace>.ts`, and one entry in
-`NAMESPACE_LOCALE_CHUNKS` in `scripts/bundle-manifest.mjs`. The lazy surfaces
-(onboarding, editor runtime, Zigbee overlay) wait for their dictionaries before
-painting; never import a non-English namespace JSON statically — the budget
-gate and `test/i18n-lazy-namespaces.test.mjs` refuse it.
-
-The current `subst()` helper does not implement plural rules. Phrase strings so
-their grammar does not depend on the numeric value (for example, use a neutral
-label followed by `{n}` rather than an English singular/plural pair).
-
-Adding a UI locale does not automatically create another full documentation
-set; maintain the existing English and Russian documentation according to the
-project's normal rules. Right-to-left layout is a separate product project,
-because the plan canvas and editors cannot be mirrored by translations alone.
-
-## Documentation screenshots
-
-The images under `docs/images/` are produced only from synthetic data by the
-`Docs screenshots` workflow (`demo/docs/capture.mjs` on the pinned Chromium)
-and accepted locally with `npm run docs:accept -- --reviewed --from=<unpacked
-artifact>`; when a change cannot move a pixel, `npm run docs:accept --
---identical` re-captures locally, compares decoded pixels and refreshes only the
-source fingerprint. Scenario version, source fingerprint and every image hash
-are recorded in the [screenshot index](docs/images/screenshots.json), and
-`node scripts/check-docs.mjs` reports a stale fingerprint: a warning on an
-ordinary push, an error on a beta candidate (a commit with a `Release:`
-trailer). The full rule is in `PROCESS.md` §8.
-
 ## Where to ask
 
 Not sure whether something is a bug, or just want to discuss an idea before
@@ -90,7 +28,7 @@ issue, but they do not replace it or maintain a separate checklist.
 ## Five-minute setup
 
 ```bash
-git clone --filter=blob:none https://github.com/Matysh/houseplan-card && cd houseplan-card
+git clone https://github.com/Matysh/houseplan-card && cd houseplan-card
 npm ci                    # frontend toolchain
 npm run typecheck         # tsc --noEmit (strict)
 npm test                  # node:test — pure logic, i18n parity, tap-action security
@@ -99,38 +37,18 @@ pip install pytest voluptuous && python -m pytest tests_backend -q   # pure back
 npm install                # also installs .githooks through the prepare script
 ```
 
-### Why `--filter=blob:none` (#345)
-
-A blobless clone keeps every commit and tag, so ranges, `merge-base` and
-`git diff` across history work exactly as in a full clone; only historical *file
-contents* are fetched on demand. Most of the pack is exactly such content that
-almost nobody reads again — documentation screenshots re-captured with the UI and
-the committed bundle rewritten by every release candidate — so a blobless clone
-is several times smaller. To see the numbers for your own clone, compare
-`git count-objects -vH` in a blobless and in a full one.
-
-Drop the flag if you work offline with history, or need `git log -p` over the whole
-tree repeatedly. Do **not** replace it with `--depth=1`: a shallow clone is about
-the same size but has no `merge-base`, so the process gate, `smoke-select` and
-every `origin/dev..HEAD` range stop working.
-
-The HA-harness backend tests (`tests_backend/test_ha_*.py`) need the
-repository-pinned Python (`.python-version`) and
-`pytest-homeassistant-custom-component home-assistant-frontend`; their canon is
-Linux CI or WSL (`bash scripts/wsl-setup.sh --verify`). Without an importable
-`homeassistant` they are not collected at all — not skipped — and pytest prints
-`HA harness NOT collected: …` (#630).
+The HA-harness backend tests (`tests_backend/test_ha_*.py`) need Python ≥3.13 and
+`pytest-homeassistant-custom-component home-assistant-frontend`; CI runs them on
+every push — locally they are skipped when `homeassistant` is not importable.
 
 ## Ground rules
 
 - **Docs in the same commit**: CHANGELOG entry for user-visible changes;
   `docs/STATUS.md` for state changes; `docs/DEVELOPMENT.md` for new gotchas.
-- Every UI string goes through `src/i18n/<lang>.json`; follow the
-  [Translations](#translations) flow for registry and backend parity.
-- The committed bundle changes only in a release candidate: `npm run
-  bundle:release` in a commit with a `Release:` trailer (#657). An ordinary task
-  restores it with `npm run bundle:clean` before committing — the `commit-msg`
-  hook refuses a bundle change otherwise.
+- Every UI string goes through `src/i18n/<lang>.json` (tests enforce en/ru key parity).
+  Adding a language = adding one JSON file + registering it in `src/i18n.ts`.
+- The built card must be committed in sync: `cp dist/houseplan-card.js
+  custom_components/houseplan/frontend/` (CI compares them byte-for-byte).
 - Tap actions have a security model (locks/alarms never toggle from the plan) —
   see `resolveToggleIntent` in `src/device-toggle.ts`; don't weaken it.
 - Every commit follows the issue and trailer contract in `PROCESS.md`.
@@ -140,5 +58,6 @@ Linux CI or WSL (`bash scripts/wsl-setup.sh --verify`). Without an importable
 ## Architecture
 
 Start with `docs/ARCHITECTURE.md` (data model, WS API, coordinate system) and
-`docs/STATUS.md` (current state). Release mechanics live in one place:
-`docs/DEVELOPMENT.md` › Release.
+`docs/STATUS.md` (current state). Release: bump the version in `package.json`,
+`manifest.json`, `const.py`, `CARD_VERSION`, tag `vX.Y.Z`, publish a GitHub release —
+the workflow attaches the card bundle.

README.md

@@ -1,6 +1,6 @@
 # 🏠 House Plan — a live home map for Home Assistant
 
-[![HACS Default](https://img.shields.io/badge/HACS-Default-41BDF5.svg)](https://github.com/hacs/integration)
+[![HACS Custom](https://img.shields.io/badge/HACS-Custom-41BDF5.svg)](https://github.com/hacs/integration)
 [![GitHub release](https://img.shields.io/github/v/release/Matysh/houseplan-card)](https://github.com/Matysh/houseplan-card/releases)
 [![CI](https://github.com/Matysh/houseplan-card/actions/workflows/validate.yml/badge.svg)](https://github.com/Matysh/houseplan-card/actions)
 [![Live demo](https://img.shields.io/badge/demo-try_it_live-00c853?logo=homeassistant&logoColor=white)](https://demo.houseplan.tech)
@@ -12,9 +12,8 @@
 
 ## Your whole home at a glance
 
-House Plan turns Home Assistant into a live map of your home. Open the dedicated
-**House Plan** item in the Home Assistant sidebar, upload a plan or draw rooms,
-bind them to Home Assistant areas, and
+House Plan turns Home Assistant into a live map of your home. Upload a plan or
+draw rooms directly on the dashboard, bind them to Home Assistant areas, and
 the area's devices appear automatically. You can immediately see where a light
 is on, a door is open, a room is too cold, Zigbee signal is weak, or a leak
 sensor has fired.
@@ -42,9 +41,6 @@ sync across screens.
   show temperature, humidity, light state and average LQI.
 - **Light and environment.** Room fills, lamp Glow, wall shadows, a day-cycle
   backdrop and sunlight through windows.
-- **Flat or 2.5D.** One switch in General settings › Display shows the plan
-  with depth everywhere: raised device tiles with soft floor shadows and a soft
-  wash of sunlight; decor and wall colours stay as you set them.
 - **Doors, windows, gates and vacuums.** Openings follow real contacts and locks;
   a robot can show its position, dock and travelled path.
 - **Several floors and screens.** Space tabs, swipe navigation, local viewport,
@@ -58,11 +54,11 @@ sync across screens.
 
 ## Your first working room
 
-1. Install the integration and open **House Plan** in the Home Assistant sidebar.
+1. Install the integration and add the card to a dashboard.
 2. Create the first **space**: upload SVG/PNG/JPG/WebP, reuse an uploaded image,
    or choose no image and draw the plan by hand.
-3. In Plan, select **Walls** and draw one continuous chain around the room: when
-   it closes an area, the room dialog opens.
+3. In Plan, select **Room outline**, place vertices, and click the first point to
+   close the outline.
 4. Name the room and bind it to a Home Assistant area. Use “No area” for a room
    that has no devices.
 5. Open Device: devices from the bound area are already placed; drag their
@@ -92,78 +88,31 @@ The [Background editor contract](docs/DECOR-EDITOR.md) and
 
 [![Open the repository in HACS](https://my.home-assistant.io/badges/hacs_repository.svg)](https://my.home-assistant.io/redirect/hacs_repository/?owner=Matysh&repository=houseplan-card&category=integration)
 
-House Plan is in the HACS default catalog — no custom repository needed.
+1. In HACS open **⋮ → Custom repositories**.
+2. Add `https://github.com/Matysh/houseplan-card` as an **Integration**.
+3. Install House Plan and restart Home Assistant.
+4. Open **Settings → Devices & services → Add integration → House Plan**.
 
-1. In HACS search for **House Plan** and install it.
-2. Restart Home Assistant.
-3. Open **Settings → Devices & services → Add integration → House Plan**.
-
-The sidebar page and optional dashboard cards are registered automatically.
-After installing or updating House Plan,
-restart Home Assistant and fully reload the page: `Ctrl+F5` on Windows/Linux or
-`Cmd+Shift+R` on macOS.
-
-#### Storage mode (Home Assistant default)
-
-No YAML is normally needed. If automatic registration did not make the card
-available, open **Settings → Dashboards → menu ⋮ → Resources → Add
-resource**, enter `/houseplan_files/houseplan-card.js`, and select **JavaScript
-module**.
-
-#### YAML resources mode (Home Assistant 2026.2+)
-
-To manage resources in `configuration.yaml` independently of the dashboard
-mode, use:
+The card is registered automatically. If you manage Lovelace resources
+manually, use the URL served by the integration:
 
 ```yaml
-lovelace:
-  resource_mode: yaml
-  resources:
-    - url: /houseplan_files/houseplan-card.js
-      type: module
+resources:
+  - url: /houseplan_files/houseplan-card.js
+    type: module
 ```
 
-#### Legacy Home Assistant 2024.6–2026.1
-
-Only for a full-YAML dashboard that is already managed in YAML, use:
-
-```yaml
-lovelace:
-  mode: yaml
-  resources:
-    - url: /houseplan_files/houseplan-card.js
-      type: module
-```
-
-`mode: yaml` changes the dashboard itself to YAML mode. Do not switch a storage
-dashboard to legacy YAML just for House Plan; use the Storage mode instructions
-above instead. Do not use the on-disk path inside `custom_components`; Home
-Assistant does not serve that path as a JavaScript module.
+Do not use the on-disk path inside `custom_components`; Home Assistant does not
+serve that path as a JavaScript module.
 
 ### Manual installation
 
-Copy the complete `custom_components/houseplan` release folder to
-`config/custom_components`, restart Home Assistant, and add the House Plan
-integration. Do not copy only `houseplan-card.js`: the card also uses an
-internal manifest and content-hashed modules from the same release.
+Copy `custom_components/houseplan` to `config/custom_components`, restart Home
+Assistant, and add the House Plan integration.
 
-### Open House Plan
+### Add the card
 
-After the integration is added, open **House Plan** in the Home Assistant
-sidebar. This full-page view is the primary entry point and needs no dashboard
-or YAML setup. It remembers the last space but always returns from another HA
-page in View rather than reopening an editor. Users without editing permission
-see the same live plan without editor controls.
-
-If the sidebar entry cannot be registered, the integration and existing
-dashboard cards continue to work; check **Settings → System → Repairs → System
-information → House Plan** after restarting and hard-refreshing HA.
-
-### Optional dashboard card
-
-Add the card only when House Plan must be embedded in a dashboard. In a Sections
-view it requests full width by default, while a manual size chosen in HA remains
-authoritative. Add it in the UI or as:
+Create a dashboard view (Panel works best) and add the card in the UI or as:
 
 ```yaml
 type: custom:houseplan-card
@@ -186,11 +135,8 @@ concurrent clients, but avoid editing the same object in two browsers at once.
 - [Full user guide](docs/USER-GUIDE.md)
 - [Mouse/touch/keyboard matrix](docs/USER-GUIDE.md#6-navigation-zoom-and-input)
 - [Plan tools](docs/USER-GUIDE.md#plan-tools-at-a-glance)
-- [Stairs and floor links](docs/STAIRS.md)
 - [Background editor](docs/DECOR-EDITOR.md)
 - [Robot vacuums](docs/VACUUM.md)
-- [Presence radars](docs/RADAR.md)
-- [PDF export](docs/PDF-EXPORT.md)
 - [Touch support](docs/TOUCH-SUPPORT.md)
 
 <!-- docs-section: support -->
@@ -203,4 +149,9 @@ concurrent clients, but avoid editing the same object in two browsers at once.
   Include the version, browser, logs and reproduction steps; private entity IDs
   may be replaced with fictional ones.
 
+Documentation screenshots are produced by the reproducible
+`npm run build && node demo/docs/capture.mjs` command using synthetic data only. Scenario version,
+source fingerprint and every image hash are recorded in the
+[screenshot index](docs/images/screenshots.json).
+
 License: [MIT](LICENSE).

README.ru.md

@@ -1,6 +1,6 @@
 # 🏠 House Plan — живой план дома для Home Assistant
 
-[![HACS Default](https://img.shields.io/badge/HACS-Default-41BDF5.svg)](https://github.com/hacs/integration)
+[![HACS Custom](https://img.shields.io/badge/HACS-Custom-41BDF5.svg)](https://github.com/hacs/integration)
 [![GitHub release](https://img.shields.io/github/v/release/Matysh/houseplan-card)](https://github.com/Matysh/houseplan-card/releases)
 [![CI](https://github.com/Matysh/houseplan-card/actions/workflows/validate.yml/badge.svg)](https://github.com/Matysh/houseplan-card/actions)
 [![Live demo](https://img.shields.io/badge/демо-попробовать-00c853?logo=homeassistant&logoColor=white)](https://demo.houseplan.tech)
@@ -12,9 +12,8 @@
 
 ## Дом целиком — одним взглядом
 
-House Plan превращает Home Assistant в живую карту дома. Откройте отдельный
-пункт **House Plan** в боковом меню Home Assistant, загрузите изображение плана
-или нарисуйте комнаты, свяжите их с зонами Home
+House Plan превращает Home Assistant в живую карту дома. Загрузите изображение
+плана или нарисуйте комнаты прямо на дашборде, свяжите их с зонами Home
 Assistant — и устройства появятся на плане автоматически. Сразу видно, где
 горит свет, открыта дверь, слишком холодно, слабый Zigbee-сигнал или сработал
 датчик протечки.
@@ -43,9 +42,6 @@ Assistant — и устройства появятся на плане авто
   а карточки комнат показывают температуру, влажность, свет и средний LQI.
 - **Свет и окружение.** Заливки комнат, Glow от ламп, тени от стен, дневной фон и
   солнечные лучи из окон.
-- **Плоский план или 2.5D.** Один переключатель в «Общие настройки ›
-  Отображение › Объёмный вид плана (2.5D)» показывает план с глубиной везде: приподнятые плитки устройств с мягкими
-  тенями и мягкая засветка солнцем; декор и цвета стен остаются вашими.
 - **Двери, окна, ворота и пылесосы.** Проёмы отражают реальные датчики и замки;
   робот показывает позицию, базу и пройденный путь.
 - **Несколько этажей и экранов.** Вкладки пространств, жесты переключения,
@@ -59,12 +55,11 @@ Assistant — и устройства появятся на плане авто
 
 ## Первая рабочая комната
 
-1. Установите интеграцию и откройте **House Plan** в боковом меню Home Assistant.
-2. Создайте первое **пространство**: загрузите SVG/PNG/JPG/WebP, возьмите уже
-   загруженное изображение либо выберите вариант без изображения, чтобы
-   нарисовать план вручную.
-3. В редакторе «План» выберите **Стены** и нарисуйте непрерывную цепочку по
-   периметру комнаты: когда она замкнёт область, откроется диалог комнаты.
+1. Установите интеграцию и добавьте карточку на дашборд.
+2. Создайте первое **пространство**: загрузите SVG/PNG/JPG/WebP либо выберите
+   вариант без изображения, чтобы нарисовать план вручную.
+3. В редакторе «План» выберите **Контур комнаты**, поставьте вершины и замкните
+   контур нажатием на первую точку.
 4. Назовите комнату и свяжите её с зоной Home Assistant. Для помещения без
    устройств выберите «Без зоны».
 5. Откройте «Устройства»: устройства связанной зоны уже размещены автоматически;
@@ -96,79 +91,31 @@ Assistant — и устройства появятся на плане авто
 
 [![Открыть репозиторий в HACS](https://my.home-assistant.io/badges/hacs_repository.svg)](https://my.home-assistant.io/redirect/hacs_repository/?owner=Matysh&repository=houseplan-card&category=integration)
 
-House Plan входит в основной каталог HACS — пользовательский репозиторий
-добавлять не нужно.
+1. В HACS откройте **⋮ → Пользовательские репозитории**.
+2. Добавьте `https://github.com/Matysh/houseplan-card` с типом **Интеграция**.
+3. Установите House Plan и перезапустите Home Assistant.
+4. Откройте **Настройки → Устройства и службы → Добавить интеграцию → House Plan**.
 
-1. Найдите **House Plan** в поиске HACS и установите.
-2. Перезапустите Home Assistant.
-3. Откройте **Настройки → Устройства и службы → Добавить интеграцию → House Plan**.
-
-Страница в боковом меню и дополнительные карточки для дашборда регистрируются
-автоматически. После установки или обновления
-House Plan перезапустите Home Assistant и полностью перезагрузите
-страницу: `Ctrl+F5` в Windows/Linux или `Cmd+Shift+R` в macOS.
-
-#### Режим Storage (по умолчанию в Home Assistant)
-
-Обычно YAML не нужен. Если авторегистрация не сделала карточку доступной,
-откройте **Настройки → Панели управления → меню ⋮ → Ресурсы → Добавить
-ресурс**, укажите `/houseplan_files/houseplan-card.js` и выберите тип
-**JavaScript-модуль**.
-
-#### YAML-ресурсы в Home Assistant 2026.2+
-
-Чтобы управлять ресурсами в `configuration.yaml` независимо от режима
-самой панели, используйте:
+Карточка регистрируется автоматически. Если ресурсы Lovelace управляются вручную,
+добавьте именно URL, который публикует интеграция:
 
 ```yaml
-lovelace:
-  resource_mode: yaml
-  resources:
-    - url: /houseplan_files/houseplan-card.js
-      type: module
+resources:
+  - url: /houseplan_files/houseplan-card.js
+    type: module
 ```
 
-#### Home Assistant 2024.6–2026.1: устаревший режим
-
-Только для панели, которая уже полностью управляется через YAML:
-
-```yaml
-lovelace:
-  mode: yaml
-  resources:
-    - url: /houseplan_files/houseplan-card.js
-      type: module
-```
-
-`mode: yaml` переводит в YAML-режим саму панель. Не переключайте
-storage-панель в устаревший YAML только ради House Plan; используйте
-инструкцию для Storage выше. Не используйте путь к файлу внутри
-`custom_components`: Home Assistant не публикует его как JavaScript-модуль.
+Не используйте путь к файлу внутри `custom_components`: Home Assistant не
+публикует его как JavaScript-модуль.
 
 ### Вручную
 
-Скопируйте всю папку `custom_components/houseplan` из релиза в
-`config/custom_components`, перезапустите Home Assistant и добавьте интеграцию
-House Plan. Одного `houseplan-card.js` недостаточно: карточке также нужны
-внутренний манифест и хешированные модули из того же релиза.
+Скопируйте `custom_components/houseplan` в `config/custom_components`,
+перезапустите Home Assistant и добавьте интеграцию House Plan.
 
-### Открытие House Plan
+### Добавление карточки
 
-После добавления интеграции откройте **House Plan** в боковом меню Home
-Assistant. Это основной полноэкранный способ работы: отдельный дашборд и YAML
-не нужны. Запоминается последнее пространство, но после перехода на другую
-страницу HA панель всегда возвращается в режим просмотра, а не в редактор.
-Пользователь без права редактирования видит тот же живой план без редакторов.
-
-Если пункт бокового меню зарегистрировать не удалось, интеграция и уже
-добавленные карточки на дашбордах продолжают работать. После перезапуска и
-жёсткого обновления HA проверьте состояние House Plan в системной информации.
-
-### Необязательная карточка для дашборда
-
-Добавляйте карточку, только если план нужно встроить в дашборд. В представлении
-Sections она по умолчанию занимает всю ширину; вручную выбранный в HA размер
-остаётся главным. Добавьте карточку через UI либо:
+Создайте представление дашборда (лучше Panel) и добавьте карточку через UI либо:
 
 ```yaml
 type: custom:houseplan-card
@@ -192,11 +139,8 @@ default_floor: ground
 - [Полное руководство пользователя](docs/USER-GUIDE.ru.md)
 - [Матрица mouse/touch/keyboard](docs/USER-GUIDE.ru.md#6-навигация-масштаб-и-жесты)
 - [Инструменты плана](docs/USER-GUIDE.ru.md#инструменты-плана-в-короткой-таблице)
-- [Лестницы и переходы между этажами](docs/STAIRS.md)
 - [Редактор подложки](docs/DECOR-EDITOR.md)
 - [Роботы-пылесосы](docs/VACUUM.md)
-- [Радары присутствия](docs/RADAR.md)
-- [Экспорт в PDF](docs/PDF-EXPORT.md)
 - [Поддержка touch](docs/TOUCH-SUPPORT.md)
 
 <!-- docs-section: support -->
@@ -209,4 +153,9 @@ default_floor: ground
   обновление страницы (`Ctrl+F5`). Приложите версию, браузер, логи и шаги
   воспроизведения; приватные entity ID можно заменить вымышленными.
 
+Скриншоты в документации получены воспроизводимой командой
+`npm run build && node demo/docs/capture.mjs` только на синтетических данных. Версия сценариев,
+fingerprint исходников и хеш каждого изображения находятся в
+[индексе снимков](docs/images/screenshots.json).
+
 Лицензия: [MIT](LICENSE).

THIRD_PARTY_NOTICES.md

@@ -1,59 +0,0 @@
-# Third-party notices
-
-## VMware Clarity Assets - `compass-line.svg`
-
-Source: <https://github.com/vmware-archive/clarity-assets/blob/bf6bdd0dd3f247f1a320d44d13fecdeda18c071c/icons/travel/compass-line.svg>
-
-Copyright (c) 2018 VMware, Inc.
-
-The MIT license (the "License") set forth below applies to all parts of the
-clarity-assets project. You may not use this file except in compliance with the
-License.
-
-MIT License
-
-Permission is hereby granted, free of charge, to any person obtaining a copy of
-this software and associated documentation files (the "Software"), to deal in
-the Software without restriction, including without limitation the rights to
-use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of
-the Software, and to permit persons to whom the Software is furnished to do so,
-subject to the following conditions:
-
-The above copyright notice and this permission notice shall be included in all
-copies or substantial portions of the Software.
-
-THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
-IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
-FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
-AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
-LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
-OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
-SOFTWARE.
-
-## Tabler Icons — summary panel outline icons
-
-Source: https://github.com/tabler/tabler-icons
-The settings, sidebar-right, eye, eye-off, plus and chevron paths were provided
-in the designer reference for #505 and are distributed as inline SVG paths.
-
-MIT License
-
-Copyright (c) 2020-2026 Paweł Kuna
-
-Permission is hereby granted, free of charge, to any person obtaining a copy
-of this software and associated documentation files (the "Software"), to deal
-in the Software without restriction, including without limitation the rights
-to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
-copies of the Software, and to permit persons to whom the Software is
-furnished to do so, subject to the following conditions:
-
-The above copyright notice and this permission notice shall be included in
-all copies or substantial portions of the Software.
-
-THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
-IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
-FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
-AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
-LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
-OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
-THE SOFTWARE.

assets/fonts/LICENSE

@@ -1,201 +0,0 @@
-                                 Apache License
-                           Version 2.0, January 2004
-                        http://www.apache.org/licenses/
-
-   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
-
-   1. Definitions.
-
-      "License" shall mean the terms and conditions for use, reproduction,
-      and distribution as defined by Sections 1 through 9 of this document.
-
-      "Licensor" shall mean the copyright owner or entity authorized by
-      the copyright owner that is granting the License.
-
-      "Legal Entity" shall mean the union of the acting entity and all
-      other entities that control, are controlled by, or are under common
-      control with that entity. For the purposes of this definition,
-      "control" means (i) the power, direct or indirect, to cause the
-      direction or management of such entity, whether by contract or
-      otherwise, or (ii) ownership of fifty percent (50%) or more of the
-      outstanding shares, or (iii) beneficial ownership of such entity.
-
-      "You" (or "Your") shall mean an individual or Legal Entity
-      exercising permissions granted by this License.
-
-      "Source" form shall mean the preferred form for making modifications,
-      including but not limited to software source code, documentation
-      source, and configuration files.
-
-      "Object" form shall mean any form resulting from mechanical
-      transformation or translation of a Source form, including but
-      not limited to compiled object code, generated documentation,
-      and conversions to other media types.
-
-      "Work" shall mean the work of authorship, whether in Source or
-      Object form, made available under the License, as indicated by a
-      copyright notice that is included in or attached to the work
-      (an example is provided in the Appendix below).
-
-      "Derivative Works" shall mean any work, whether in Source or Object
-      form, that is based on (or derived from) the Work and for which the
-      editorial revisions, annotations, elaborations, or other modifications
-      represent, as a whole, an original work of authorship. For the purposes
-      of this License, Derivative Works shall not include works that remain
-      separable from, or merely link (or bind by name) to the interfaces of,
-      the Work and Derivative Works thereof.
-
-      "Contribution" shall mean any work of authorship, including
-      the original version of the Work and any modifications or additions
-      to that Work or Derivative Works thereof, that is intentionally
-      submitted to Licensor for inclusion in the Work by the copyright owner
-      or by an individual or Legal Entity authorized to submit on behalf of
-      the copyright owner. For the purposes of this definition, "submitted"
-      means any form of electronic, verbal, or written communication sent
-      to the Licensor or its representatives, including but not limited to
-      communication on electronic mailing lists, source code control systems,
-      and issue tracking systems that are managed by, or on behalf of, the
-      Licensor for the purpose of discussing and improving the Work, but
-      excluding communication that is conspicuously marked or otherwise
-      designated in writing by the copyright owner as "Not a Contribution."
-
-      "Contributor" shall mean Licensor and any individual or Legal Entity
-      on behalf of whom a Contribution has been received by Licensor and
-      subsequently incorporated within the Work.
-
-   2. Grant of Copyright License. Subject to the terms and conditions of
-      this License, each Contributor hereby grants to You a perpetual,
-      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
-      copyright license to reproduce, prepare Derivative Works of,
-      publicly display, publicly perform, sublicense, and distribute the
-      Work and such Derivative Works in Source or Object form.
-
-   3. Grant of Patent License. Subject to the terms and conditions of
-      this License, each Contributor hereby grants to You a perpetual,
-      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
-      (except as stated in this section) patent license to make, have made,
-      use, offer to sell, sell, import, and otherwise transfer the Work,
-      where such license applies only to those patent claims licensable
-      by such Contributor that are necessarily infringed by their
-      Contribution(s) alone or by combination of their Contribution(s)
-      with the Work to which such Contribution(s) was submitted. If You
-      institute patent litigation against any entity (including a
-      cross-claim or counterclaim in a lawsuit) alleging that the Work
-      or a Contribution incorporated within the Work constitutes direct
-      or contributory patent infringement, then any patent licenses
-      granted to You under this License for that Work shall terminate
-      as of the date such litigation is filed.
-
-   4. Redistribution. You may reproduce and distribute copies of the
-      Work or Derivative Works thereof in any medium, with or without
-      modifications, and in Source or Object form, provided that You
-      meet the following conditions:
-
-      (a) You must give any other recipients of the Work or
-          Derivative Works a copy of this License; and
-
-      (b) You must cause any modified files to carry prominent notices
-          stating that You changed the files; and
-
-      (c) You must retain, in the Source form of any Derivative Works
-          that You distribute, all copyright, patent, trademark, and
-          attribution notices from the Source form of the Work,
-          excluding those notices that do not pertain to any part of
-          the Derivative Works; and
-
-      (d) If the Work includes a "NOTICE" text file as part of its
-          distribution, then any Derivative Works that You distribute must
-          include a readable copy of the attribution notices contained
-          within such NOTICE file, excluding those notices that do not
-          pertain to any part of the Derivative Works, in at least one
-          of the following places: within a NOTICE text file distributed
-          as part of the Derivative Works; within the Source form or
-          documentation, if provided along with the Derivative Works; or,
-          within a display generated by the Derivative Works, if and
-          wherever such third-party notices normally appear. The contents
-          of the NOTICE file are for informational purposes only and
-          do not modify the License. You may add Your own attribution
-          notices within Derivative Works that You distribute, alongside
-          or as an addendum to the NOTICE text from the Work, provided
-          that such additional attribution notices cannot be construed
-          as modifying the License.
-
-      You may add Your own copyright statement to Your modifications and
-      may provide additional or different license terms and conditions
-      for use, reproduction, or distribution of Your modifications, or
-      for any such Derivative Works as a whole, provided Your use,
-      reproduction, and distribution of the Work otherwise complies with
-      the conditions stated in this License.
-
-   5. Submission of Contributions. Unless You explicitly state otherwise,
-      any Contribution intentionally submitted for inclusion in the Work
-      by You to the Licensor shall be under the terms and conditions of
-      this License, without any additional terms or conditions.
-      Notwithstanding the above, nothing herein shall supersede or modify
-      the terms of any separate license agreement you may have executed
-      with Licensor regarding such Contributions.
-
-   6. Trademarks. This License does not grant permission to use the trade
-      names, trademarks, service marks, or product names of the Licensor,
-      except as required for reasonable and customary use in describing the
-      origin of the Work and reproducing the content of the NOTICE file.
-
-   7. Disclaimer of Warranty. Unless required by applicable law or
-      agreed to in writing, Licensor provides the Work (and each
-      Contributor provides its Contributions) on an "AS IS" BASIS,
-      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
-      implied, including, without limitation, any warranties or conditions
-      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
-      PARTICULAR PURPOSE. You are solely responsible for determining the
-      appropriateness of using or redistributing the Work and assume any
-      risks associated with Your exercise of permissions under this License.
-
-   8. Limitation of Liability. In no event and under no legal theory,
-      whether in tort (including negligence), contract, or otherwise,
-      unless required by applicable law (such as deliberate and grossly
-      negligent acts) or agreed to in writing, shall any Contributor be
-      liable to You for damages, including any direct, indirect, special,
-      incidental, or consequential damages of any character arising as a
-      result of this License or out of the use or inability to use the
-      Work (including but not limited to damages for loss of goodwill,
-      work stoppage, computer failure or malfunction, or any and all
-      other commercial damages or losses), even if such Contributor
-      has been advised of the possibility of such damages.
-
-   9. Accepting Warranty or Additional Liability. While redistributing
-      the Work or Derivative Works thereof, You may choose to offer,
-      and charge a fee for, acceptance of support, warranty, indemnity,
-      or other liability obligations and/or rights consistent with this
-      License. However, in accepting such obligations, You may act only
-      on Your own behalf and on Your sole responsibility, not on behalf
-      of any other Contributor, and only if You agree to indemnify,
-      defend, and hold each Contributor harmless for any liability
-      incurred by, or claims asserted against, such Contributor by reason
-      of your accepting any such warranty or additional liability.
-
-   END OF TERMS AND CONDITIONS
-
-   APPENDIX: How to apply the Apache License to your work.
-
-      To apply the Apache License to your work, attach the following
-      boilerplate notice, with the fields enclosed by brackets "[]"
-      replaced with your own identifying information. (Don't include
-      the brackets!)  The text should be enclosed in the appropriate
-      comment syntax for the file format. We also recommend that a
-      file or class name and description of purpose be included on the
-      same "printed page" as the copyright notice for easier
-      identification within third-party archives.
-
-   Copyright [yyyy] [name of copyright owner]
-
-   Licensed under the Apache License, Version 2.0 (the "License");
-   you may not use this file except in compliance with the License.
-   You may obtain a copy of the License at
-
-       http://www.apache.org/licenses/LICENSE-2.0
-
-   Unless required by applicable law or agreed to in writing, software
-   distributed under the License is distributed on an "AS IS" BASIS,
-   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
-   See the License for the specific language governing permissions and
-   limitations under the License.

assets/furniture/houseplan-0.4.0/LICENSE.md

@@ -1,21 +0,0 @@
-MIT License
-
-Copyright (c) 2026 JB (justbusiness)
-
-Permission is hereby granted, free of charge, to any person obtaining a copy
-of this software and associated documentation files (the "Software"), to deal
-in the Software without restriction, including without limitation the rights
-to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
-copies of the Software, and to permit persons to whom the Software is
-furnished to do so, subject to the following conditions:
-
-The above copyright notice and this permission notice shall be included in all
-copies or substantial portions of the Software.
-
-THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
-IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
-FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
-AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
-LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
-OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
-SOFTWARE.

assets/furniture/houseplan-0.4.0/README.md

@@ -1,37 +0,0 @@
-# House Plan furniture pack 0.4.0
-
-Canonical source artwork for the built-in House Plan furniture library.
-
-- `svg/menu/`: 33 front-view category illustrations used only by the lazy
-  editor bundle.
-- `svg/plan/`: 60 top-view drawings used on the plan.
-- `pack.json`: stable ids, category links, default dimensions and names. The
-  filename deliberately avoids the `*manifest.json` suffix reserved by HACS.
-
-This release replaces pack 0.3.0 together with its 12 retained code-drawn
-primitives: every public symbol is now designer artwork, and `computer`,
-`hood`, `oven` and `cactus` are new ids (#593).
-
-The original author, Sergey Matyunin (`Matysh`), granted House Plan permission
-to use, modify and distribute all 93 SVG files under the repository MIT
-License without separate UI attribution in
-[issue #593](https://github.com/Matysh/houseplan-card/issues/593#issuecomment-5739841899).
-
-The reviewed source archive is `houseplan-furniture-0.4.0.zip`, attached to
-[issue #593](https://github.com/Matysh/houseplan-card/issues/593), with SHA-256
-`69BA5E0C398542D59F24269F637F57B8EBF31C2836C9D493F084AD29AB299FDE`.
-
-`LICENSE.md` of this pack carries the copyright line `JB (justbusiness)`. That
-is the same author under his own domain, not a third party; the authoritative
-spelling of the name is Sergey Matyunin (Сергей Матюнин), fixed 2026-08-29 by
-the owner's decision in issue #369.
-
-One field differs from the archive on purpose: `symbols[cactus].menu_icon` is
-`plant`, not `exercise`. The `exercise` category tile draws an exercise
-machine, so opening it onto a cactus would misdescribe the palette. `exercise`
-therefore stays an empty, hidden category and 32 of the 33 categories are
-populated (owner's decision in #593).
-
-The editable source is linked from `pack.json`. Generated TypeScript must
-not be edited by hand; run `npm run furniture:generate` after changing this
-directory.

assets/furniture/houseplan-0.4.0/svg/menu/air_conditioner.svg

@@ -1,3 +0,0 @@
-<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 110 110">
-  <path d="M85 71.5 L85 63 M25 71.5 L25 63 M25 71.5 L89.5 71.5 C90.8807 71.5 92 70.3807 92 69 L92 41.5 C92 40.1193 90.8807 39 89.5 39 L20.5 39 C19.1193 39 18 40.1193 18 41.5 L18 69 C18 70.3807 19.1193 71.5 20.5 71.5 L25 71.5 Z M85 63 C85 61.6193 83.8807 60.5 82.5 60.5 L27.5 60.5 C26.1193 60.5 25 61.6193 25 63 M85 63 L85 66.5 L25 66.5 L25 63" fill="none" stroke="currentColor" stroke-width="1.5" stroke-linecap="round" stroke-linejoin="round"/>
-</svg>

assets/furniture/houseplan-0.4.0/svg/menu/armchair.svg

@@ -1,3 +0,0 @@
-<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 110 110">
-  <path d="M77.5 48.5 L77.5 39 C77.5 33.4772 73.0228 29 67.5 29 L42.5 29 C36.9772 29 32.5 33.4772 32.5 39 L32.5 48.5205 M77.5 48.5 C80.8137 48.5 83.5 51.1863 83.5 54.5 C83.5 57.1123 81.8302 59.3334 79.5 60.1572 L79.5 71.5 C79.5 73.7091 77.7091 75.5 75.5 75.5 M77.5 48.5 C74.2576 48.5 71.617 51.072 71.5049 54.2871 C71.5012 54.3576 71.5 54.4286 71.5 54.5 L71.5 61.75 M38 61.75 L38 54 C38 53.2396 37.7873 52.5291 37.4189 51.9238 C36.5228 50.0421 34.6765 48.7002 32.5 48.5205 M32.5 48.5205 C32.3351 48.5069 32.1684 48.5 32 48.5 M75.5 75.5 L34 75.5 M75.5 75.5 L72.5 75.5 M34 75.5 C31.7909 75.5 30 73.7091 30 71.5 L30 60.1572 C27.6698 59.3334 26 57.1123 26 54.5 C26 51.1863 28.6863 48.5 32 48.5 M34 75.5 L36.5 75.5 M32 48.5 C34.3914 48.5 36.4549 49.8996 37.4189 51.9238 M38 61.75 C38 64.3734 40.1266 66.5 42.75 66.5 L66.75 66.5 C69.3734 66.5 71.5 64.3734 71.5 61.75 M38 61.75 C38 59.1266 40.1266 57 42.75 57 L66.75 57 C69.3734 57 71.5 59.1266 71.5 61.75 M36.5 75.5 L44.5 75.5 M36.5 75.5 L36.5 80.5 C36.5 81.3284 37.1716 82 38 82 L41.3921 82 C42.0506 82 42.6321 81.5705 42.8258 80.9411 L44.5 75.5 M44.5 75.5 L64.5 75.5 M72.5 75.5 L64.5 75.5 M72.5 75.5 L72.5 80.5 C72.5 81.3284 71.8284 82 71 82 L67.6079 82 C66.9494 82 66.3679 81.5705 66.1742 80.9411 L64.5 75.5" fill="none" stroke="currentColor" stroke-width="1.5" stroke-linecap="round" stroke-linejoin="round"/>
-</svg>

assets/furniture/houseplan-0.4.0/svg/menu/bathtub.svg

@@ -1,3 +0,0 @@
-<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 110 110">
-  <path d="M28 74.8457 L28 80 C28 80.8284 28.6716 81.5 29.5 81.5 L32.8921 81.5 C33.5506 81.5 34.1321 81.0705 34.3258 80.4411 L35.6923 76 M28.0191 74.8558 C28.0127 74.8524 28.0063 74.8491 28 74.8457 C25.4198 73.4833 23.483 71.0169 22.8673 67.9996 M19.5 51.5 L90 51.5 M19.5 51.5 C18.1193 51.5 17 50.3807 17 49 C17 47.6193 18.1193 46.5 19.5 46.5 M19.5 51.5 L22.8673 67.9996 M90 51.5 C91.3807 51.5 92.5 50.3807 92.5 49 C92.5 47.6193 91.3807 46.5 90 46.5 M90 51.5 L86.6327 67.9996 C85.9778 71.2088 83.8285 73.7948 81 75.0922 M90 46.5 L19.5 46.5 M90 46.5 L20 46.5 M19.5 46.5 L20 46.5 M22.8673 67.9996 C23.4846 71.0243 25.4293 73.4954 28.0191 74.8558 M30 36 L30 34 C30 32.6739 29.4732 31.4021 28.5355 30.4645 C27.5979 29.5268 26.3261 29 25 29 C23.6739 29 22.4021 29.5268 21.4645 30.4645 C20.5268 31.4021 20 32.6739 20 34 L20 46.5 M81 75.0922 C79.7247 75.6771 78.3114 76 76.8347 76 L73.3077 76 M81 75.0922 L81 80 C81 80.8284 80.3284 81.5 79.5 81.5 L76.1079 81.5 C75.4494 81.5 74.8679 81.0705 74.6742 80.4411 L73.3077 76 M73.3077 76 L35.6923 76 M35.6923 76 L32.6653 76 C31.1128 76 29.6303 75.643 28.3047 75 C28.2086 74.9534 28.1134 74.9053 28.0191 74.8558" fill="none" stroke="currentColor" stroke-width="1.5" stroke-linecap="round" stroke-linejoin="round"/>
-</svg>

assets/furniture/houseplan-0.4.0/svg/menu/bed.svg

@@ -1,3 +0,0 @@
-<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 110 110">
-  <path d="M16 75.5 L24 75.5 M16 75.5 L16 80.5 C16 81.3284 16.6716 82 17.5 82 L20.8921 82 C21.5506 82 22.1321 81.5705 22.3258 80.9411 L24 75.5 M16 75.5 L15 75.5 M24 75.5 L86.5 75.5 M94.5 75.5 L86.5 75.5 M94.5 75.5 L94.5 80.5 C94.5 81.3284 93.8284 82 93 82 L89.6079 82 C88.9494 82 88.3679 81.5705 88.1742 80.9411 L86.5 75.5 M94.5 75.5 L95.5 75.5 M88 50.1296 L88 31.5 C88 30.1193 86.8807 29 85.5 29 L25 29 C23.6193 29 22.5 30.1193 22.5 31.5 L22.5 50.1296 M87.9383 50.1068 C87.9589 50.1143 87.9795 50.1219 88 50.1296 C91.7967 51.5483 94.5 55.2085 94.5 59.5 M22.5617 50.1068 C22.5411 50.1143 22.5205 50.1219 22.5 50.1296 C18.7033 51.5483 16 55.2085 16 59.5 M94.5 65.5 L94.5 59.5 M94.5 65.5 L16 65.5 M94.5 65.5 L95.5 65.5 M16 65.5 L16 59.5 M16 65.5 L15 65.5 M84.5 49.5 L26 49.5 M84.5 49.5 L80 49.5 M94.5 59.5 C94.5 55.1853 91.7674 51.5088 87.9383 50.1068 C86.8662 49.7142 85.7081 49.5 84.5 49.5 M26 49.5 L30.5 49.5 M16 59.5 C16 55.1853 18.7326 51.5088 22.5617 50.1068 C23.6338 49.7142 24.7919 49.5 26 49.5 M15 75.5 L95.5 75.5 M15 75.5 C14.4477 75.5 14 75.0523 14 74.5 L14 66.5 C14 65.9477 14.4477 65.5 15 65.5 M95.5 75.5 C96.0523 75.5 96.5 75.0523 96.5 74.5 L96.5 66.5 C96.5 65.9477 96.0523 65.5 95.5 65.5 M95.5 65.5 L15 65.5 M51.5 49.5 L51.5 45.5 C51.5 42.7386 49.2614 40.5 46.5 40.5 L35.5 40.5 C32.7386 40.5 30.5 42.7386 30.5 45.5 L30.5 49.5 M51.5 49.5 L30.5 49.5 M51.5 49.5 L59 49.5 M80 49.5 L80 45.5 C80 42.7386 77.7614 40.5 75 40.5 L64 40.5 C61.2386 40.5 59 42.7386 59 45.5 L59 49.5 M80 49.5 L59 49.5" fill="none" stroke="currentColor" stroke-width="1.5" stroke-linecap="round" stroke-linejoin="round"/>
-</svg>

assets/furniture/houseplan-0.4.0/svg/menu/bidet.svg

@@ -1,3 +0,0 @@
-<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 110 110">
-  <path d="M46 67.5 L64.5 67.5 M46 67.5 C40.4772 67.5 36 63.0228 36 57.5 L36 53 M46 67.5 C45.4902 67.5 44.9893 67.4618 44.5 67.3882 L44.5 79.5 C44.5 80.0523 44.9477 80.5 45.5 80.5 L65 80.5 C65.5523 80.5 66 80.0523 66 79.5 L66 67.3882 C65.5107 67.4618 65.0098 67.5 64.5 67.5 M64.5 67.5 C70.0229 67.5 74.5 63.0228 74.5 57.5 L74.5 53 M74.5 53 L74.5 47.5 C74.5 46.9477 74.0523 46.5 73.5 46.5 M74.5 53 L36 53 M36 53 L36 47.5 C36 46.9477 36.4477 46.5 37 46.5 M73.5 46.5 L37 46.5 M73.5 46.5 L60 46.5 M37 46.5 L50.5 46.5 M51.5 40 L59 40 M51.5 40 C50.9477 40 50.5 40.4477 50.5 41 L50.5 46.5 M51.5 40 L53 40 M59 40 C59.5523 40 60 40.4477 60 41 L60 46.5 M59 40 L57.5 40 M60 46.5 L50.5 46.5 M57.5 40 L57.5 30 C57.5 29.4477 57.0523 29 56.5 29 L54 29 C53.4477 29 53 29.4477 53 30 M57.5 40 L53 40 M53 40 L53 30 M53 40 L53 36 M53 30 L53 31.5 M53 31.5 L49 31.5 C48.4477 31.5 48 31.9477 48 32.5 L48 35 C48 35.5523 48.4477 36 49 36 L53 36 M53 31.5 L53 36" fill="none" stroke="currentColor" stroke-width="1.5" stroke-linecap="round" stroke-linejoin="round"/>
-</svg>

assets/furniture/houseplan-0.4.0/svg/menu/boiler.svg

@@ -1,3 +0,0 @@
-<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 110 110">
-  <path d="M51.5 81.5 L51.5 86 C51.5 86.5523 51.0523 87 50.5 87 L47.5 87 C46.9477 87 46.5 86.5523 46.5 86 L46.5 81.5 M51.5 81.5 L46.5 81.5 M51.5 81.5 L59 81.5 M46.5 81.5 L44 81.5 M64 81.5 L64 86 C64 86.5523 63.5523 87 63 87 L60 87 C59.4477 87 59 86.5523 59 86 L59 81.5 M64 81.5 L59 81.5 M64 81.5 L66.5 81.5 M74.5 73 L74.5 73.5 C74.5 77.9183 70.9183 81.5 66.5 81.5 M44 81.5 C39.5817 81.5 36 77.9183 36 73.5 L36 73 L36 31 C36 26.5817 39.5817 23 44 23 L66.5 23 C70.9183 23 74.5 26.5817 74.5 31 L74.5 73 M74.5 73 L36 73 M66.5 81.5 L44 81.5 M55 42.5 L58.5 39 M62.5 42.5 C62.5 46.366 59.366 49.5 55.5 49.5 C51.634 49.5 48.5 46.366 48.5 42.5 C48.5 38.634 51.634 35.5 55.5 35.5 C59.366 35.5 62.5 38.634 62.5 42.5 Z" fill="none" stroke="currentColor" stroke-width="1.5" stroke-linecap="round" stroke-linejoin="round"/>
-</svg>

assets/furniture/houseplan-0.4.0/svg/menu/chair.svg

@@ -1,3 +0,0 @@
-<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 110 110">
-  <path d="M41.25 60.5 L68.75 60.5 M68.75 60.5 C70.5449 60.5 72 59.0449 72 57.25 C72 55.6281 70.8119 54.2836 69.2585 54.0395 C69.0928 54.0135 68.923 54 68.75 54 L41.25 54 C41.077 54 40.9072 54.0135 40.7415 54.0395 C39.1881 54.2836 38 55.6281 38 57.25 C38 59.0449 39.4551 60.5 41.25 60.5 M41.25 60.5 L46 60.5 M68.75 60.5 L64 60.5 M64 60.5 L69.5 60.5 L69.5 82 C69.5 82.8284 68.8284 83.5 68 83.5 L67.3752 83.5 C66.5972 83.5 65.9483 82.9051 65.8809 82.1299 L64 60.5 Z M64 60.5 L46 60.5 M46 60.5 L40.5 60.5 L40.5 82 C40.5 82.8284 41.1716 83.5 42 83.5 L42.6248 83.5 C43.4028 83.5 44.0517 82.9051 44.1191 82.1299 L46 60.5 Z M40.7415 54.0395 C40.5847 53.5546 40.5 53.0372 40.5 52.5 L40.5 39.5 C40.5 32.5964 46.0964 27 53 27 L57 27 C63.9036 27 69.5 32.5964 69.5 39.5 L69.5 52.5 C69.5 53.0372 69.4153 53.5546 69.2585 54.0395" fill="none" stroke="currentColor" stroke-width="1.5" stroke-linecap="round" stroke-linejoin="round"/>
-</svg>

assets/furniture/houseplan-0.4.0/svg/menu/coffee_table.svg

@@ -1,3 +0,0 @@
-<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 110 110">
-  <path d="M85.2381 55 L86.5 55 C87.0523 55 87.5 54.5523 87.5 54 L87.5 51 L84.6598 43.4847 C84.2586 42.5818 83.3633 42 82.3753 42 L26.6247 42 C25.6367 42 24.7414 42.5818 24.3402 43.4847 L21.5 51 L21.5 54 C21.5 54.5523 21.9477 55 22.5 55 L25 55 M87.5 51 L21.5 51 M25 55 L25 66.5 C25 67.3284 25.6716 68 26.5 68 L27.2113 68 C27.983 68 28.6288 67.4144 28.7041 66.6464 L29.8459 55 M25 55 L29.8459 55 M29.8459 55 L80.3922 55 M80.3922 55 L81.534 66.6464 C81.6093 67.4144 82.2551 68 83.0268 68 L83.7381 68 C84.5665 68 85.2381 67.3284 85.2381 66.5 L85.2381 55 M80.3922 55 L85.2381 55" fill="none" stroke="currentColor" stroke-width="1.5" stroke-linecap="round" stroke-linejoin="round"/>
-</svg>

assets/furniture/houseplan-0.4.0/svg/menu/computer.svg

@@ -1,3 +0,0 @@
-<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 110 110">
-  <path d="M43 65 L48 65 M43 65 L24.5 65 C23.1193 65 22 63.8807 22 62.5 L22 40.5 C22 39.1193 23.1193 38 24.5 38 L64.5 38 C65.8807 38 67 39.1193 67 40.5 L67 62.5 C67 63.8807 65.8807 65 64.5 65 L48 65 M43 65 L43 72 M48 65 L48 72 M37 72 L43 72 M54.0711 72 L48 72 M76 60 L84 60 M76 43 L84 43 M35 53 L35 46 L39.5 46 C40.4283 46 41.3185 46.3687 41.9749 47.0251 C42.6313 47.6815 43 48.5717 43 49.5 C43 50.4283 42.6312 51.3185 41.9749 51.9749 C41.3185 52.6313 40.4283 53 39.5 53 L35 53 Z M35 53 L35 56 M54.5355 54.5355 C53.8363 55.2348 52.9454 55.711 51.9755 55.9039 C51.0055 56.0969 50.0002 55.9978 49.0866 55.6194 C48.173 55.241 47.3921 54.6001 46.8427 53.7779 C46.2932 52.9556 46 51.9889 46 51 C46 50.0111 46.2932 49.0444 46.8427 48.2221 C47.3921 47.3999 48.173 46.759 49.0866 46.3806 C50.0002 46.0022 51.0055 45.9031 51.9755 46.0961 C52.9454 46.289 53.8363 46.7652 54.5355 47.4645 M48 72 L43 72 M74.5 72 L85.5 72 C86.8807 72 88 70.8807 88 69.5 L88 40.5 C88 39.1193 86.8807 38 85.5 38 L74.5 38 C73.1193 38 72 39.1193 72 40.5 L72 69.5 C72 70.8807 73.1193 72 74.5 72 Z" fill="none" stroke="currentColor" stroke-width="1.5" stroke-linecap="round" stroke-linejoin="round"/>
-</svg>

assets/furniture/houseplan-0.4.0/svg/menu/cooktop.svg

@@ -1,3 +0,0 @@
-<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 110 110">
-  <path d="M25 31.5 C25 30.1193 26.1193 29 27.5 29 L82.5 29 C83.8807 29 85 30.1193 85 31.5 L85 78.5 C85 79.8807 83.8807 81 82.5 81 L27.5 81 C26.1193 81 25 79.8807 25 78.5 L25 31.5 Z M49.5 66.5 C49.5 70.9183 45.9183 74.5 41.5 74.5 C37.0817 74.5 33.5 70.9183 33.5 66.5 C33.5 62.0817 37.0817 58.5 41.5 58.5 C45.9183 58.5 49.5 62.0817 49.5 66.5 Z M76 43.5 C76 47.9183 72.4183 51.5 68 51.5 C63.5817 51.5 60 47.9183 60 43.5 C60 39.0817 63.5817 35.5 68 35.5 C72.4183 35.5 76 39.0817 76 43.5 Z M73 66.5 C73 69.2614 70.7614 71.5 68 71.5 C65.2386 71.5 63 69.2614 63 66.5 C63 63.7386 65.2386 61.5 68 61.5 C70.7614 61.5 73 63.7386 73 66.5 Z M49.5 43.5 C49.5 47.9183 45.9183 51.5 41.5 51.5 C37.0817 51.5 33.5 47.9183 33.5 43.5 C33.5 39.0817 37.0817 35.5 41.5 35.5 C45.9183 35.5 49.5 39.0817 49.5 43.5 Z" fill="none" stroke="currentColor" stroke-width="1.5" stroke-linecap="round" stroke-linejoin="round"/>
-</svg>

assets/furniture/houseplan-0.4.0/svg/menu/dining_table.svg

@@ -1,3 +0,0 @@
-<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 110 110">
-  <path d="M26.875 47 L23.5 47 C22.9477 47 22.5 46.5523 22.5 46 L22.5 43 L24.8802 35.5939 C25.2539 34.633 26.1791 34 27.2102 34 L83.7898 34 C84.8209 34 85.7462 34.633 86.1198 35.5939 L88.5 43 L88.5 46 C88.5 46.5523 88.0523 47 87.5 47 L84.125 47 M22.5 43 L88.5 43 M78.875 47 L84.742 73.8205 C84.8926 74.5092 85.5024 75 86.2073 75 L86.7474 75 C87.6682 75 88.3716 74.1781 88.2294 73.2684 L84.125 47 M78.875 47 L84.125 47 M78.875 47 L32.125 47 M32.125 47 L26.258 73.8205 C26.1074 74.5092 25.4976 75 24.7927 75 L24.2526 75 C23.3318 75 22.6284 74.1781 22.7706 73.2684 L26.875 47 M32.125 47 L26.875 47" fill="none" stroke="currentColor" stroke-width="1.5" stroke-linecap="round" stroke-linejoin="round"/>
-</svg>

assets/furniture/houseplan-0.4.0/svg/menu/dishwasher.svg

@@ -1,3 +0,0 @@
-<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 110 110">
-  <path d="M81 82.5 L81 27.5 M81 82.5 C81 83.8807 79.8807 85 78.5 85 L31.5 85 C30.1193 85 29 83.8807 29 82.5 L29 55.5 M81 82.5 L81 40 M81 27.5 C81 26.1193 79.8807 25 78.5 25 L31.5 25 C30.1193 25 29 26.1193 29 27.5 M81 27.5 L81 40 M29 27.5 L29 55.5 M29 27.5 L29 40 M81 40 C81 38.6193 79.8807 37.5 78.5 37.5 L31.5 37.5 C30.1193 37.5 29 38.6193 29 40 M29 40 L29 55.5 M35.75 31 L45.25 31 M55.9943 55 C55.9943 55 54.6654 56.8105 54.5153 58.1429 C54.3169 59.9042 56.1139 60.6968 55.9943 62.4643 C55.8942 63.9429 54.5153 66 54.5153 66 M60.4943 55 C60.4943 55 59.1654 56.8105 59.0153 58.1429 C58.8169 59.9042 60.6139 60.6968 60.4943 62.4643 C60.3942 63.9429 59.0153 66 59.0153 66 M50.9943 55 C50.9943 55 49.6654 56.8105 49.5153 58.1429 C49.3169 59.9042 51.1139 60.6968 50.9943 62.4643 C50.8942 63.9429 49.5153 66 49.5153 66 M72 60.5 C72 69.8888 64.3888 77.5 55 77.5 C45.6112 77.5 38 69.8888 38 60.5 C38 51.1112 45.6112 43.5 55 43.5 C64.3888 43.5 72 51.1112 72 60.5 Z M66.5 60.5 C66.5 66.8513 61.3513 72 55 72 C48.6487 72 43.5 66.8513 43.5 60.5 C43.5 54.1487 48.6487 49 55 49 C61.3513 49 66.5 54.1487 66.5 60.5 Z M69.5 31 C69.5 32.1046 68.6046 33 67.5 33 C66.3954 33 65.5 32.1046 65.5 31 C65.5 29.8954 66.3954 29 67.5 29 C68.6046 29 69.5 29.8954 69.5 31 Z M77 31 C77 32.1046 76.1046 33 75 33 C73.8954 33 73 32.1046 73 31 C73 29.8954 73.8954 29 75 29 C76.1046 29 77 29.8954 77 31 Z" fill="none" stroke="currentColor" stroke-width="1.5" stroke-linecap="round" stroke-linejoin="round"/>
-</svg>

assets/furniture/houseplan-0.4.0/svg/menu/dryer.svg

@@ -1,3 +0,0 @@
-<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 110 110">
-  <path d="M81 82.5 L81 27.5 M81 82.5 C81 83.8807 79.8807 85 78.5 85 L31.5 85 C30.1193 85 29 83.8807 29 82.5 L29 55.5 M81 82.5 L81 40 M81 27.5 C81 26.1193 79.8807 25 78.5 25 L31.5 25 C30.1193 25 29 26.1193 29 27.5 M81 27.5 L81 40 M29 27.5 L29 55.5 M29 27.5 L29 40 M81 40 C81 38.6193 79.8807 37.5 78.5 37.5 L31.5 37.5 C30.1193 37.5 29 38.6193 29 40 M29 40 L29 55.5 M35.75 31 L45.25 31 M55.9943 55 C55.9943 55 54.6654 56.8105 54.5153 58.1429 C54.3169 59.9042 56.1139 60.6968 55.9943 62.4643 C55.8942 63.9429 54.5153 66 54.5153 66 M60.4943 55 C60.4943 55 59.1654 56.8105 59.0153 58.1429 C58.8169 59.9042 60.6139 60.6968 60.4943 62.4643 C60.3942 63.9429 59.0153 66 59.0153 66 M50.9943 55 C50.9943 55 49.6654 56.8105 49.5153 58.1429 C49.3169 59.9042 51.1139 60.6968 50.9943 62.4643 C50.8942 63.9429 49.5153 66 49.5153 66 M72 60.5 C72 69.8888 64.3888 77.5 55 77.5 C45.6112 77.5 38 69.8888 38 60.5 C38 51.1112 45.6112 43.5 55 43.5 C64.3888 43.5 72 51.1112 72 60.5 Z M66.5 60.5 C66.5 66.8513 61.3513 72 55 72 C48.6487 72 43.5 66.8513 43.5 60.5 C43.5 54.1487 48.6487 49 55 49 C61.3513 49 66.5 54.1487 66.5 60.5 Z M69.5 31 C69.5 32.1046 68.6046 33 67.5 33 C66.3954 33 65.5 32.1046 65.5 31 C65.5 29.8954 66.3954 29 67.5 29 C68.6046 29 69.5 29.8954 69.5 31 Z M77 31 C77 32.1046 76.1046 33 75 33 C73.8954 33 73 32.1046 73 31 C73 29.8954 73.8954 29 75 29 C76.1046 29 77 29.8954 77 31 Z" fill="none" stroke="currentColor" stroke-width="1.5" stroke-linecap="round" stroke-linejoin="round"/>
-</svg>

assets/furniture/houseplan-0.4.0/svg/menu/exercise.svg

@@ -1,3 +0,0 @@
-<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 110 110">
-  <path d="M55.091 60.072 L65.7741 35.5156 M42.2119 56.2083 L55.091 60.072 L60.8511 61.8001 L66.5032 63.4957 C70.733 64.7646 73.6297 68.6579 73.6297 73.074 L73.6297 76.2635 L29.3385 76.2635 L29.3385 65.7866 C29.3385 60.9371 32.7227 57.0804 37.0256 56.051 C38.5108 55.6956 40.1055 55.6771 41.7081 56.0709 M41.7081 56.0709 C41.876 56.1122 42.044 56.1579 42.2119 56.2083 L60.8511 61.8001 M71.9311 35.5156 L76.4108 35.5156 C78.2451 35.5156 79.9321 34.5112 80.8064 32.8987 L83.8375 27.308 C84.3011 26.4529 83.9993 25.384 83.1569 24.8976 C82.2982 24.4018 81.2002 24.696 80.7045 25.5547 L77.8652 30.4723 C77.3293 31.4005 76.3389 31.9723 75.2671 31.9723 L65.6573 31.9723 C64.6788 31.9723 63.8856 32.7655 63.8856 33.744 C63.8856 34.7224 64.6788 35.5156 65.6573 35.5156 L65.7741 35.5156 M71.9311 35.5156 C71.9603 35.7673 71.9261 36.0298 71.8188 36.2793 L60.8511 61.8001 M71.9311 35.5156 L65.7741 35.5156 M41.7081 56.0709 L38.03 42.6022 M37.0256 56.051 L33.3529 42.6022 M38.03 42.6022 L33.3529 42.6022 L29.7814 42.6022 C28.5583 42.6022 27.5668 41.6107 27.5668 40.3876 C27.5668 39.1646 28.5583 38.1731 29.7814 38.1731 L41.2971 38.1731 C42.5202 38.1731 43.5117 39.1646 43.5117 40.3876 C43.5117 41.6107 42.5202 42.6022 41.2971 42.6022 L38.03 42.6022 Z M25.7952 78.921 C25.7952 77.4533 26.985 76.2635 28.4526 76.2635 L74.5155 76.2636 C75.9832 76.2636 77.173 77.4533 77.173 78.921 C77.173 80.3887 75.9832 81.5785 74.5155 81.5785 L28.4526 81.5785 C26.985 81.5785 25.7952 80.3887 25.7952 78.921 Z M29.3385 81.5785 L29.3385 84.5677 C29.3385 85.3962 30.01 86.0677 30.8385 86.0677 L33.6379 86.0677 C34.2512 86.0677 34.8028 85.6943 35.0306 85.1248 L36.5002 81.5785 L29.3385 81.5785 Z M73.6297 81.5785 L73.6297 84.5677 C73.6297 85.3962 72.9581 86.0677 72.1297 86.0677 L69.3303 86.0677 C68.717 86.0677 68.1654 85.6943 67.9376 85.1248 L66.5002 81.5785 L73.6297 81.5785 Z M45.2833 66.0766 C45.2833 68.7673 43.102 70.9486 40.4113 70.9486 C37.7205 70.9486 35.5392 68.7673 35.5392 66.0766 C35.5392 63.3858 37.7205 61.2045 40.4113 61.2045 C43.102 61.2045 45.2833 63.3858 45.2833 66.0766 Z" fill="none" stroke="currentColor" stroke-width="1.5" stroke-linecap="round" stroke-linejoin="round"/>
-</svg>

assets/furniture/houseplan-0.4.0/svg/menu/fireplace.svg

@@ -1,3 +0,0 @@
-<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 110 110">
-  <path d="M71.1884 73.8943 L71.1884 50.4399 C71.1884 47.6784 68.9498 45.4399 66.1884 45.4399 L43.1445 45.4399 C40.3831 45.4399 38.1445 47.6784 38.1445 50.4399 L38.1445 73.8942 M38.1445 73.8942 L26.7031 73.8942 L26.7031 34.4252 L82.6629 34.4252 L82.6629 73.8942 L71.1884 73.8943 L38.1445 73.8942 Z M62.0101 62.8795 L47.3239 62.8795 C45.8031 62.8795 44.5703 64.1124 44.5703 65.6332 C44.5703 67.154 45.8031 68.3868 47.3239 68.3868 M47.3239 68.3868 C45.8031 68.3868 44.5703 69.6195 44.5703 71.1403 C44.5703 72.6611 45.8031 73.894 47.3239 73.894 M47.3239 68.3868 C48.8447 68.3868 50.0776 69.6195 50.0776 71.1403 C50.0776 72.6611 48.8447 73.894 47.3239 73.894 M47.3239 68.3868 L61.9918 68.3868 M47.3239 73.894 L62.0101 73.894 C63.5309 73.894 64.7637 72.6611 64.7637 71.1403 C64.7637 69.6242 63.5385 68.3945 62.0243 68.3869 M62.0114 68.3869 C62.0049 68.3869 61.9983 68.3869 61.9918 68.3868 M62.0114 68.3869 C62.0157 68.3869 62.02 68.3869 62.0243 68.3869 M62.0114 68.3869 L62.0243 68.3869 M62.0114 68.3869 L61.9918 68.3868 M61.9918 68.3868 C60.48 68.3763 59.2578 67.1475 59.2578 65.6332 C59.2578 64.1124 60.4906 62.8796 62.0114 62.8796 C63.5322 62.8796 64.7651 64.1124 64.7651 65.6332 C64.7651 67.1498 63.5392 68.3799 62.0243 68.3869 M61.9918 68.3868 L62.0101 68.3868 C62.0148 68.3868 62.0195 68.3868 62.0243 68.3869 M24 81.6962 L85.3341 81.6962 C85.8864 81.6962 86.3341 81.2485 86.3341 80.6962 L86.3341 74.8942 C86.3341 74.3419 85.8864 73.8942 85.3341 73.8942 L24 73.8942 C23.4477 73.8942 23 74.3419 23 74.8942 L23 80.6962 C23 81.2485 23.4477 81.6962 24 81.6962 Z M24 34.4252 L85.3341 34.4252 C85.8864 34.4252 86.3341 33.9775 86.3341 33.4252 L86.3341 29 C86.3341 28.4477 85.8864 28 85.3341 28 L24 28 C23.4477 28 23 28.4477 23 29 L23 33.4252 C23 33.9775 23.4477 34.4252 24 34.4252 Z" fill="none" stroke="currentColor" stroke-width="1.5" stroke-linecap="round" stroke-linejoin="round"/>
-</svg>

assets/furniture/houseplan-0.4.0/svg/menu/fridge.svg

@@ -1,3 +0,0 @@
-<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 110 110">
-  <path d="M35.5 87 C34.1193 87 33 85.8807 33 84.5 M35.5 87 L74.5 87 M35.5 87 L35.5 90.5 C35.5 91.0523 35.9477 91.5 36.5 91.5 L73.5 91.5 C74.0523 91.5 74.5 91.0523 74.5 90.5 L74.5 87 M33 84.5 L33 20.5 M33 84.5 L33 46.5 M77.5 84.5 L77.5 20.5 M77.5 84.5 C77.5 85.8807 76.3807 87 75 87 L74.5 87 M77.5 84.5 L77.5 46.5 M77.5 20.5 C77.5 19.1193 76.3807 18 75 18 L35.5 18 C34.1193 18 33 19.1193 33 20.5 M77.5 20.5 L77.5 46.5 M33 20.5 L33 46.5 M33 46.5 L77.5 46.5 M38.5 41 L38.5 31.5 M38.5 62 L38.5 52.5" fill="none" stroke="currentColor" stroke-width="1.5" stroke-linecap="round" stroke-linejoin="round"/>
-</svg>

assets/furniture/houseplan-0.4.0/svg/menu/hood.svg

@@ -1,3 +0,0 @@
-<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 110 110">
-  <path d="M66 57 L83 69 L83 71.5 C83 72.8807 81.8807 74 80.5 74 L29.5 74 C28.1193 74 27 72.8807 27 71.5 L27 69 L44 57 M44 57 L66 57 M44 57 L44 37.5 C44 36.1193 45.1193 35 46.5 35 L63.5 35 C64.8807 35 66 36.1193 66 37.5 L66 57 M83 69 L27 69" fill="none" stroke="currentColor" stroke-width="1.5" stroke-linecap="round" stroke-linejoin="round"/>
-</svg>

assets/furniture/houseplan-0.4.0/svg/menu/kitchen_cabinet.svg

@@ -1,3 +0,0 @@
-<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 110 110">
-  <path d="M72 84.95 L72 88 C72 88.5523 71.5523 89 71 89 L39 89 C38.4477 89 38 88.5523 38 88 L38 84.95 M55 20 L71.5 20 C72.8807 20 74 21.1193 74 22.5 L74 39.5 C74 40.8807 72.8807 42 71.5 42 L55 42 M55 20 L55 42 M55 20 L38.5 20 C37.1193 20 36 21.1193 36 22.5 L36 39.5 C36 40.8807 37.1193 42 38.5 42 L55 42 M59 33 L59 38 M51 33 L51 38 M55 85 L71.5 85 C72.8807 85 74 83.8807 74 82.5 L74 65.5 C74 64.1193 72.8807 63 71.5 63 L55 63 M55 85 L55 63 M55 85 L38.5 85 C37.1193 85 36 83.8807 36 82.5 L36 65.5 C36 64.1193 37.1193 63 38.5 63 L55 63 M67 67 L62 67 M48 67 L43 67" fill="none" stroke="currentColor" stroke-width="1.5" stroke-linecap="round" stroke-linejoin="round"/>
-</svg>

assets/furniture/houseplan-0.4.0/svg/menu/kitchen_sink.svg

@@ -1,3 +0,0 @@
-<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 110 110">
-  <path d="M49 54 L49 59 M51.5 37.5 L44 37.5 M51.5 37.5 C52.0523 37.5 52.5 37.9477 52.5 38.5 L52.5 44 M51.5 37.5 L48 37.5 M44 37.5 C43.4477 37.5 43 37.9477 43 38.5 L43 44 M44 37.5 L48 37.5 M43 44 L21.5 44 C20.1193 44 19 45.1193 19 46.5 L19 81.5 C19 82.8807 20.1193 84 21.5 84 L89.5 84 C90.8807 84 92 82.8807 92 81.5 L92 46.5 C92 45.1193 90.8807 44 89.5 44 L52.5 44 M43 44 L52.5 44 M58 33 L58 31 C58 29.6739 57.4732 28.4021 56.5355 27.4645 C55.5979 26.5268 54.3261 26 53 26 C51.6739 26 50.4021 26.5268 49.4645 27.4645 C48.5268 28.4021 48 29.6739 48 31 L48 37.5 M62 54 L62 59 M26 50 L52.5 50 C53.0523 50 53.5 50.4477 53.5 51 L53.5 77 C53.5 77.5523 53.0523 78 52.5 78 L26 78 C25.4477 78 25 77.5523 25 77 L25 51 C25 50.4477 25.4477 50 26 50 Z M58.5 50 L85 50 C85.5523 50 86 50.4477 86 51 L86 77 C86 77.5523 85.5523 78 85 78 L58.5 78 C57.9477 78 57.5 77.5523 57.5 77 L57.5 51 C57.5 50.4477 57.9477 50 58.5 50 Z" fill="none" stroke="currentColor" stroke-width="1.5" stroke-linecap="round" stroke-linejoin="round"/>
-</svg>

assets/furniture/houseplan-0.4.0/svg/menu/nightstand.svg

@@ -1,3 +0,0 @@
-<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 110 110">
-  <path d="M34.5 76 C33.1193 76 32 74.8807 32 73.5 M34.5 76 L41.2308 76 M34.5 76 C34.3288 76 34.1616 75.9828 34 75.95 L34 78.5 C34 79.3284 34.6716 80 35.5 80 L38.8921 80 C39.5506 80 40.1321 79.5705 40.3258 78.9411 L41.2308 76 M32 73.5 L32 33 M32 73.5 L32 57.5 M78 73.5 L78 33 M69.2692 76 L75.5 76 C75.8556 76 76.1938 75.9258 76.5 75.792 C77.383 75.4062 78 74.5252 78 73.5 M78 73.5 L78 57.5 M78 33 C78 31.6193 76.8807 30.5 75.5 30.5 L34.5 30.5 C33.1193 30.5 32 31.6193 32 33 M78 33 L78 39.5 M32 33 L32 39.5 M32 39.5 L78 39.5 M32 39.5 L32 57.5 M78 39.5 L78 57.5 M78 57.5 L32 57.5 M50.5 48.5 L60 48.5 M50.5 66 L60 66 M41.2308 76 L69.2692 76 M69.2692 76 L70.1742 78.9411 C70.3679 79.5705 70.9494 80 71.6079 80 L75 80 C75.8284 80 76.5 79.3284 76.5 78.5 L76.5 75.792" fill="none" stroke="currentColor" stroke-width="1.5" stroke-linecap="round" stroke-linejoin="round"/>
-</svg>

assets/furniture/houseplan-0.4.0/svg/menu/oven.svg

@@ -1,3 +0,0 @@
-<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 110 110">
-  <path d="M29 76 C29 77.3807 30.1193 78.5 31.5 78.5 L78.5 78.5 C79.8807 78.5 81 77.3807 81 76 M29 76 L29 40 M29 76 L29 82.5 C29 83.8807 30.1193 85 31.5 85 L78.5 85 C79.8807 85 81 83.8807 81 82.5 L81 76 M81 76 L81 40 M81 40 C81 38.6193 79.8807 37.5 78.5 37.5 L31.5 37.5 C30.1193 37.5 29 38.6193 29 40 M81 40 L81 27.5 C81 26.1193 79.8807 25 78.5 25 L31.5 25 C30.1193 25 29 26.1193 29 27.5 L29 40 M35.75 31 L45.25 31 M43 42 L67 42 M40.5 72 L69.5 72 C70.8807 72 72 70.8807 72 69.5 L72 49.5 C72 48.1193 70.8807 47 69.5 47 L40.5 47 C39.1193 47 38 48.1193 38 49.5 L38 69.5 C38 70.8807 39.1193 72 40.5 72 Z M69.5 31 C69.5 32.1046 68.6046 33 67.5 33 C66.3954 33 65.5 32.1046 65.5 31 C65.5 29.8954 66.3954 29 67.5 29 C68.6046 29 69.5 29.8954 69.5 31 Z M77 31 C77 32.1046 76.1046 33 75 33 C73.8954 33 73 32.1046 73 31 C73 29.8954 73.8954 29 75 29 C76.1046 29 77 29.8954 77 31 Z" fill="none" stroke="currentColor" stroke-width="1.5" stroke-linecap="round" stroke-linejoin="round"/>
-</svg>

assets/furniture/houseplan-0.4.0/svg/menu/plant.svg

@@ -1,3 +0,0 @@
-<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 110 110">
-  <path d="M55.7064 55.8805 L55.7064 52.9357 M55.7064 52.9357 C56.839 47.0461 62.7965 41.9801 68.6182 37.5322 M55.7064 52.9357 C50.7678 48.7899 47.7236 46.7763 41.6621 43.8748 M67.4992 61.3174 L65.9151 75.8488 C65.7779 77.1181 64.7063 78.0801 63.4296 78.0801 L48.4373 78.0801 C47.1606 78.0801 46.089 77.1181 45.9518 75.8488 L44.3593 61.3174 L67.4992 61.3174 Z M60.2363 44.7807 C58.4234 36.1732 66.8047 29.604 76.9989 31.869 C76.9989 40.024 68.3904 48.6318 60.2363 44.7807 Z M50.476 49.9288 C51.9926 41.2641 43.391 34.9863 33.2805 37.5996 C33.5602 45.7498 42.4589 54.0573 50.476 49.9288 Z M43.1152 61.3174 L68.7509 61.3174 C69.3031 61.3174 69.7509 60.8697 69.7509 60.3174 L69.7509 56.8809 C69.7509 56.3286 69.3031 55.8809 68.7509 55.8809 L43.1152 55.8809 C42.5629 55.8809 42.1152 56.3286 42.1152 56.8809 L42.1152 60.3174 C42.1152 60.8697 42.5629 61.3174 43.1152 61.3174 Z" fill="none" stroke="currentColor" stroke-width="1.5" stroke-linecap="round" stroke-linejoin="round"/>
-</svg>

assets/furniture/houseplan-0.4.0/svg/menu/rug.svg

@@ -1,3 +0,0 @@
-<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 110 110">
-  <path d="M90.2693 33.8735 L84.648 33.8735 M25.6208 33.8735 L19.9995 33.8735 M90.2693 39.0264 L84.648 39.0264 M25.6208 39.0264 L19.9995 39.0264 M90.2693 44.1792 L84.648 44.1792 M25.6208 44.1792 L19.9995 44.1792 M90.2693 49.332 L84.648 49.332 M25.6208 49.332 L19.9995 49.332 M90.2693 54.4854 L84.648 54.4854 M25.6208 54.4854 L19.9995 54.4854 M90.2693 59.6382 L84.648 59.6382 M25.6208 59.6382 L19.9995 59.6382 M90.2693 64.791 L84.648 64.791 M25.6208 64.791 L19.9995 64.791 M90.2693 69.9438 L84.648 69.9438 M25.6208 69.9438 L19.9995 69.9438 M90.2693 75.0967 L84.648 75.0967 M25.6208 75.0967 L19.9995 75.0967 M28.121 32 L82.145 32 C83.5257 32 84.645 33.1193 84.645 34.5 L84.645 74.939 C84.645 76.3197 83.5257 77.439 82.145 77.439 L28.121 77.439 C26.7403 77.439 25.621 76.3197 25.621 74.939 L25.621 34.5 C25.621 33.1193 26.7403 32 28.121 32 Z M29.8369 32 L29.8369 77.439 M80.4302 32 L80.4302 77.439 M37.8005 54.4852 L55.6014 46.0532 L73.4022 54.4852 L55.6014 62.9172 L37.8005 54.4852 Z" fill="none" stroke="currentColor" stroke-width="1.5" stroke-linecap="round" stroke-linejoin="round"/>
-</svg>

assets/furniture/houseplan-0.4.0/svg/menu/shelving.svg

@@ -1,3 +0,0 @@
-<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 110 110">
-  <path d="M64 58.5 L64 47 C64 46.4477 64.4477 46 65 46 L68 46 C68.5523 46 69 46.4477 69 47 M64 58.5 L69 58.5 M64 58.5 L28 58.5 L28 39 L35.5 39 M69 58.5 L69 47 M69 58.5 L69 44.5 M69 58.5 L76 58.5 M69 47 L69 44.5 M52.5 39 L52.5 27.5 C52.5 26.9477 52.0523 26.5 51.5 26.5 L48.5 26.5 C47.9477 26.5 47.5 26.9477 47.5 27.5 M52.5 39 L47.5 39 M52.5 39 L81 39 L81 58.5 L76 58.5 M47.5 39 L47.5 27.5 M47.5 39 L47.5 25 M47.5 39 L40.5 39 M47.5 27.5 L47.5 25 M40.5 39 L40.5 27.5 M40.5 39 L40.5 25 M40.5 39 L35.5 39 M35.5 39 L35.5 27.5 C35.5 26.9477 35.9477 26.5 36.5 26.5 L39.5 26.5 C40.0523 26.5 40.5 26.9477 40.5 27.5 M40.5 27.5 L40.5 25 M49 72 L36.5 72 M50.5 72 L36.5 72 C35.9477 72 35.5 71.5523 35.5 71 L35.5 68.5 C35.5 67.9477 35.9477 67.5 36.5 67.5 L49 67.5 C49.5523 67.5 50 67.9477 50 68.5 L50 71 C50 71.5523 49.5523 72 49 72 M50.5 78 C51.0523 78 51.5 77.5523 51.5 77 L51.5 73 C51.5 72.4477 51.0523 72 50.5 72 L49 72 M36.5 72 C35.9477 72 35.5 72.4477 35.5 73 L35.5 77 C35.5 77.5523 35.9477 78 36.5 78 M76 58.5 L76 44.5 C76 43.9477 75.5523 43.5 75 43.5 L70 43.5 C69.4477 43.5 69 43.9477 69 44.5 M47.5 25 C47.5 24.4477 47.0523 24 46.5 24 L41.5 24 C40.9477 24 40.5 24.4477 40.5 25 M50.5 78 L36.5 78 M50.5 78 L81 78 L81 85 L28 85 L28 78 L36.5 78 M28 89.5 L28 23 C28 21.6193 29.1193 20.5 30.5 20.5 L78.5 20.5 C79.8807 20.5 81 21.6193 81 23 L81 89.5" fill="none" stroke="currentColor" stroke-width="1.5" stroke-linecap="round" stroke-linejoin="round"/>
-</svg>

assets/furniture/houseplan-0.4.0/svg/menu/shower.svg

@@ -1,3 +0,0 @@
-<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 110 110">
-  <path d="M39 84 L39 31.7143 C39 25.245 44.2564 20 50.75 20 C56.4663 20 61.2394 24.5462 62.1824 29.0091 M51.5 39.25 C51.5 33.5891 56.0891 29 61.75 29 C67.4109 29 72 33.5891 72 39.25 L51.5 39.25 M54.75 44.25 L54.75 46.75 M62 44.25 L62 46.75 M69.25 44.25 L69.25 46.75 M54.75 50.5 L54.75 53 M62 50.5 L62 53 M69.25 50.5 L69.25 53 M54.75 56.75 L54.75 59.25 M62 56.75 L62 59.25 M69.25 56.75 L69.25 59.25 M54.75 63 L54.75 65.5 M62 63 L62 65.5 M69.25 63 L69.25 65.5 M31 84 L80 84 C80.5523 84 81 84.4477 81 85 L81 88 C81 88.5523 80.5523 89 80 89 L31 89 C30.4477 89 30 88.5523 30 88 L30 85 C30 84.4477 30.4477 84 31 84" fill="none" stroke="currentColor" stroke-width="1.5" stroke-linecap="round" stroke-linejoin="round"/>
-</svg>

assets/furniture/houseplan-0.4.0/svg/menu/sink.svg

@@ -1,3 +0,0 @@
-<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 110 110">
-  <path d="M51 41.5 L58.5 41.5 M51 41.5 C50.4477 41.5 50 41.9477 50 42.5 L50 48 M51 41.5 L55 41.5 M58.5 41.5 C59.0523 41.5 59.5 41.9477 59.5 42.5 L59.5 48 M58.5 41.5 L55 41.5 M59.5 48 L77 48 C78.3807 48 79.5 49.1193 79.5 50.5 L79.5 57 C79.5 62.5228 75.0228 67 69.5 67 L40 67 C34.4772 67 30 62.5228 30 57 L30 50.5 C30 49.1193 31.1193 48 32.5 48 L50 48 M59.5 48 L50 48 M45 37 L45 35 C45 33.6739 45.5268 32.4021 46.4645 31.4645 C47.4021 30.5268 48.6739 30 50 30 C51.3261 30 52.5979 30.5268 53.5355 31.4645 C54.4732 32.4021 55 33.6739 55 35 L55 41.5 M45 80 L64.5 80 C65.0523 80 65.5 79.5523 65.5 79 L65.5 67 L44 67 L44 79 C44 79.5523 44.4477 80 45 80 Z" fill="none" stroke="currentColor" stroke-width="1.5" stroke-linecap="round" stroke-linejoin="round"/>
-</svg>

assets/furniture/houseplan-0.4.0/svg/menu/sofa.svg

@@ -1,3 +0,0 @@
-<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 110 110">
-  <path d="M88.5 44.6689 L88.5 34 C88.5 31.2386 86.2614 29 83.5 29 L59.5 29 C56.7386 29 54.5 31.2386 54.5 34 M88.5 44.6689 C89.2354 44.2435 90.0893 44 91 44 M88.5 44.6689 C88.3992 44.7272 88.3006 44.7889 88.2045 44.8539 M54.5 61.75 L54.5 34 M54.5 61.75 C54.5 64.3734 52.3734 66.5 49.75 66.5 L25.25 66.5 C22.6266 66.5 20.5 64.3734 20.5 61.75 M54.5 61.75 C54.5 59.1266 52.3734 57 49.75 57 L25.25 57 C24.6761 57 24.1261 57.1018 23.6168 57.2882 M54.5 61.75 C54.5 64.3734 56.6266 66.5 59.25 66.5 L83.75 66.5 C86.3734 66.5 88.5 64.3734 88.5 61.75 M88.5 61.75 C88.5 59.9118 87.4558 58.3175 85.9283 57.5278 C85.8889 57.5075 85.8493 57.4877 85.8093 57.4684 C85.1863 57.1682 84.4878 57 83.75 57 L59.25 57 C56.6266 57 54.5 59.1266 54.5 61.75 M54.5 34 C54.5 31.2386 52.2614 29 49.5 29 L25.5 29 C22.7386 29 20.5 31.2386 20.5 34 L20.5 44.416 M20.5 44.416 C19.8875 44.1484 19.2111 44 18.5 44 M20.5 44.416 C22.2659 45.1876 23.5 46.9497 23.5 49 M18.5 44 C21.2614 44 23.5 46.2386 23.5 49 M18.5 44 L18 44 C15.2386 44 13 46.2386 13 49 L13 70.5 C13 73.2614 15.2386 75.5 18 75.5 M23.5 49 L23.5 57.3328 M23.5 57.3328 C21.7427 58.0295 20.5 59.7446 20.5 61.75 M23.5 57.3328 C23.5387 57.3174 23.5776 57.3026 23.6168 57.2882 M91 44 C89.9645 44 89.0025 44.3148 88.2045 44.8539 C86.8744 45.7525 86 47.2741 86 49 L86 57.5657 M85.9283 57.5278 C85.9523 57.5402 85.9762 57.5528 86 57.5657 C87.4884 58.3677 88.5 59.9407 88.5 61.75 M91 44 L91.5 44 C94.2614 44 96.5 46.2386 96.5 49 L96.5 70.5 C96.5 73.2614 94.2614 75.5 91.5 75.5 M91.5 75.5 L18 75.5 M91.5 75.5 L90.5 75.5 M18 75.5 L18.5 75.5 M20.5 61.75 C20.5 59.7005 21.798 57.9542 23.6168 57.2882 M18.5 75.5 L26.5 75.5 M18.5 75.5 L18.5 80.5 C18.5 81.3284 19.1716 82 20 82 L23.3921 82 C24.0506 82 24.6321 81.5705 24.8258 80.9411 L26.5 75.5 M26.5 75.5 L82.5 75.5 M90.5 75.5 L82.5 75.5 M90.5 75.5 L90.5 80.5 C90.5 81.3284 89.8284 82 89 82 L85.6079 82 C84.9494 82 84.3679 81.5705 84.1742 80.9411 L82.5 75.5" fill="none" stroke="currentColor" stroke-width="1.5" stroke-linecap="round" stroke-linejoin="round"/>
-</svg>

assets/furniture/houseplan-0.4.0/svg/menu/stairs.svg

@@ -1,3 +0,0 @@
-<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 110 110">
-  <path d="M73.4707 46.8057 L73.4707 28.5242 M73.4707 46.8057 L73.1504 46.8057 M73.4707 46.8057 L82.6039 46.8057 M73.4707 28.5242 L73.425 28.5242 M73.4707 28.5242 L75.6731 28.5242 M62.8987 54.2946 L62.8987 36.7397 M61.5762 61.7837 L61.5762 55.2944 C61.5762 54.7421 62.0239 54.2944 62.5762 54.2944 L62.8987 54.2946 L72.1504 54.2945 M52.3262 61.7837 L52.3262 45.1306 M52.3262 61.7837 L52.0039 61.7837 M52.3262 61.7837 L61.5762 61.7837 M62.8987 36.7397 L52.3262 45.1306 L42.1934 53.1725 L31.6211 61.5632 M42.1934 69.2725 L42.1934 53.1725 M42.1934 69.2725 L41.873 69.2725 M83.6035 69.2725 L83.6024 69.2725 L51.0039 69.2725 L42.1934 69.2725 M83.6031 76.7612 L83.6031 83.25 C83.6031 83.8023 83.1554 84.25 82.6031 84.25 L31.6231 84.2499 M41.873 69.2725 L83.6035 69.2725 L83.6031 76.7612 M83.6031 76.7612 L31.6231 76.7612 M31.6231 76.7612 L40.873 76.7613 L83.6031 76.7612 M31.6231 84.2499 L27.7773 84.2499 C27.2251 84.2499 26.7773 83.8021 26.7773 83.2499 L26.7773 57.4971 C26.7773 56.9448 27.2251 56.4971 27.7773 56.4971 L28.9352 56.4971 M31.6231 84.2499 L31.6231 76.7612 M31.6231 76.7612 L31.6211 61.5632 L31.6231 56.4971 M29.0212 56.4971 L31.6231 56.4971 L31.6228 57.2227 M31.6211 61.5632 L62.8987 36.7397 M31.6211 61.5632 L31.6228 57.2227 M73.425 28.5242 L75.6731 28.5242 M73.425 28.5242 C73.3119 28.5242 73.202 28.5624 73.1134 28.6328 L62.8987 36.7397 M75.6731 28.5242 C76.6463 28.5242 77.4352 27.7353 77.4352 26.7621 C77.4352 25.7889 76.6463 25 75.6731 25 L71.9495 25 C71.7935 25 71.6421 25.0532 71.5204 25.1508 L31.6228 57.2227 M41.873 69.2725 C41.3208 69.2725 40.873 69.7202 40.873 70.2725 L40.873 76.7613 M52.0039 61.7837 L83.6024 61.7837 M52.0039 61.7837 C51.4516 61.7837 51.0039 62.2314 51.0039 62.7837 L51.0039 69.2725 M83.6022 54.2944 L83.6024 61.7837 L83.6024 69.2725 M83.6024 61.7837 L61.5762 61.7837 M83.6022 54.2944 L83.6039 47.8057 C83.6039 47.2534 83.1562 46.8057 82.6039 46.8057 M83.6022 54.2944 L72.1504 54.2945 M73.1504 46.8057 L82.6039 46.8057 M73.1504 46.8057 C72.5981 46.8057 72.1504 47.2534 72.1504 47.8057 L72.1504 54.2945 M28.9352 56.4971 C28.9495 56.4973 28.9638 56.4974 28.9782 56.4974 C28.9925 56.4974 29.0069 56.4973 29.0212 56.4971 M28.9352 56.4971 C27.2519 56.4741 25.8945 55.1024 25.8945 53.4137 C25.8945 51.7107 27.2751 50.3301 28.9782 50.3301 C30.6812 50.3301 32.0618 51.7107 32.0618 53.4137 C32.0618 55.1024 30.7044 56.4741 29.0212 56.4971 M28.9352 56.4971 L29.0212 56.4971" fill="none" stroke="currentColor" stroke-width="1.5" stroke-linecap="round" stroke-linejoin="round"/>
-</svg>

assets/furniture/houseplan-0.4.0/svg/menu/toilet.svg

@@ -1,3 +0,0 @@
-<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 110 110">
-  <path d="M64.5372 72.1021 L67.6892 84.7575 C67.847 85.3886 67.3696 86 66.7191 86 L37.6483 86 C37.0414 86 36.5743 85.4636 36.6578 84.8624 L38.9999 68 C40.0716 64 32.5 64.5 32 57 L32 26.5 C32 25.1193 33.1193 24 34.5 24 L45 24 C46.3807 24 47.5 25.1193 47.5 26.5 L47.5 52 M32 57 L47.5 57 M47.5 52 L76.5 52 C77.8807 52 79 53.1193 79 54.5 L79 57 M47.5 52 L47.5 57 M54.9999 71.75 C58.5528 72.6096 61.7379 72.6416 64.5372 72.1021 C73.95 70.2877 79 62.0101 79 57 M79 57 L47.5 57" fill="none" stroke="currentColor" stroke-width="1.5" stroke-linecap="round" stroke-linejoin="round"/>
-</svg>

assets/furniture/houseplan-0.4.0/svg/menu/tv.svg

@@ -1,3 +0,0 @@
-<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 110 110">
-  <path d="M23.5 31 L86 31 C87.3807 31 88.5 32.1193 88.5 33.5 L88.5 67.5 C88.5 68.8807 87.3807 70 86 70 L23.5 70 C22.1193 70 21 68.8807 21 67.5 L21 33.5 C21 32.1193 22.1193 31 23.5 31 M50 70 L50 78 M59.5 70 L59.5 78 M40 78 L70 78 M42.5466 45.9951 L52.5466 45.9951 M47.5466 45.9951 L47.5 56.0336 M56.75 45.5 L61.75 55.5 L66.75 45.5" fill="none" stroke="currentColor" stroke-width="1.5" stroke-linecap="round" stroke-linejoin="round"/>
-</svg>

assets/furniture/houseplan-0.4.0/svg/menu/wardrobe.svg

@@ -1,3 +0,0 @@
-<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 110 110">
-  <path d="M54.5 20.5 L30.5 20.5 C29.1193 20.5 28 21.6193 28 23 L28 82.5 C28 83.8807 29.1193 85 30.5 85 L54.5 85 M54.5 20.5 L54.5 85 M54.5 20.5 L78.5 20.5 C79.8807 20.5 81 21.6193 81 23 L81 82.5 C81 83.8807 79.8807 85 78.5 85 L54.5 85 M79 84.95 L79 88.5 C79 89.0523 78.5523 89.5 78 89.5 L31 89.5 C30.4477 89.5 30 89.0523 30 88.5 L30 84.95 M50.5 48 L50.5 57.5 M58.5 48 L58.5 57.5" fill="none" stroke="currentColor" stroke-width="1.5" stroke-linecap="round" stroke-linejoin="round"/>
-</svg>

assets/furniture/houseplan-0.4.0/svg/menu/washer.svg

@@ -1,3 +0,0 @@
-<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 110 110">
-  <path d="M81 40 C81 38.6193 79.8807 37.5 78.5 37.5 L31.5 37.5 C30.1193 37.5 29 38.6193 29 40 M35.75 31 L45.25 31 M31.5 85 L78.5 85 C79.8807 85 81 83.8807 81 82.5 L81 55.5 L81 27.5 C81 26.1193 79.8807 25 78.5 25 L31.5 25 C30.1193 25 29 26.1193 29 27.5 L29 56 L29 82.5 C29 83.8807 30.1193 85 31.5 85 Z M72 60.5 C72 69.8888 64.3888 77.5 55 77.5 C45.6112 77.5 38 69.8888 38 60.5 C38 51.1112 45.6112 43.5 55 43.5 C64.3888 43.5 72 51.1112 72 60.5 Z M66.5 60.5 C66.5 66.8513 61.3513 72 55 72 C48.6487 72 43.5 66.8513 43.5 60.5 C43.5 54.1487 48.6487 49 55 49 C61.3513 49 66.5 54.1487 66.5 60.5 Z M69.5 31 C69.5 32.1046 68.6046 33 67.5 33 C66.3954 33 65.5 32.1046 65.5 31 C65.5 29.8954 66.3954 29 67.5 29 C68.6046 29 69.5 29.8954 69.5 31 Z M77 31 C77 32.1046 76.1046 33 75 33 C73.8954 33 73 32.1046 73 31 C73 29.8954 73.8954 29 75 29 C76.1046 29 77 29.8954 77 31 Z" fill="none" stroke="currentColor" stroke-width="1.5" stroke-linecap="round" stroke-linejoin="round"/>
-</svg>

assets/furniture/houseplan-0.4.0/svg/menu/work_table.svg

@@ -1,3 +0,0 @@
-<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 110 110">
-  <path d="M68.5 61 L68.5 73.5 C68.5 74.3284 69.1716 75 70 75 L87 75 C87.8284 75 88.5 74.3284 88.5 73.5 L88.5 61 L88.4844 47 M26.4844 47 L26.4844 73.5 C26.4844 74.3284 25.8128 75 24.9844 75 L23.9844 75 C23.1559 75 22.4844 74.3284 22.4844 73.5 L22.4844 47 L22.4844 43 L24.866 35.5974 C25.2388 34.6346 26.165 34 27.1974 34 L83.7743 34 C84.8054 34 85.7307 34.633 86.1044 35.5939 L88.4844 43 L88.4844 47 M88.4844 47 L68.5 47 M68.5 47 L68.5 61 M68.5 47 L26.4844 47 M68.5 61 L88.5 61 M76.5 51 L80.5 51 M88.4844 43 L22.4844 43 M22.4844 47 L26.4844 47 M76.5 65 L80.5 65" fill="none" stroke="currentColor" stroke-width="1.5" stroke-linecap="round" stroke-linejoin="round"/>
-</svg>

assets/furniture/houseplan-0.4.0/svg/plan/ac.svg

@@ -1,3 +0,0 @@
-<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 90 25">
-  <path d="M34.875 14.7505 C35.2252 14.9053 35.6091 14.9906 36 15.0005 C36.4382 15.0087 36.872 14.9219 37.2641 14.7477 C37.656 14.5735 37.9944 14.317 38.25 14.0005 C38.5056 13.684 38.844 13.4276 39.2359 13.2534 C39.628 13.0791 40.0618 12.9924 40.5 13.0005 C40.9382 12.9924 41.372 13.0791 41.7641 13.2534 C42.156 13.4276 42.4944 13.684 42.75 14.0005 C43.0056 14.317 43.344 14.5735 43.7359 14.7477 C44.128 14.9219 44.5618 15.0087 45 15.0005 C45.4382 15.0087 45.872 14.9219 46.2641 14.7477 C46.656 14.5735 46.9944 14.317 47.25 14.0005 C47.5056 13.684 47.844 13.4276 48.2359 13.2534 C48.628 13.0791 49.0618 12.9924 49.5 13.0005 C49.9382 12.9924 50.372 13.0791 50.7641 13.2534 C51.156 13.4276 51.4944 13.684 51.75 14.0005 C52.0056 14.317 52.344 14.5735 52.7359 14.7477 C53.128 14.9219 53.5618 15.0087 54 15.0005 C54.3909 14.9906 54.7748 14.9053 55.125 14.7505 M34.875 10.7505 C35.2252 10.9053 35.6091 10.9906 36 11.0005 C36.4382 11.0087 36.872 10.9219 37.2641 10.7477 C37.656 10.5735 37.9944 10.317 38.25 10.0005 C38.5056 9.684 38.844 9.4276 39.2359 9.2534 C39.628 9.0791 40.0618 8.9924 40.5 9.0005 C40.9382 8.9924 41.372 9.0791 41.7641 9.2534 C42.156 9.4276 42.4944 9.684 42.75 10.0005 C43.0056 10.317 43.344 10.5735 43.7359 10.7477 C44.128 10.9219 44.5618 11.0087 45 11.0005 C45.4382 11.0087 45.872 10.9219 46.2641 10.7477 C46.656 10.5735 46.9944 10.317 47.25 10.0005 C47.5056 9.684 47.844 9.4276 48.2359 9.2534 C48.628 9.0791 49.0618 8.9924 49.5 9.0005 C49.9382 8.9924 50.372 9.0791 50.7641 9.2534 C51.156 9.4276 51.4944 9.684 51.75 10.0005 C52.0056 10.317 52.344 10.5735 52.7359 10.7477 C53.128 10.9219 53.5618 11.0087 54 11.0005 C54.3909 10.9906 54.7748 10.9053 55.125 10.7505 M2.8125 25 L87.1875 25 C88.7408 25 90 23.8807 90 22.5 L90 2.5 C90 1.1193 88.7408 0 87.1875 0 L2.8125 0 C1.2592 0 0 1.1193 0 2.5 L0 22.5 C0 23.8807 1.2592 25 2.8125 25 Z" fill="none" stroke="currentColor" stroke-width="1.5" stroke-linecap="round" stroke-linejoin="round"/>
-</svg>

assets/furniture/houseplan-0.4.0/svg/plan/armchair.svg

@@ -1,3 +0,0 @@
-<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 90 90">
-  <path d="M78.5252 10.0692 C78.5335 9.9054 78.5377 9.7404 78.5377 9.5745 C78.5377 4.2866 74.2612 0 68.9858 0 L21.0141 0 C15.7388 0 11.4623 4.2866 11.4623 9.5745 C11.4623 9.7404 11.4665 9.9054 11.4748 10.0692 M80.086 74.5803 C80.5155 74.6465 80.9554 74.6809 81.4033 74.6809 C86.1511 74.6809 90 70.8229 90 66.0638 L90 18.1915 C90 13.4324 86.1511 9.5745 81.4033 9.5745 C80.3938 9.5745 79.425 9.7489 78.5252 10.0692 C75.1928 11.2557 72.8066 14.4443 72.8066 18.1915 L72.8066 18.3523 M72.8066 18.3523 C71.6366 18.8647 70.3443 19.1489 68.9858 19.1489 L21.0141 19.1489 C19.6557 19.1489 18.3634 18.8647 17.1934 18.3523 M72.8066 18.3523 L72.8066 66.0638 C72.8066 70.3739 75.9635 73.9449 80.086 74.5803 M11.4748 10.0692 C14.8072 11.2557 17.1934 14.4443 17.1934 18.1915 L17.1934 18.3523 M17.1934 18.3523 L17.1934 66.0638 C17.1934 70.3739 14.0365 73.9449 9.914 74.5803 C9.4845 74.6465 9.0446 74.6809 8.5967 74.6809 C3.8489 74.6809 0 70.8229 0 66.0638 L0 18.1915 C0 13.4324 3.8489 9.5745 8.5967 9.5745 C9.6062 9.5745 10.575 9.7489 11.4748 10.0692 M80.086 74.5803 C78.355 83.3709 70.622 90 61.3443 90 L28.6557 90 C19.378 90 11.645 83.3709 9.914 74.5803" fill="none" stroke="currentColor" stroke-width="1.5" stroke-linecap="round" stroke-linejoin="round"/>
-</svg>

assets/furniture/houseplan-0.4.0/svg/plan/armchair_office.svg

@@ -1,3 +0,0 @@
-<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 65 65">
-  <path d="M60.1252 17.0822 C60.1252 16.8061 60.1056 16.5347 60.0677 16.2692 M51.1877 11.3883 L13.8126 11.3883 C10.6715 11.3883 8.1251 8.8389 8.1251 5.6941 C8.1251 2.5494 10.6715 0 13.8126 0 L51.1877 0 C54.3288 0 56.8752 2.5494 56.8752 5.6941 C56.8752 8.8389 54.3288 11.3883 51.1877 11.3883 Z M13.8126 11.3883 L10.5626 11.388 C7.6973 11.388 5.3268 13.5094 4.9327 16.269 M51.1877 11.3883 L54.4377 11.388 C57.3031 11.388 59.6736 13.5095 60.0677 16.2692 M60.125 44.2992 C62.8174 44.2992 65 42.114 65 39.4185 L65 21.1495 C65 18.454 62.8174 16.2688 60.125 16.2688 C60.1059 16.2688 60.0868 16.2689 60.0677 16.2692 M60.125 44.2992 C57.4326 44.2992 55.25 42.114 55.25 39.4185 L55.25 21.1495 C55.25 18.4731 57.4017 16.2999 60.0677 16.2692 M46.7004 58.3142 L52.0002 58.3142 C52.8312 58.3142 53.633 58.1893 54.388 57.9573 C57.71 56.9362 60.1252 53.8403 60.1252 50.1797 L60.125 44.2992 M4.9327 16.269 C4.9135 16.2688 4.8943 16.2687 4.875 16.2687 C2.1826 16.2687 0 18.4538 0 21.1493 L0 39.4183 C0 42.1138 2.1826 44.299 4.875 44.299 C7.5674 44.299 9.75 42.1138 9.75 39.4183 L9.75 21.1493 C9.75 18.4731 7.5985 16.2999 4.9327 16.269 Z M18.4085 58.3142 L13.0001 58.3142 C12.1998 58.3142 11.4264 58.1983 10.6959 57.9824 C7.3309 56.988 4.8751 53.871 4.8751 50.1797 L4.875 44.299 M46.7004 58.3142 L52.5456 64.1662 C53.6394 65.261 55.4072 65.2801 56.524 64.2091 C57.6747 63.1047 57.694 61.2672 56.5669 60.1387 L54.388 57.9573 M46.7004 58.3142 L18.4085 58.3142 M10.6959 57.9824 L8.542 60.1387 C7.4149 61.2672 7.4342 63.1047 8.5849 64.2091 C9.7016 65.2802 11.4694 65.2609 12.5633 64.1662 L18.4085 58.3142" fill="none" stroke="currentColor" stroke-width="1.5" stroke-linecap="round" stroke-linejoin="round"/>
-</svg>

assets/furniture/houseplan-0.4.0/svg/plan/bathtub.svg

@@ -1,3 +0,0 @@
-<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 170 75">
-  <path d="M0 2.5 C0 1.1193 1.1193 0 2.5 0 L167.5 0 C168.881 0 170 1.1193 170 2.5 L170 72.5 C170 73.8807 168.881 75 167.5 75 L2.5 75 C1.1193 75 0 73.8807 0 72.5 L0 2.5 Z M10 37.5 C10 22.3122 22.3122 10 37.5 10 L132.5 10 C147.688 10 160 22.3122 160 37.5 C160 52.6878 147.688 65 132.5 65 L37.5 65 C22.3122 65 10 52.6878 10 37.5 Z M29 37.5 C29 39.9853 26.9853 42 24.5 42 C22.0147 42 20 39.9853 20 37.5 C20 35.0147 22.0147 33 24.5 33 C26.9853 33 29 35.0147 29 37.5 Z" fill="none" stroke="currentColor" stroke-width="1.5" stroke-linecap="round" stroke-linejoin="round"/>
-</svg>

assets/furniture/houseplan-0.4.0/svg/plan/bathtub_corner.svg

@@ -1,3 +0,0 @@
-<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 140 140">
-  <path d="M0 2.5 C0 1.1193 1.1193 0 2.5 0 L137.705 0 C138.972 0 140 1.0275 140 2.2951 C140 78.3474 78.3474 140 2.2951 140 C1.0275 140 0 138.972 0 137.705 L0 2.5 Z M10 30 C10 18.9543 18.9543 10 30 10 L122.745 10 C123.99 10 125 11.0096 125 12.2549 C125 74.5223 74.5223 125 12.2549 125 C11.0095 125 10 123.99 10 122.745 L10 30 Z M30 25 C30 27.7614 27.7614 30 25 30 C22.2386 30 20 27.7614 20 25 C20 22.2386 22.2386 20 25 20 C27.7614 20 30 22.2386 30 25 Z" fill="none" stroke="currentColor" stroke-width="1.5" stroke-linecap="round" stroke-linejoin="round"/>
-</svg>

assets/furniture/houseplan-0.4.0/svg/plan/bed_double.svg

@@ -1,3 +0,0 @@
-<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 160 200">
-  <path d="M0 10.5845 C0 16.4302 4.7469 21.1691 10.6024 21.1691 L149.398 21.1691 C155.253 21.1691 160 16.4302 160 10.5845 M74.6988 59.6584 L74.6988 44.2627 C74.6988 38.9484 70.3835 34.6404 65.0602 34.6404 L43.8554 34.6404 C38.5322 34.6404 34.2169 38.9484 34.2169 44.2627 L34.2169 59.6584 M128.675 59.6584 L128.675 44.2627 C128.675 38.9484 124.359 34.6404 119.036 34.6404 L97.8313 34.6404 C92.5081 34.6404 88.1928 38.9484 88.1928 44.2627 L88.1928 59.6584 M0 59.6584 L160 59.6584 M160 82.752 L0 82.752 M9.6386 200 L150.361 200 C155.685 200 160 195.692 160 190.378 L160 9.6223 C160 4.3081 155.685 0 150.361 0 L9.6386 0 C4.3153 0 0 4.3081 0 9.6223 L0 190.378 C0 195.692 4.3153 200 9.6386 200 Z" fill="none" stroke="currentColor" stroke-width="1.5" stroke-linecap="round" stroke-linejoin="round"/>
-</svg>

assets/furniture/houseplan-0.4.0/svg/plan/bed_single.svg

@@ -1,3 +0,0 @@
-<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 90 200">
-  <path d="M0 10.533 C0 16.3503 4.7153 21.0661 10.5319 21.0661 L79.4681 21.0661 C85.2847 21.0661 90 16.3503 90 10.533 M65.1064 59.368 L65.1064 44.0472 C65.1064 38.7588 60.8197 34.4718 55.5319 34.4718 L34.4681 34.4718 C29.1803 34.4718 24.8936 38.7588 24.8936 44.0472 L24.8936 59.368 M0 59.368 L90 59.368 M90 82.3492 L0 82.3492 M9.5745 200 L80.4255 200 C85.7134 200 90 195.713 90 190.424 L90 9.5755 C90 4.2871 85.7134 0 80.4255 0 L9.5745 0 C4.2866 0 0 4.2871 0 9.5755 L0 190.424 C0 195.713 4.2866 200 9.5745 200 Z" fill="none" stroke="currentColor" stroke-width="1.5" stroke-linecap="round" stroke-linejoin="round"/>
-</svg>

assets/furniture/houseplan-0.4.0/svg/plan/bidet.svg

@@ -1,3 +0,0 @@
-<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 40 60">
-  <path d="M23 0.0005 L23 11.5005 C23 12.8812 21.8807 14.0005 20.5 14.0005 L19.5 14.0005 C18.1193 14.0005 17 12.8812 17 11.5005 L17 0.0005 M23 10.0005 L26.5 10.0005 C27.8807 10.0005 29 8.8812 29 7.5005 L29 6.5005 C29 5.1198 27.8807 4.0005 26.5 4.0005 L23 4.0005 M17 10.0005 L13.5 10.0005 C12.1193 10.0005 11 8.8812 11 7.5005 L11 6.5005 C11 5.1198 12.1193 4.0005 13.5 4.0005 L17 4.0005 M2.5 0 L37.5 0 C38.8807 0 40 1.1193 40 2.5 L40 40.6452 C40 51.3345 31.3345 60 20.6452 60 L19.3548 60 C8.6655 60 0 51.3345 0 40.6452 L0 2.5 C0 1.1193 1.1193 0 2.5 0 Z M7.5 18.0005 L32.5 18.0005 C33.8807 18.0005 35 19.1198 35 20.5005 L35 40.8069 C35 48.6458 28.6453 55.0005 20.8065 55.0005 L19.1935 55.0005 C11.3547 55.0005 5 48.6458 5 40.8069 L5 20.5005 C5 19.1198 6.1193 18.0005 7.5 18.0005 Z M24 27.0005 C24 29.2096 22.2091 31.0005 20 31.0005 C17.7909 31.0005 16 29.2096 16 27.0005 C16 24.7913 17.7909 23.0005 20 23.0005 C22.2091 23.0005 24 24.7913 24 27.0005 Z" fill="none" stroke="currentColor" stroke-width="1.5" stroke-linecap="round" stroke-linejoin="round"/>
-</svg>

assets/furniture/houseplan-0.4.0/svg/plan/bidet_built_in.svg

@@ -1,3 +0,0 @@
-<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 40 50">
-  <path d="M0 32.4047 C0 42.1223 8.6655 50 19.3548 50 L20.6452 50 C31.3345 50 40 42.1223 40 32.4047 L40 2.2727 C40 1.0175 38.8807 0 37.5 0 L2.5 0 C1.1193 0 0 1.0175 0 2.2727 L0 32.4047 Z M5 32.5514 C5 39.6775 11.3547 45.4545 19.1935 45.4545 L20.8065 45.4545 C28.6453 45.4545 35 39.6775 35 32.5514 L35 11.3636 C35 10.1085 33.8807 9.0909 32.5 9.0909 L7.5 9.0909 C6.1193 9.0909 5 10.1085 5 11.3636 L5 32.5514 Z M25 33.6364 C25 36.1467 22.7614 38.1818 20 38.1818 C17.2386 38.1818 15 36.1467 15 33.6364 C15 31.126 17.2386 29.0909 20 29.0909 C22.7614 29.0909 25 31.126 25 33.6364 Z" fill="none" stroke="currentColor" stroke-width="1.5" stroke-linecap="round" stroke-linejoin="round"/>
-</svg>

assets/furniture/houseplan-0.4.0/svg/plan/bookshelf.svg

@@ -1,3 +0,0 @@
-<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 100 35">
-  <path d="M6 29 L50 17.5 M94 6 L50 17.5 M6 6 L50 17.5 M94 29 L50 17.5 M2.5 0 L97.5 0 C98.8807 0 100 1.1193 100 2.5 L100 32.5 C100 33.8807 98.8807 35 97.5 35 L2.5 35 C1.1193 35 0 33.8807 0 32.5 L0 2.5 C0 1.1193 1.1193 0 2.5 0 Z" fill="none" stroke="currentColor" stroke-width="1.5" stroke-linecap="round" stroke-linejoin="round"/>
-</svg>

assets/furniture/houseplan-0.4.0/svg/plan/cabinet_shoe.svg

@@ -1,3 +0,0 @@
-<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 80 35">
-  <path d="M39.6926 15.9138 L41.3539 13.919 M42.6062 17.8572 L44.295 15.6837 M2.5 35 L77.5 35 C78.8807 35 80 33.8807 80 32.5 L80 2.5 C80 1.1193 78.8807 0 77.5 0 L2.5 0 C1.1193 0 0 1.1193 0 2.5 L0 32.5 C0 33.8807 1.1193 35 2.5 35 Z M48.8271 17.1185 L47.6393 16.9997 C46.8954 16.9254 46.1943 16.6166 45.6371 16.1181 L40.5781 11.5916 C39.1831 10.3435 36.9606 11.1849 36.7418 13.0439 C36.5376 14.7804 34.5536 15.6699 33.1213 14.6672 L31.4306 13.4837 C30.3613 12.8422 29.0009 13.6124 29.0009 14.8594 L29.0009 19.1871 C29.0009 21.1363 30.5811 22.7165 32.5303 22.7165 L48.5479 22.7165 C50.0976 22.7165 51.3539 21.4602 51.3539 19.9105 C51.3539 18.469 50.2615 17.262 48.8271 17.1185 Z" fill="none" stroke="currentColor" stroke-width="1.5" stroke-linecap="round" stroke-linejoin="round"/>
-</svg>

assets/furniture/houseplan-0.4.0/svg/plan/cabinet_sink.svg

@@ -1,3 +0,0 @@
-<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 80 50">
-  <path d="M0 2.5 C0 1.1193 1.1193 0 2.5 0 L77.5 0 C78.8807 0 80 1.1193 80 2.5 L80 47.5 C80 48.8807 78.8807 50 77.5 50 L2.5 50 C1.1193 50 0 48.8807 0 47.5 L0 2.5 Z M35.6813 33.35 C38.4689 35.55 42.5317 35.55 45.3194 33.35 C48.107 31.15 48.8146 27.38 46.997 24.4125 L40.5066 15 L34.0012 24.4125 C32.186 27.38 32.8936 31.1475 35.6813 33.35 Z" fill="none" stroke="currentColor" stroke-width="1.5" stroke-linecap="round" stroke-linejoin="round"/>
-</svg>

assets/furniture/houseplan-0.4.0/svg/plan/cabinet_tv.svg

@@ -1,3 +0,0 @@
-<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 140 45">
-  <path d="M56 17 L61.625 17 M61.625 17 L67.25 17 M61.625 17 L61.625 27.9688 M72.0312 17 L77.6562 28.25 L83.2812 17 M2.5 45 L137.5 45 C138.881 45 140 43.8807 140 42.5 L140 2.5 C140 1.1193 138.881 0 137.5 0 L2.5 0 C1.1193 0 0 1.1193 0 2.5 L0 42.5 C0 43.8807 1.1193 45 2.5 45 Z" fill="none" stroke="currentColor" stroke-width="1.5" stroke-linecap="round" stroke-linejoin="round"/>
-</svg>

assets/furniture/houseplan-0.4.0/svg/plan/cactus.svg

@@ -1,3 +0,0 @@
-<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 70 120">
-  <path d="M13.6111 31.8884 C13.6111 29.0479 11.4347 26.7451 8.75 26.7451 L4.8611 26.7451 C2.1764 26.7451 0 29.0478 0 31.8884 C0 34.729 2.1764 37.0317 4.8611 37.0317 L8.75 37.0317 C11.4347 37.0317 13.6111 34.729 13.6111 31.8884 Z M13.6111 31.8884 L15.5556 31.8884 C16.6294 31.8884 17.5 32.8095 17.5 33.9457 L17.5 46.2896 C17.5 47.4259 18.3706 48.3469 19.4444 48.3469 L21.3889 48.3469 M48.6111 49.3756 L50.5556 49.3756 C51.6294 49.3756 52.5 50.2967 52.5 51.4329 L52.5 63.7769 C52.5 64.9131 53.3706 65.8342 54.4444 65.8342 L56.3889 65.8342 M49.6421 16.4301 C49.8068 13.4672 49.1767 10.6587 47.952 8.2293 C45.4922 3.35 40.634 0 35 0 C29.366 0 24.5078 3.35 22.048 8.2293 M47.952 8.2293 L62.2232 8.2293 C63.2971 8.2293 64.1676 9.1504 64.1676 10.2866 L64.1676 14.4012 C64.1676 15.5374 63.2971 16.4585 62.2232 16.4585 L49.6421 16.4301 M49.6421 16.4301 L45.866 84.3501 M22.048 8.2293 L7.7787 8.2293 C6.7048 8.2293 5.8343 9.1504 5.8343 10.2866 L5.8343 14.4012 C5.8343 15.5374 6.7048 16.4585 7.7787 16.4585 L20.3579 16.4301 M22.048 8.2293 C20.8233 10.6587 20.1932 13.4672 20.3579 16.4301 M20.3579 16.4301 L24.134 84.3501 M24.134 84.3501 L16.4172 84.3501 C15.281 84.3501 14.3599 83.429 14.3599 82.2928 L14.3599 81.6598 C14.3599 79.7369 12.8867 78.1781 11.0693 78.1781 C9.252 78.1781 7.7787 79.7369 7.7787 81.6598 L7.7787 104.4421 C7.7787 108.1271 9.6425 111.5311 12.6644 113.3651 L22.7946 119.5111 C24.4864 120.5381 26.6451 119.8931 27.5795 118.0821 C28.4688 116.3581 27.9229 114.1991 26.339 113.1761 L17.153 107.2411 C15.4181 106.1201 14.3599 104.1241 14.3599 101.9731 L14.3599 94.6367 C14.3599 93.5005 15.281 92.5794 16.4172 92.5794 L24.5915 92.5794 M24.134 84.3501 L45.866 84.3501 M24.5915 92.5794 L45.4085 92.5794 L53.5847 92.5794 C54.7209 92.5794 55.642 93.5005 55.642 94.6367 L55.642 101.9731 C55.642 104.1241 54.5838 106.1201 52.8489 107.2411 L43.6629 113.1761 C42.079 114.1991 41.5331 116.3581 42.4224 118.0821 C43.3568 119.8931 45.5155 120.5381 47.2073 119.5111 L57.3375 113.3651 C60.3594 111.5311 62.2232 108.1271 62.2232 104.4421 L62.2232 81.6598 C62.2232 79.7369 60.7499 78.1781 58.9326 78.1781 C57.1152 78.1781 55.642 79.7369 55.642 81.6598 L55.642 82.2928 C55.642 83.429 54.7209 84.3501 53.5847 84.3501 L45.866 84.3501 M45.4085 92.5794 L45.2931 94.6544 C44.9725 100.4211 40.4594 104.9231 35 104.9231 C29.5406 104.9231 25.0275 100.4211 24.7069 94.6544 L24.5915 92.5794 M29.6788 36.3713 L26.7748 17.8019 C25.9908 12.7888 29.6457 8.2293 34.4482 8.2293 L35.5518 8.2293 C40.3543 8.2293 44.0092 12.7888 43.2252 17.8019 L40.3212 36.3713 C39.8904 39.126 37.639 41.1463 35 41.1463 C32.361 41.1463 30.1096 39.126 29.6788 36.3713 Z M65.1389 69.9489 L61.25 69.9489 C58.5653 69.9489 56.3889 67.6461 56.3889 64.8056 C56.3889 61.965 58.5653 59.6622 61.25 59.6622 L65.1389 59.6622 C67.8236 59.6622 70 61.965 70 64.8056 C70 67.6461 67.8236 69.9489 65.1389 69.9489 Z" fill="none" stroke="currentColor" stroke-width="1.5" stroke-linecap="round" stroke-linejoin="round"/>
-</svg>

assets/furniture/houseplan-0.4.0/svg/plan/chair.svg

@@ -1,3 +0,0 @@
-<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 50 50">
-  <path d="M41.9118 10.2941 L8.0882 10.2941 C5.2456 10.2941 2.9412 7.9897 2.9412 5.1471 C2.9412 2.3044 5.2456 0 8.0882 0 L41.9118 0 C44.7544 0 47.0588 2.3044 47.0588 5.1471 C47.0588 7.9897 44.7544 10.2941 41.9118 10.2941 Z M8.0882 10.2941 L5.1471 10.2942 C2.3044 10.2942 0 12.5986 0 15.4412 L0 42.6471 C0 46.708 3.292 50 7.3529 50 L42.6471 50 C46.708 50 50 46.708 50 42.6471 L50 15.4412 C50 12.5986 47.6956 10.2942 44.8529 10.2942 L41.9118 10.2941" fill="none" stroke="currentColor" stroke-width="1.5" stroke-linecap="round" stroke-linejoin="round"/>
-</svg>

assets/furniture/houseplan-0.4.0/svg/plan/chair_bar.svg

@@ -1,3 +0,0 @@
-<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 45 48">
-  <path d="M41.6417 15.9532 C43.2205 18.9284 43.9595 23.0373 43.9595 26.6364 C43.9595 38.4352 34.3521 48 22.5008 48 C10.6496 48 1.0422 38.4352 1.0422 26.6364 C1.0422 23.0373 1.7394 18.9194 3.3182 15.9441 M41.6417 15.9532 C40.2574 16.2589 38.7505 15.8756 37.6736 14.8035 M41.6417 15.9532 C42.4118 15.7831 43.1439 15.3999 43.743 14.8035 M3.472 15.9767 C3.4206 15.9668 3.3693 15.9559 3.3182 15.9441 C2.5629 15.7698 1.8457 15.3895 1.257 14.8035 M37.6736 14.8035 C35.681 12.8197 33.3155 11.2458 30.7121 10.1722 C28.1086 9.0986 25.318 8.5465 22.5 8.5465 C19.682 8.5465 16.8914 9.0986 14.2879 10.1722 C11.6845 11.2458 9.319 12.8197 7.3264 14.8035 C6.2789 15.8463 4.8246 16.2374 3.472 15.9767 M37.6736 14.8035 C39.3496 16.4721 42.067 16.4721 43.743 14.8035 M3.472 15.9767 C2.6605 15.8203 1.8855 15.4292 1.257 14.8035 C-0.419 13.1349 -0.419 10.4295 1.257 8.7609 C4.0466 5.9836 7.3585 3.7808 11.0033 2.2778 C14.6481 0.7747 18.5548 0 22.5 0 C26.4452 0 30.3519 0.7747 33.9967 2.2778 C37.6415 3.7808 40.9534 5.9836 43.743 8.7609 C45.419 10.4295 45.419 13.1349 43.743 14.8035" fill="none" stroke="currentColor" stroke-width="1.5" stroke-linecap="round" stroke-linejoin="round"/>
-</svg>

assets/furniture/houseplan-0.4.0/svg/plan/coffee_table.svg

@@ -1,3 +0,0 @@
-<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 120 60">
-  <path d="M0 2.5 C0 1.1193 1.1193 0 2.5 0 L117.5 0 C118.881 0 120 1.1193 120 2.5 L120 57.5 C120 58.8807 118.881 60 117.5 60 L2.5 60 C1.1193 60 0 58.8807 0 57.5 L0 2.5 Z M106 13 L106 7 C106 6.4477 106.4477 6 107 6 L113 6 C113.5523 6 114 6.4477 114 7 L114 13 C114 13.5523 113.5523 14 113 14 L107 14 C106.4477 14 106 13.5523 106 13 Z M106 53 L106 47 C106 46.4477 106.4477 46 107 46 L113 46 C113.5523 46 114 46.4477 114 47 L114 53 C114 53.5523 113.5523 54 113 54 L107 54 C106.4477 54 106 53.5523 106 53 Z M6 13 L6 7 C6 6.4477 6.4477 6 7 6 L13 6 C13.5523 6 14 6.4477 14 7 L14 13 C14 13.5523 13.5523 14 13 14 L7 14 C6.4477 14 6 13.5523 6 13 Z M6 53 L6 47 C6 46.4477 6.4477 46 7 46 L13 46 C13.5523 46 14 46.4477 14 47 L14 53 C14 53.5523 13.5523 54 13 54 L7 54 C6.4477 54 6 53.5523 6 53 Z" fill="none" stroke="currentColor" stroke-width="1.5" stroke-linecap="round" stroke-linejoin="round"/>
-</svg>

assets/furniture/houseplan-0.4.0/svg/plan/coffee_table_oval.svg

@@ -1,3 +0,0 @@
-<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 120 60">
-  <path d="M0 30 C0 13.4315 13.4315 0 30 0 L90 0 C106.569 0 120 13.4315 120 30 C120 46.5685 106.569 60 90 60 L30 60 C13.4315 60 0 46.5685 0 30 Z M82 13 L82 7 C82 6.4477 82.4477 6 83 6 L89 6 C89.5523 6 90 6.4477 90 7 L90 13 C90 13.5523 89.5523 14 89 14 L83 14 C82.4477 14 82 13.5523 82 13 Z M82 53 L82 47 C82 46.4477 82.4477 46 83 46 L89 46 C89.5523 46 90 46.4477 90 47 L90 53 C90 53.5523 89.5523 54 89 54 L83 54 C82.4477 54 82 53.5523 82 53 Z M30 13 L30 7 C30 6.4477 30.4477 6 31 6 L37 6 C37.5523 6 38 6.4477 38 7 L38 13 C38 13.5523 37.5523 14 37 14 L31 14 C30.4477 14 30 13.5523 30 13 Z M30 53 L30 47 C30 46.4477 30.4477 46 31 46 L37 46 C37.5523 46 38 46.4477 38 47 L38 53 C38 53.5523 37.5523 54 37 54 L31 54 C30.4477 54 30 53.5523 30 53 Z" fill="none" stroke="currentColor" stroke-width="1.5" stroke-linecap="round" stroke-linejoin="round"/>
-</svg>

assets/furniture/houseplan-0.4.0/svg/plan/coffee_table_round.svg

@@ -1,3 +0,0 @@
-<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 80 80">
-  <path d="M0 40 C0 17.9086 17.9086 0 40 0 C62.0914 0 80 17.9086 80 40 C80 62.0914 62.0914 80 40 80 C17.9086 80 0 62.0914 0 40 M57.9495 25.6076 L53.7069 21.365 C53.3164 20.9745 53.3164 20.3413 53.7069 19.9508 L57.9495 15.7082 C58.34 15.3177 58.9732 15.3177 59.3637 15.7082 L63.6063 19.9508 C63.9968 20.3413 63.9968 20.9745 63.6063 21.365 L59.3637 25.6076 C58.9732 25.9981 58.34 25.9981 57.9495 25.6076 Z M57.9495 63.8682 L53.7069 59.6256 C53.3164 59.235 53.3164 58.6019 53.7069 58.2114 L57.9495 53.9688 C58.34 53.5782 58.9732 53.5782 59.3637 53.9688 L63.6063 58.2114 C63.9968 58.6019 63.9968 59.235 63.6063 59.6256 L59.3637 63.8682 C58.9732 64.2587 58.34 64.2587 57.9495 63.8682 Z M19.9494 25.6068 L15.7068 21.3642 C15.3163 20.9737 15.3163 20.3405 15.7068 19.95 L19.9494 15.7074 C20.3399 15.3169 20.9731 15.3169 21.3636 15.7074 L25.6062 19.95 C25.9967 20.3405 25.9967 20.9737 25.6062 21.3642 L21.3636 25.6068 C20.9731 25.9973 20.3399 25.9973 19.9494 25.6068 Z M19.9492 63.868 L15.7066 59.6254 C15.3161 59.2348 15.3161 58.6017 15.7066 58.2112 L19.9492 53.9686 C20.3397 53.578 20.9729 53.578 21.3634 53.9686 L25.606 58.2112 C25.9965 58.6017 25.9965 59.2348 25.606 59.6254 L21.3634 63.868 C20.9729 64.2585 20.3397 64.2585 19.9492 63.868 Z" fill="none" stroke="currentColor" stroke-width="1.5" stroke-linecap="round" stroke-linejoin="round"/>
-</svg>

assets/furniture/houseplan-0.4.0/svg/plan/coffee_table_rounded.svg

@@ -1,3 +0,0 @@
-<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 120 60">
-  <path d="M0 10 C0 4.4771 4.4771 0 10 0 L110 0 C115.523 0 120 4.4771 120 10 L120 50 C120 55.5228 115.523 60 110 60 L10 60 C4.4771 60 0 55.5228 0 50 L0 10 Z M106 13 L106 7 C106 6.4477 106.4477 6 107 6 L113 6 C113.5523 6 114 6.4477 114 7 L114 13 C114 13.5523 113.5523 14 113 14 L107 14 C106.4477 14 106 13.5523 106 13 Z M106 53 L106 47 C106 46.4477 106.4477 46 107 46 L113 46 C113.5523 46 114 46.4477 114 47 L114 53 C114 53.5523 113.5523 54 113 54 L107 54 C106.4477 54 106 53.5523 106 53 Z M6 13 L6 7 C6 6.4477 6.4477 6 7 6 L13 6 C13.5523 6 14 6.4477 14 7 L14 13 C14 13.5523 13.5523 14 13 14 L7 14 C6.4477 14 6 13.5523 6 13 Z M6 53 L6 47 C6 46.4477 6.4477 46 7 46 L13 46 C13.5523 46 14 46.4477 14 47 L14 53 C14 53.5523 13.5523 54 13 54 L7 54 C6.4477 54 6 53.5523 6 53 Z" fill="none" stroke="currentColor" stroke-width="1.5" stroke-linecap="round" stroke-linejoin="round"/>
-</svg>

assets/furniture/houseplan-0.4.0/svg/plan/computer.svg

@@ -1,3 +0,0 @@
-<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 120 60">
-  <path d="M26.6667 6.7692 L2.5 6.7692 C1.1193 6.7692 0 7.8885 0 9.2692 L0 12.7308 C0 14.1115 1.1193 15.2308 2.5 15.2308 L26.6667 15.2308 M26.6667 6.7692 L26.6667 2.5 C26.6667 1.1193 27.786 0 29.1667 0 L52.6111 0 C53.9918 0 55.1111 1.1193 55.1111 2.5 L55.1111 6.7692 M26.6667 6.7692 L55.1111 6.7692 M55.1111 6.7692 L77.5 6.7692 C78.8807 6.7692 80 7.8885 80 9.2692 L80 12.7308 C80 14.1115 78.8807 15.2308 77.5 15.2308 L55.1111 15.2308 M26.6667 15.2308 L26.6667 19.5 C26.6667 20.8807 27.786 22 29.1667 22 L52.6111 22 C53.9918 22 55.1111 20.8807 55.1111 19.5 L55.1111 15.2308 M26.6667 15.2308 L55.1111 15.2308 M93.8438 60 L117.5 60 C118.881 60 120 58.8807 120 57.5 L120 2.5 C120 1.1193 118.881 0 117.5 0 L93.8438 0 C92.463 0 91.3438 1.1193 91.3438 2.5 L91.3438 57.5 C91.3438 58.8807 92.463 60 93.8438 60 Z M9.5 55 L56.5 55 C57.8807 55 59 53.8807 59 52.5 L59 41.5 C59 40.1193 57.8807 39 56.5 39 L9.5 39 C8.1193 39 7 40.1193 7 41.5 L7 52.5 C7 53.8807 8.1193 55 9.5 55 Z M75 55 C77.2091 55 79 53.2091 79 51 L79 43 C79 40.7909 77.2091 39 75 39 C72.7909 39 71 40.7909 71 43 L71 51 C71 53.2091 72.7909 55 75 55 Z" fill="none" stroke="currentColor" stroke-width="1.5" stroke-linecap="round" stroke-linejoin="round"/>
-</svg>

assets/furniture/houseplan-0.4.0/svg/plan/cooktop_two.svg

@@ -1,3 +0,0 @@
-<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 30 50">
-  <path d="M15 32 L15 30 M19.0009 36 L21 36 M15 42 L15 40 M9.0009 36 L11 36 M3.125 50 L26.875 50 C28.6009 50 30 48.6009 30 46.875 L30 3.125 C30 1.3991 28.6009 0 26.875 0 L3.125 0 C1.3991 0 0 1.3991 0 3.125 L0 46.875 C0 48.6009 1.3991 50 3.125 50 Z M22 15 C22 18.866 18.866 22 15 22 C11.134 22 8 18.866 8 15 C8 11.134 11.134 8 15 8 C18.866 8 22 11.134 22 15 Z M20 36 C20 38.7614 17.7614 41 15 41 C12.2386 41 10 38.7614 10 36 C10 33.2386 12.2386 31 15 31 C17.7614 31 20 33.2386 20 36 Z" fill="none" stroke="currentColor" stroke-width="1.5" stroke-linecap="round" stroke-linejoin="round"/>
-</svg>

assets/furniture/houseplan-0.4.0/svg/plan/desk.svg

@@ -1,3 +0,0 @@
-<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 140 70">
-  <path d="M0 2.5 C0 1.1193 1.1193 0 2.5 0 L137.5 0 C138.881 0 140 1.1193 140 2.5 L140 67.5 C140 68.8807 138.881 70 137.5 70 L2.5 70 C1.1193 70 0 68.8807 0 67.5 L0 2.5 Z M6 13 L6 7 C6 6.4477 6.4477 6 7 6 L13 6 C13.5523 6 14 6.4477 14 7 L14 13 C14 13.5523 13.5523 14 13 14 L7 14 C6.4477 14 6 13.5523 6 13 Z M126 13 L126 7 C126 6.4477 126.4477 6 127 6 L133 6 C133.5523 6 134 6.4477 134 7 L134 13 C134 13.5523 133.5523 14 133 14 L127 14 C126.4477 14 126 13.5523 126 13 Z M6 63 L6 57 C6 56.4477 6.4477 56 7 56 L13 56 C13.5523 56 14 56.4477 14 57 L14 63 C14 63.5523 13.5523 64 13 64 L7 64 C6.4477 64 6 63.5523 6 63 Z M126 63 L126 57 C126 56.4477 126.4477 56 127 56 L133 56 C133.5523 56 134 56.4477 134 57 L134 63 C134 63.5523 133.5523 64 133 64 L127 64 C126.4477 64 126 63.5523 126 63 Z M23 60 L117 60" fill="none" stroke="currentColor" stroke-width="1.5" stroke-linecap="round" stroke-linejoin="round"/>
-</svg>

assets/furniture/houseplan-0.4.0/svg/plan/desk_corner.svg

@@ -1,3 +0,0 @@
-<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 160 160">
-  <path d="M160 65.5 C160 66.8807 158.881 68 157.5 68 L95 68 C81.1929 68 70 79.1929 70 93 L70 157.5 C70 158.881 68.8807 160 67.5 160 L2.5 160 C1.1193 160 0 158.881 0 157.5 L0 2.5 C0 1.1193 1.1193 0 2.5 0 L157.5 0 C158.881 0 160 1.1193 160 2.5 L160 65.5 Z M6 13 L6 7 C6 6.4477 6.4477 6 7 6 L13 6 C13.5523 6 14 6.4477 14 7 L14 13 C14 13.5523 13.5523 14 13 14 L7 14 C6.4477 14 6 13.5523 6 13 Z M146 13 L146 7 C146 6.4477 146.4477 6 147 6 L153 6 C153.5523 6 154 6.4477 154 7 L154 13 C154 13.5523 153.5523 14 153 14 L147 14 C146.4477 14 146 13.5523 146 13 Z M146 61 L146 55 C146 54.4477 146.4477 54 147 54 L153 54 C153.5523 54 154 54.4477 154 55 L154 61 C154 61.5523 153.5523 62 153 62 L147 62 C146.4477 62 146 61.5523 146 61 Z M6 153 L6 147 C6 146.4477 6.4477 146 7 146 L13 146 C13.5523 146 14 146.4477 14 147 L14 153 C14 153.5523 13.5523 154 13 154 L7 154 C6.4477 154 6 153.5523 6 153 Z M56 153 L56 147 C56 146.4477 56.4477 146 57 146 L63 146 C63.5523 146 64 146.4477 64 147 L64 153 C64 153.5523 63.5523 154 63 154 L57 154 C56.4477 154 56 153.5523 56 153 Z M110 58 L96.3636 58 C91.5883 58 86.8597 58.9406 82.4479 60.768 C78.036 62.5955 74.0273 65.274 70.6507 68.6507 C67.274 72.0273 64.5955 76.036 62.768 80.4479 C60.9406 84.8597 60 89.5883 60 94.3636 L60 108" fill="none" stroke="currentColor" stroke-width="1.5" stroke-linecap="round" stroke-linejoin="round"/>
-</svg>

assets/furniture/houseplan-0.4.0/svg/plan/dishwasher.svg

@@ -1,3 +0,0 @@
-<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 60 60">
-  <path d="M20 41.9429 C20.3592 42.1215 20.7529 42.2199 21.1538 42.2314 C21.6033 42.2408 22.0482 42.1407 22.4503 41.9396 C22.8523 41.7386 23.1994 41.4427 23.4615 41.0775 C23.7237 40.7124 24.0707 40.4165 24.4728 40.2155 C24.8749 40.0144 25.3198 39.9143 25.7692 39.9237 C26.2186 39.9143 26.6636 40.0144 27.0657 40.2155 C27.4677 40.4165 27.8148 40.7124 28.0769 41.0775 C28.339 41.4427 28.6861 41.7386 29.0882 41.9396 C29.4902 42.1407 29.9352 42.2408 30.3846 42.2314 C30.834 42.2408 31.279 42.1407 31.681 41.9396 C32.0831 41.7386 32.4302 41.4427 32.6923 41.0775 C32.9544 40.7124 33.3015 40.4165 33.7036 40.2155 C34.1056 40.0144 34.5506 39.9143 35 39.9237 C35.4494 39.9143 35.8944 40.0144 36.2964 40.2155 C36.6985 40.4165 37.0456 40.7124 37.3077 41.0775 C37.5698 41.4427 37.9169 41.7386 38.319 41.9396 C38.721 42.1407 39.166 42.2408 39.6154 42.2314 C40.0164 42.2199 40.41 42.1215 40.7692 41.9429 M20 37.3277 C20.3592 37.5063 20.7529 37.6047 21.1538 37.6162 C21.6033 37.6256 22.0482 37.5254 22.4503 37.3244 C22.8523 37.1234 23.1994 36.8275 23.4615 36.4623 C23.7237 36.0971 24.0707 35.8012 24.4728 35.6002 C24.8749 35.3992 25.3198 35.2991 25.7692 35.3085 C26.2186 35.2991 26.6636 35.3992 27.0657 35.6002 C27.4677 35.8012 27.8148 36.0971 28.0769 36.4623 C28.339 36.8275 28.6861 37.1234 29.0882 37.3244 C29.4902 37.5254 29.9352 37.6256 30.3846 37.6162 C30.834 37.6256 31.279 37.5254 31.681 37.3244 C32.0831 37.1234 32.4302 36.8275 32.6923 36.4623 C32.9544 36.0971 33.3015 35.8012 33.7036 35.6002 C34.1056 35.3992 34.5506 35.2991 35 35.3085 C35.4494 35.2991 35.8944 35.3992 36.2964 35.6002 C36.6985 35.8012 37.0456 36.0971 37.3077 36.4623 C37.5698 36.8275 37.9169 37.1234 38.319 37.3244 C38.721 37.5254 39.166 37.6256 39.6154 37.6162 C40.0164 37.6047 40.41 37.5063 40.7692 37.3277 M34.9998 27.2308 L34.9998 18 C31.4275 21.5338 31.274 24.3992 31.2911 27.2308 L34.9998 27.2308 Z M34.9998 27.2308 L34.9998 31.8462 L34.2581 31.8462 L34.2581 29.5385 M26.8405 18.7692 L26.8405 23.3846 M26.8405 23.3846 L26.8405 31.8462 M26.8405 23.3846 C26.2503 23.3846 25.6843 23.1415 25.267 22.7087 C24.8497 22.2759 24.6152 21.689 24.6152 21.0769 L24.6152 18.7692 M26.8405 23.3846 C27.4307 23.3846 27.9967 23.1415 28.414 22.7087 C28.8313 22.2759 29.0658 21.689 29.0658 21.0769 L29.0658 18.7692 M2.5 60 L57.5 60 C58.8807 60 60 58.8807 60 57.5 L60 2.5 C60 1.1193 58.8807 0 57.5 0 L2.5 0 C1.1193 0 0 1.1193 0 2.5 L0 57.5 C0 58.8807 1.1193 60 2.5 60 Z" fill="none" stroke="currentColor" stroke-width="1.5" stroke-linecap="round" stroke-linejoin="round"/>
-</svg>

assets/furniture/houseplan-0.4.0/svg/plan/dryer.svg

@@ -1,3 +0,0 @@
-<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 60 60">
-  <path d="M30.8408 23.9231 C30.8408 23.9231 29.8187 26.0121 29.7032 27.5495 C29.5506 29.5818 30.9329 30.4963 30.8408 32.5357 C30.7639 34.2418 29.7032 36.6154 29.7032 36.6154 M25.0713 23.9231 C25.0713 23.9231 24.0491 26.0121 23.9337 27.5495 C23.781 29.5818 25.1633 30.4963 25.0713 32.5357 C24.9943 34.2418 23.9337 36.6154 23.9337 36.6154 M36.6104 23.9231 C36.6104 23.9231 35.5882 26.0121 35.4727 27.5495 C35.3201 29.5818 36.7024 30.4963 36.6104 32.5357 C36.5334 34.2418 35.4727 36.6154 35.4727 36.6154 M2.5 60 L57.5 60 C58.8807 60 60 58.8807 60 57.5 L60 2.5 C60 1.1193 58.8807 0 57.5 0 L2.5 0 C1.1193 0 0 1.1193 0 2.5 L0 57.5 C0 58.8807 1.1193 60 2.5 60 Z M43.5385 30.2692 C43.5385 37.5976 37.5976 43.5385 30.2692 43.5385 C22.9408 43.5385 17 37.5976 17 30.2692 C17 22.9408 22.9408 17 30.2692 17 C37.5976 17 43.5385 22.9408 43.5385 30.2692 Z" fill="none" stroke="currentColor" stroke-width="1.5" stroke-linecap="round" stroke-linejoin="round"/>
-</svg>

assets/furniture/houseplan-0.4.0/svg/plan/fireplace.svg

@@ -1,3 +0,0 @@
-<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 120 40">
-  <path d="M104.516 34.1865 L104.516 37.8022 C104.516 39.016 103.397 40 102.016 40 L17.9839 40 C16.6032 40 15.4839 39.016 15.4839 37.8022 L15.4839 34.1865 M104.516 34.1865 L15.4839 34.1865 M104.516 34.1865 L117.5 34.1865 C118.881 34.1865 120 33.2025 120 31.9886 L120 2.1978 C120 0.984 118.881 0 117.5 0 L2.5 0 C1.1193 0 0 0.984 0 2.1978 L0 31.9886 C0 33.2025 1.1193 34.1865 2.5 34.1865 L15.4839 34.1865 M59.9992 15.6396 C62.9823 11.9458 60.2128 6.9042 58.7206 5.6558 C58.7206 9.4468 55.8629 11.5728 54.0319 13.1439 C52.2034 14.7161 51.0488 16.822 51.0488 19.3836 C51.0488 23.5196 55.0561 26.8716 59.9992 26.8716 C64.9424 26.8716 68.9497 23.5196 68.9497 19.3836 C68.9497 17.4719 67.3744 14.4671 65.9666 13.1439 C63.3019 16.8879 61.8021 16.8879 59.9992 15.6396 Z" fill="none" stroke="currentColor" stroke-width="1.5" stroke-linecap="round" stroke-linejoin="round"/>
-</svg>

assets/furniture/houseplan-0.4.0/svg/plan/fridge.svg

@@ -1,3 +0,0 @@
-<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 60 65">
-  <path d="M27.4202 21.3572 L29.9916 22.7501 L32.563 21.3572 M29.9916 18.5715 L29.9916 27.6251 L33.8487 30.0208 M37.613 24.5163 L37.7853 27.6252 L40.1844 29.3412 M41.1262 25.5358 L33.8889 30.0626 L33.9018 34.8791 M40.1844 35.6592 L37.7853 37.3752 L37.613 40.484 M41.1259 39.4644 L33.8886 34.9376 L30.0443 37.3584 M32.563 43.643 L29.9916 42.2501 L27.4202 43.643 M29.9916 46.4283 L29.9916 37.3747 L26.1345 34.979 M22.3702 40.484 L22.1979 37.3752 L19.7988 35.6592 M18.8571 39.4643 L26.0944 34.9375 L26.0816 30.121 M19.7988 29.3412 L22.1979 27.6252 L22.3702 24.5163 M18.8571 25.5358 L26.0944 30.0626 L29.9387 27.6418 M2.1429 65 L57.8571 65 C59.0406 65 60 63.9607 60 62.6786 L60 2.3214 C60 1.0393 59.0406 0 57.8571 0 L2.1429 0 C0.9594 0 0 1.0393 0 2.3214 L0 62.6786 C0 63.9607 0.9594 65 2.1429 65 Z" fill="none" stroke="currentColor" stroke-width="1.5" stroke-linecap="round" stroke-linejoin="round"/>
-</svg>

assets/furniture/houseplan-0.4.0/svg/plan/hood.svg

@@ -1,3 +0,0 @@
-<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 60 50">
-  <path d="M41.7863 0 L57.5 0 C58.8807 0 60 1.1193 60 2.5 L60 47.5 C60 48.2192 59.6963 48.8674 59.2102 49.3235 C58.7631 49.743 58.1616 50 57.5 50 L2.5 50 C1.8373 50 1.2348 49.7421 0.7874 49.3213 C0.3027 48.8653 0 48.218 0 47.5 L0 2.5 C0 1.1193 1.1193 0 2.5 0 L18.2148 0 M18.2148 0 L41.7863 0 M18.2148 0 L18.2148 23.0357 M41.7863 0 L41.7863 23.0357 M59.2102 49.3235 L41.7863 23.0357 M0.7874 49.3213 L18.2148 23.0357 M41.7863 23.0357 L18.2148 23.0357" fill="none" stroke="currentColor" stroke-width="1.5" stroke-linecap="round" stroke-linejoin="round"/>
-</svg>

assets/furniture/houseplan-0.4.0/svg/plan/kitchen_floor.svg

@@ -1,3 +0,0 @@
-<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 60 60">
-  <path d="M0 2.5 C0 1.1193 1.1193 0 2.5 0 L57.5 0 C58.8807 0 60 1.1193 60 2.5 L60 57.5 C60 58.8807 58.8807 60 57.5 60 L2.5 60 C1.1193 60 0 58.8807 0 57.5 L0 2.5 Z" fill="none" stroke="currentColor" stroke-width="1.5" stroke-linecap="round" stroke-linejoin="round"/>
-</svg>

assets/furniture/houseplan-0.4.0/svg/plan/kitchen_floor_corner.svg

@@ -1,3 +0,0 @@
-<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 90 90">
-  <path d="M46.0305 41.4695 C46.0305 42.8502 47.1498 43.9695 48.5305 43.9695 L87.5 43.9695 C88.8807 43.9695 90 45.0888 90 46.4695 L90 87.5 C90 88.8807 88.8807 90 87.5 90 L2.5 90 C1.1193 90 0 88.8807 0 87.5 L0 2.5 C0 1.1193 1.1193 0 2.5 0 L43.5305 0 C44.9112 0 46.0305 1.1193 46.0305 2.5 L46.0305 41.4695 Z" fill="none" stroke="currentColor" stroke-width="1.5" stroke-linecap="round" stroke-linejoin="round"/>
-</svg>

assets/furniture/houseplan-0.4.0/svg/plan/kitchen_sink.svg

@@ -1,3 +0,0 @@
-<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 60 50">
-  <path d="M39.4138 6 L51.5 6 C52.8807 6 54 7.1193 54 8.5 L54 41.5 C54 42.8807 52.8807 44 51.5 44 L8.5 44 C7.1193 44 6 42.8807 6 41.5 L6 8.5 C6 7.1193 7.1193 6 8.5 6 L20.5862 6 M33 0 L33 13.5 C33 14.8807 31.8807 16 30.5 16 L29.5 16 C28.1193 16 27 14.8807 27 13.5 L27 0 M33 9 L36.5 9 C37.8807 9 39 7.8807 39 6.5 L39 5.5 C39 4.1193 37.8807 3 36.5 3 L33 3 M27 9 L23.5 9 C22.1193 9 21 7.8807 21 6.5 L21 5.5 C21 4.1193 22.1193 3 23.5 3 L27 3 M2.5 50 L57.5 50 C58.8807 50 60 48.8807 60 47.5 L60 2.5 C60 1.1193 58.8807 0 57.5 0 L2.5 0 C1.1193 0 0 1.1193 0 2.5 L0 47.5 C0 48.8807 1.1193 50 2.5 50 Z M34 26 C34 28.2091 32.2092 30 30 30 C27.7909 30 26 28.2091 26 26 C26 23.7909 27.7909 22 30 22 C32.2092 22 34 23.7909 34 26 Z" fill="none" stroke="currentColor" stroke-width="1.5" stroke-linecap="round" stroke-linejoin="round"/>
-</svg>