Skip to content

Open-source platform for 3D AI agents. Turn text or a photo into a rigged, animated GLB avatar, give it an LLM brain, memory and a wallet, and embed it anywhere with one web component. Remote MCP server, x402 payments, Three.js, browser-native.

chore(prompts): log order 095's owner-gated repo creation and PRs, keep the order open

nirholas4df89c58cdf9
diff --git a/prompts/finish/095-partners-12-home-assistant-hacs.md b/prompts/finish/095-partners-12-home-assistant-hacs.md
index f16a90a9f..eec6da9a9 100644
--- a/prompts/finish/095-partners-12-home-assistant-hacs.md
+++ b/prompts/finish/095-partners-12-home-assistant-hacs.md
@@ -2,6 +2,21 @@
How to run: paste this file's repo path into a fresh Claude Code chat in this repository and say "run this work order". Runnable now, no gate.
+**Evolve status (2026-10-13):** every task is built and verified; the order stays open because the
+last steps are owner-gated third-party actions. `home-assistant-integration/` now validates clean
+against the real hassfest and HACS checks (`manifest.json`'s documentation link fixed, version
+bumped to `1.0.1`, `hacs.json`'s minimum Home Assistant version corrected to `2024.12.0`), ships
+real local brand icons at `custom_components/three_ws/brand/`, and `scripts/export-hacs-repo.mjs`
+builds the exact standalone-repository tree. All five Definition of Done lines are verified with
+real command output (hassfest, the real upstream HACS validators, a full real end-to-end container
+install with 18 real entities and a confirmed auto-reconnect, `npm test`, `npm run audit:docs`).
+What remains is creating `github.com/nirholas/three-ws-home-assistant`, cutting its `v1.0.1`
+release, and opening the `hacs/default` and `home-assistant/brands` pull requests, all logged as
+row 58 in [_context/production-100-OWNER-ACTIONS.md](_context/production-100-OWNER-ACTIONS.md)
+with the exact submission text in
+[marketing/growth/submissions/home-assistant.md](../../marketing/growth/submissions/home-assistant.md).
+Full detail in [_context/partners-PROGRESS.md](_context/partners-PROGRESS.md)'s 2026-10-13 entry.
+
## Operating clause (binding)
- Read CLAUDE.md first, then [_context/partners-00-CONTEXT.md](_context/partners-00-CONTEXT.md). CLAUDE.md overrides everything, including this file.
diff --git a/prompts/finish/_context/partners-PROGRESS.md b/prompts/finish/_context/partners-PROGRESS.md
index b1f2eabfb..a64a72cce 100644
--- a/prompts/finish/_context/partners-PROGRESS.md
+++ b/prompts/finish/_context/partners-PROGRESS.md
@@ -652,3 +652,71 @@ stays in place (not deleted) until those account signups and submissions land. C
`9c36dd51f` (Framer code component), `a722c6017` (Webflow Code Component), `bc5369b04` (docs,
STRUCTURE.md, changelog, pages index, submission text), this entry's commit (owner-actions row
and the order file's Evolve status paragraph).
+
+## 2026-10-13: order 095 built and verified end to end; standalone-repo creation and two pull requests remain, order file stays open
+
+Order 095 asked for the Home Assistant integration to be made ready for the HACS default store.
+Step 0 found a working integration with wrong manifest metadata (a 404ing documentation link, a
+too-low `hacs.json` minimum HA version) and no brand icon, and no standalone repository yet.
+
+- **Local validation (task 1)**: ran the real `ghcr.io/home-assistant/hassfest` Docker image
+ against a built export tree: `Integrations: 1, Invalid integrations: 0`. HACS's own
+ `hacs/action` is architecturally incapable of validating a repository that does not exist yet
+ (confirmed by reading `hacs.async_register_repository` in its real source), so its individual
+ local-file validators (`hacsjson.py`, `integration_manifest.py`, `brands.py`, `information.py`,
+ with the real `voluptuous` schema objects pulled from `hacs/integration`) were run directly
+ against the exported tree instead: all pass. The GitHub-settings-dependent checks
+ (`description`, `topics`, `issues`, `archived`, `license`) stay deferred to that repository's
+ own future CI.
+- **Manifest and metadata (task 2)**: `manifest.json`'s `documentation` fixed from a 404 to the
+ live `/docs/home-relay`, `version` bumped to `1.0.1`. `hacs.json`'s `homeassistant` corrected
+ from `2024.6.0` to `2024.12.0`: `relay_client.py` uses `aiohttp.ClientWSTimeout`, absent before
+ aiohttp 3.11, first bundled in HA 2024.12.0 (verified against HA's real
+ `package_constraints.txt` across releases 2024.6.0 through 2025.1.0). `codeowners` and
+ `issue_tracker` were already correct. No config-flow translations needed beyond what already
+ ships; the flow's existing `strings.json`/`translations/en.json` cover every field.
+- **Brand icon (task 3)**: real 256x256/512x512 PNGs (light and dark) rendered via `sharp` from
+ the existing `public/pwa-icon.svg` cube mark, shipped at
+ `custom_components/three_ws/brand/{icon,icon@2x,dark_icon,dark_icon@2x}.png` (HA 2026.3.0's
+ local brand images feature, which also satisfies HACS's own `brands.py` check). The
+ `home-assistant/brands` PR text (for the same four files, copied unchanged) is in the
+ submission doc.
+- **Standalone-repo export (task 4)**: new `scripts/export-hacs-repo.mjs` builds the integration,
+ README, `info.md`, LICENSE, `hacs.json`, and `.github/workflows/{hassfest,hacs}.yml` into
+ `dist/hacs-export/`. This monorepo runs no GitHub Actions of its own, so those two workflow
+ files exist only inside the exported tree.
+- **Submission text (task 5)**: `marketing/growth/submissions/home-assistant.md`, for owner order
+ 938: the `hacs/default` PR (exact alphabetical insertion point in the `integration` file,
+ between `nimroddolev/chime_tts` and `nishithdev/wled-taskmap`) and the `home-assistant/brands`
+ PR, both with title/description text, plus the full verification packet.
+- **Docs (task 6)**: `home-assistant-integration/README.md` gained the minimum-HA-version line
+ and a fix to a real pre-existing inaccuracy found during end-to-end testing (the connectivity
+ sensor's entity ID is device-name-prefixed, not the fixed name the README claimed).
+ `docs/home-relay.md` now notes the integration is ready for the HACS default store once the
+ standalone repository is live. `data/changelog.json` entry added, `npm run build:pages` run.
+- **Real end-to-end install (Definition of Done line 2)**: no cloud-backed Neon database or
+ published standalone repository exists in this workspace, so this ran a real
+ `ghcr.io/home-assistant/home-assistant:stable` container (HA 2026.9.4), onboarded via its own
+ REST API, paired through the integration's real `config_flow.py` against a real
+ `services/home-relay` server (`createRelay`) and a real `mintInstallToken`-signed install
+ token, justified by the integration's own documented self-hosted `platform_url` option. Result:
+ `{"type": "create_entry", "result": {"state": "loaded"}}`, the integration dialled in on its
+ own, opened a session, and answered a real `get_states` call with 18 real entities. After the
+ relay was restarted, the integration's own backoff reconnected it without intervention, and
+ `binary_sensor.evolve_test_home_three_ws_connection` read `state: "on"` with no `last_error`.
+- **`npm test`**: 43 failed files / 2355 passed (79 failed tests, 35373 passed, 244 skipped),
+ one file and one test better than the documented pre-existing baseline (44/2354, 80/35372);
+ none of the failures reference home-assistant, hacs, or export-hacs-repo.
+- **`npm run audit:docs`**: 21 findings, unchanged from the documented baseline.
+- **`npm run check:rules`** against every touched path across all commits: `OK: no hard-rule
+ violations in the added lines`.
+
+Two steps are owner-gated (CLAUDE.md gate 2: a step needing a new third-party repository and
+pull requests from a personal GitHub account) and cannot be done inside this session: creating
+`github.com/nirholas/three-ws-home-assistant` from the exported tree, cutting its `v1.0.1`
+release, and opening the `hacs/default` and `home-assistant/brands` pull requests. Logged as row
+58 in [_context/production-100-OWNER-ACTIONS.md](production-100-OWNER-ACTIONS.md). The order
+file stays in place (not deleted) until that repository and both pull requests land. Commits:
+`90590dee5` (manifest/hacs.json fixes, brand icons, README/docs fixes, changelog),
+`0c6ac3614` (export script, submission packet), this entry's commit (owner-actions row and the
+order file's Evolve status paragraph).
diff --git a/prompts/finish/_context/production-100-OWNER-ACTIONS.md b/prompts/finish/_context/production-100-OWNER-ACTIONS.md
index 00ef90ee5..34f7e52a4 100644
--- a/prompts/finish/_context/production-100-OWNER-ACTIONS.md
+++ b/prompts/finish/_context/production-100-OWNER-ACTIONS.md
@@ -9,7 +9,7 @@ it and, if that unblocks a work order, say which one in the owning pack's `produ
Rows carry the date they were added so staleness is visible. Re-verify a row before acting
on it; some resolve themselves as other work lands.
-## Open rows (2026-10-13 (order 094 close-out): row 57 added for the WordPress.org/Framer/Webflow account signups and submissions for the three <agent-3d> site-builder embeds; 2026-10-13 (order 092 close-out): row 55 added for the VRoid Hub avatar-import OAuth app registration and migration; 2026-10-13 (triage-lane sweep, fifth pass): row 53 added for the Birdeye compute-units cap behind `pump-price-history-upstreams-502` (confirmed live, a billing/plan decision only); row 1 re-measured, deploy gap still 0 against the pushed `threews/main` ref and the 8 page-404/wrong-canonical findings this pass confirmed as deploy lag; row 47 re-measured, still a no-op (`COINGECKO_API_KEY` still absent); the previously-unclassified `/dist-lib/agent-3d.js` and `/agent-3d/latest/agent-3d.js` 500s ("Response size was too large") are the same bug row 48 already tracks, fixed on `evolve` in `f939d5ef1`, confirmed still green (`npx vitest run tests/lib-bundle-size.test.js tests/whisper-stt.test.js`, 16/16) and awaiting the pending deploy, no new row; 2026-10-13 (triage-lane sweep, fourth pass): row 1 re-measured, deploy gap still 0 against the pushed `threews/main` ref; the `ccv-ai-providers-unavailable-503` finding's Groq/OpenRouter/Vertex angles confirmed already covered by rows 6 and 20, no new row added; 2026-10-13 (order 087 close-out): row 51 added for the LiveKit and Pipecat avatar integrations, both built and verified end to end this session, with the PyPI publishes and the two upstream pull requests left as owner actions; 2026-10-13 (order 085 close-out): row 50 added for publishing the CC0 bulk animation library to production, and the Adobe Mixamo permission letter draft is ready to send as owner order 938; 2026-10-12 (order 084 close-out): row 49 added for the Tripo signed webhook's three linked steps (apply the `forge_webhook_deliveries` migration, set `TRIPO_WEBHOOK_SECRET`, register the dashboard webhook), not an active bug since the secret is unset and polling answers every Tripo job today; 2026-10-12 18:10 UTC (triage-lane sweep, third pass): row 48 added for the dist-lib CDN embed size fix (previously-unclassified `/dist-lib/agent-3d.js` 500s, root-caused and fixed on `evolve`, pure code change awaiting the next deploy); 2026-10-12 17:54 UTC (triage-lane sweep, second pass): row 1's same-day "11 behind" figure corrected to the real deploy gap of 0 (querying `/api/version` live, not `/api/healthz`, which has no commit field), row 47 added for CoinGecko's keyless tier being rate-limited (`COINGECKO_API_KEY` already absent from the service, so the finding's own pre-approved env fix is a no-op); 2026-10-12 (triage-lane sweep): row 1 re-measured against the canonical `threews` remote, 11 commits behind `main` (down from 28, local stale ref corrected), row 45 added for the HF image-provider (fal-ai/nscale) credit exhaustion, a separate pool from row 6; 2026-10-11 (best3d order 070 close-out): rows 43 and 44 added for the `model-partcrafter` and `model-holopart` first deploys; 2026-10-11 (triage-lane sweep): row 42 added for the MCP client-sessions nullable-column migration, an active production bug; row 1 re-measured, 28 commits behind `main` (up from 5); 2026-10-11 (best3d order 069 close-out): rows 40 and 41 added for the `model-rig-nonhuman` and `model-anigen` first deploys; 2026-10-11 (best3d order 068 close-out): row 39 added for the `model-pixal3d` first deploy; 2026-10-11 (best3d order 067 retry): row 38 added for the `model-trellis2` first deploy; 2026-10-11 (order 404 close-out): row 34 deleted, its premise cleared by merge commit `d77b89178` (the `evolve`/`main` reconciliation) which also carried the `x-mention-reply.js` `chainFor()` fix row 34 called out, verified live with `RUN_LLM_TESTS=1 npx vitest run tests/x-mention-reply.llm.test.js` (16/16 `source: 'model'`, no `buildBody` TypeError); 2026-10-11 (scout lane): row 36 added for the Cloudflare R2 flapping degraded/down pattern; 2026-10-11 (even later): row 24 re-measured again after order 400's ring-leak-scan tiering/lock fix shipped on `evolve`; 2026-10-11 (later): row 35 added for the agent mention-policy migration; 2026-10-11 04:16 UTC: rows 1 and 24 re-measured by the deep triage sweep; row 34 added for the evolve/main branch divergence; 2026-10-10: row 33 added for the xAI MCP e2e key; rows 1, 19 and 24 re-measured by the triage sweep; 2026-10-09: rows 1, 2 and 24 re-measured by the triage sweep, row 31 added for the GPU worker redeploy and row 32 for database table retention; row 30 added for the Grok Bot CLI setup rerun; 2026-10-08: row 26 added for the coin-gated MCP catalog regeneration; rows 1 and 2 re-measured by the triage sweep, row 24 added for the paid Solana RPC credits, row 25 added for the MCP connector OAuth deploy; 2026-09-30: row 23 added for the $THREE receiver wallets; 2026-09-29: row 19 re-measured after the agent-sniper deploy; 2026-09-09: row 19 added, and row 1 corrected because its outage premise no longer holds; rows 1, 2, 3, 9, 13, 15 and 16 re-measured 2026-09-04; the former row 18 was cleared that day and its number is not reused; the 2026-09-02 and 2026-08-09 passes are folded in below)
+## Open rows (2026-10-13 (order 095 close-out): row 58 added for the Home Assistant integration's standalone repository, release, and the hacs/default and home-assistant/brands pull requests; 2026-10-13 (order 094 close-out): row 57 added for the WordPress.org/Framer/Webflow account signups and submissions for the three <agent-3d> site-builder embeds; 2026-10-13 (order 092 close-out): row 55 added for the VRoid Hub avatar-import OAuth app registration and migration; 2026-10-13 (triage-lane sweep, fifth pass): row 53 added for the Birdeye compute-units cap behind `pump-price-history-upstreams-502` (confirmed live, a billing/plan decision only); row 1 re-measured, deploy gap still 0 against the pushed `threews/main` ref and the 8 page-404/wrong-canonical findings this pass confirmed as deploy lag; row 47 re-measured, still a no-op (`COINGECKO_API_KEY` still absent); the previously-unclassified `/dist-lib/agent-3d.js` and `/agent-3d/latest/agent-3d.js` 500s ("Response size was too large") are the same bug row 48 already tracks, fixed on `evolve` in `f939d5ef1`, confirmed still green (`npx vitest run tests/lib-bundle-size.test.js tests/whisper-stt.test.js`, 16/16) and awaiting the pending deploy, no new row; 2026-10-13 (triage-lane sweep, fourth pass): row 1 re-measured, deploy gap still 0 against the pushed `threews/main` ref; the `ccv-ai-providers-unavailable-503` finding's Groq/OpenRouter/Vertex angles confirmed already covered by rows 6 and 20, no new row added; 2026-10-13 (order 087 close-out): row 51 added for the LiveKit and Pipecat avatar integrations, both built and verified end to end this session, with the PyPI publishes and the two upstream pull requests left as owner actions; 2026-10-13 (order 085 close-out): row 50 added for publishing the CC0 bulk animation library to production, and the Adobe Mixamo permission letter draft is ready to send as owner order 938; 2026-10-12 (order 084 close-out): row 49 added for the Tripo signed webhook's three linked steps (apply the `forge_webhook_deliveries` migration, set `TRIPO_WEBHOOK_SECRET`, register the dashboard webhook), not an active bug since the secret is unset and polling answers every Tripo job today; 2026-10-12 18:10 UTC (triage-lane sweep, third pass): row 48 added for the dist-lib CDN embed size fix (previously-unclassified `/dist-lib/agent-3d.js` 500s, root-caused and fixed on `evolve`, pure code change awaiting the next deploy); 2026-10-12 17:54 UTC (triage-lane sweep, second pass): row 1's same-day "11 behind" figure corrected to the real deploy gap of 0 (querying `/api/version` live, not `/api/healthz`, which has no commit field), row 47 added for CoinGecko's keyless tier being rate-limited (`COINGECKO_API_KEY` already absent from the service, so the finding's own pre-approved env fix is a no-op); 2026-10-12 (triage-lane sweep): row 1 re-measured against the canonical `threews` remote, 11 commits behind `main` (down from 28, local stale ref corrected), row 45 added for the HF image-provider (fal-ai/nscale) credit exhaustion, a separate pool from row 6; 2026-10-11 (best3d order 070 close-out): rows 43 and 44 added for the `model-partcrafter` and `model-holopart` first deploys; 2026-10-11 (triage-lane sweep): row 42 added for the MCP client-sessions nullable-column migration, an active production bug; row 1 re-measured, 28 commits behind `main` (up from 5); 2026-10-11 (best3d order 069 close-out): rows 40 and 41 added for the `model-rig-nonhuman` and `model-anigen` first deploys; 2026-10-11 (best3d order 068 close-out): row 39 added for the `model-pixal3d` first deploy; 2026-10-11 (best3d order 067 retry): row 38 added for the `model-trellis2` first deploy; 2026-10-11 (order 404 close-out): row 34 deleted, its premise cleared by merge commit `d77b89178` (the `evolve`/`main` reconciliation) which also carried the `x-mention-reply.js` `chainFor()` fix row 34 called out, verified live with `RUN_LLM_TESTS=1 npx vitest run tests/x-mention-reply.llm.test.js` (16/16 `source: 'model'`, no `buildBody` TypeError); 2026-10-11 (scout lane): row 36 added for the Cloudflare R2 flapping degraded/down pattern; 2026-10-11 (even later): row 24 re-measured again after order 400's ring-leak-scan tiering/lock fix shipped on `evolve`; 2026-10-11 (later): row 35 added for the agent mention-policy migration; 2026-10-11 04:16 UTC: rows 1 and 24 re-measured by the deep triage sweep; row 34 added for the evolve/main branch divergence; 2026-10-10: row 33 added for the xAI MCP e2e key; rows 1, 19 and 24 re-measured by the triage sweep; 2026-10-09: rows 1, 2 and 24 re-measured by the triage sweep, row 31 added for the GPU worker redeploy and row 32 for database table retention; row 30 added for the Grok Bot CLI setup rerun; 2026-10-08: row 26 added for the coin-gated MCP catalog regeneration; rows 1 and 2 re-measured by the triage sweep, row 24 added for the paid Solana RPC credits, row 25 added for the MCP connector OAuth deploy; 2026-09-30: row 23 added for the $THREE receiver wallets; 2026-09-29: row 19 re-measured after the agent-sniper deploy; 2026-09-09: row 19 added, and row 1 corrected because its outage premise no longer holds; rows 1, 2, 3, 9, 13, 15 and 16 re-measured 2026-09-04; the former row 18 was cleared that day and its number is not reused; the 2026-09-02 and 2026-08-09 passes are folded in below)
| # | Action | Size | Unblocks | Detail lives in |
|---|---|---|---|---|
@@ -72,6 +72,7 @@ on it; some resolve themselves as other work lands.
| 56 | **Publish the AI SDK/LangChain packages and submit the six agent-registry entries plus the LangChain integration issue** (added 2026-10-13 by the evolve loop closing out order 093-partners-10). `packages/ai-sdk/` (`@three-ws/ai-sdk`) and `packages/langchain/` (`@three-ws/langchain`) are both built, real-API-tested (`npm test` in each: 5/5 passing, live calls against production forge/rig/render/agent-chat/animate), and `npm pack --dry-run` clean. Neither has ever been published (new package names, no npm publish has run from this workspace). The six registry entries for Hermes, Kilo, OpenHands, OpenCode, Dify and cursor.directory are written in `marketing/growth/submissions/agent-registries/` in each registry's confirmed real format, and the LangChain integration-package issue text is at [`packages/langchain/INTEGRATION_ISSUE.md`](../../packages/langchain/INTEGRATION_ISSUE.md). Summary: (a) `cd packages/ai-sdk && npm publish --access public`, then the same in `packages/langchain/`; (b) open the LangChain integration issue against `langchain-ai/langchainjs` using `packages/langchain/INTEGRATION_ISSUE.md`'s text; (c) submit each of the six registry entries per its own file's "Owner steps" section in `marketing/growth/submissions/agent-registries/`. | two npm publishes + one GitHub issue + six registry submissions | Lists three.ws in the Vercel AI SDK and LangChain JS tool ecosystems and in six agent-framework registries | [093-partners-10-agent-tool-packages.md](../093-partners-10-agent-tool-packages.md), [packages/langchain/INTEGRATION_ISSUE.md](../../packages/langchain/INTEGRATION_ISSUE.md), [marketing/growth/submissions/agent-registries/](../../marketing/growth/submissions/agent-registries/) |
| 57 | **Create a WordPress.org account and submit the plugin; create a Framer account and submit the Marketplace listing; create a Webflow account, run `webflow devlink import`, and submit the Apps marketplace listing** (added 2026-10-13 by the evolve loop closing out order 094-partners-11). All three embeds for `<agent-3d>` are built and verified: the WordPress plugin ([`integrations/wordpress/three-ws-agent/`](../../integrations/wordpress/three-ws-agent)) passes the official Plugin Check tool against a real local WordPress 7.1.3 in Docker ("Checks complete. No errors found.", reproduced in [`docs/wordpress-embed.md`](../../docs/wordpress-embed.md)); the Framer code component ([`integrations/framer/`](../../integrations/framer)) and the Webflow Code Component ([`integrations/webflow/`](../../integrations/webflow)) each boot a live WebGL canvas against the real pinned production CDN release in a real-React Playwright harness (`tests/e2e/agent-3d-framer-component.spec.js`, `tests/e2e/agent-3d-webflow-component.spec.js`, both passing), and the Webflow component additionally compiles through the real, unmodified `@webflow/webflow-cli`'s `devlink bundle` ("Code Library bundled successfully!"). No WordPress.org, Framer, or Webflow account exists in this workspace, so nothing past this point is testable here. Full step-by-step with exact settings and listing copy for all three: [`marketing/growth/submissions/site-builders.md`](../../marketing/growth/submissions/site-builders.md). Summary: (a) create a WordPress.org account, submit the plugin zip for review, and commit to the assigned SVN repo once approved; (b) create a Framer account, paste the three component files into a project, confirm it renders in Framer's own canvas, and submit to the Marketplace; (c) create a Webflow account, run `webflow auth login` then `webflow devlink import` from `integrations/webflow/`, confirm the component drags into the Designer, and submit to the Apps marketplace. | three account signups + two submissions + one SVN commit + one devlink import | Lists three.ws's `<agent-3d>` embed in the WordPress.org plugin directory, the Framer Marketplace, and the Webflow Apps marketplace | [094-partners-11-site-builder-embeds.md](../094-partners-11-site-builder-embeds.md), [marketing/growth/submissions/site-builders.md](../../marketing/growth/submissions/site-builders.md) |
+| 58 | **Create `github.com/nirholas/three-ws-home-assistant` from the exported tree, confirm its two CI workflows pass, cut a `v1.0.1` release, then open the `hacs/default` and `home-assistant/brands` pull requests** (added 2026-10-13 by the evolve loop closing out order 095-partners-12). `home-assistant-integration/` now validates clean: `manifest.json`'s broken `documentation` link fixed to the live `/docs/home-relay`, `version` bumped to `1.0.1`, `hacs.json`'s minimum Home Assistant version corrected to `2024.12.0` (the first release bundling the `aiohttp.ClientWSTimeout` the integration's relay client uses, confirmed against HA's own `package_constraints.txt` history), and real local brand icons added at `custom_components/three_ws/brand/{icon,icon@2x,dark_icon,dark_icon@2x}.png`. `node scripts/export-hacs-repo.mjs` builds the exact standalone-repository tree (the integration, README, LICENSE, `hacs.json`, and the two validation workflows, which live only in that exported tree since this monorepo runs no GitHub Actions of its own) under `dist/hacs-export/`. Verified this session with the real tools HACS's own CI runs: the real `ghcr.io/home-assistant/hassfest` Docker image against the exported tree ("Invalid integrations: 0"), the real upstream HACS schema/brand/readme validators from `hacs/integration`'s own source (all pass; the GitHub-settings-dependent checks are architecturally impossible to run before the repository exists), and a full real end-to-end install: a real `ghcr.io/home-assistant/home-assistant:stable` container onboarded via its own REST API, paired through the real config flow against a real `services/home-relay` server, 18 real entities read back, and a confirmed auto-reconnect after a relay restart. Full step-by-step with exact settings and PR text for both targets: [`marketing/growth/submissions/home-assistant.md`](../../marketing/growth/submissions/home-assistant.md). Summary: (a) push `dist/hacs-export/` (rebuild with `node scripts/export-hacs-repo.mjs` first) to a new public personal repository at `github.com/nirholas/three-ws-home-assistant`, set its description/topics/issues, confirm `hassfest.yml` and `hacs.yml` both pass on `main`, and cut a `v1.0.1` release; (b) add it to HACS as a custom repository in a real Home Assistant instance and confirm it installs; (c) fork `hacs/default`, add `"nirholas/three-ws-home-assistant"` to the `integration` file between `nimroddolev/chime_tts` and `nishithdev/wled-taskmap`, and open the PR with the title/description already written in the submission file; (d) fork `home-assistant/brands`, copy the four PNGs already sitting in this repository into `custom_integrations/three_ws/`, and open that PR with its own title/description. | one repository creation + one release cut + two pull requests | Lists three.ws's Home Assistant integration in the HACS default store and gives it an official brand icon | [095-partners-12-home-assistant-hacs.md](../095-partners-12-home-assistant-hacs.md), [marketing/growth/submissions/home-assistant.md](../../marketing/growth/submissions/home-assistant.md) |
Deleted 2026-09-01: the former row 5 (`WALLET_ENCRYPTION_KEY_PREVIOUS` policy), which
declared itself "delete on reading" and had outlived that by three weeks.