redbar

Write the missing tests for the gaps redbar found, following the canonical standard for that layer (Playwright's best practices for e2e, Vitest/Jest idiom for unit, Testcontainers for integration). Reads `.redbar/gaps.json`, writes one test file per gap, RUNS each test it wrote, and never leaves a failing test behind — a test that fails twice is marked needs-human and deleted. Use after /redbar.inspect, or when asked to write the missing tests, cover a gap, or fix coverage.

Set a project up so redbar can inspect it. Detects the language and the test runner it actually uses, then proposes the test libraries that are missing (unit, integration, e2e) and prints the exact install command. It NEVER installs anything and never edits a manifest — the human approves and runs the command. Use when redbar reports no coverage report, when a project has no test setup, or when asked how to start testing a repo.

Find the test-coverage gaps in what changed on this branch. Runs the redbar engine, which crosses the project's coverage report with `git diff` and ranks the untested symbols by criticality. It calls no model to produce the number — the number comes from the coverage report and git. Use before opening a PR, when asked "what should I test?", or when asked what the branch left untested. It writes `.redbar/gaps.json` and reports what came back.