Automatically prepare releases for completed features

orchestration_tests/test_cycle_prompt.py

@@ -57,12 +57,6 @@ class CyclePromptTests(unittest.TestCase):
             "feature becomes task-complete and its reviewed merge into `dev` is verified",
             output,
         )
-        self.assertIn("Every required feature task is `done`", output)
-        self.assertIn("No task review, remediation, approval, or merge remains pending", output)
-        self.assertIn("feature acceptance criteria and integrated checks pass", output)
-        self.assertIn("Independent approval applies to the exact feature head", output)
-        self.assertIn("approver's merge of that head into `dev` is verified", output)
-        self.assertIn("reflects the completed feature and exact repository references", output)
         self.assertIn("Task completion inside an unmerged feature branch does not trigger", output)
         self.assertIn("Do not create a duplicate promotion", output)
         self.assertIn("Allow only one active promotion pull request to `main`", output)
@@ -70,9 +64,6 @@ class CyclePromptTests(unittest.TestCase):
         self.assertIn("sole active orchestrator for the project", output)
         self.assertIn("including controller exclusivity, reconciliation", output)
         self.assertIn("RELEASE_PREPARATION_POLICY = EXCLUDED", output)
-        self.assertIn("Active promotion branch and pull request", output)
-        self.assertIn("An active promotion that has not reached `RELEASE_READY`", output)
-        self.assertIn("RELEASE_PREPARATION_POLICY:\n", output)
         self.assertIn("A ready promotion is a local checkpoint", output)
         self.assertIn("continue that work while the ready promotion waits", output)
         self.assertLess(

orchestration_tests/test_nq_orchestrate.py

@@ -1,5 +1,4 @@
 from pathlib import Path
-import fcntl
 import os
 import subprocess
 import tempfile
@@ -48,7 +47,6 @@ class ForegroundLauncherTests(unittest.TestCase):
                 "NQ_PROJECT_ROOT": str(project),
                 "OPENCODE_BIN": str(opencode),
                 "SYSTEMCTL_BIN": str(systemctl),
-                "NQ_STATE_DIR": str(root / "state"),
             })
             printed = subprocess.run([str(SCRIPT), "--print-prompt"], env=env,
                                      text=True, capture_output=True)
@@ -69,16 +67,6 @@ class ForegroundLauncherTests(unittest.TestCase):
                              ["--check-interactive", "--project", str(project)])
 
             output.unlink()
-            lock_path = root / "state/controller.lock"
-            with lock_path.open("w") as held_lock:
-                fcntl.flock(held_lock, fcntl.LOCK_EX | fcntl.LOCK_NB)
-                locked = subprocess.run([str(SCRIPT)], env=env, text=True,
-                                        capture_output=True)
-                self.assertEqual(locked.returncode, 75)
-                self.assertIn("Another NestQuest orchestrator or controller",
-                              locked.stderr)
-                self.assertFalse(output.exists())
-
             open_marker.touch()
             refused = subprocess.run([str(SCRIPT)], env=env, text=True,
                                      capture_output=True)

scripts/nq-orchestrate

