feat: audit orchestrator systems for dual-mode agent candidates

[github-actions]

Summary

This is a sub-issue of #1310. PR #1304 introduced a dual-mode agent pattern in the code review system. This audit determines whether other orchestrator systems in the repo could benefit from adopting the same pattern.

Acceptance Criteria

1. Review each orchestrator system listed below and evaluate whether any of their subagents have clear standalone value that would benefit from dual-mode design:
   • RPI Agent (Task Researcher, Task Implementor / Phase Implementor)
   • Security Reviewer (Codebase Profiler, Skill Assessor, etc.)
   • DT Coach
   • GitHub/Jira Backlog agents
   • RAI Planner
   • SSSC Planner
2. For each subagent identified as a dual-mode candidate, document: the orchestrator it belongs to, its current file pattern, and the rationale for dual-mode adoption.
3. Produce a summary recommendation: a list of subagents to convert (if any), and a list of subagents that should remain separate-file.

Context

The dual-mode pattern uses conditional sections (Orchestrated Input gates, Lane Boundary toggles) to partition behavior based on whether a state file (e.g., diff-state.json) is provided. Audit results will inform future issues to convert individual agents where appropriate.

See: #1304 and #1310
Related to #1310

Note

🔒 Integrity filter blocked 1 item

The following item were blocked because they don't meet the GitHub integrity level.

• #785 search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".

To allow these resources, lower min-integrity in your GitHub frontmatter:

tools:
  github:
    min-integrity: approved  # merged | approved | unapproved | none

Generated by Issue Triage for issue #1310 · ◷