specweave 1.0.593 → 2.0.3

package/plugins/specweave/skills/review/SKILL.md

@@ -0,0 +1,102 @@
+---
+description: Adversarial fresh-context review of an increment before it ships. Every finding cites path:line and is re-verified. Use when saying "review", "grill this", or "critique the implementation".
+version: 2.0.0
+argument-hint: "<increment-id> [--full]"
+---
+
+# Review Increment
+
+One review surface (it replaces the old grill / code-reviewer / judge-llm passes).
+Reads the increment's spec, its diff and the code around it, then reports what is
+actually wrong — with `path:line` for every claim. Writes
+`reports/review.md` + `reports/review.json` under the increment.
+`specweave complete` prints a notice when review.md is absent but never blocks.
+
+## Usage
+
+```
+sw:review <increment-id>            # single adversarial pass
+sw:review <increment-id> --full     # 3 parallel lenses: correctness, security, spec-compliance
+```
+
+## Rules
+
+1. **Fresh context. The session that wrote the code never approves it.** Run the pass
+   through a subagent (Claude Code: `Task({ subagent_type: "general-purpose", … })`) or a
+   new session in any other tool. If you wrote this code in this context and cannot spawn
+   one, say so in the report instead of claiming an independent review.
+2. **Every finding cites `path:line`** and states a concrete failure: inputs or state →
+   wrong output, crash, data loss, or leak. No "consider refactoring", no style opinions.
+3. **Re-verify before reporting.** Re-open the cited lines — and run the test that would
+   fail — and drop anything that does not survive. A wrong finding costs more than a
+   missed one. Unverifiable but plausible findings are reported as `plausible`, not as fact.
+4. **Severity**: critical / high / medium / low. Only critical and high are blocking.
+5. **Nit cap 5.** At most five low findings; if there are more, report the five worst and
+   one line saying how many were dropped.
+6. **Scope is the increment's diff**, not the repository:
+   `git diff $(git merge-base HEAD <base>)...HEAD -- <the tasks' Files>`.
+
+## Steps
+
+1. **Scope**: read `spec.md` (ACs + Approach) and the `Files:` fields in `tasks.md`.
+   Collect the diff for those files plus the code they call.
+2. **Pass** — in this order:
+   - correctness: wrong logic, unhandled error paths, races, off-by-one, resource leaks;
+   - security: injection, path traversal, secret leakage, missing authz, unsafe spawn/exec;
+   - spec-compliance: ACs marked done but not implemented, tests that assert nothing,
+     behaviour that contradicts spec.md.
+   With `--full`, run those three as parallel subagents and merge their findings
+   (dedupe by `file:line + summary`).
+3. **Verify** each candidate finding as per rule 3.
+4. **Report**: write both files (shapes below).
+5. **Hand back**: fix critical/high findings yourself or hand them to `sw:do`, then re-run
+   `specweave verify <id>` and close with `sw:done`.
+
+## Report shape
+
+`reports/review.md`:
+
+```markdown
+# Review — <id> <title>
+Verdict: fix first | ship · reviewed <n> files · <n> findings (<n> critical, <n> high)
+Reviewer context: subagent | new session | same session (NOT independent)
+
+## [critical] src/core/tasks/ledger.ts:142 — stale claim never released
+Given two agents claim T-01 inside the lease window … → the second write wins and the
+first agent's `done` line is dropped.
+Fix: compare-and-append on the claim line before writing.
+```
+
+`reports/review.json` (machine-readable, same findings):
+
+```json
+{
+  "ok": false,
+  "increment": "0042",
+  "reviewedAt": "2026-09-02T12:00:00Z",
+  "mode": "single",
+  "findings": [
+    {
+      "severity": "critical",
+      "file": "src/core/tasks/ledger.ts",
+      "line": 142,
+      "summary": "stale claim never released; second writer drops the first done line",
+      "confidence": "confirmed"
+    }
+  ],
+  "droppedNits": 0
+}
+```
+
+`ok` is `true` only when there is no critical or high finding.
+
+## Anti-patterns
+
+- Approving your own work in the same context — that is the one thing this skill exists to prevent.
+- Findings without a line number, or with a line number you did not re-read.
+- Padding the count with style nits (see the nit cap).
+- Reviewing the whole repo instead of the increment's diff.
+
+## Resources
+
+- [Official Documentation](https://verified-skill.com/docs/reference/skills#review)

package/plugins/specweave/skills/sync/SKILL.md

@@ -0,0 +1,63 @@
+---
+description: One sync surface for GitHub, Jira and Azure DevOps: push progress, pull or import issues, check health, run setup. Use when saying "sync", "push to GitHub", or "import issues".
+version: 2.0.0
+argument-hint: "push|pull|status|setup [increment-id]"
+---
+
+# sw:sync — external tracker sync
+
+Everything goes through the CLI. Never call `gh`, `curl`, or a provider REST API
+directly: the CLI owns token resolution, the rate budget, duplicate detection and
+the bidirectional links.
+
+## Commands
+
+| Intent | Command |
+|---|---|
+| Push local progress to issues | `specweave sync push [increment-id]` |
+| Preview a push | `specweave sync push <id> --dry-run` |
+| Push to one provider | `specweave sync push <id> --provider github` |
+| Fix stale/duplicate milestones first | `specweave sync push <id> --reconcile` |
+| Report external changes | `specweave sync pull [--since 7]` |
+| Import issues as increments | `specweave sync pull --create-increments` |
+| Tokens, health, retry queue, gaps | `specweave sync status [--json]` |
+| Connect a provider | `specweave sync setup [--provider github]` |
+| Validate an existing config | `specweave sync setup --validate` |
+
+`sync push` runs tasks.md → spec.md ACs → living docs → provider write, then
+drains the retry queue through the same entry point. Exit code of
+`sync status` is 1 when anything needs attention; `--json` prints one parsable
+report (`providers`, `github`, `health`, `resilience`, `gaps`, `hasIssues`).
+
+Not sync: `specweave doctor --fix-status` repairs metadata.json ↔ spec.md status
+desyncs, and `specweave sync-living-docs` regenerates internal living docs.
+
+## Providers
+
+Read the provider from `.specweave/config.json` (`sync.github` / `sync.profiles`);
+never guess. GitHub is the first-class path. **Jira and Azure DevOps are
+community-maintained**: push and close work, nothing else is guaranteed — say so
+before promising Jira/ADO behaviour.
+
+Tokens resolve in one documented order: `.specweave/config.json` → `process.env`
+(`GITHUB_TOKEN`, then `GH_TOKEN`) → project `.env` → `gh auth token`.
+`sync status` prints which layer and which account won. A 404 on write means the
+token's account has no write access to `owner/repo` — fix the token, do not retry.
+
+Concept mapping tables: `plugins/specweave/reference/{github,jira,ado}/*-specweave-mapping.md`.
+
+## Bidirectional links (required both ways)
+
+- Local → external: the issue key lives in `metadata.json` under `externalLinks`.
+- External → local: the issue body carries the increment id and the commit sha.
+
+If either side is missing after a push, the link is broken — re-run
+`specweave sync push <id> --force` rather than editing the issue by hand.
+
+## Rules
+
+1. Push after tasks change, not on every edit.
+2. Never edit `externalLinks` by hand.
+3. `--dry-run` first when the increment has never synced.
+4. Report `sync status` output verbatim when it reports issues; do not paraphrase
+   token or permission errors.

package/plugins/specweave/skills/team/SKILL.md

@@ -0,0 +1,89 @@
+---
+description: Run one increment with several agents in parallel - a worktree each, claims through the ledger, one closure. Use when the work has 3+ disjoint lanes, or when saying "team" or "parallel agents".
+version: 2.0.0
+---
+
+# Team
+
+Run one increment with N agents in parallel — **any vendor, any subscription**
+(Claude Code, Codex, OpenCode, Cursor, Gemini, a human). Coordination happens
+only through committed files: `tasks.md` (definitions), `ledger.jsonl`
+(append-only state), `handoff.md`. No message bus, no shared memory; Claude
+Code's TeamCreate/Task tools are accelerators, never requirements.
+
+## You are the orchestrator
+
+- You plan, split, spawn, watch, merge, close. You do **not** implement.
+- Fan out when domains ≥ 3 or tasks ≥ 15 or the user asked for parallel work; otherwise `sw:do` directly.
+- One increment, one `tasks.md`, one ledger. Do not create per-agent increments.
+
+## The 5 rules every agent gets (paste verbatim into each agent prompt)
+
+1. **One worktree per agent**: `git worktree add ../<id>-<agent> -b inc/<id>-<agent>` (Claude: `claude --worktree <id>-<agent>`). Branch name contains the increment id. Set `SPECWEAVE_AGENT=<agent>` (else id = `<tool>@<host>`).
+2. **Claim before edit**: `specweave task next <id>` → `specweave task claim T-NN <id>`. Edit only that task's `Files`. Need another file → claim its task or add a task.
+3. **Append only**: never edit or delete ledger lines, never edit another task's state line. On a ledger merge conflict keep every line from both sides (`.gitattributes` has `**/ledger.jsonl merge=union`).
+4. **Done needs evidence**: commit with the id in the subject, then `specweave task done T-NN <id> --run "<Test>"` (exit 0 required). Paste the output in your reply.
+5. **When stopping**: `specweave task release --all-mine` then `specweave handoff <id>`.
+
+No CLI on that machine? The agent appends the JSON line itself:
+`{"t":"T-NN","e":"claim|done|release|block|skip","by":"<agent>","at":"<ISO UTC>","evidence":"<sha + test>","note":"…"}`.
+
+## Phase 1 — Split (before spawning)
+
+1. Read `spec.md` once. Confirm `tasks.md` is in 2.0 form: `### T-NN Title` + `- AC: … | Files: … | Test: …`. If not, rewrite it (this is the only time tasks.md changes structure).
+2. **Files are the ownership unit.** Two tasks that touch the same file cannot run in parallel: merge them into one task or add `**Dependencies**: T-NN`. Shared contracts (types, API schemas, migrations) go into an early task that everything else depends on.
+3. Group tasks into lanes (backend / frontend / db / tests / docs …) so each lane's Files are disjoint. Lanes = agents. 2–5 agents; more rarely helps.
+4. Run `specweave task list <id>` — it must show every task `open`. Commit `tasks.md`.
+
+## Phase 2 — Spawn
+
+For each lane spawn one agent (Claude: `Task({ subagent_type: "general-purpose", … })` or a TeamCreate teammate; other vendors: a terminal in the lane's worktree with the prompt below). Prompt template:
+
+```
+You are agent <agent> on increment <id> (<title>). Worktree: <path>. Branch inc/<id>-<agent>.
+Your lane: <lane name>. Tasks you may claim: T-NN, T-MM (others belong to other lanes).
+Rules: <the 5 rules above>.
+Loop: specweave task next <id> → claim → implement inside Files → commit "<id>: …" → task done --run.
+Contract: <shared types / API / schema the lane must respect>.
+When your tasks are done or you are blocked: task release --all-mine, specweave handoff <id>, then reply with:
+  DONE: T-NN (sha, test output tail) | BLOCKED: T-MM (reason) | HANDOFF: <handoff.md path>
+```
+
+Agent templates for common lanes live in `agents/` (backend, frontend, database, security, testing, pm, architect, researcher, reviewer-security, brainstorm-*). `_protocol.md` is prepended automatically by `specweave team`.
+
+## Phase 3 — Watch (cheap)
+
+- Poll `specweave task list <id>` (or read `ledger.jsonl`) instead of chatting. `blocked` rows are your queue: unblock (provide the secret, split the task, decide) and reply to that agent only.
+- Stale claim (older than `tasks.leaseHours`, default 2h) with no progress → the agent is gone: `task claim --force` by a replacement agent, or reassign the lane.
+- Do not re-read agents' full diffs; read their DONE lines and the ledger evidence.
+
+## Phase 4 — Merge
+
+1. Every agent has released + handed off. Merge lane branches into the increment branch in dependency order; ledger conflicts resolve by union (keep all lines). tasks.md conflicts: keep both agents' state lines, then `specweave task render <id>`.
+2. `specweave verify <id>` on the merged tree → `reports/verify.json`. Red → open a fix task, assign one agent, repeat.
+3. `sw:review` (optional, recommended) on the merged diff → `reports/review.md`.
+4. `specweave complete <id> --yes` (add `--reason` only if the user accepts a red verify). Only the lead closes.
+5. Remove worktrees: `git worktree remove ../<id>-<agent>`.
+
+## Other modes (same skeleton, different lanes)
+
+| Mode | Lanes | Merge artifact |
+|---|---|---|
+| brainstorm | advocate / critic / pragmatist (see `agents/brainstorm-*.md`) | `reports/brainstorm.md`, then `sw:increment` |
+| plan | pm (spec.md) + architect (Approach/plan.md) in parallel | reviewed spec.md before any task is claimed |
+| review | correctness / security / spec-compliance lenses (`sw:review --full` runs these) | `reports/review.md` |
+| research | one topic per agent | `reports/research-<topic>.md` |
+| test | unit / integration / e2e | `specweave verify` commands in `testing.commands` |
+
+## Anti-patterns
+
+- Agents editing files outside their task's `Files` ("I just fixed a typo there") — that is how merges break. Add a task.
+- Marking `[x]` in tasks.md by hand. The ledger wins; `task render` overwrites it.
+- Per-agent increments to avoid conflicts — you lose the single ledger and the single verify.
+- The lead implementing "just this small piece". Spawn an agent or finish the team first.
+- Closing while a claim is live. Wait for release/handoff or take it over explicitly.
+
+## Resources
+
+- `specweave task --help`, `specweave verify --help`, `specweave handoff --help`
+- [Official Documentation](https://verified-skill.com/docs/reference/skills#team)

package/plugins/specweave/skills/{team-lead → team}/agents/_protocol.md

@@ -79,7 +79,7 @@ Approve only if you have no unsaved state. Approving terminates your process.
 
 ## Rules (apply to every agent)
 
-- Do NOT run `sw:done` or `sw:grill` — team-lead handles closure centrally
+- Do NOT run `sw:done` or `sw:review` — the lead closes the increment centrally
 - WRITE only to your assigned file patterns (listed in the domain template below)
 - READ any file for context
 - Send STATUS heartbeat after every 2-3 tasks minimum

package/plugins/specweave/skills/{team-lead → team}/agents/architect.md

@@ -10,8 +10,10 @@ MISSION:
   Produce plan.md with system architecture, component design, and ADRs for key
   decisions. You own the HOW. Works in parallel with Security reviewer.
 
-SKILLS TO INVOKE:
-  Skill({ skill: "sw:architect" })
+PROCEDURE:
+  Write the Approach section of spec.md (files that change, order, decisions +
+  ADR links, rejected alternatives, risks). plan.md only when the design genuinely
+  overflows one section.
 
 FILE OWNERSHIP (WRITE access):
   [MASTER_INCREMENT_PATH]/plan.md

package/plugins/specweave/skills/{team-lead → team}/agents/backend.md

@@ -5,7 +5,7 @@ You are the BACKEND agent for increment [INCREMENT_ID].
 MASTER SPEC: [MASTER_INCREMENT_PATH]/spec.md — read before planning. Work MUST
 satisfy ACs relevant to your domain.
 
-SKILLS: sw:architect · infra:devops (if deployment config) · sw:service-connect (auth/external)
+REFERENCE: spec.md Approach for the architecture; the increment ADRs for auth/external services
 
 FILE OWNERSHIP (WRITE):
   src/api/** · src/services/** · src/middleware/** · src/routes/** ·
@@ -15,7 +15,7 @@ READ: Any file (especially prisma/schema.prisma, src/types/)
 
 AUTH SETUP:
   If project needs auth, set up the provider (Supabase, Firebase, Auth0, etc.)
-  using sw:service-connect. Ensure auth middleware works end-to-end before
+  following the increment ADRs. Ensure auth middleware works end-to-end before
   signaling COMPLETION.
 
 WORKFLOW:
@@ -26,7 +26,7 @@ WORKFLOW:
   5. Wait for Phase 1 contracts: prisma/schema.prisma, src/types/
   6. Create plan.md and tasks.md
   7. Send PLAN_READY (shared protocol) — do NOT wait for approval
-  8. sw:auto: API endpoints, services, middleware, OpenAPI spec
+  8. Deliverables: API endpoints, services, middleware, OpenAPI spec
   9. STATUS heartbeat after each task
   10. `npm test` — do NOT signal COMPLETION until green
   11. Send COMPLETION with backend-specific fields

package/plugins/specweave/skills/{team-lead → team}/agents/database.md

@@ -4,7 +4,7 @@ You are the DATABASE agent for increment [INCREMENT_ID].
 
 MASTER SPEC: [MASTER_INCREMENT_PATH]/spec.md — read before planning.
 
-SKILLS: sw:architect
+REFERENCE: spec.md Approach + the increment ADRs
 
 FILE OWNERSHIP (WRITE):
   prisma/schema.prisma · prisma/migrations/** · src/db/** ·
@@ -19,7 +19,7 @@ WORKFLOW:
   4. Design schema changes
   5. Create plan.md and tasks.md
   6. Send PLAN_READY (shared protocol) — do NOT wait for approval
-  7. sw:auto: Prisma migrations, seed data, schema validation
+  7. Deliverables: Prisma migrations, seed data, schema validation
   8. STATUS heartbeat after each task
   9. `npm test` — do NOT signal COMPLETION until green
   10. Send CONTRACT_READY once schema.prisma stabilizes (Schema path, Tables,

package/plugins/specweave/skills/{team-lead → team}/agents/frontend.md

@@ -5,7 +5,7 @@ You are the FRONTEND agent for increment [INCREMENT_ID].
 MASTER SPEC: [MASTER_INCREMENT_PATH]/spec.md — read before planning. Work MUST
 satisfy ACs relevant to your domain.
 
-SKILLS: sw:architect · sw:service-connect
+REFERENCE: spec.md Approach + the increment ADRs
 
 FILE OWNERSHIP (WRITE):
   src/components/** · src/pages/** · src/hooks/** · src/styles/** ·
@@ -26,7 +26,7 @@ WORKFLOW:
   5. Wait for Phase 1 contracts: src/types/, openapi.yaml
   6. Create plan.md and tasks.md
   7. Send PLAN_READY (shared protocol) — do NOT wait for approval
-  8. sw:auto
+  8. Deliverables
   9. STATUS heartbeat after each task
   10. `npm test` — do NOT signal COMPLETION until green
   11. Send COMPLETION with frontend-specific fields

package/plugins/specweave/skills/{team-lead → team}/agents/pm.md

@@ -11,8 +11,9 @@ MISSION:
   boundaries. You own the WHAT — defining what the feature does and how success is
   measured. You work in parallel with the Architect agent who owns the HOW.
 
-SKILLS TO INVOKE:
-  Skill({ skill: "sw:pm" })
+PROCEDURE:
+  Follow sw:increment (Problem / Scope / numbered ACs / Approach). Do not invent
+  a different spec shape.
 
 FILE OWNERSHIP (WRITE access):
   [MASTER_INCREMENT_PATH]/spec.md

package/plugins/specweave/skills/{team-lead → team}/agents/security.md

@@ -4,7 +4,7 @@ You are the SECURITY agent for increment [INCREMENT_ID].
 
 MASTER SPEC: [MASTER_INCREMENT_PATH]/spec.md — hardening MUST address relevant ACs.
 
-SKILLS: sw:security
+REFERENCE: spec.md Approach + the increment ADRs
 
 FILE OWNERSHIP (WRITE):
   src/auth/** · src/middleware/auth* · src/middleware/security* ·
@@ -20,7 +20,7 @@ WORKFLOW:
   4. Audit code from other agents for security issues
   5. Create plan.md and tasks.md
   6. Send PLAN_READY (shared protocol) — do NOT wait for approval
-  7. sw:auto: auth/authz middleware, input validation, sanitization, OWASP hardening
+  7. Deliverables: auth/authz middleware, input validation, sanitization, OWASP hardening
   8. STATUS heartbeat after each task
   9. `npm test` + `npm audit` + dependency check
   10. Do NOT signal COMPLETION until green

package/plugins/specweave/skills/{team-lead → team}/agents/testing.md

@@ -5,9 +5,9 @@ You are the TESTING agent for increment [INCREMENT_ID].
 MASTER SPEC: [MASTER_INCREMENT_PATH]/spec.md — tests MUST cover ALL ACs.
 
 SKILLS:
-  sw:e2e --generate [INCREMENT_ID]   (generate E2E from ACs)
-  sw:e2e --run [INCREMENT_ID]        (run E2E + produce e2e-report.json)
-  sw:e2e --a11y [INCREMENT_ID]       (E2E + accessibility audit)
+  npx playwright test            (run the suite named in testing.commands)
+  specweave verify [INCREMENT_ID]    (runs testing.commands, writes reports/verify.json)
+  (optional) install skills-optional/e2e for AC-traced Playwright generation
 
 FILE OWNERSHIP (WRITE):
   tests/** · __tests__/** · src/**/*.test.ts · src/**/*.test.tsx ·
@@ -23,7 +23,7 @@ WORKFLOW:
   4. Wait for other agents to produce initial code
   5. Create plan.md and tasks.md
   6. Send PLAN_READY (shared protocol) — do NOT wait for approval
-  7. sw:auto: unit for services/components, integration for APIs, E2E for journeys
+  7. Deliverables: unit for services/components, integration for APIs, E2E for journeys
   8. STATUS heartbeat after each task
   9. `npm test && npx playwright test`
   10. Do NOT signal COMPLETION until green — fix and repeat if failures

package/src/templates/.gitattributes.template

@@ -33,3 +33,6 @@
 *.zip binary
 *.tar.gz binary
 *.tgz binary
+
+# Append-only task ledger: keep every line from both sides on a merge
+**/ledger.jsonl merge=union

package/src/templates/.gitignore.template

@@ -1,17 +1,43 @@
+# NOTE: gitignore has no inline comments — a "#" after a pattern is part of the
+# pattern. Keep every comment on its own line.
+
 # SpecWeave
+# Runtime state / logs / backups / jobs are machine-local and regenerated
 .specweave/cache/
-.specweave/increments/*/logs/       # Gitignored, but structure preserved
+.specweave/state/
+.specweave/logs/
+.specweave/backups/
+.specweave/jobs/
+# Increment logs and test results (folder structure is preserved)
+.specweave/increments/*/logs/
 .specweave/increments/*/test-results/
-.specweave/docs-site-internal/      # Generated Docusaurus site for internal docs
-.claude-plugin/                     # Plugin marketplace (framework files)
-plugins/                            # Plugin implementations (framework files)
+# Binary evidence and agent worktrees (never committed)
+.specweave/increments/**/reports/artifacts/
+.claude/worktrees/
+# Generated Docusaurus site for internal docs
+.specweave/docs-site-internal/
+# Framework files (plugin marketplace + plugin implementations)
+.claude-plugin/
+plugins/
+# Work handoff (secret-scrubbed, never auto-committed)
+.handoff/
+
+# Binary evidence in reports/ (videos, screenshots, app bundles)
+**/reports/*.mp4
+**/reports/*.png
+**/reports/*.jpg
+**/reports/*.aab
+**/reports/*.ipa
+**/reports/*.dSYM/
 
 # Dependencies (framework-agnostic)
-node_modules/          # JavaScript/TypeScript
+# JavaScript/TypeScript
+node_modules/
 .pnpm-store/
 .yarn/
 .npm/
-__pycache__/           # Python
+# Python
+__pycache__/
 *.pyc
 *.pyo
 *.pyd
@@ -19,22 +45,29 @@ __pycache__/           # Python
 venv/
 env/
 ENV/
-target/                # Rust
+# Rust
+target/
 Cargo.lock
-vendor/                # Go
+# Go
+vendor/
 go.sum
 
 # Build outputs (framework-agnostic)
-.next/                 # NextJS
-dist/                  # Generic
-build/                 # Generic
-out/                   # Generic
-.output/               # Nuxt
-*.egg-info/            # Python
-__pypackages__/        # Python
-*.class                # Java
-*.jar                  # Java
-bin/                   # Go, Java
+# Next.js / Nuxt
+.next/
+.output/
+# Generic
+dist/
+build/
+out/
+# Python
+*.egg-info/
+__pypackages__/
+# Java
+*.class
+*.jar
+# Go, Java
+bin/
 
 # Environment
 .env
@@ -48,17 +81,20 @@ bin/                   # Go, Java
 *.sqlite3
 *.db-shm
 *.db-wal
-prisma/migrations/*/migration.sql   # Prisma (TypeScript)
-*/migrations/__pycache__/           # Django (Python)
+# Prisma (TypeScript)
+prisma/migrations/*/migration.sql
+# Django (Python)
+*/migrations/__pycache__/
 
 # Testing (framework-agnostic)
-coverage/              # Generic
-.nyc_output/           # JavaScript
-.coverage              # Python
-htmlcov/               # Python
-*.cover                # Python
-.pytest_cache/         # Python
-test-results/          # Playwright
+coverage/
+.nyc_output/
+.coverage
+htmlcov/
+*.cover
+.pytest_cache/
+# Playwright
+test-results/
 
 # IDEs
 .vscode/