← ClaudeAtlas

rembric-smoke-testslisted

End-to-end smoke against the local rembric dev server (`pnpm run dev`, host Next.js dev on :3000). Apply when the user says "smoke", "probar contra docker", "dev:up", or after applying an OpenSpec change that touches HTTP (`apps/web/src/app/api/`), MCP tools (`packages/mcp/src/`), or DB migrations (`packages/db/src/migrations/`). Encodes bring-up, readiness verification, probe pattern and teardown — not the probes themselves.
susomejias/rembric · ★ 12 · Testing & QA · score 72
Install: claude install-skill susomejias/rembric
# Rembric smoke pattern Real-stack verification of a change before opening the PR. Read `apps/web/package.json::dev` (`next dev`) and `docs/docker.md` → "Local dev (host)" for the source of truth on how the server boots and where it listens — this file gives you only the pattern that survives those changing. > The Docker dev stack is **retired**. `pnpm run dev:docker:up` is not a root script, `docker-compose.dev.yml` does not exist, and the compose files describe only the published image. Local dev is the Next.js server on the host. ## 0. Preflight: free the RAM the build needs `/tmp` is a tmpfs on this box, so everything under it is RAM. Every vitest run leaves a `rembric-test-*` directory behind and nothing cleans them: 1624 of them once held 8 GB, leaving 2.4 GB free, and `pnpm run dev` died with `exit code: 137` (`Killed`) mid-`pnpm install`. That failure reads like a network or lockfile problem and is neither. ```bash free -h # the `shared` column is the tmpfs find /tmp -maxdepth 1 -name 'rembric-test-*' -mmin +60 -exec rm -rf {} + ``` Keep the `-mmin +60`: other sessions may be mid-run, and a bare glob takes their fixtures with it. ## 1. Bring up from the change's worktree ```bash cd <your-worktree> REMBRIC_DATA_DIR=./data-dev REMBRIC_ADMIN_TOKEN=<16+-char-token> pnpm run dev # → http://127.0.0.1:3000/dashboard ``` Point `REMBRIC_DATA_DIR` at a scratch directory (gitignored `./data-dev` is the convention) — ne