opencodekit 0.16.4 → 0.16.6

package/dist/template/.opencode/skill/beads/references/BOUNDARIES.md

@@ -1,4 +1,4 @@
-# Boundaries: When to Use bd\_\* vs TodoWrite
+# Boundaries: When to Use br vs TodoWrite
 
 Decision criteria for choosing between beads tools and TodoWrite.
 
@@ -6,12 +6,12 @@ Decision criteria for choosing between beads tools and TodoWrite.
 
 **"Could I resume this work after 2 weeks away?"**
 
-- If beads would help you resume → **use bd\_\***
+- If beads would help you resume → **use br**
 - If markdown skim would suffice → **TodoWrite is fine**
 
 ## Decision Matrix
 
-### Use bd\_\* for:
+### Use br for:
 
 **Multi-Session Work**
 
@@ -78,7 +78,7 @@ Decision criteria for choosing between beads tools and TodoWrite.
 
 ## Detailed Comparison
 
-| Aspect           | bd\_\*                            | TodoWrite              |
+| Aspect           | br CLI                            | TodoWrite              |
 | ---------------- | --------------------------------- | ---------------------- |
 | **Persistence**  | Git-backed, survives compaction   | Session-only           |
 | **Dependencies** | Graph-based, auto ready detection | Manual                 |
@@ -89,10 +89,10 @@ Decision criteria for choosing between beads tools and TodoWrite.
 
 ## Integration Patterns
 
-### Pattern 1: bd\_\* as Strategic, TodoWrite as Tactical
+### Pattern 1: br as Strategic, TodoWrite as Tactical
 
 ```
-bd task: "Implement user authentication" (epic)
+br task: "Implement user authentication" (epic)
   ├─ Child: "Create login endpoint"
   ├─ Child: "Add JWT validation"  ← Currently working
   └─ Child: "Implement logout"
@@ -108,16 +108,17 @@ TodoWrite (for JWT validation):
 
 ```
 Session start:
-- bd_claim() gets "Add JWT validation"
+- br ready gets "Add JWT validation"
+- br update <id> --status in_progress
 - Extract acceptance criteria into TodoWrite
 - Work through TodoWrite items
-- Update bd notes as you learn
-- bd_done() when TodoWrite complete
+- Update br notes as you learn
+- br close <id> when TodoWrite complete
 ```
 
 ### Pattern 3: Transition Mid-Session
 
-**From TodoWrite to bd\_\*:**
+**From TodoWrite to br:**
 
 Trigger signals:
 
@@ -129,11 +130,11 @@ Trigger signals:
 **How to transition:**
 
 ```
-1. bd_add() with current TodoWrite content
+1. br create with current TodoWrite content
 2. Note: "Discovered multi-session work"
 3. Add dependencies as discovered
 4. Keep TodoWrite for current session
