From 9ab4896c90524808f8e7d4fb6a1be7fd95bc3c45 Mon Sep 17 00:00:00 2001
From: Codex <codex@houseplan.tech>
Date: Thu, 10 Sep 2026 00:44:17 +0300
Subject: [PATCH] =?UTF-8?q?ci:=20mirror=20release.yml=20from=20dev=20(#514?=
 =?UTF-8?q?=20=E2=80=94=20E2E=20gate=20for=20stable=20releases)?=
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

The `release` event runs the workflow from the default branch;
byte-identical to dev@44046025.

Issue: #514
User-Visible: no
---
 .github/workflows/release.yml | 14 ++++++++++++++
 1 file changed, 14 insertions(+)

diff --git a/.github/workflows/release.yml b/.github/workflows/release.yml
index 2af7e991..c31f6d2a 100755
--- a/.github/workflows/release.yml
+++ b/.github/workflows/release.yml
@@ -50,6 +50,20 @@ jobs:
           set -euo pipefail
           SHA=$(git rev-parse HEAD)
           node scripts/release-gate.mjs "$SHA" --workflow=performance.yml --label="Полные бенчмарки производительности"
+      # #514: the only check on a real Home Assistant. houseplan-e2e installs
+      # the release's houseplan.zip — the bytes HACS ships — into HA in docker
+      # and walks the sidebar page, dashboards, roles, PDF, restart and the
+      # stable→tag upgrade. A red, missing or cancelled run withholds the
+      # assets exactly like Full Performance. 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: ${{ !github.event.release.prerelease }}
+        env:
+          GH_TOKEN: ${{ secrets.E2E_DISPATCH_TOKEN || secrets.HP_PROCESS_TOKEN }}
+          TAG: ${{ github.event.release.tag_name }}
+        run: node scripts/e2e-gate.mjs --tag="$TAG"
   build:
     name: Сборка бандла и загрузка ассетов
     needs: gate