docs: document running the dev server for QA (#677)

## What

Adds a "Running the server for QA" subsection to the project `CLAUDE.md`
so commands/skills that ask the user to open the app in Chrome have
clear, project-level steps.

## Steps documented

1. First run in a worktree? Prepare it with `./worktree.sh
<main-repo-path>`.
2. Start the server if it isn't running: `composer run dev`.
3. Get the dynamic per-worktree URL — `composer run dev` prints and
copies it to the clipboard on startup; don't guess it.

Docs-only change.
This commit is contained in:
Víctor Falcón 2026-07-14 23:38:11 +02:00 committed by GitHub
parent 55eff788e8
commit 9e237802f6
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
1 changed files with 8 additions and 0 deletions

View File

@ -15,6 +15,14 @@ composer run dev # Start full dev environment (PHP server, queue, Vite,
bun run dev # Vite dev server only bun run dev # Vite dev server only
``` ```
### Running the server for QA
When a command or skill needs the user to open the app in Chrome to review a change:
1. **First run in a worktree?** Prepare it: `./worktree.sh /path/to/main/repo` (copies `.env` + `storage/keys`, installs `bun` and `composer` deps). Skip if already set up.
2. **Start the server** if it isn't running: `composer run dev`.
3. **Get the URL** — it's dynamic per worktree, so don't guess it. On startup `composer run dev` prints and copies it to the clipboard (`✓ <URL> copied to clipboard`); read it from the `server` pane output. Ask the user to open that URL in Chrome to QA.
### Build & Quality ### Build & Quality
```bash ```bash