Post-Implementation Verification

After completing any feature, bug fix, or refactor — run verification before claiming the work is done.

Base Verification (after every code change)

Frontend (`cofee_frontend/`)

cd cofee_frontend && bunx tsc --noEmit 2>&1 | head -30

Must pass. Pre-existing errors in app/template.tsx:15 and CreateProjectModal.tsx:57 are known — no new errors allowed.

Backend (`cofee_backend/`)

cd cofee_backend && uv run ruff check cpv3/ 2>&1 | head -20
cd cofee_backend && uv run pytest 2>&1 | tail -30

Lint and tests must pass.

Remotion (`remotion_service/`)

cd remotion_service && bunx tsc --noEmit 2>&1 | head -30

Must pass.

Final Verification (before PR/merge)

Run base verification PLUS:

Frontend

cd cofee_frontend && bun run build 2>&1 | tail -20       # Production build
cd cofee_frontend && bun run test:e2e 2>&1 | tail -30    # Playwright E2E

Backend

cd cofee_backend && uv run ruff format --check cpv3/     # Format check

If you changed models: uv run alembic check to verify migrations are up-to-date.

Verification Report

VERIFICATION REPORT
===================
Subproject:  [frontend/backend/remotion]
Level:       [base/final]
Type check:  [PASS/FAIL]
Lint:        [PASS/FAIL]
Tests:       [PASS/FAIL] (X passed, Y failed)
Build:       [PASS/FAIL or SKIPPED]
E2E:         [PASS/FAIL or SKIPPED]

Files changed: [count]
Status: [READY/NOT READY]

Issues to fix:
1. ...

When to Skip

Typo fixes in comments
Documentation-only changes
Changes to CLAUDE.md / agent definitions

When to Always Run Final

Cross-service changes (frontend + backend)
Schema/model changes
Auth or security-related changes

1.7 KiB Raw Blame History