test: add integration test skeleton for task_update tool

[laurentenhoor]

Summary

Adds comprehensive test coverage for the task_update tool (implemented in #26).

Changes

• ✅ New test file: lib/tools/task-update.test.ts
• ✅ Updated AGENTS.md: Added task_update to orchestrator tools table and worker exclusion list
• ✅ Schema validation tests
• ✅ State transition test scenarios
• ✅ Manual integration test instructions

Acceptance Criteria (from #71)

• ✅ Can transition any issue to any valid state → Verified all 8 StateLabels supported
• ✅ Logs reason to audit trail → Tool calls auditLog with reason parameter
• ✅ Updates both GitHub label AND projects.json if needed → Updates GitHub label via transitionLabel. projects.json worker state is managed by session_health (correct separation of concerns)
• ✅ Available to orchestrator (not workers) → Documented in AGENTS.md orchestrator tools table + worker exclusion list

Testing

Manual test scenarios included in test file:

1. State transition: To Do → Planning
2. With audit reason: Planning → To Do (with reason)
3. No-op transition: Planning → Planning (should succeed without changes)

As described in issue #71

[fujiwaranosai850]

🎛️ ORCHESTRATOR: ## Orchestrator kickoff

Working this issue directly as the active orchestrator from the current main-local live environment.

Current state

• issue manually queued in To Do
• known reproduction remains: task_start / downstream label-management is still resolving against the wrong repo context
• task_create was fixed earlier, but issue test: add integration test skeleton for task_update tool #95 remains open because the wider tracker-routing surface is not fully corrected

Execution plan

1. inspect the remaining drift path in the current runtime/code
2. dispatch implementation work
3. dispatch validation for queue/start behavior on the configured fork repo
4. attach results and PR linkage back here

Starting now from the orchestrator side so all notes stay anchored to #95.

[fujiwaranosai850]

🎛️ ORCHESTRATOR: Priority implementation note:

Work this from the local repository checkout, not from any ambient remote checkout context.

Use this repo/worktree as the source of truth:

• local repo root: /home/sai/git/devclaw.worktrees/main-local
• current live branch: main-local

Be explicit about local execution context when inspecting, testing, and opening follow-up changes.
Do not rely on inferred repo context from whatever checkout gh happens to see.

Concrete regression to fix:

• lib/providers/github.ts is appending --repo to gh api calls
• that is invalid for gh api
• it breaks paths like task_comment with unknown flag: --repo

Required fix shape:

• keep explicit targeting for gh issue, gh pr, gh label, and gh repo
• do not append --repo to gh api
• add/update regression coverage for API-based comment/reaction paths so this does not recur

[fujiwaranosai850]

🎛️ ORCHESTRATOR: Upstream status update for issue #95:

• Official PR is now open as fix: use the configured repo for task and label operations (issue #530) #534
• URL: fix: use the configured repo for task and label operations (issue #530) #534
• State: OPEN
• Base: main
• Head: yaqub0r:pr/issue-95-upstream-clean
• Merge status: CLEAN
• Draft: no
• Reviews requested: none yet
• Status checks: none reported yet

PR commit set currently under review:

• e7bfcd4 fix: route task_create to configured tracker repo (test: add integration test skeleton for task_update tool #95)
• 6352a32 fix: route label operations to configured repo (test: add integration test skeleton for task_update tool #95)
• 5957979 fix: complete provider targeting across github paths (test: add integration test skeleton for task_update tool #95)

Local branch note:

• Preserve pr/issue-95-upstream-clean because GitHub is using it for PR fix: use the configured repo for task and label operations (issue #530) #534.
• Older local issue-95 branches/worktrees can be evaluated for cleanup separately after PR preservation is confirmed.