fix(taskctl): add taskctl permission to adversarial-pipeline and fix verdict prompt syntax

[randomm]

Fixes #259, #260

Problems Fixed

Bug 1: Missing taskctl permission (#259)

adversarial-pipeline had "*": "deny" with no taskctl exception. The taskctl MCP tool was completely blocked — the agent could never submit a verdict regardless of prompt instructions.

Fix: Added taskctl: "allow" to adversarial-pipeline permissions.

Bug 2: Wrong prompt syntax (#259)

Prompt instructed the agent to call taskctl verdict <taskId> --verdict APPROVED (CLI bash syntax). The agent correctly identified it couldn't find the binary and gave up.

Fix: Updated prompt to describe taskctl as an MCP tool with correct parameter names (command, taskId, verdict, verdictSummary, verdictIssues).

Tests Added (#260)

New test/tasks/agent-permissions.test.ts:

• adversarial-pipeline has taskctl permission
• adversarial-pipeline has bash permission
• developer-pipeline denies taskctl (separation of concerns)
• adversarial-pipeline denies everything else (minimal permissions)
• developer-pipeline denies task tool