Initialize beads issue tracking and update git policy

- Initialize beads (.beads/ directory)
- Add Claude Code hooks for SessionStart/PreCompact
- Update CLAUDE.md to clarify all build artifacts are committed
- Update .gitignore to allow node_modules and dist

.beads/.gitignore

@@ -0,0 +1,29 @@
+# SQLite databases
+*.db
+*.db?*
+*.db-journal
+*.db-wal
+*.db-shm
+
+# Daemon runtime files
+daemon.lock
+daemon.log
+daemon.pid
+bd.sock
+
+# Legacy database files
+db.sqlite
+bd.db
+
+# Merge artifacts (temporary files from 3-way merge)
+beads.base.jsonl
+beads.base.meta.json
+beads.left.jsonl
+beads.left.meta.json
+beads.right.jsonl
+beads.right.meta.json
+
+# Keep JSONL exports and config (source of truth for git)
+!issues.jsonl
+!metadata.json
+!config.json

.beads/README.md

@@ -0,0 +1,81 @@
+# Beads - AI-Native Issue Tracking
+
+Welcome to Beads! This repository uses **Beads** for issue tracking - a modern, AI-native tool designed to live directly in your codebase alongside your code.
+
+## What is Beads?
+
+Beads is issue tracking that lives in your repo, making it perfect for AI coding agents and developers who want their issues close to their code. No web UI required - everything works through the CLI and integrates seamlessly with git.
+
+**Learn more:** [github.com/steveyegge/beads](https://github.com/steveyegge/beads)
+
+## Quick Start
+
+### Essential Commands
+
+```bash
+# Create new issues
+bd create "Add user authentication"
+
+# View all issues
+bd list
+
+# View issue details
+bd show <issue-id>
+
+# Update issue status
+bd update <issue-id> --status in-progress
+bd update <issue-id> --status done
+
+# Sync with git remote
+bd sync
+```
+
+### Working with Issues
+
+Issues in Beads are:
+- **Git-native**: Stored in `.beads/issues.jsonl` and synced like code
+- **AI-friendly**: CLI-first design works perfectly with AI coding agents
+- **Branch-aware**: Issues can follow your branch workflow
+- **Always in sync**: Auto-syncs with your commits
+
+## Why Beads?
+
+✨ **AI-Native Design**
+- Built specifically for AI-assisted development workflows
+- CLI-first interface works seamlessly with AI coding agents
+- No context switching to web UIs
+
+🚀 **Developer Focused**
+- Issues live in your repo, right next to your code
+- Works offline, syncs when you push
+- Fast, lightweight, and stays out of your way
+
+🔧 **Git Integration**
+- Automatic sync with git commits
+- Branch-aware issue tracking
+- Intelligent JSONL merge resolution
+
+## Get Started with Beads
+
+Try Beads in your own projects:
+
+```bash
+# Install Beads
+curl -sSL https://raw.githubusercontent.com/steveyegge/beads/main/scripts/install.sh | bash
+
+# Initialize in your repo
+bd init
+
+# Create your first issue
+bd create "Try out Beads"
+```
+
+## Learn More
+
+- **Documentation**: [github.com/steveyegge/beads/docs](https://github.com/steveyegge/beads/tree/main/docs)
+- **Quick Start Guide**: Run `bd quickstart`
+- **Examples**: [github.com/steveyegge/beads/examples](https://github.com/steveyegge/beads/tree/main/examples)
+
+---
+
+*Beads: Issue tracking that moves at the speed of thought* ⚡

.beads/config.yaml

@@ -0,0 +1,56 @@
+# Beads Configuration File
+# This file configures default behavior for all bd commands in this repository
+# All settings can also be set via environment variables (BD_* prefix)
+# or overridden with command-line flags
+
+# Issue prefix for this repository (used by bd init)
+# If not set, bd init will auto-detect from directory name
+# Example: issue-prefix: "myproject" creates issues like "myproject-1", "myproject-2", etc.
+# issue-prefix: ""
+
+# Use no-db mode: load from JSONL, no SQLite, write back after each command
+# When true, bd will use .beads/issues.jsonl as the source of truth
+# instead of SQLite database
+# no-db: false
+
+# Disable daemon for RPC communication (forces direct database access)
+# no-daemon: false
+
+# Disable auto-flush of database to JSONL after mutations
+# no-auto-flush: false
+
+# Disable auto-import from JSONL when it's newer than database
+# no-auto-import: false
+
+# Enable JSON output by default
+# json: false
+
+# Default actor for audit trails (overridden by BD_ACTOR or --actor)
+# actor: ""
+
+# Path to database (overridden by BEADS_DB or --db)
+# db: ""
+
+# Auto-start daemon if not running (can also use BEADS_AUTO_START_DAEMON)
+# auto-start-daemon: true
+
+# Debounce interval for auto-flush (can also use BEADS_FLUSH_DEBOUNCE)
+# flush-debounce: "5s"
+
+# Multi-repo configuration (experimental - bd-307)
+# Allows hydrating from multiple repositories and routing writes to the correct JSONL
+# repos:
+#   primary: "."  # Primary repo (where this database lives)
+#   additional:   # Additional repos to hydrate from (read-only)
+#     - ~/beads-planning  # Personal planning repo
+#     - ~/work-planning   # Work planning repo
+
+# Integration settings (access with 'bd config get/set')
+# These are stored in the database, not in this file:
+# - jira.url
+# - jira.project
+# - linear.url
+# - linear.api-key
+# - github.org
+# - github.repo
+# - sync.branch - Git branch for beads commits (use BEADS_SYNC_BRANCH env var or bd config set)

.beads/metadata.json

@@ -0,0 +1,4 @@
+{
+  "database": "beads.db",
+  "jsonl_export": "issues.jsonl"
+}

.claude/settings.local.json

@@ -0,0 +1,54 @@
+{
+  "hooks": {
+    "PreCompact": [
+      {
+        "hooks": [
+          {
+            "command": "bd prime",
+            "type": "command"
+          }
+        ],
+        "matcher": ""
+      }
+    ],
+    "SessionStart": [
+      {
+        "hooks": [
+          {
+            "command": "bd prime",
+            "type": "command"
+          }
+        ],
+        "matcher": ""
+      }
+    ]
+  },
+  "permissions": {
+    "allow": [
+      "Bash(npx playwright install:*)",
+      "Bash(curl:*)",
+      "Bash(mkdir:*)",
+      "Bash(git init:*)",
+      "Bash(apt-get install:*)",
+      "Bash(git config:*)",
+      "Bash(git add:*)",
+      "Bash(git commit:*)",
+      "Bash(mysqldump:*)",
+      "Bash(php -l:*)",
+      "Bash(wp --allow-root theme:*)",
+      "Bash(npm install:*)",
+      "Bash(npm run build:*)",
+      "Bash(/var/www/html/dev_commit.sh:*)",
+      "Bash(wp --allow-root rewrite:*)",
+      "Bash(wp --allow-root post-type:*)",
+      "Bash(wp --allow-root term create:*)",
+      "Bash(wp:*)",
+      "Bash(bd --help:*)",
+      "Bash(bd init:*)",
+      "Bash(bd doctor:*)",
+      "Bash(bd setup:*)"
+    ],
+    "ask": [],
+    "deny": []
+  }
+}

.gitignore

@@ -1,7 +1,7 @@
-# Dependencies
-node_modules/
+# Dependencies - COMMITTED for snapshot purposes
+# node_modules/
 
-# Build outputs (keep dist/ for deployment)
+# Build outputs - COMMITTED for snapshot purposes
 # dist/
 
 # Environment

CLAUDE.md

@@ -1,4 +1,44 @@
-# HomeProz WordPress Website Development
+
+## TOOLING: BEADS (Issue Tracking)
+
+Git-backed issue tracker for AI agents. Use `bd` for task management, NOT markdown TODOs or TodoWrite.
+
+**Git policy**: `.beads/` directory IS committed. `issues.jsonl` is the source of truth (db rebuilds from it). Issue state travels with code.
+
+**Hooks installed**: SessionStart and PreCompact hooks auto-run `bd prime` to inject workflow context.
+
+### Essential Commands
+
+| Command | Purpose |
+|---------|---------|
+| `bd ready` | Show unblocked issues ready to work |
+| `bd create "title"` | Create new issue |
+| `bd show <id>` | View issue details |
+| `bd update <id> --status in_progress` | Claim/start work |
+| `bd close <id>` | Complete issue |
+| `bd sync` | Sync with git remote |
+| `bd list --status open` | List open issues |
+| `bd dep add <id> <blocks-id>` | Add dependency |
+
+### Workflow
+
+1. `bd ready`  ^f^r find available work
+2. `bd update <id> --status in_progress`  ^f^r claim it
+3. Work on the issue
+4. Discover new work?  ^f^r `bd create "title" --deps discovered-from:<parent-id>`
+5. `bd close <id>`  ^f^r mark complete
+6. `bd sync`  ^f^r push changes
+
+### Issue Types & Priorities
+
+**Types**: `bug`, `feature`, `task`, `epic`, `chore`
+**Priorities**: `0` (critical)  ^f^r `4` (backlog), default `2`
+
+**End of session**: Create issues for discovered work, `bd sync`, verify clean git state.
+
+
+
+# PROJECT: HomeProz WordPress Website Development
 
 ## Project Overview
 
@@ -108,13 +148,14 @@ Contract documents in parent directory:
 ### Version Control
 
 1. **Git is for SNAPSHOTS** - not optimized for public/collaboration
-2. After every development phase:
+2. **Commit everything** - build artifacts (`dist/`, `node_modules/`), database dumps, and all generated files are committed. No `.gitignore` exclusions for build output.
+3. After every development phase:
    ```bash
    mysqldump -u [user] -p [database] > db-snapshot-phase-X.sql
    git add -A
    git commit -m "Phase X: [description]"
    ```
-3. Database dumps committed alongside code
+4. Database dumps committed alongside code
 
 ### Decision Making