opencodekit 0.16.2 → 0.16.4

package/dist/template/.opencode/memory/beads-workflow.md

@@ -11,11 +11,11 @@ Based on Steve Yegge's best practices and official beads documentation.
 
 | Principle                | Why                              | How                                  |
 | ------------------------ | -------------------------------- | ------------------------------------ |
-| One task per session     | Fresh context prevents confusion | Restart after `bd close`             |
+| One task per session     | Fresh context prevents confusion | Restart after `br close`             |
 | Plan outside beads first | Better planning tools exist      | Use `/brainstorm` → `/plan` → import |
-| File lots of issues      | Track any work >2 minutes        | `bd create` liberally                |
-| "Land the plane" = PUSH  | `bd sync` means git push         | Always verify push succeeded         |
-| Keep DB small            | Performance degrades >500 issues | `bd cleanup --days 7` weekly         |
+| File lots of issues      | Track any work >2 minutes        | `br create` liberally                |
+| "Land the plane" = PUSH  | `br sync --flush-only` means git push         | Always verify push succeeded         |
+| Keep DB small            | Performance degrades >500 issues | `br cleanup --days 7` weekly         |
 
 ## Hierarchy Model: Epic → Task → Subtask
 
@@ -50,27 +50,27 @@ Epic (feature-level)
 
 ```bash
 # Create epic
-bd create "User Authentication" -t epic -p 2
+br create "User Authentication" -t epic -p 2
 # Returns: bd-epic
 
 # Create tasks with dependencies
-bd create "Setup database schema" -t task -p 2
-bd dep add bd-xxx1 bd-epic
+br create "Setup database schema" -t task -p 2
+br dep add bd-xxx1 bd-epic
 
-bd create "Implement API endpoints" -t task -p 2
-bd dep add bd-xxx2 bd-epic
-bd dep add bd-xxx2 bd-xxx1 --type blocks  # Sequential
+br create "Implement API endpoints" -t task -p 2
+br dep add bd-xxx2 bd-epic
+br dep add bd-xxx2 bd-xxx1 --type blocks  # Sequential
 
 # Create subtasks for complex tasks
-bd create "POST /api/users endpoint" -t subtask -p 2
-bd dep add bd-xxx2.1 bd-xxx2
+br create "POST /api/users endpoint" -t subtask -p 2
+br dep add bd-xxx2.1 bd-xxx2
 
-bd create "GET /api/users/:id endpoint" -t subtask -p 2
-bd dep add bd-xxx2.2 bd-xxx2
-bd dep add bd-xxx2.2 bd-xxx2.1 --type blocks  # Sequential subtasks
+br create "GET /api/users/:id endpoint" -t subtask -p 2
+br dep add bd-xxx2.2 bd-xxx2
+br dep add bd-xxx2.2 bd-xxx2.1 --type blocks  # Sequential subtasks
 
 # Verify hierarchy
-bd dep tree bd-epic
+br dep tree bd-epic
 ```
 
 ## Git Worktree Integration
@@ -122,9 +122,9 @@ main-repo/
 | Mode        | Configuration                          | Use When                 |
 | ----------- | -------------------------------------- | ------------------------ |
 | Default     | Daemon auto-disabled in worktrees      | Most cases               |
-| Sync branch | `bd config set sync-branch beads-sync` | Full daemon in worktrees |
+| Sync branch | `br config set sync-branch beads-sync` | Full daemon in worktrees |
 | External DB | `export BEADS_DIR=~/project/.beads`    | Complete separation      |
-| Sandbox     | `bd --sandbox` or `BEADS_NO_DAEMON=1`  | Claude Code, containers  |
+| Sandbox     | `br --sandbox` or `BEADS_NO_DAEMON=1`  | Claude Code, containers  |
 
 ### Worktree Cleanup
 
