# Full handoff prompt (paste into another model)

Copy everything below the line into the other AI dev instance to ground it and define what to do.

---

You are picking up work on the **LLMHosts.com** codebase. Your job is to continue from where things left off with full context and execute the next highest-priority work to a masterclass standard. You have full control and permissions; do not ask for permission — read the repo and GitHub, then act.

**What this repo is:** LLMHosts.com turns a home GPU into production AI infrastructure accessible from anywhere. SaaS, all pay, no open source. Stack: Python 3.12 + FastAPI (proxy), Next.js 16 + TypeScript (frontend), SQLite/Prisma. All task state and execution order live in **GitHub** (issues, Project #5, milestones, labels). The repo is the code and docs; GitHub is the single source of truth for what to do and what’s done.

**Do the following in order:**

1. **Sync from GitHub (run these commands and read the output):**
   ```bash
   gh issue list --state open --limit 25
   gh pr list --state open
   gh project item-list 5 --owner LookNoHandsMom --limit 30
   gh run list --limit 5
   git status && git log --oneline -5
   ```

2. **Read these repo files in this order (full read, top to bottom):**
   - `AGENTS.md` — project identity, architecture, commands, session protocol.
   - `docs/SSOT-AND-HANDOFF.md` — where state lives, GitHub Pro usage, key docs list, sync protocol, handoff steps.
   - `docs/planning/VISION-AND-CAPABILITIES-INDEX.md` — vision, capability areas → docs/issues, execution order, definition of masterclass.
   - Issue **#325** (fetch with `gh issue view 325` or in browser) — master execution playbook; body + recent comments give execution order and remaining work.

3. **Orient:** From the issue list and #325, determine: (a) what was last worked on (git log, open PRs), (b) what needs attention (open issues, failing CI), (c) what is highest priority (labels P0-blocker, P1-critical, priority:high; milestones; #325’s list).

4. **Pick the next task:** Choose the highest-priority open issue you can work on. If it’s an E2E run (#359, #360–#362), you need access to the real machine (Alienware, Mac Mini, etc.) and test account; if you don’t have that, pick the next task (e.g. #354–#358, #320–#324, or conversion/launch items). For any issue: open it → read the **body** (Source doc §, Execution steps, Acceptance criteria) → open the **linked doc sections** in the repo → implement or run per the acceptance criteria.

5. **Execute to masterclass standard:**  
   - Implement or run the task so that all acceptance criteria in the issue body are met.  
   - Follow the linked doc (playbook section, MASTER-E2E-PLAN, P5-full-test-guide, etc.).  
   - Before claiming done: run `pytest tests/ -q` and `cd frontend && npm run test -- --run` (or the relevant verification); fix any regressions.  
   - Close the issue with a comment (what was done, where). If it’s part of an epic, add a comment to the epic. If it’s a major batch, add a progress comment to #325.

6. **Sync back to GitHub:** Commit with a conventional message (e.g. `feat(scope): description`), push to a feature branch, open or update a PR with `Closes #<number>` in the body. Do not push directly to `main` (branch protection requires PR + CI). After merge (or if you only commented), the state is synced — next agent or human continues from `gh issue list` and #325.

7. **Loop:** Repeat from step 1 (or from step 3 if you’re in the same session). Keep going until the user stops you or there is no more open work you can do (e.g. only human-run E2E left).

**Rules:**  
- No local state is required; everything needed is in the repo + GitHub. Secrets (API keys, passwords) come from the project owner or environment.  
- Every micro and macro item is in GitHub with acceptance criteria and doc links; complete items to that standard.  
- If you are unsure what to do next, read #325 again and the open issue list; use `docs/planning/VISION-AND-CAPABILITIES-INDEX.md` to see which capability area each issue belongs to and which doc to follow.  
- For E2E runs: test account brendonurban@gmail.com; password from project owner; API key from app (Dashboard → API Keys). Execution steps: `docs/testing/README.md` → `docs/testing/MASTER-E2E-PLAN.md` → `docs/testing/P5-full-test-guide.md` (Part A, Phase 0, Part B, Part C); report recap + Unresolved issues in the run’s GitHub issue.

**Start now:** Run the commands in step 1, then read the files in step 2, then proceed through steps 3–7.
