Working PR for ADR-269 Agent orchestration

_spec_AgentOrchestration.md

@@ -614,6 +614,7 @@ One-time operator configuration required before the pipeline can run. No code ch
 - [ ] `~/.dev-team` added to `permissions.additionalDirectories` in `~/.claude/settings.json` (eliminates per-write permission prompts)
 - [ ] Plugin installation confirmed current (latest changes pulled from `dev-team-agents` repo)
 - [ ] Given `GH_TOKEN` is set to Claude's PAT, when the developer agent runs `gh pr create`, then no account-picker prompt appears
+- [ ] Increment the version in `plugins/dev-team/.claude-plugin/plugin.json` by 0.0.1
 
 ---
 
@@ -627,6 +628,7 @@ Run a full implement pipeline cycle to confirm the step-machine architecture wor
 - [ ] Given a full researcher → developer → reviewer → sign-off cycle, when it completes, then the context file at `~/.dev-team/<repo-slug>/<work-item-id>.md` contains all expected sections and no `claude -p` processes are spawned
 - [ ] Given `GH_TOKEN` is set, when the developer agent creates a PR, then no account-picker prompt appears
 - [ ] Sub-agents (researcher, developer, reviewer) successfully make Jira MCP and GitHub MCP calls directly without top-level relay
+- [ ] Increment the version in `plugins/dev-team/.claude-plugin/plugin.json` by 0.0.1
 
 ---
 
@@ -645,6 +647,7 @@ Implement `agents/troubleshooter.md` with the sign-off deadlock condition as the
 - [ ] Unknown trigger fallback: returns `{"action": "needs_user_input", "reason": "Unknown trigger: <trigger>. Manual inspection required."}`
 - [ ] Writes diagnosis to `<!-- section:Troubleshooter Log -->` before returning in all cases
 - [ ] Given the pipeline has reached `signoff_cycle_count == 2` with a deadlocked thread, when the troubleshooter runs, then it asks the user how to proceed and acts on the answer without re-running the sign-off
+- [ ] Increment the version in `plugins/dev-team/.claude-plugin/plugin.json` by 0.0.1
 
 ## Related Epics
 

hooks/hooks.json

@@ -0,0 +1,8 @@
+{
+  "hooks": [
+    {
+      "event": "SessionStart",
+      "command": "python \"${CLAUDE_PLUGIN_ROOT}/scripts/dev_team_update.py\" --data-dir \"${CLAUDE_PLUGIN_DATA}\" --threshold-hours 4"
+    }
+  ]
+}

plugins/dev-team/.claude-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "dev-team",
-  "version": "1.2.0",
+  "version": "1.2.3",
   "description": "Dev-team agent pipeline: researcher, developer, reviewer, and debugger agents for implementing Jira tasks and fixing GitHub issues.",
   "commands": "./commands"
 }

plugins/dev-team/agents/developer.md

@@ -22,6 +22,11 @@ tools:
   - mcp__jira__editJiraIssue
   - mcp__jira__addCommentToJiraIssue
   - mcp__plugin_github_github__create_pull_request
+  - mcp__plugin_github_github__pull_request_read
+  - mcp__plugin_github_github__pull_request_review_write
+  - mcp__plugin_github_github__add_comment_to_pending_review
+  - mcp__plugin_github_github__add_reply_to_pull_request_comment
+  - mcp__plugin_github_github__update_pull_request
 ---
 
 You are the Developer for the AdaptiveRemote development team.

plugins/dev-team/agents/researcher.md

@@ -7,6 +7,7 @@ description: >
 model: sonnet
 tools:
   - Read
+  - Edit
   - Glob
   - Grep
   - Bash

plugins/dev-team/agents/reviewer.md

@@ -8,6 +8,7 @@ description: >
 model: sonnet
 tools:
   - Read
+  - Edit
   - Glob
   - Grep
   - Bash

plugins/dev-team/agents/script-runner.md

@@ -1,43 +1,12 @@
 ---
 name: script-runner
 description: >
-  Runs a shell command, writes full combined output to a log file, and returns a
-  single-line result indicator. Used by the dev-team orchestration loop to execute
-  validate scripts (build, test) as parallel pipeline steps.
+  Runs a Python script as a pipeline step, captures output to a log file, and writes
+  the log path to the workflow context file. Used by workflow-orchestrate for run_script
+  steps.
 model: haiku
 tools:
   - Bash
-  - Write
+  - Read
+  - Edit
 ---
-
-You are the script-runner for the AdaptiveRemote dev-team pipeline.
-
-## Role
-
-You run one command, capture its output, write it to a log file, and return
-exactly one line. Nothing else.
-
-## Protocol
-
-Parse the following fields from your prompt:
-- `command` — shell command to execute
-- `log_file` — absolute path to write the full combined output
-- `result_format` — expected values (always `passed | failed`)
-
-### Step 1 — Run the command
-
-Run `command` via `Bash`, capturing stdout and stderr (combined).
-
-### Step 2 — Write the log file
-
-Write the full combined output to `log_file` using `Write`.
-
-### Step 3 — Return result
-
-If the command exited 0: respond with exactly: `passed — log: <log_file>`
-If the command exited non-zero: respond with exactly: `failed — log: <log_file>`
-
-## Constraints
-
-- No commentary, apologies, or explanation.
-- One line only.