.gitignore

# ====================================
# KATA Architecture - .gitignore
# ====================================

# Dependencies
node_modules/

# ===== Playwright Test Artifacts =====
/test-results/
/playwright-report/
/blob-report/
/playwright/.cache/
/playwright/.auth/
.playwright/user-data
.playwright/output
**/evidence/

# ===== Auth Storage (Session State) =====
/.auth/

# ===== Test Data (Downloads) =====
/tests/data/downloads/*
!/tests/data/downloads/.gitkeep

# ===== API Documentation (OpenAPI) =====
# Regenerate with: bun run api:sync
# openapi.json is intermediate (downloaded from backend)
# types.ts is committed (used in code)
/api/openapi.json
/api/.openapi-config.json

# ===== Allure Reports =====
/allure-results/
/allure-report/
/.allure/

# ===== Auto-generated AI prompts (single-use, written by bun run update) =====
/.agents/prompts/

# ===== Custom Reports =====
/reports/
*.json.bak

# `.context/reports/` is generated output, same as the PBI cache below: sprint
# trackers, adapt-framework plans, regression reports, GO/NO-GO verdicts, the
# coverage matrix, the test map. Every one is rebuilt by the command that owns
# it, so committing them only produces conflicts between sessions that ran at
# different times. Only the README, which explains the directory, is tracked.
.context/reports/*
!.context/reports/README.md

# ===== Environment =====
.env
.env.local
.env.*.local
.envrc.local
.direnv/
# Force-track .envrc (overrides global ~/.gitignore_global, which often
# blanket-ignores it). Our .envrc has no secrets — it only sources .env.
!.envrc

# ===== IDE & Editor =====
.idea/
.windsurf/
.cursor/
*.swp
*.swo
*.code-workspace
.DS_Store

# ===== OS Files =====
.DS_Store
Thumbs.db

# ===== Build Artifacts =====
dist/
build/
*.tsbuildinfo

# ===== AI CLI Tools & Configs =====
.serena
.gemini/
.claude/settings.local.json
.claude/scheduled_tasks.lock
# Git worktrees created by the agent harness (EnterWorktree) or by hand. A
# worktree under here is a separate branch's FULL checkout, never repo source:
# leaving it untracked invites `git add -A` to commit a duplicate tree, and
# `git clean -fd` to delete it and orphan the metadata in .git/worktrees/.
# Matches the .prettierignore entry that already calls it "not this tree".
.claude/worktrees/
.playwright-mcp
.backups/

# `.template/installer.lock.json` is TRACKED (small, immutable sentinel that
# marks a repo as bootstrapped from this boilerplate).
# `.template/installer.state.json` is GITIGNORED (per-dev runtime idempotency
# state written by cli/install.ts — must never enter the repo).
# `.template/claude-md.upstream.sha` is GITIGNORED (per-dev runtime marker —
# records the last upstream CLAUDE.md the updater advised about, so the merge
# nudge fires once per upstream change, not every `bun up`).
# `.template/upstream-sha/` is the same idea generalized: one marker per entry
# of PROTECTED_WATCHLIST, written by the protected-file drift hook.
.template/installer.state.json
.template/claude-md.upstream.sha
.template/upstream-sha/

# ===== MCP Configuration =====
# .mcp.json and opencode.jsonc are COMMITTED — they reference secrets via
# ${VAR} / {env:VAR} expansion. Real values live in .env (ignored above).
# Local per-developer overrides go in *.local.* files (ignored below).
.mcp.local.json
opencode.local.jsonc
dbhub.local.toml
# Installer state (cli/install.ts) — gitignored; tracks what bun run setup
# already did so re-runs are idempotent.
.template/installer.state.json

# ===== Local Useful Files =====

# AI Tool Specific (user-local settings only)
.claude/settings.local.json

# Refcheck config — local-only validation tool, not part of repo contract
.refcheckrc.toml

# Planning / audit scaffolding (working notes, plan drafts, audit
# reports, session handoffs). Kept on local disk only — never pushed.
.scratch/

# Session-management state for long workflow skills (per
# .claude/skills/agentic-qa-core/references/session-management.md).
# Contains per-skill plan.md / progress.md and archived sessions.
# Local-only — canonical artifacts are committed under .context/.
.session/

# ===== SDD / Framework Internals =====
# Auto-generated skill registry + per-session SDD artifacts. Local only.
.atl/

# Framework internals — auto-managed by tooling, never committed by hand.
# NOTE: do NOT use a broad pattern like `*_*/` here — it accidentally
# ignores any directory containing an underscore (e.g. future skills, refs,
# business data maps named with underscores). List paths explicitly.
.context/_framework/
.husky/_/

# ===== Auto-generated framework caches with timestamps =====
.context/_framework/testing-capabilities.json

# ===== PBI: Jira-backed cache (Jira is the source of truth) =====
# `.context/PBI/` mirrors Jira. `bun run context:hydrate` rebuilds it from
# scratch, so committing it only produces merge conflicts between sessions that
# re-synced at different times. Ignore the whole tree, then re-include the three
# things Jira does NOT own.
#
# Git cannot re-include a file whose parent directory is excluded, so each level
# is excluded with `/*` and the directory we want is negated before descending.
# Keep that ladder intact — collapsing it to `.context/PBI/` silently drops
# test-specs/ from version control.
.context/PBI/*
!.context/PBI/README.md
!.context/PBI/templates/
!.context/PBI/epics/
.context/PBI/epics/*
!.context/PBI/epics/*/
.context/PBI/epics/*/*
!.context/PBI/epics/*/test-specs/

# ===== Skill-creator eval workspaces (local iteration artifacts, never committed) =====
.claude/skills/*-workspace/

# ===== T3 community skills (re-fetched, never committed) =====
# These three are installed into .claude/skills/ by cli/install.ts
# (PROJECT_LEVEL_SKILLS) and re-fetched from upstream on every install.
# Committing them would turn the installer's re-fetch into merge conflicts
# against the committed copies — so they are deliberately ignored. Keep this
# list in sync with PROJECT_LEVEL_SKILLS in cli/install.ts.
.claude/skills/playwright-cli/
.claude/skills/playwright-best-practices/
.claude/skills/resend-cli/

# ===== refcheck per-dev config (local-only) =====
.refcheckrc.toml

# ===== Force-track skills lockfile =====
# skills.lock.json is generated by `bunx skills add` in scaffolded projects to
# pin the exact community-skill versions installed. It MUST be committed so
# teams reproduce the same skill set. Defensive entry — nothing above currently
# matches it, but this guards against future blanket *.lock or skills.* rules.
!skills.lock.json
!**/skills.lock.json