@@ -161,13 +161,13 @@ Subagents (read-only, stateless workers)
 
 | Agent     | Can Do                   | Cannot Do              |
 | --------- | ------------------------ | ---------------------- |
-| `build`   | All beads ops, `bd sync` | -                      |
-| `plan`    | All beads ops, `bd sync` | -                      |
-| `general` | Read, small edits        | `bd sync`, beads write |
-| `explore` | Read, grep, glob         | Edit, write, `bd sync` |
-| `scout`   | Fetch, search, Context7  | Edit, write, `bd sync` |
-| `plan`    | Read, create artifacts   | Edit files, `bd sync`  |
-| `review`  | Read, analyze, suggest   | Edit files, `bd sync`  |
+| `build`   | All beads ops, `br sync --flush-only` | -                      |
+| `plan`    | All beads ops, `br sync --flush-only` | -                      |
+| `general` | Read, small edits        | `br sync --flush-only`, beads write |
+| `explore` | Read, grep, glob         | Edit, write, `br sync --flush-only` |
+| `scout`   | Fetch, search, Context7  | Edit, write, `br sync --flush-only` |
+| `plan`    | Read, create artifacts   | Edit files, `br sync --flush-only`  |
+| `review`  | Read, analyze, suggest   | Edit files, `br sync --flush-only`  |
 | `vision`  | Analyze images, mockups  | All beads operations   |
 
 ### Parallel Research Pattern