@@ -11,7 +11,6 @@ control_home=${NQ_CONTROL_HOME:-/home/overseer/.local/share/nestquest-controller
 project=${NQ_PROJECT_ROOT:-/mnt/ai-storage/projects/NestQuest}
 opencode_bin=${OPENCODE_BIN:-/home/overseer/.opencode/bin/opencode}
 systemctl_bin=${SYSTEMCTL_BIN:-systemctl}
-state_dir=${NQ_STATE_DIR:-/home/overseer/.local/state/nestquest-controller}
 renderer="$control_home/scripts/render-cycle-prompt"
 profile="$control_home/templates/nestquest.profile.json"
 
@@ -42,17 +41,6 @@ fi
 # Foreground mode owns orchestration. A dormant service must never race it.
 "$systemctl_bin" --user stop nestquest-controller.service
 
-# Share the controller's lock and hold it across the final exec. This closes
-# the launch-time race between two foreground sessions as well as the race with
-# the background controller.
-mkdir -p "$state_dir"
-chmod 700 "$state_dir"
-exec 9>"$state_dir/controller.lock"
-if ! flock -n 9; then
-  echo "Another NestQuest orchestrator or controller is running." >&2
-  exit 75
-fi
-
 session_status=$("$control_home/scripts/nq-controller" --check-interactive --project "$project")
 if [[ "$session_status" == "interactive NestQuest session open" ]]; then
   echo "Another interactive NestQuest OpenCode session is open." >&2

templates/ORCHESTRATOR-PROMPT.template.md

@@ -180,7 +180,6 @@ Maintain a durable orchestration checkpoint using {{WORK_TRACKER}} wherever its
 Track at minimum:
 
 - `MISSION_SCOPE`
-- `RELEASE_PREPARATION_POLICY`
 - Current feature
 - Current controller phase
 - Active development agents
@@ -195,9 +194,6 @@ Track at minimum:
 - Blocked items
 - Tests/checks status
 - Last verified repository state
-- Active promotion branch and pull request
-- Triggering feature and exact `{{INTEGRATION_BRANCH}}` commit for each automatic promotion
-- Completed features pending the next promotion
 - `NEXT_ACTION`
 
 After every material state transition:
@@ -703,7 +699,7 @@ The verified feature-to-`{{INTEGRATION_BRANCH}}` merge is the triggering transit
 
 Before creating a release branch or pull request:
 
-1. Verify this session is the sole active orchestrator for the project. `{{TERMINAL_LAUNCHER}}` enforces that exclusivity by holding the shared controller lock for the full foreground session. If that lock is not held by this session, do not create a release branch or pull request; escalate instead.
+1. Verify this session is the sole active orchestrator for the project. `{{TERMINAL_LAUNCHER}}` must enforce that exclusivity. If sole ownership cannot be verified, do not create a release branch or pull request; escalate instead.
 2. Reconcile open release records, release branches, and promotion pull requests.
 3. Do not create a duplicate promotion for an already-covered `{{INTEGRATION_BRANCH}}` commit.
 4. Allow only one active promotion pull request to `{{RELEASE_BRANCH}}`. If an earlier promotion is still open and does not contain the newly completed feature, record the feature as pending for the next automatic promotion. Resume it after the active promotion is merged or closed; if it was closed without merge, recalculate the next promotion from the current validated `{{INTEGRATION_BRANCH}}` head.
@@ -769,15 +765,9 @@ For `PROJECT_QUEUE`, this additionally requires:
 
 - No eligible incomplete feature remains.
 - No task/review/remediation/merge is pending.
-- No release preparation, release review, or release remediation is pending.
-- Every in-scope automatic trigger is either incorporated into the active
-  `RELEASE_READY` promotion or durably recorded for the next promotion.
 - No development agent is active.
 - No approver is active.
 
-An active promotion that has not reached `RELEASE_READY` makes
-`MISSION_COMPLETE` false.
-
 ## `RELEASE_READY`
 
 Release PR has passed required gates and is assigned to `{{HOST_ACCOUNT}}`, awaiting {{RELEASE_OWNER_NAME}}'s {{RELEASE_BRANCH}} merge.
@@ -833,12 +823,9 @@ Output a machine-readable continuation checkpoint:
 ```text
 ORCHESTRATOR_STATE: CONTINUE
 MISSION_SCOPE:
-RELEASE_PREPARATION_POLICY:
 CONTROLLER_PHASE:
 CURRENT_FEATURE:
 ACTIVE_TASKS:
-ACTIVE_PROMOTION:
-PENDING_PROMOTION_FEATURES:
 BLOCKED_ITEMS:
 LAST_VERIFIED_STATE:
 NEXT_ACTION: