Remove the shipped Home Assistant plan; keep the launch checklist - #286
Merged
Conversation
plans/home-assistant-integration.md was a working plan and every phase in it is marked shipped + deployed. Nothing links to it, and its content survives where it matters: the integration has its own repository, the /api/integration endpoints are in AGENTS.md, and IntegrationsPage.jsx ships the key-minting UI. Deleted, and plans/ with it. **Deliberately NOT deleting docs/LAUNCH_HANDOFF.md**, despite it looking like exactly this kind of file. It is a live pre-launch tracker and eight of its twelve items are still open — including Clerk production keys (explicitly deferred to "last minute" before launch), lawyer review of the legal templates (which still carry DRAFT — NOT FOR EXECUTION at the top), and the day-before go/no-go checklist. Item 9 changed as recently as today, when required status checks were added to master. Deleting the launch checklist while pre-launch would throw away the plan for the thing about to happen. It should go once launch is done, not before. Did fix one genuinely temporary thing inside it: step 5 of the email setup pointed at `~/.claude/plans/gentle-coalescing-teacup.md`, a scratch file on one machine that no reader will ever have. Replaced the pointer with the steps it was pointing at. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Removed
plans/home-assistant-integration.md— a working plan whose every phase is marked shipped + deployed. Nothing links to it, and its content survives where it matters: the integration has its own repo,/api/integrationis documented inAGENTS.md, andIntegrationsPage.jsxships the key-minting UI. Deleted, andplans/with it.Deliberately kept:
docs/LAUNCH_HANDOFF.mdIt looks like exactly the kind of file you asked me to remove. It isn't — it's a live pre-launch tracker, and 8 of its 12 items are still open:
Deleting it while pre-launch would throw away the plan for the thing that's about to happen. It should go after launch, not before — at which point it's genuinely spent and I'll remove it without asking.
Fixed one genuinely temporary thing inside it
Step 5 of the email setup pointed at
~/.claude/plans/gentle-coalescing-teacup.md— a scratch file on one machine that no reader will ever have. Replaced the dangling pointer with the steps it was pointing at.Flagged separately, not touched
8 MB of built frontend output is committed — 55 files under
backend/static/, not gitignored. The Dockerfile rebuilds it fresh, so production doesn't depend on the committed copy. Butmain.py:1569serves the SPA from that directory, so a plainpython start.pyon a fresh clone would show no UI without it. That's a real trade-off and a different category from temporary notes, so it's your call rather than mine.79 links verified.
🤖 Generated with Claude Code