@@ -215,10 +215,10 @@ Task({
 
 | Task         | Frequency      | Command               | Why                                    |
 | ------------ | -------------- | --------------------- | -------------------------------------- |
-| Health check | Weekly         | `bd doctor --fix`     | Repairs orphaned issues, sync problems |
-| Cleanup      | Every few days | `bd cleanup --days 7` | Keep DB under 200-500 issues           |
-| Upgrade      | Weekly         | `bd upgrade`          | Latest features and fixes              |
-| Git hooks    | Once per repo  | `bd hooks install`    | Auto-sync on commit/merge/checkout     |
+| Health check | Weekly         | `br doctor --fix`     | Repairs orphaned issues, sync problems |
+| Cleanup      | Every few days | `br cleanup --days 7` | Keep DB under 200-500 issues           |
+| Upgrade      | Weekly         | `br upgrade`          | Latest features and fixes              |
+| Git hooks    | Once per repo  | `br hooks install`    | Auto-sync on commit/merge/checkout     |
 
 ## Command Configuration Best Practices
 
@@ -297,32 +297,32 @@ model: gemini-2.5-pro # Override default model
 
 | Command                      | Agent   | Beads Operations                                       | When to Use                 |
 | ---------------------------- | ------- | ------------------------------------------------------ | --------------------------- |
-| `/triage`                    | build   | `bd doctor`, `bd list`, `bd ready`, `bd cleanup`       | Start of day, find work     |
-| `/triage --quick`            | build   | `bd ready`, `bd list --status=in_progress`             | Fast check, what's next     |
-| `/start <id>`                | build   | `bd update --status in_progress`, `bd hooks install`   | Claim a task                |
+| `/triage`                    | build   | `br doctor`, `br list`, `br ready`, `br cleanup`       | Start of day, find work     |
+| `/triage --quick`            | build   | `br ready`, `br list --status=in_progress`             | Fast check, what's next     |
+| `/start <id>`                | build   | `br update --status in_progress`, `br hooks install`   | Claim a task                |
 | `/start <id> --worktree`     | build   | + Create git worktree                                  | Isolated feature work       |
 | `/start <id> --research`     | build   | + Parallel subagent research                           | Complex task preparation    |
-| `/create`                    | build   | `bd create`, `bd sync`                                 | Create new tracked task     |
-| `/new-feature`               | plan    | `bd create` (epic + subtasks), `bd dep add`, `bd sync` | Complex feature with phases |
+| `/create`                    | build   | `br create`, `br sync --flush-only`                                 | Create new tracked task     |
+| `/new-feature`               | plan    | `br create` (epic + subtasks), `br dep add`, `br sync --flush-only` | Complex feature with phases |
 | `/new-feature --worktree`    | plan    | + Create git worktree for epic                         | Isolated feature branch     |
-| `/issue <num>`               | build   | `bd create`, `bd sync`, `gh issue comment`             | Import GitHub issue         |
-| `/plan <id>`                 | plan    | `bd create` (subtasks), `bd dep add`, `bd sync`        | Break down task             |
+| `/issue <num>`               | build   | `br create`, `br sync --flush-only`, `gh issue comment`             | Import GitHub issue         |
+| `/plan <id>`                 | plan    | `br create` (subtasks), `br dep add`, `br sync --flush-only`        | Break down task             |
 | `/plan <id> --create-beads`  | plan    | Create child beads after planning                      | Auto-hierarchy creation     |
-| `/implement <id>`            | build   | `bd update --status in_progress`, `bd sync`            | Do the work                 |
+| `/implement <id>`            | build   | `br update --status in_progress`, `br sync --flush-only`            | Do the work                 |
 | `/implement <id> --parallel` | build   | + Aggressive subagent research                         | Complex implementation      |
-| `/commit [id]`               | build   | `bd sync` (if bead-id provided)                        | Commit with traceability    |
-| `/finish <id>`               | build   | `bd close`, `bd sync`                                  | Complete task (asks first)  |
-| `/handoff <id>`              | build   | `bd sync`                                              | Pause work, save context    |
-| `/resume <id>`               | build   | `bd update --status in_progress`                       | Continue previous work      |
-| `/pr <id>`                   | build   | `bd-msg`, `bd sync`                                    | Create pull request         |
-| `/fix`                       | build   | `bd sync` (after user confirms commit)                 | Fix bugs with tracking      |
-| `/status`                    | explore | `bd status`, `bd list`, `bd-inbox`, `bd-release`       | Dashboard view              |
+| `/commit [id]`               | build   | `br sync --flush-only` (if bead-id provided)                        | Commit with traceability    |
+| `/finish <id>`               | build   | `br close`, `br sync --flush-only`                                  | Complete task (asks first)  |
+| `/handoff <id>`              | build   | `br sync --flush-only`                                              | Pause work, save context    |
+| `/resume <id>`               | build   | `br update --status in_progress`                       | Continue previous work      |
+| `/pr <id>`                   | build   | `br-msg`, `br sync --flush-only`                                    | Create pull request         |
+| `/fix`                       | build   | `br sync --flush-only` (after user confirms commit)                 | Fix bugs with tracking      |
+| `/status`                    | explore | `br status`, `br list`, `br-inbox`, `br-release`       | Dashboard view              |
 
 ### Research Commands (Read-Only Beads)
 
 | Command            | Agent   | Beads Operations      | Notes                      |
 | ------------------ | ------- | --------------------- | -------------------------- |
-| `/research <id>`   | scout   | `bd show` (read-only) | NO `bd sync` - subagent    |
+| `/research <id>`   | scout   | `br show` (read-only) | NO `br sync --flush-only` - subagent    |
 | `/brainstorm`      | plan    | None                  | Pure planning, no tracking |
 | `/analyze-project` | explore | None                  | Codebase exploration       |
 | `/summarize`       | explore | None                  | Session/code summary       |
@@ -460,7 +460,7 @@ For tasks that can run autonomously until completion. The agent loops until it o
 
 ```bash
 # Create PRD from beads
-bd list --status=open --json > PRD.json
+br list --status=open --json > PRD.json
 
 # Start Ralph loop
 /ralph-loop "Complete all open tasks" --prd PRD.json
@@ -470,7 +470,7 @@ ralph-status   # Check progress
 ralph-stop     # Stop gracefully
 
 # After completion, sync beads
-bd sync
+br sync --flush-only
 ```
 
 **Key constraints:**
@@ -486,17 +486,17 @@ bd sync
 
 | Agent   | Can Do                          | Cannot Do |
 | ------- | ------------------------------- | --------- |
-| `build` | All beads operations, `bd sync` | -         |
-| `plan`  | All beads operations, `bd sync` | -         |
+| `build` | All beads operations, `br sync --flush-only` | -         |
+| `plan`  | All beads operations, `br sync --flush-only` | -         |
 
 ### Subagents (Read-Only Beads)
 
 | Agent     | Can Do                                 | Cannot Do             |
 | --------- | -------------------------------------- | --------------------- |
-| `plan`    | `bd show`, `bd list`, create artifacts | `bd sync`, `bd close` |
-| `scout`   | `bd show` (read context)               | Any writes            |
-| `explore` | `bd show`, `bd list`                   | Any writes            |
-| `review`  | `bd show`                              | Any writes            |
+| `plan`    | `br show`, `br list`, create artifacts | `br sync --flush-only`, `br close` |
+| `scout`   | `br show` (read context)               | Any writes            |
+| `explore` | `br show`, `br list`                   | Any writes            |
+| `review`  | `br show`                              | Any writes            |
 | `vision`  | None                                   | All beads operations  |
 
 ## File Locking (Multi-Agent)
@@ -529,10 +529,10 @@ Closes: bd-a1b2c3
 ## Session End Checklist
 
 1. [ ] All work committed
-2. [ ] `bd sync` run (pushes to git)
+2. [ ] `br sync --flush-only` run (pushes to git)
 3. [ ] If incomplete: `/handoff <id>` created
 4. [ ] If complete: `/finish <id>` run
-5. [ ] No stale file locks (`bd-release({ _: true })`)
+5. [ ] No stale file locks (`br-release({ _: true })`)
 6. [ ] Worktrees cleaned up (if used)
 
 ## Troubleshooting
@@ -540,25 +540,25 @@ Closes: bd-a1b2c3
 | Problem                      | Solution                                            |
 | ---------------------------- | --------------------------------------------------- |
 | "bd command not found"       | `npm install -g beads-village`                      |
-| Orphaned issues              | `bd doctor --fix`                                   |
-| DB too large                 | `bd cleanup --days 3`                               |
-| Sync conflicts               | `bd sync --force` (careful!)                        |
+| Orphaned issues              | `br doctor --fix`                                   |
+| DB too large                 | `br cleanup --days 3`                               |
+| Sync conflicts               | `br sync --force` (careful!)                        |
 | Stale handoff                | Check if rebase needed before `/resume`             |
-| Task not in `bd ready`       | Check blockers: `bd show <id>`                      |
+| Task not in `br ready`       | Check blockers: `br show <id>`                      |
 | "Branch already checked out" | `rm -rf .git/beads-worktrees && git worktree prune` |
-| Daemon issues in worktree    | `bd config set sync-branch beads-sync`              |
-| Sandbox environment          | `bd --sandbox` or `BEADS_NO_DAEMON=1`               |
+| Daemon issues in worktree    | `br config set sync-branch beads-sync`              |
+| Sandbox environment          | `br --sandbox` or `BEADS_NO_DAEMON=1`               |
 
 ## Anti-Patterns
 
 | Don't                                  | Why                   | Do Instead                       |
 | -------------------------------------- | --------------------- | -------------------------------- |
-| Skip `bd sync` at session end          | Changes won't persist | Always sync before stopping      |
+| Skip `br sync --flush-only` at session end          | Changes won't persist | Always sync before stopping      |
 | Create beads for trivial fixes         | DB bloat              | Use `/quick-build`               |
-| Work on blocked tasks                  | Wastes time           | Use `bd ready` to find unblocked |
-| Subagents running `bd sync`            | Coordination issues   | Only leader agents sync          |
+| Work on blocked tasks                  | Wastes time           | Use `br ready` to find unblocked |
+| Subagents running `br sync --flush-only`            | Coordination issues   | Only leader agents sync          |
 | Force through complex with quick-build | Technical debt        | Proper `/create` workflow        |
-| Ignore `bd doctor` warnings            | Corruption risk       | Fix issues promptly              |
+| Ignore `br doctor` warnings            | Corruption risk       | Fix issues promptly              |
 | Skip worktree for XL features          | Merge conflicts       | Use `--worktree` flag            |
 | Implement epic directly                | Too large             | Work on subtasks instead         |
 | Wait for subagent results              | Blocks progress       | Fire parallel, continue working  |

package/dist/template/.opencode/plans/1770013678126-witty-planet.md

@@ -144,7 +144,7 @@ Implement the `/init` slash command that provides one-command project onboarding
 **Implementation Details**:
 
 1. If user says yes to beads:
-   - Run `bd init` if available
+   - Run `br init` if available
    - Or create basic structure manually:
      - `.beads/config.yaml`
      - `.beads/issues.jsonl`

package/dist/template/.opencode/plans/1770112267595-shiny-rocket.md

@@ -0,0 +1,258 @@
+# Plan: Patch-Package Style Feature for Template File Modifications
+
+## Summary
+
+Add a patch system that preserves user modifications to template files across upgrades. When users edit built-in skills, commands, agents, or tools, their changes are saved as patches and automatically reapplied after template updates.
+
+## Problem
+
+```
+User edits .opencode/skill/beads/skill.md (built-in template file)
+User runs `ock upgrade`
+→ Current behavior: Template file overwrites OR user version preserved forever (never gets template updates)
+→ User loses customizations OR misses template improvements
+```
+
+## Solution
+
+Save user modifications as unified diff patches. On upgrade:
+
+1. Apply new template files
+2. Automatically reapply user patches
+3. Handle conflicts gracefully
+
+---
+
+## File Structure
+
+```
+.opencode/
+├── patches/
+│   ├── .patches.json                 # Metadata index (hashes, versions)
+│   ├── skill-beads-skill.md.patch    # Unified diff patches
+│   ├── command-ship.md.patch
+│   └── *.patch.rej                   # Failed patches (conflicts)
+├── .version                          # Already exists
+└── ... (other template files)
+```
+
+---
+
+## New Commands
+
+### `ock patch save <file>`
+
+Save current modifications as a patch.
+
+```bash
+$ ock patch save .opencode/skill/beads/skill.md
+
+✓ Saved patch: .opencode/patches/skill-beads-skill.md.patch
+  Original: a1b2c3d4 → Current: e5f6g7h8
+```
+
+### `ock patch list`
+
+List all saved patches with status.
+
+```bash
+$ ock patch list
+
+Active Patches (3):
+  skill/beads/skill.md    ✓ Clean
+  command/ship.md         ⚠ Stale (template changed)
+  agent/build.md          ✗ Conflict
+```
+
+### `ock patch apply` (automatic during upgrade)
+
+Reapply patches after template update.
+
+### `ock patch remove <file>`
+
+Remove a saved patch.
+
+---
+
+## `.patches.json` Schema
+
+```json
+{
+  "version": "1.0.0",
+  "patches": {
+    "skill/beads/skill.md": {
+      "originalHash": "sha256:a1b2c3d4...",
+      "currentHash": "sha256:e5f6g7h8...",
+      "patchFile": "skill-beads-skill.md.patch",
+      "createdAt": "2026-02-03T10:00:00Z",
+      "templateVersion": "1.2.3"
+    }
+  }
+}
+```
+
+---
+
+## Upgrade Flow (Modified)
+
+```
+1. User runs: ock upgrade
+2. Check version (existing logic)
+3. For PRESERVE_DIRS files that exist in template:
+   - Copy template file (overwrite user's version)
+   - Check if patch exists in .patches.json
+   - If patch exists, apply it
+   - If patch fails, save conflict to .patch.rej
+4. Report: "✓ Updated X files, reapplied Y patches, Z conflicts"
+```
+
+---
+
+## Conflict Resolution
+
+| Scenario                        | Action                                    |
+| ------------------------------- | ----------------------------------------- |
+| Template unchanged              | Auto-apply patch                          |
+| Template changed, patch applies | Auto-apply with info message              |
+| Template changed, patch fails   | Save `.patch.rej`, skip file, notify user |
+
+**Conflict UI:**
+
+```
+⚠ CONFLICT: skill/beads/skill.md
+
+Template changed in v1.3.0 and your patch no longer applies.
+
+Options:
+  [1] View diff between versions
+  [2] Keep new template (discard patch)
+  [3] Keep your version (skip update)
+  [4] Manually merge (edit patch.rej)
+
+Saved: .opencode/patches/skill-beads-skill.md.patch.rej
+```
+
+---
+
+## Implementation Phases
+
+### Phase 1: Core Patch Infrastructure
+
+**Files to create:**
+
+- `src/commands/patch.ts` - Patch save/list/apply/remove commands
+- `src/utils/patch.ts` - Diff generation, hash calculation, patch application
+
+**Files to modify:**
+
+- `src/index.ts` - Register `patch` command
+
+**Key functions:**
+
+```typescript
+// src/utils/patch.ts
+export function generatePatch(templatePath: string, userPath: string): string;
+export function applyPatch(filePath: string, patchContent: string): boolean;
+export function calculateHash(content: string): string;
+export function loadPatchMetadata(opencodeDir: string): PatchMetadata;
+export function savePatchMetadata(opencodeDir: string, metadata: PatchMetadata): void;
+```
+
+### Phase 2: Upgrade Integration
+
+**Files to modify:**
+
+- `src/commands/upgrade.ts` - Integrate patch apply after template copy
+
+**Changes:**
+
+1. After `copyDirWithPreserve()`, call `applyPatches()`
+2. Modify `PRESERVE_DIRS` logic: still preserve, but ALSO check for patches
+3. Add patch status to upgrade summary
+
+### Phase 3: CLI Polish
+
+- Interactive conflict resolution
+- `--dry-run` flag for patch apply
+- Pretty diff viewer for conflicts
+
+---
+
+## Dependencies
+
+Use existing Node.js capabilities:
+
+- `crypto.createHash('sha256')` - Hash calculation
+- **diff** library (`npm:diff`) - Generate unified diffs
+- **patch-package** or custom parser - Apply patches
+
+Alternative: Shell out to `git diff` and `git apply` (simpler, but requires git).
+
+---
+
+## Critical Files
+
+| File                      | Purpose                    |
+| ------------------------- | -------------------------- |
+| `src/commands/patch.ts`   | New - Patch commands       |
+| `src/utils/patch.ts`      | New - Patch utilities      |
+| `src/commands/upgrade.ts` | Modify - Integrate patches |
+| `src/index.ts`            | Modify - Register command  |
+
+---
+
+## Verification
+
+1. **Unit tests**: `src/commands/patch.test.ts`
+   - Test patch generation from diff
+   - Test patch application
+   - Test conflict detection
+
+2. **Integration test**:
+
+   ```bash
+   # Setup
+   ock init
+   echo "# Custom section" >> .opencode/skill/beads/skill.md
+   ock patch save .opencode/skill/beads/skill.md
+
+   # Simulate upgrade
+   ock upgrade --force
+
+   # Verify
+   grep "Custom section" .opencode/skill/beads/skill.md  # Should exist
+   ```
+
+3. **Conflict test**:
+   - Modify template file in dist/template
+   - Run upgrade
+   - Verify conflict detection and `.patch.rej` creation
+
+---
+
+## Complexity Estimate
+
+| Component           | Effort | Notes                          |
+| ------------------- | ------ | ------------------------------ |
+| Hash/diff utilities | 2h     | Use `diff` library             |
+| Patch save command  | 2h     | Generate + store patch         |
+| Patch list command  | 1h     | Read metadata, show status     |
+| Patch apply logic   | 3h     | Apply patches, handle failures |
+| Upgrade integration | 2h     | Hook into existing flow        |
+| Conflict UI         | 2h     | Interactive resolution         |
+| Tests               | 2h     | Unit + integration             |
+
+**Total: ~14 hours (2 days)**
+
+---
+
+## Open Questions
+
+1. **Git dependency?** Should we require git for `git diff`/`git apply` or use pure JS?
+   - Recommendation: Pure JS (`diff` library) for portability
+
+2. **Auto-save patches?** Should we auto-detect modifications on upgrade?
+   - Recommendation: Manual `ock patch save` for now (explicit is better)
+
+3. **Nested directories?** How to handle `skill/beads/skill.md` path → filename conversion?
+   - Recommendation: Replace `/` with `-` → `skill-beads-skill.md.patch`

package/dist/template/.opencode/plans/swarm-protocol.md

@@ -15,11 +15,11 @@ Use `.beads/` as the single source of truth for task state + dependencies, while
 
 Canonical state lives in `.beads/issues.jsonl` (tasks) and `.beads/artifacts/<id>/` (task artifacts).
 
-- Create tasks: `bd create "Title" -p <1-3>`
-- See unblocked work: `bd ready`
-- Inspect context: `bd show <id>`
-- Claim work: `bd update <id> --status=in_progress`
-- Close work: `bd close <id> --reason="..."` then `bd sync`
+- Create tasks: `br create "Title" -p <1-3>`
+- See unblocked work: `br ready`
+- Inspect context: `br show <id>`
+- Claim work: `br update <id> --status=in_progress`
+- Close work: `br close <id> --reason="..."` then `br sync --flush-only`
 
 ## Task Artifact Contract
 
@@ -115,9 +115,9 @@ Immediately stop execution and return to planning if:
 
 ## Lead Checklist
 
-1. `bd ready` -> pick task -> `bd show <id>`
+1. `br ready` -> pick task -> `br show <id>`
 2. Ensure `.beads/artifacts/<id>/spec.md` has acceptance checks
-3. `bd update <id> --status=in_progress`
+3. `br update <id> --status=in_progress`
 4. Delegate with the packet format
 5. Require worker report + evidence
-6. `bd close <id> --reason="..."` + `bd sync`
+6. `br close <id> --reason="..."` + `br sync --flush-only`

package/dist/template/.opencode/plugin/README.md

@@ -85,10 +85,10 @@ Session 3: read_session("previous") → Tests (90k) → close
 **Swarm protocol guardrails (Beads-as-board)** - nudges agents to follow the Beads-first workflow.
 
 - Treats `.beads/` as the single source of truth for the swarm task board
-- If user expresses implementation intent and no task is `in_progress`, injects a nudge to use `bd ready/show/update`
+- If user expresses implementation intent and no task is `in_progress`, injects a nudge to use `br ready/show/update`
 - If there are `in_progress` tasks but `.beads/artifacts/<id>/spec.md` is missing, nudges to create it before implementation
 - On `file.edited`, warns if code is being changed without a claimed task or with missing `spec.md`
-- On `session.idle`, reminds to `bd close` + `bd sync` when work is done
+- On `session.idle`, reminds to `br close` + `br sync` when work is done
 
 ### notification.ts
 

package/dist/template/.opencode/plugin/compaction.ts

@@ -60,7 +60,7 @@ export const CompactionPlugin: Plugin = async ({ $, directory }) => {
       let beadsContext = "";
       try {
         const result =
-          await $`cd ${directory} && bd list --status in_progress --json 2>/dev/null`.quiet();
+          await $`cd ${directory} && br list --status in_progress --json 2>/dev/null`.quiet();
         if (result.stdout) {
           const inProgress = JSON.parse(result.stdout.toString());
           if (inProgress.length > 0) {

package/dist/template/.opencode/plugin/swarm-enforcer.ts

@@ -7,7 +7,7 @@
  * - Ensure `spec.md` exists for in-progress tasks
  * - Close/sync in-progress work at session end
  *
- * This plugin is intentionally non-destructive: it never runs `bd update/close/sync`.
+ * This plugin is intentionally non-destructive: it never runs `br update/close/sync`.
  */
 
 import fsPromises from "node:fs/promises";
@@ -132,9 +132,9 @@ function buildNudge(params: {
 
 Pick a task before code changes:
 
-1) \`bd ready\` → find unblocked work
-2) \`bd show <id>\` → inspect task
-3) \`bd update <id> --status=in_progress\` → claim it
+1) \`br ready\` → find unblocked work
+2) \`br show <id>\` → inspect task
+3) \`br update <id> --status in_progress\` → claim it
 
 For parallel work, use the Task tool to spawn subagents.
 ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
@@ -253,7 +253,7 @@ export const SwarmEnforcer: Plugin = async ({ client, directory }) => {
 			if (cachedInProgress.length === 0) {
 				await showToast(
 					"Beads: No task claimed",
-					"Run bd ready/show/update to claim a task before edits.",
+					"Run br ready/show/update to claim a task before edits.",
 					"warning",
 				);
 				return;
@@ -282,7 +282,7 @@ export const SwarmEnforcer: Plugin = async ({ client, directory }) => {
 				.join(", ");
 			await showToast(
 				"Beads: Work still in progress",
-				`In-progress: ${list}. Close with bd close + bd sync when done.`,
+				`In-progress: ${list}. Close with br close + br sync when done.`,
 				"info",
 			);
 		},

package/dist/template/.opencode/skill/beads/SKILL.md

@@ -553,25 +553,25 @@ beads_sync({ operation: "pull" });
 
 | Task         | Frequency      | Command               | Why                                            |
 | ------------ | -------------- | --------------------- | ---------------------------------------------- |
-| Health check | Weekly         | `bd doctor`           | Repairs database issues, detects orphaned work |
-| Cleanup      | Every few days | `bd cleanup --days 7` | Keep DB under 200-500 issues for performance   |
-| Upgrade      | Weekly         | `bd upgrade`          | Get latest features and fixes                  |
-| Git hooks    | Once per repo  | `bd hooks install`    | Auto-sync on commit/merge/checkout             |
+| Health check | Weekly         | `br doctor`           | Repairs database issues, detects orphaned work |
+| Cleanup      | Every few days | `br cleanup --days 7` | Keep DB under 200-500 issues for performance   |
+| Upgrade      | Weekly         | `br upgrade`          | Get latest features and fixes                  |
+| Git hooks    | Once per repo  | `br hooks install`    | Auto-sync on commit/merge/checkout             |
 
 ### Key Principles
 
 1. **Plan outside Beads first** - Use planning tools, then import tasks to beads
 2. **One task per session, then restart** - Fresh context prevents confusion
 3. **File lots of issues** - Any work >2 minutes should be tracked
-4. **Use short prefixes** - `bd-`, `vc-`, `wy-` etc.
-5. **"Land the plane" = PUSH** - `bd sync` means git push, not "ready when you are"
+4. **Use short prefixes** - `br-`, `vc-`, `wy-` etc.
+5. **"Land the plane" = PUSH** - `br sync --flush-only` means git push, not "ready when you are"
 6. **Include issue ID in commits** - `git commit -m "Fix bug (bd-abc)"`
 
 ### Database Health
 
 ```bash
 # Check database size
-bd list --status=all --json | wc -l
+br list --status=all --json | wc -l
 
 # Target: under 200-500 issues
 # If over, run cleanup more aggressively: