Copier update: Task runner (v0.0.156 -> v0.1.5)

Pull in the latest base template changes:
- Task runner shim (Taskfile.yaml + .config/taskfiles/) with copier-update,
  copier-update-from-ref and prune-copier-rejects tasks, mirrored into template/
- Rename .claude/settings/permissions/write.jsonc to edit.jsonc
- Dependency and GitHub Action version bumps in extensions/context.py, with
  pyproject.toml and uv.lock regenerated to match
- CI workflow-summary gate now iterates the needs context via jq rather than
  listing each job by hand

Conflicts resolved:
- extensions/context.py: re-add pyright_version, which failed to re-apply after
  the surrounding version pins moved upstream. template/pyproject.toml.jinja
  consumes it, so without it the generated pyproject renders an empty specifier.
- template/.github/workflows/ci.yaml.jinja: drop the local per-job
  success_pattern checks, now covered by the upstream jq loop over needs.
- template/README.md.jinja: the update overwrote the jinja template with the
  base template's literal README. Restored and hand-merged the two real upstream
  changes (Task paragraph, task copier-update).

Also mark template/scripts/delete_false_positive_rej.py executable. The new
prune-copier-rejects task invokes it as ./scripts/..., so generated repos would
have failed with exit 127.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

Author: ejfine

.claude/.beads/config.yaml

@@ -26,11 +26,6 @@
 # Default actor for audit trails (overridden by BD_ACTOR or --actor)
 # actor: ""
 
-# Export events (audit trail) to .beads/events.jsonl on each flush/sync
-# When enabled, new events are appended incrementally using a high-water mark.
-# Use 'bd export --events' to trigger manually regardless of this setting.
-# events-export: false
-
 # Multi-repo configuration (experimental - bd-307)
 # Allows hydrating from multiple repositories and routing writes to the correct JSONL
 # repos:

.claude/commands/add-command.md

@@ -11,7 +11,7 @@ argument-hint: <command-name> <description>
 - Write natural, descriptive code without meta-commentary about the development process
 - The code should speak for itself - TDD is the process, not the product
 
-Beads is available for task tracking. Use `mcp__beads__*` tools to manage issues (the user interacts via `bd` commands).
+Beads is available for task tracking. Use `bd` CLI commands to manage issues.
 
 ## Plan File Restriction
 

.claude/commands/commit.md

@@ -11,7 +11,7 @@ argument-hint: [optional-commit-description]
 - Write natural, descriptive code without meta-commentary about the development process
 - The code should speak for itself - TDD is the process, not the product
 
-Beads is available for task tracking. Use `mcp__beads__*` tools to manage issues (the user interacts via `bd` commands).
+Beads is available for task tracking. Use `bd` CLI commands to manage issues.
 
 ## Plan File Restriction
 

.claude/commands/create-adr.md

@@ -17,7 +17,7 @@ Create a new ADR to document an architectural decision. ADRs capture the "why" b
 - Write natural, descriptive code without meta-commentary about the development process
 - The code should speak for itself - TDD is the process, not the product
 
-Beads is available for task tracking. Use `mcp__beads__*` tools to manage issues (the user interacts via `bd` commands).
+Beads is available for task tracking. Use `bd` CLI commands to manage issues.
 
 ## Plan File Restriction
 

.claude/commands/create-issues.md

@@ -15,7 +15,7 @@ Create structured implementation plan that bridges product thinking (PRD) with t
 - Write natural, descriptive code without meta-commentary about the development process
 - The code should speak for itself - TDD is the process, not the product
 
-Beads is available for task tracking. Use `mcp__beads__*` tools to manage issues (the user interacts via `bd` commands).
+Beads is available for task tracking. Use `bd` CLI commands to manage issues.
 
 ## Plan File Restriction
 
@@ -113,7 +113,7 @@ For each task, create a bd issue with:
 
 ```bash
 bd create "Task title" \
-  --type [feature|bug|task|chore] \
+  --type [feature|bug|task|epic|chore|decision] \
   --priority [1-3] \
   --description "Context and what needs to be built" \
   --design "Technical approach, architecture notes" \
@@ -149,8 +149,10 @@ bd create "Task title" \
 
 **Dependencies**: Link related issues
 
+The first argument is the issue that becomes blocked; the second is the blocker it waits on.
+
 ```bash
