Run orchestration directly in foreground OpenCode

templates/README.md

@@ -7,6 +7,7 @@ example. Render a concrete prompt with:
 
 ```bash
 scripts/render-cycle-prompt templates/nestquest.profile.json --output /tmp/opencode/nestquest-prompt.md
+scripts/render-cycle-prompt templates/nestquest.profile.json --runtime terminal --output /tmp/opencode/nestquest-terminal-prompt.md
 ```
 
 For another project, copy the profile and set its project name, tracker,
@@ -16,9 +17,17 @@ section, especially task/feature semantics, release rules, permissions,
 review gates, and the host runtime section. The template assumes an OpenCode
 controller, a feature/task tracker, a versioned context store, a code host,
 and a separate reviewer and approver. Adapt those sections when the project's
-systems differ.
+systems differ. The default `service` runtime reproduces the CTXD prompt.
+The `terminal` runtime replaces Section 27 with a single-session foreground
+loop suitable for `opencode --agent ... --prompt ...`.
 
-Publish the reviewed **rendered** prompt into that project's context store
-with its version check. Give the project its own agent definitions, service
-unit, broker, and OpenCode start/stop commands. The template itself does not
-start a controller or register another project.
+For NestQuest, `nq-orchestrate --print-prompt` emits the fully rendered
+foreground prompt without starting OpenCode. `nq-orchestrate [mission.md]`
+renders that same prompt, appends the optional mission, and supplies it to the
+foreground orchestrator agent.
+
+Publish the reviewed **service-rendered** prompt into that project's context
+store with its version check when CTXD should retain both runtime choices.
+Give the project its own agent definitions, broker, profile, and terminal
+launcher. The template itself does not start an orchestrator or register
+another project.

templates/nestquest.profile.json

@@ -21,12 +21,14 @@
   "CODE_HOST": "Gitea",
   "TASK_ID_EXAMPLE": "TASK-123",
   "FEATURE_BRANCH_EXAMPLE": "feature/NQ-17-family-calendar",
-  "OPENCODE_VERSION": "1.18.31",
+  "OPENCODE_VERSION": "1.18.32",
+  "PROJECT_ROOT": "/mnt/ai-storage/projects/NestQuest",
   "CONTROL_HOME": "/home/overseer/.local/share/nestquest-controller",
   "SERVICE_NAME": "nestquest-controller.service",
   "START_COMMAND": "/start-nestquest-development",
   "STOP_COMMAND": "/stop-nestquest-development",
   "STATUS_COMMAND": "/nestquest-development-status",
+  "TERMINAL_LAUNCHER": "nq-orchestrate",
   "ROLE_LAUNCHER": "nq-agent",
   "REVIEW_LAUNCHER": "nq-review",
   "MERGE_BROKER": "nq-approve-merge",

templates/runtime/terminal.md

@@ -0,0 +1,34 @@
+# 27. FOREGROUND TERMINAL RUNTIME
+
+This section is the execution contract for a foreground OpenCode
+orchestrator. It replaces the service runtime section in the rendered prompt
+and takes precedence over any service-specific runtime instructions later
+read from {{CONTEXT_STORE}}.
+
+The user explicitly started this run with `{{TERMINAL_LAUNCHER}}`. Begin
+work immediately in `{{PROJECT_ROOT}}`; do not start, wait for, or delegate
+control to `{{SERVICE_NAME}}`. This single OpenCode session owns the
+orchestration loop until a global terminal condition, an explicit user stop,
+or a host-forced yield.
+
+Execute `CONTROLLER_TICK` repeatedly inside this foreground session. Do not
+end a turn merely to emit `ORCHESTRATOR_STATE: CONTINUE`, and do not treat
+one task, review, pull request, or feature merge as completion. After every
+child result or external state change, reconcile {{CONTEXT_STORE}},
+{{WORK_TRACKER}}, Git, pull requests, and checks, then perform the next
+eligible action.
+
+The installed role launchers live at `{{CONTROL_HOME}}/scripts/`. Use
+`{{ROLE_LAUNCHER}}` for developer and approver sessions. Use
+`{{REVIEW_LAUNCHER}}` with WORKTREE, BASE_REF, HEAD_REF,
+REVIEW_PROMPT_FILE, PR_NUMBER, OUTPUT_FILE for a fresh read-only
+{{REVIEWER_DISPLAY_NAME}} review. Review output belongs under
+`{{SCRATCH_DIR}}`, and exact-head approval must be posted by
+`{{REVIEW_ACCOUNT}}`. The feature-to-{{INTEGRATION_BRANCH}} approver must
+use `{{MERGE_BROKER}}`; the orchestrator and developer never perform that
+merge.
+
+If the host forces a yield before a global terminal condition, return the
+machine-readable checkpoint from Section 22. The user can resume the same
+OpenCode session from the terminal. A yield is a checkpoint, not a claim that
+the project queue is complete.