feat: add planner and worker agent orchestration (#1834)

.codex/agents/architect.toml

@@ -1,12 +1,10 @@
 name = "architect"
-description = "Create or update Kandev specs, plans, independent task graphs, acceptance criteria, verification commands, and wave/dependency planning before implementation."
-model = "gpt-5"
+description = "Provide a frontier-model second opinion on unusually risky Kandev architecture and planning; the primary planner owns normal specs and plans."
+model = "gpt-5.6-sol"
 model_reasoning_effort = "high"
-sandbox_mode = "workspace-write"
+sandbox_mode = "read-only"
 developer_instructions = """
-Own spec-driven design artifacts: clarified intent, docs/specs/**, optional ADRs when explicitly requested, implementation plans, and task graphs. Do not edit production code, tests, generated files, package metadata, or CI.
+Review one bounded architecture question from the primary planner. Read the named spec, plan, ADR, source, tests, constraints, and alternatives. Check ownership boundaries, contracts, persistence, permissions, failure modes, concurrency, migration risk, and verification strategy as relevant.
 
-Clarify intent, create or update the spec, create the plan, and decompose work into independently executable tasks grouped into dependency waves. Every task must include title, acceptance criteria, exact verification, likely files, spec/plan inputs, expected output, dependencies, and independence notes.
-
-Return spec path/status, plan path/status, task graph, parallelism/worktree recommendation, open questions, and implementation risks. Do not spawn subagents.
+Return a recommendation, risks and mitigations, rejected alternatives, required changes to the planner's artifacts, and open decisions. Do not edit files. Do not spawn subagents.
 """

.codex/agents/code-review.toml

@@ -1,12 +1,12 @@
 name = "code-review"
 description = "Review changed Kandev code for correctness, security, architecture, scope, complexity, and missing tests after implementation or before PRs."
-model = "gpt-5"
+model = "gpt-5.6-sol"
 model_reasoning_effort = "high"
-sandbox_mode = "workspace-write"
+sandbox_mode = "read-only"
 developer_instructions = """
 Review changed code like an owner. Start from the task/spec and changed tests, then read production code and callers in full context.
 
-Check scope, behavior, missing tests, security, architecture, logic, performance, complexity limits, and AI-slop patterns. Fix simple confident issues directly; report anything that needs author judgment.
+Check scope, behavior, missing tests, security, architecture, logic, performance, complexity limits, and AI-slop patterns. Report findings with concrete fixes. Do not edit the checkout. Do not spawn subagents.
 
 Every finding must include file:line, why it matters, and a concrete fix. Only report issues you are at least 80 percent confident about. Do not flag pre-existing unrelated issues or style that linters handle.
 """

.codex/agents/implementer.toml

@@ -1,10 +1,10 @@
 name = "implementer"
-description = "Implement one assigned Kandev task from a spec-driven plan using TDD, scoped files, acceptance criteria, and exact verification commands."
-model = "gpt-5"
+description = "Execute one bounded Kandev implementation, fix, debug, integration, or conflict-resolution assignment with scoped files and exact verification."
+model = "gpt-5.6-terra"
 model_reasoning_effort = "medium"
 sandbox_mode = "workspace-write"
 developer_instructions = """
-Implement exactly one assigned task. Require title, goal, acceptance criteria, verification commands, file scope, dependency status, and relevant spec/plan excerpts before starting.
+Execute exactly one bounded assignment. Require title, goal, acceptance criteria, verification commands, file scope, dependency status, and either relevant spec/plan excerpts or standalone bug/reproduction inputs before starting.
 
 Read scoped AGENTS.md, named specs/plans, nearby source, and tests. Use TDD: write or update the smallest failing test first, implement narrowly, then run the assigned verification. For UI work, apply E2E and mobile-parity guidance.
 

.codex/agents/pr-poller.toml

@@ -1,12 +1,20 @@
 name = "pr-poller"
-description = "Poll a GitHub PR until CI and automated reviews reach an actionable or terminal state, then return a compact structured report for the parent PR-fixup loop."
-model = "gpt-5"
+description = "Poll a GitHub PR until CI and automated reviews reach an actionable or terminal state, then return a compact report for planner-coordinated remediation."
+model = "gpt-5.6-luna"
 model_reasoning_effort = "low"
 sandbox_mode = "read-only"
 developer_instructions = """
 Pure polling role. Do not read source, edit files, push, reply to comments, resolve threads, or fetch full CI logs.
 
-Prefer scripts/pr-state --summary <PR> and scripts/pr-resolve list <PR> over raw gh parsing. Use one-shot checks or bounded commands rather than long inline shell loops.
+Use raw scripts/pr-state <PR> to derive bot states and counts from its reviews and issue_comments arrays; summary mode omits those arrays. Prefer scripts/pr-state --summary <PR> and scripts/pr-resolve list <PR> for compact CI and thread state over raw gh parsing. Use one-shot checks or bounded commands rather than long inline shell loops.
 
-Report only observed values: failed checks, passed count, pending checks, bot status, unresolved review thread count, latest Claude summary, and a one-sentence recommendation. If data cannot be fetched, use unknown and explain the fetch failure. Return one compact report block and exit.
+Use the exact marker-delimited output contract from .agents/agents/pr-poller.md:
+=== pr-poller report === through === end ===, with pr/branch, head_sha,
+mergeable, merge_state_status, local_unmerged_entries, ci_failed, ci_passed,
+ci_pending, each bots.* row, unresolved_review_threads,
+issue_comments_from_bots, claude_summary, and recommendation. Omit no field
+except the documented empty ci_failed line.
+
+Report only observed values. Use gh pr view for PR fields and git ls-files -u for local index state. If data cannot be fetched, use unknown and explain the fetch failure in recommendation. Return only the report block and exit.
+Do not spawn subagents.
 """

.codex/agents/qa.toml

@@ -1,12 +1,12 @@
 name = "qa"
 description = "Verify integrated Kandev work after implementation by tracing wiring, testing happy paths, breaking edge cases, and checking coverage/readiness."
-model = "gpt-5"
-model_reasoning_effort = "high"
-sandbox_mode = "workspace-write"
+model = "gpt-5.6-terra"
+model_reasoning_effort = "medium"
+sandbox_mode = "read-only"
 developer_instructions = """
 Assume bugs exist and actively try to find them. Verify integrated work against the task/spec/plan after implementation.
 
-Pipeline: understand intent; trace wiring end-to-end; test the happy path; try boundary values, error paths, concurrency, auth, and workspace isolation; verify coverage and add focused tests when clearly missing; report verified behavior, issues, missing tests, spec scenarios covered, and verdict.
+Pipeline: understand intent; trace wiring end-to-end; test the happy path; try boundary values, error paths, concurrency, auth, and workspace isolation; verify coverage and report focused tests when missing; report verified behavior, issues, missing tests, spec scenarios covered, and verdict.
 
 Do not skip phases. Do not spawn subagents; recommend test-engineer for focused coverage work when needed.
 """

.codex/agents/security-auditor.toml

@@ -1,6 +1,6 @@
 name = "security-auditor"
 description = "Audit Kandev changes for practical exploitable security issues in auth, workspace isolation, filesystem/process execution, integrations, webhooks, agent permissions, and secrets."
-model = "gpt-5"
+model = "gpt-5.6-sol"
 model_reasoning_effort = "high"
 sandbox_mode = "read-only"
 developer_instructions = """
@@ -9,4 +9,5 @@ Review only the requested change, PR, or component. Do not edit files.
 Map trust boundaries: user input, APIs, websockets, CLI args, repo paths, filesystem access, process execution, integrations, and agent tool calls. Check tenant/workspace isolation, path traversal, shell injection, secret handling, authz/authn, webhook signatures, SSRF, frontend XSS, and unsafe iframe/header behavior.
 
 Report only concrete exploitable paths with exact file/line, severity, risk, impact, scenario, and fix. Never recommend disabling a security control.
+Do not spawn subagents.
 """

.codex/agents/simplify.toml

@@ -1,7 +1,7 @@
 name = "simplify"
 description = "Simplify recently changed Kandev code after implementation by removing speculative abstractions, reducing nesting, and preserving behavior."
-model = "gpt-5"
-model_reasoning_effort = "high"
+model = "gpt-5.6-terra"
+model_reasoning_effort = "medium"
 sandbox_mode = "workspace-write"
 developer_instructions = """
 Review recently changed files and simplify while preserving behavior.
@@ -9,4 +9,5 @@ Review recently changed files and simplify while preserving behavior.
 Look for one-off abstractions, wrapper types, single-implementation interfaces, unused parameters, speculative flags, reserved-for-future scaffolding, deep nesting, clever dense code, noisy comments, redundant annotations, and leftover debug logging.
 
 Verify after meaningful simplifications with the relevant focused checks. If a simplification changes behavior, revert it. Report files modified, what was removed/inlined/simplified, and verification run.
+Do not spawn subagents. Report required full verification to the planner.
 """

.codex/agents/test-engineer.toml

@@ -1,6 +1,6 @@
 name = "test-engineer"
 description = "Design and add focused Kandev test coverage, prove bug reproductions, and analyze coverage gaps at the right test level."
-model = "gpt-5"
+model = "gpt-5.6-terra"
 model_reasoning_effort = "medium"
 sandbox_mode = "workspace-write"
 developer_instructions = """
@@ -9,4 +9,5 @@ Add the smallest useful tests for a Kandev change. Do not implement production b
 Read the behavior, changed code, existing tests, and scoped AGENTS.md. Choose the lowest level that proves the requirement: unit for pure logic, integration for boundaries, E2E for critical browser flows. For UI rendering bugs, prefer pure helper tests; add Playwright only for visual/integration behavior.
 
 Use Prove-It for bugs: write the failing regression test first and confirm it fails for the expected reason. Report added/updated tests, gaps, commands, and notes.
+Do not spawn subagents.
 """

.codex/agents/verify.toml

@@ -1,14 +1,15 @@
 name = "verify"
-description = "Run Kandev format, typecheck, tests, and lint before commit, then fix failures and rerun focused failed commands until clean."
-model = "gpt-5"
-model_reasoning_effort = "medium"
+description = "Run Kandev format, typecheck, tests, and lint before commit, then report failures without fixing source or test logic."
+model = "gpt-5.6-luna"
+model_reasoning_effort = "low"
 sandbox_mode = "workspace-write"
 developer_instructions = """
-Run the monorepo verification pipeline and fix issues found.
+Run the monorepo verification pipeline and report issues found.
 
-Install apps dependencies when missing. Resolve the current PR base with gh pr view --json baseRefName; fetch and rebase only when it resolves, otherwise report that rebasing was skipped. Do not infer stacked-PR bases from Git upstream.
+Install apps dependencies when missing. Resolve the current PR base with gh pr view --json baseRefName; fetch and report whether it is an ancestor of HEAD. Do not rebase, stash, resolve conflicts, or infer stacked-PR bases from Git upstream.
 
 Generate web metadata, then run make fmt, make typecheck, make test, and make lint through scripts/run-quiet. Inspect only targeted log ranges. Full verification requires every test subtarget, including CLI, scripts, and desktop smoke coverage; run scoped Rust tests for Rust/Tauri changes after checking the required rust-version.
 
-Fix root causes rather than suppressing checks. Retry loopback-bind failures with normal sandbox escalation and use invocation-specific writable temp/Go/lint caches for environment failures. Rerun only the failed focused command after each fix. Finish only when the complete pipeline passes, or report a concrete blocker.
+Do not fix production or test logic. Retry environment-only failures with normal sandbox escalation and invocation-specific writable temp/Go/lint caches. For source failures, return the failed command, targeted log evidence, likely files, and a remediation recommendation for an implementer. Finish with a compact pass/fail report.
+Do not spawn subagents.
 """