-bd dep add ISSUE-123 ISSUE-456 --type blocks
+bd dep add <blocked-id> <blocker-id> --type blocks
 ```
 
 ### Validation
@@ -179,20 +181,20 @@ After creating issues, verify:
 
 ### Beads Integration
 
-Use Beads MCP to:
+Use the `bd` CLI to:
 
 - Track work with `bd ready` to find next task
 - Create issues with `bd create "description"`
 - Track dependencies with `bd dep add`
 
-See <https://github.com/steveyegge/beads> for more information.
+See <https://github.com/gastownhall/beads> for more information.
 
 ## Integration with Other Commands
 
 - **Before /create-issues**: Use `/spike` if you need technical exploration first
 - **After /create-issues**: Use `/red` to start TDD on first task
 - **During work**: Use `bd update` to add notes/findings back to issues
-- **When stuck**: Check `bd show ISSUE-ID` to review acceptance criteria
+- **When stuck**: Check `bd show <id>` to review acceptance criteria
 
 <!--
 ============== WARNING ==============================================================================

.claude/commands/gap.md

@@ -11,7 +11,7 @@ argument-hint: [optional additional info]
 - Write natural, descriptive code without meta-commentary about the development process
 - The code should speak for itself - TDD is the process, not the product
 
-Beads is available for task tracking. Use `mcp__beads__*` tools to manage issues (the user interacts via `bd` commands).
+Beads is available for task tracking. Use `bd` CLI commands to manage issues.
 
 ## Plan File Restriction
 

.claude/commands/green.md

@@ -19,7 +19,7 @@ GREEN PHASE! Apply the below to the user input above.
 - Write natural, descriptive code without meta-commentary about the development process
 - The code should speak for itself - TDD is the process, not the product
 
-Beads is available for task tracking. Use `mcp__beads__*` tools to manage issues (the user interacts via `bd` commands).
+Beads is available for task tracking. Use `bd` CLI commands to manage issues.
 
 ## Plan File Restriction
 

.claude/commands/issue.md

@@ -13,7 +13,7 @@ Analyze GitHub issue and create TDD implementation plan.
 - Write natural, descriptive code without meta-commentary about the development process
 - The code should speak for itself - TDD is the process, not the product
 
-Beads is available for task tracking. Use `mcp__beads__*` tools to manage issues (the user interacts via `bd` commands).
+Beads is available for task tracking. Use `bd` CLI commands to manage issues.
 
 ## Plan File Restriction
 
@@ -81,13 +81,13 @@ Understand the requirement by asking (use AskUserQuestion if needed):
 
 ### Beads Integration
 
-Use Beads MCP to:
+Use the `bd` CLI to:
 
 - Track work with `bd ready` to find next task
 - Create issues with `bd create "description"`
-- Track dependencies with `bd dep add`
+- Track dependencies with `bd dep add <blocked-id> <blocker-id>`
 
-See <https://github.com/steveyegge/beads> for more information.
+See <https://github.com/gastownhall/beads> for more information.
 
 ## TDD Fundamentals
 

.claude/commands/polish.md

@@ -11,7 +11,7 @@ argument-hint: [branch, PR#, file, or area to polish]
 - Write natural, descriptive code without meta-commentary about the development process
 - The code should speak for itself - TDD is the process, not the product
 
-Beads is available for task tracking. Use `mcp__beads__*` tools to manage issues (the user interacts via `bd` commands).
+Beads is available for task tracking. Use `bd` CLI commands to manage issues.
 
 ## Plan File Restriction
 

.claude/commands/red.md

@@ -19,7 +19,7 @@ RED PHASE! Apply the below to the user input above.
 - Write natural, descriptive code without meta-commentary about the development process
 - The code should speak for itself - TDD is the process, not the product
 
-Beads is available for task tracking. Use `mcp__beads__*` tools to manage issues (the user interacts via `bd` commands).
+Beads is available for task tracking. Use `bd` CLI commands to manage issues.
 
 ## Plan File Restriction