feat: upgrade agent team with browser, MCP, CLI tools, rules, and hooks

- Add Chrome browser access to 6 visual agents (18 tools each)
- Add Playwright access to 2 testing agents (22 tools each)
- Add 4 MCP servers: Postgres Pro, Redis, Lighthouse, Docker (.mcp.json)
- Add 3 new rules: testing.md, security.md, remotion-service.md
- Add Context7 library references to all domain agents
- Add CLI tool instructions per agent (curl, ffprobe, k6, semgrep, etc.)
- Update team protocol with new capabilities column
- Add orchestrator dispatch guidance for new agent capabilities
- Init git repo tracking docs + Claude config only

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

AGENTS.md

@@ -0,0 +1,24 @@
+# Repository Guidelines
+
+## Project Structure & Module Organization
+This workspace has three services: `cofee_frontend/` for the Next.js UI, `cofee_backend/` for the FastAPI API, and `remotion_service/` for video rendering. Frontend routes live in `cofee_frontend/app/`; app code lives in `cofee_frontend/src/{pages,widgets,features,entities,shared}`; E2E specs live in `cofee_frontend/tests/e2e/specs/`. Backend code lives in `cofee_backend/cpv3/`, with modules under `cpv3/modules/` and tests in `tests/unit/` and `tests/integration/`. Remotion API code lives in `remotion_service/server/`, compositions in `remotion_service/src/`, and assets in `remotion_service/public/`.
+
+## Build, Test, and Development Commands
+- `cd cofee_frontend && bun dev` starts frontend.
+- `cd cofee_frontend && bunx tsc --noEmit` is the current reliable frontend check; `bun run test:e2e` runs Playwright.
+- `cd cofee_backend && uv sync && uv run uvicorn cpv3.main:app --reload` starts backend.
+- `cd cofee_backend && uv run pytest` runs backend tests; `uv run ruff check cpv3/` and `uv run ruff format cpv3/` lint and format Python code.
+- `cd cofee_backend && docker-compose up` starts Postgres, Redis, MinIO, API, and worker.
+- `cd remotion_service && bun run server` starts the render API; `bun run dev` opens Remotion Studio; `bun run lint` runs ESLint and TypeScript checks.
+
+## Coding Style & Naming Conventions
+Prefer early returns, descriptive names, and named constants over magic values. Frontend formatting uses tabs, no semicolons, double quotes, and sorted imports; use aliases such as `@shared/*` and keep FSD imports one-way: `pages -> widgets -> features -> entities -> shared`. Backend code targets Python 3.11+, uses absolute imports, async functions, and the standard module file set: `models.py`, `schemas.py`, `repository.py`, `service.py`, `router.py`. Keep user-facing UI text in Russian.
+
+## Testing Guidelines
+Frontend Playwright files use `*.spec.ts` and `*.integration.spec.ts`; prefer `getByRole` locators and cover error paths, not just happy paths. Backend tests follow `test_*.py` naming and should land in `tests/unit/` or `tests/integration/` based on scope. No repository-wide coverage gate is configured, so add regression tests for behavior changes. `remotion_service` currently relies on linting plus manual render verification.
+
+## Commit & Pull Request Guidelines
+Recent history favors short, lowercase subjects, sometimes with prefixes such as `feature:`, `chore:`, or `init:`. Keep commits scoped to one service when possible, for example `feature: add silence settings validation`. PRs should name the service, link the task, list commands run, include screenshots or video for UI and captioning changes, and mention backend schema updates plus regenerated frontend API types when relevant.
+
+## Contributor Notes
+Check the root `CLAUDE.md` and the matching service-level `CLAUDE.md` or `AGENTS.md` before non-trivial changes.