Run orchestration directly in foreground OpenCode

This commit is contained in:
2026-09-22 21:11:28 -04:00
parent 8ddae78551
commit 2e763cfa77
16 changed files with 270 additions and 128 deletions
@@ -1,11 +0,0 @@
---
description: Show the NestQuest development cycle status
agent: cycle-control
---
Run exactly this one shell command:
`/home/overseer/.local/share/nestquest-controller/scripts/nq-cycle status`
Report whether the controller is active and its last tick state.
Do not suggest enabling automatic startup.
@@ -1,12 +1,11 @@
---
description: Start the NestQuest development cycle on this host
agent: cycle-control
description: Run the NestQuest orchestrator now in this OpenCode terminal
agent: terminal-orchestrator
---
Run exactly this one shell command:
`/home/overseer/.local/share/nestquest-controller/scripts/nq-cycle start`
Report its status. If it says an interactive NestQuest OpenCode session is
open, tell me to close this session; the background controller will begin
afterward. Do not launch a developer agent or a controller tick in this chat.
Run the NestQuest project queue now in this foreground OpenCode session.
Read the current CTXD prompt and Maestro state, but use the FOREGROUND
TERMINAL RUNTIME instead of the service runtime. Reconcile repository and
pull-request state, then execute CONTROLLER_TICK repeatedly until a global
terminal condition, explicit user stop, genuine global block, or host-forced
yield. Do not start or wait for the systemd controller.
@@ -1,10 +0,0 @@
---
description: Stop the NestQuest development cycle on this host
agent: cycle-control
---
Run exactly this one shell command:
`/home/overseer/.local/share/nestquest-controller/scripts/nq-cycle stop`
Report the service status. Do not stop any other OpenCode session or task.