# Alpha Release Readiness Checklist: Builder Kit v1 (Local-First)

## 1. Pre-release Repository Checks
**Expected Result:** The codebase is safe to share, clean, and properly tagged on GitHub without any sensitive data included.
- [ ] Verify the repository is completely clean (`git status` shows no pending changes).
- [ ] Confirm no private API keys, tokens, or passwords are accidentally hardcoded or included in `.env` templates.
- [ ] Ensure the latest stable tags (e.g., `installer-test-mode-v1`, `help-system-v1.1`) are pushed to the main repository.
- [ ] Verify that `start_assistant_windows.bat` uses dynamic WSL detection instead of hardcoded paths.
- [ ] Check that the `README.md` or setup instructions accurately reflect the current local-first approach.

## 2. Clean Install Checks (Authentic Windows Path)
**Expected Result:** A completely new computer can download and run the kit without old files getting in the way.
> **WARNING:** Do not proceed to actual testing if you have not backed up or renamed your current working workspace to avoid accidental deletion.
- [ ] Copy/download ZIP to Windows Downloads
- [ ] Right-click Extract All
- [ ] Open extracted folder
- [ ] Double-click START_HERE_WINDOWS.bat
- [ ] Confirm the launcher selects Ubuntu, not Ubuntu-18.04
- [ ] Confirm dependency install works or skips if already installed
- [ ] Confirm TutorClaw opens
- [ ] Ask TutorClaw: “Give me the Simple Tour”

## 3. Required User Setup Checks
**Expected Result:** The user is clearly prompted to provide their own provider API keys before any complicated setup begins.
- [ ] Run `bash install.sh` without creating an `.env` file first.
- [ ] Confirm the installer stops immediately and instructs the user to fill out their `.env` file.
- [ ] Confirm the `.env` template is successfully generated with clear placeholders (e.g., `your-real-key`).
- [ ] Add valid Gemini and Google API keys to the `.env` file and verify the installer now allows you to proceed.

## 4. Installer Checks
**Expected Result:** The installation runs from start to finish smoothly without errors or manual fixes.
- [ ] Run the installer and verify the Python environment and dependencies install cleanly.
- [ ] Confirm the OpenClaw bundled installation finishes without crashing.
- [ ] Verify the installer correctly writes the runtime configuration to the user's hidden OpenClaw directory.
- [ ] Verify the final summary screen displays the correct installation paths for the runtime config and environment variables.

## 5. Shortcut/Launcher Checks
**Expected Result:** The user can launch their assistant using a simple, standard Windows icon.
- [ ] Confirm the installer automatically creates a "Start My Assistant" shortcut on the Windows Desktop.
- [ ] Confirm a second "Start My Assistant" shortcut is placed inside the project folder.
- [ ] Double-click the desktop shortcut and verify it successfully launches the local assistant server without showing path errors.
- [ ] Verify the launcher works regardless of the user's specific Windows or Linux username.

## 6. First-Run Assistant Checks
**Expected Result:** The user can access the chat interface and the assistant introduces itself appropriately.
- [ ] Open a browser and navigate to the dashboard (`http://127.0.0.1:18789`).
- [ ] Confirm the connection succeeds and the chat interface loads without endless spinning.
- [ ] Send a basic greeting (e.g., "Hello").
- [ ] Verify the assistant responds properly and does not identify itself as "C-3PO" or use old system prompts.

## 7. Help System Checks
**Expected Result:** The beginner guide files are active, readable, and ready for the user.
- [ ] Verify the `knowledge_base` folder was successfully created in the active workspace.
- [ ] Check that `help_index.json` and the `.md` help guides (e.g., `getting_started.md`, `what_can_i_do.md`) are present.
- [ ] Ask the assistant: "How do I get started?" and confirm it references its internal help guides.
- [ ] Ask the assistant: "What can you do?" and confirm it provides an accurate summary based on the knowledge base.

## 8. Tool Readiness and Permissions Checks
**Expected Result:** The assistant respects user permissions and clearly explains tool requirements before acting.
- [ ] Ask the assistant to perform an action requiring a tool (e.g., "Read this PDF for me").
- [ ] Confirm the assistant first states whether it has the required tool available and if it needs your permission to proceed.
- [ ] Confirm the assistant pauses and explicitly waits for your "Yes/No" approval before running any newly introduced scripts or commands.
- [ ] Start a `/new` session and verify the "Tool Readiness Rule" is still strictly enforced from the very first message.

## 9. Safety/Update-Policy Checks
**Expected Result:** The assistant stays private and does not attempt unwanted background downloads.
- [ ] Verify that automatic system updates are disabled in the OpenClaw configuration (`update.auto.enabled = false`).
- [ ] Verify that checking for updates on startup is disabled (`update.checkOnStart = false`).
- [ ] Confirm the default local model is correctly set to `google/gemini-2.5-flash-lite`.

## 10. Reset/Uninstall/Recovery Checks
**Expected Result:** The user can safely wipe their assistant clean and start over if something breaks.
> **WARNING:** Do not proceed with testing wipe commands unless you are absolutely sure you are in a test environment.
- [ ] Verify that deleting the `.openclaw` runtime folder completely resets the assistant's memory and configuration.
- [ ] Re-run the installer after a wipe and confirm it cleanly rebuilds the environment without conflicts.

## 11. Known Limitations Before Alpha
**Expected Result:** You understand what is *not* working yet so you can communicate this to early testers.
- [ ] Outline any current limits (e.g., "Requires WSL to be pre-installed by the user").
- [ ] Note any tools that are currently disabled or fragile (e.g., PDF reading, complex bash scripts).
- [ ] Document that cloud/VPS deployments are entirely unsupported in this local-first version.

## 12. Alpha Pass/Fail Decision
**Expected Result:** A definitive go/no-go choice for releasing the alpha.
- [ ] **PASS:** All critical boxes above are checked. The assistant installs cleanly, respects paths, launches via shortcut, and obeys tool permissions. It is safe for alpha testing.
- [ ] **FAIL:** One or more critical boxes failed. Do not release until the failing components are patched.
