The single biggest 2→3 blocker: nothing turns an external signal (new issue, PR comment, cron, channel message) into a running agent. Decide the home and shape of the trigger layer: ci-workflows reusable (GitHub-event-driven, the vendor-converged label/assignment pattern)? a new plugin? the future runner repo? routines//schedule? Claude Tag channel monitoring? Evidence: explore-plugins-inventory.md gap 2→3 #1; RESEARCH-headless-agents.md invocation-adapter + queue seams; RESEARCH-product-surface.md routines/Tag maturity.
The single biggest 2→3 blocker: nothing turns an external signal (new issue, PR comment, cron, channel message) into a running agent. Decide the home and shape of the trigger layer: ci-workflows reusable (GitHub-event-driven, the vendor-converged label/assignment pattern)? a new plugin? the future runner repo? routines//schedule? Claude Tag channel monitoring? Evidence: explore-plugins-inventory.md gap 2→3 #1; RESEARCH-headless-agents.md invocation-adapter + queue seams; RESEARCH-product-surface.md routines/Tag maturity.