-5. Update bd notes before session ends
+5. Update br notes before session ends
 ```
 
 ## Common Mistakes
@@ -147,9 +148,9 @@ Trigger signals:
 - Lose design decisions
 - Duplicate work
 
-**Solution:** Use bd\_\* instead.
+**Solution:** Use br instead.
 
-### Mistake 2: bd\_\* for Simple Linear Tasks
+### Mistake 2: br for Simple Linear Tasks
 
 **What happens:**
 
@@ -168,9 +169,9 @@ Trigger signals:
 - Keep using TodoWrite despite poor fit
 - Lose context when session ends
 
-**Solution:** Transition to bd\_\* when complexity appears.
+**Solution:** Transition to br when complexity appears.
 
-### Mistake 4: Creating Too Many bd Issues
+### Mistake 4: Creating Too Many br Issues
 
 **What happens:**
 
@@ -178,7 +179,7 @@ Trigger signals:
 - Database cluttered
 - Hard to find meaningful work
 
-**Solution:** Use 2-week test. Would bd help after 2 weeks? If no, skip.
+**Solution:** Use 2-week test. Would br help after 2 weeks? If no, skip.
 
 ## The Transition Point
 
@@ -191,28 +192,28 @@ Trigger signals:
 - "User might not continue today"
 - "Found three related issues"
 
-When you notice these: Create bd issue, preserve context.
+When you notice these: Create br issue, preserve context.
 
 ## Summary Heuristics
 
 **Time horizon:**
 
 - Same session → TodoWrite
-- Multiple sessions → bd\_\*
+- Multiple sessions → br
 
 **Dependency structure:**
 
 - Linear steps → TodoWrite
-- Blockers/prerequisites → bd\_\*
+- Blockers/prerequisites → br
 
 **Scope clarity:**
 
 - Well-defined → TodoWrite
-- Exploratory → bd\_\*
+- Exploratory → br
 
 **Multi-agent:**
 
 - Single agent → Either
-- Multiple agents → bd\_\*
+- Multiple agents → br
 
 **When in doubt:** Use the 2-week test.

package/dist/template/.opencode/skill/beads/references/DEPENDENCIES.md

@@ -4,15 +4,13 @@ Beads supports task dependencies for ordering work.
 
 ## Overview
 
-Dependencies affect what work is "ready" - tasks with unmet dependencies won't appear in `bd_claim()` results.
+Dependencies affect what work is "ready" - tasks with unmet dependencies won't appear in `br ready` results.
 
 ## Creating Dependencies
 
-```typescript
-bd_add({
-  title: "Implement API endpoint",
-  deps: ["task:setup-db"], // depends on setup-db task
-});
+```bash
+br create --title "Implement API endpoint" --blocked-by setup-db
+# This task depends on setup-db completing first
 ```
 
 ## Dependency Patterns
