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

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