@@ -23,7 +21,7 @@ bd_add({
 setup-db → implement-api → add-tests → deploy
 ```
 
-Each task depends on the previous. `bd_claim()` shows only the current step.
+Each task depends on the previous. `br ready` shows only the current step.
 
 ### Parallel Then Merge
 
@@ -47,19 +45,15 @@ One foundational task blocks multiple features.
 
 ## Epic with Children
 
-```typescript
-// Create epic
-bd_add({ title: "OAuth Integration", type: "epic" });
-// Returns: { id: "oauth-abc" }
-
-// Create children with parent
-bd_add({ title: "Setup credentials", parent: "oauth-abc" });
-bd_add({
-  title: "Implement flow",
-  parent: "oauth-abc",
-  deps: ["task:credentials"],
-});
-bd_add({ title: "Add UI", parent: "oauth-abc", deps: ["task:flow"] });
+```bash
+# Create epic
+br create --title "OAuth Integration" --type epic --priority 1
+# Returns: oauth-abc
+
+# Create children with parent
+br create --title "Setup credentials" --parent oauth-abc
+br create --title "Implement flow" --parent oauth-abc --blocked-by credentials
+br create --title "Add UI" --parent oauth-abc --blocked-by flow
 ```
 
 ## Automatic Unblocking
@@ -67,9 +61,9 @@ bd_add({ title: "Add UI", parent: "oauth-abc", deps: ["task:flow"] });
 When you close a task that's blocking others:
 
 ```
-1. bd_done({ id: "setup-db" })
+1. br close setup-db --reason "Schema created"
 2. Beads automatically updates: implement-api is now ready
-3. bd_claim() returns implement-api
+3. br ready returns implement-api
 4. No manual unblocking needed
 ```
 
@@ -91,8 +85,8 @@ docs depends on feature  // "prefer to update docs after"
 
 **Wrong:**
 
-```
-bd_add({ title: "API", deps: ["task:tests"] })  // API depends on tests?
+```bash
+br create --title "API" --blocked-by tests  # API depends on tests?
 ```
 
 **Problem:** Usually tests depend on API, not the other way.
@@ -121,10 +115,10 @@ bd_add({ title: "API", deps: ["task:tests"] })  // API depends on tests?
 
 ## Viewing Dependencies
 
-```typescript
-bd_show({ id: "task-abc" });
-// Shows what blocks this task and what this task blocks
+```bash
+br show <id>
+# Shows what blocks this task and what this task blocks
 
-bd_blocked();
-// Shows all blocked tasks across project
+br list --status open
+# Shows all open tasks, check dependencies in details
 ```

package/dist/template/.opencode/skill/beads/references/RESUMABILITY.md

@@ -52,28 +52,26 @@ DESIRED OUTPUT:
 Actual structure, not just "return markdown"
 ```
 
-```
+````
 
 ## Example: Before vs After
 
 ### Not Resumable
 
 ```
-
 Title: Add dynamic capabilities
 Notes: Working on it. Made some progress.
-
-```
+````
 
 **Problem:** Future agent doesn't know:
+
 - Which API endpoints to call
 - What responses look like
 - What format to return
 
 ### Resumable
 
-```
-
+````
 Title: Add dynamic capabilities resources
 
 Notes:
@@ -82,12 +80,11 @@ IN PROGRESS: Formatting response as markdown.
 NEXT: Add caching for API responses.
 
 WORKING CODE:
-
 ```python
 service = build('drive', 'v3', credentials=creds)
 about = service.about().get(fields='importFormats').execute()
 # Returns dict with 49 entries
-```
+````
 
 DESIRED OUTPUT:
 

package/dist/template/.opencode/skill/beads/references/WORKFLOWS.md

@@ -2,17 +2,19 @@
 
 Detailed step-by-step workflows for common beads usage patterns.
 
+**Note:** `br` (beads_rust) is non-invasive and never executes git commands. After `br sync --flush-only`, you must manually run `git add .beads/ && git commit`.
+
 ## Session Start Workflow
 
 **Every session when beads is available:**
 
 ```
 Session Start:
-- [ ] bd_init({ team: "project", role: "fe" })
-- [ ] bd_claim() to get ready work
-- [ ] If none ready, bd_ls({ status: "open" })
-- [ ] bd_show({ id }) for full context
-- [ ] bd_reserve({ paths }) before editing
+- [ ] br ready to find unblocked work
+- [ ] br update <id> --status in_progress to claim
+- [ ] If none ready, br list --status open
+- [ ] br show <id> for full context
+- [ ] Begin work
 ```
 
 ## Compaction Survival
@@ -23,8 +25,8 @@ Session Start:
 
 ```
 After Compaction:
-- [ ] bd_ls({ status: "in_progress" }) to see active work
-- [ ] bd_show({ id }) for each in_progress task
+- [ ] br list --status in_progress to see active work
+- [ ] br show <id> for each in_progress task
 - [ ] Read notes: COMPLETED, IN PROGRESS, BLOCKERS, KEY DECISIONS
 - [ ] Reconstruct TodoWrite from notes if needed
 ```
@@ -54,7 +56,7 @@ Working on auth. Made some progress.
 Discovery:
 - [ ] Notice bug, improvement, or follow-up
 - [ ] Assess: blocker or deferrable?
-- [ ] bd_add({ title, desc, pri })
+- [ ] br create --title "..." --type bug --priority 1
 - [ ] If blocker: pause and switch
 - [ ] If deferrable: continue current work
 ```
@@ -86,15 +88,15 @@ A **Ready Front** is the set of tasks with all dependencies satisfied.
 
 **Example: OAuth Integration**
 
-```typescript
-// Create epic
-bd_add({ title: "OAuth integration", type: "epic" });
+```bash
+# Create epic
+br create --title "OAuth integration" --type epic --priority 1
 
-// Walk backward: What does OAuth need?
-bd_add({ title: "Login/logout endpoints", parent: "oauth-abc" });
-bd_add({ title: "Token storage and refresh", parent: "oauth-abc" });
-bd_add({ title: "Authorization code flow", parent: "oauth-abc" });
-bd_add({ title: "OAuth client credentials", parent: "oauth-abc" }); // foundation
+# Walk backward: What does OAuth need?
+br create --title "Login/logout endpoints" --parent oauth-abc
+br create --title "Token storage and refresh" --parent oauth-abc
+br create --title "Authorization code flow" --parent oauth-abc
+br create --title "OAuth client credentials" --parent oauth-abc  # foundation
 ```
 
 ## Side Quest Handling
@@ -102,9 +104,9 @@ bd_add({ title: "OAuth client credentials", parent: "oauth-abc" }); // foundatio
 ```
 Side Quest:
 - [ ] During main work, discover problem
-- [ ] bd_add() for side quest
+- [ ] br create for side quest
 - [ ] Assess: blocker or deferrable?
-- [ ] If blocker: bd_release(), switch to side quest
+- [ ] If blocker: switch to side quest
 - [ ] If deferrable: note it, continue main work
 ```
 
@@ -116,8 +118,10 @@ Side Quest:
 Session End:
 - [ ] Work reaching stopping point
 - [ ] Update notes with COMPLETED/IN PROGRESS/NEXT
-- [ ] bd_done() if task complete
+- [ ] br close <id> --reason "..." if task complete
 - [ ] Otherwise leave in_progress with notes
+- [ ] br sync --flush-only
+- [ ] git add .beads/ && git commit -m "session end"
 - [ ] RESTART SESSION
 ```
 
@@ -125,8 +129,8 @@ Session End:
 
 ```
 Session Start with in_progress:
-- [ ] bd_ls({ status: "in_progress" })
-- [ ] bd_show({ id }) for each
+- [ ] br list --status in_progress
+- [ ] br show <id> for each
 - [ ] Read notes field
 - [ ] Continue from notes context
 ```
@@ -137,9 +141,8 @@ Session Start with in_progress:
 
 ```
 Unblocking:
-- [ ] bd_ls({ status: "open" }) to see all tasks
-- [ ] bd_blocked() to find blocked tasks
-- [ ] Identify blocker tasks
+- [ ] br list --status open to see all tasks
+- [ ] Identify blocked tasks and their blockers
 - [ ] Work on blockers first
 - [ ] Closing blocker unblocks dependent work
 ```
@@ -150,14 +153,15 @@ Unblocking:
 
 ```
 Hybrid:
-- [ ] bd_claim() for high-level task
+- [ ] br ready to find high-level task
+- [ ] br update <id> --status in_progress
 - [ ] Create TodoWrite from acceptance criteria
 - [ ] Work through TodoWrite items
-- [ ] Update bd notes as you learn
-- [ ] When TodoWrite complete, bd_done()
+- [ ] Update br notes as you learn
+- [ ] When TodoWrite complete, br close <id>
 ```
 
-**Why hybrid**: bd provides persistent structure, TodoWrite provides visible progress.
+**Why hybrid**: br provides persistent structure, TodoWrite provides visible progress.
 
 ## Common Patterns
 
@@ -166,7 +170,7 @@ Hybrid:
 ```
 1. Create research task
 2. Update notes with findings
-3. bd_add() for discoveries
+3. br create for discoveries
 4. Close research with conclusion
 ```
 
@@ -185,7 +189,7 @@ Hybrid:
 ```
 1. Create tasks for each step
 2. Work through in dependency order
-3. bd_claim() shows next step
+3. br ready shows next step
 4. Each completion unblocks next
 ```
 
@@ -194,10 +198,9 @@ Hybrid:
 ### Starting Any Session
 
 ```
-- [ ] bd_init()
-- [ ] bd_claim() or bd_ls()
-- [ ] bd_show() for context
-- [ ] bd_reserve() files
+- [ ] br ready
+- [ ] br update <id> --status in_progress
+- [ ] br show <id> for context
 - [ ] Begin work
 ```
 
@@ -205,10 +208,9 @@ Hybrid:
 
 ```
 - [ ] Notice new work needed
-- [ ] bd_add() with clear title
-- [ ] Add context in desc
+- [ ] br create --title "..." with clear title
+- [ ] Add context in description
 - [ ] Assess blocker vs deferrable
-- [ ] Update statuses
 ```
 
 ### Completing Work
@@ -216,7 +218,9 @@ Hybrid:
 ```
 - [ ] Implementation done
 - [ ] Tests passing
-- [ ] bd_done() with summary
-- [ ] bd_claim() for next work
+- [ ] br close <id> --reason "..."
+- [ ] br sync --flush-only
+- [ ] git add .beads/ && git commit
+- [ ] br ready for next work
 - [ ] RESTART SESSION
 ```