@ornexus/neocortex 4.60.65 → 4.60.67

package/targets-stubs/claude-code/neocortex-root.md

@@ -1,6 +1,6 @@
 ---
 name: neocortex-root
-description: "🧠 Neocortex Root Agent v4.60.65 | OrNexus Team"
+description: "🧠 Neocortex Root Agent v4.60.67 | OrNexus Team"
 model: opus
 color: blue
 tools:
@@ -108,7 +108,7 @@ SEMPRE que este agente for invocado, imprima o banner abaixo como PRIMEIRO outpu
 ┌────────────────────────────────────────────────────────────┐
 │                                                            │
 │       #######           N E O C O R T E X                  │
-│      ###  ########      v4.60.65                           │
+│      ###  ########      v4.60.67                           │
 │ #########      #####                                       │
 │ ##    ##############    Development Orchestrator           │
 │ ##   ###  ######  ##    OrNexus Team                       │
@@ -226,7 +226,7 @@ operator remediation according to the server response.
 A child `*yolo` terminal success, including a merge/status `done` result, stops
 only that child story. It is not a yoloop stop. After the child returns, I
 resume ownership as the root agent and re-invoke `*yoloop` when the latest
-yoloop metadata has `yoloopComplete === false` and `yoloopAborted === false`.
+yoloop metadata has `yoloopComplete === false`, `yoloopAborted === false`, and `yoloopReleaseBlocked !== true`.
 
 ## Exemplos
 
@@ -273,7 +273,7 @@ Per iteration, when a `kind: 'task'` directive is returned:
    prompt only, such as `*yolo @docs/stories/<id>.story.md`.
 3. Wait for the child execution to return.
 4. Re-invoke `*yoloop <args>` only when the latest response metadata has all
-   of: `yoloopComplete === false`, `yoloopAborted === false`,
+   of: `yoloopComplete === false`, `yoloopAborted === false`, `yoloopReleaseBlocked !== true`,
    `safeToContinueYoloop !== false`, and the latest scoped CI merge decision,
    when present, has `blockingChecks=[]`. Otherwise STOP and report the
    outcome to the user.
@@ -291,7 +291,7 @@ Skill(skill="loop", args="@neocortex *yoloop @docs/epics/")
 
 The `/loop` skill repeatedly invokes `@neocortex *yoloop @docs/epics/` until one
 of the termination tokens appears in the response body (`[YOLOOP_COMPLETE]`,
-`[YOLOOP_ABORTED]`).
+`[YOLOOP_ABORTED]`, `[YOLOOP_RELEASE_BLOCKED]`).
 
 When public metadata includes `epicTerminalGitDirective`, the root executes it
 before re-invoking yoloop. The recorded origin is authoritative; never assume

package/targets-stubs/claude-code/neocortex.agent.yaml

@@ -4,7 +4,7 @@ agent:
     name: 'Neocortex'
     title: 'Development Orchestrator'
     icon: '>'
-    version: '4.60.65'
+    version: '4.60.67'
     architecture: 'thin-client'
     module: stand-alone
     hasSidecar: false

package/targets-stubs/claude-code/neocortex.md

@@ -1,6 +1,6 @@
 ---
 name: neocortex
-description: "🧠 Neocortex v4.60.65 | OrNexus Team"
+description: "🧠 Neocortex v4.60.67 | OrNexus Team"
 model: opus
 color: blue
 permissionMode: bypassPermissions
@@ -104,7 +104,7 @@ SEMPRE que este agente for invocado, imprima o banner abaixo como PRIMEIRO outpu
 ┌────────────────────────────────────────────────────────────┐
 │                                                            │
 │       #######           N E O C O R T E X                  │
-│      ###  ########      v4.60.65                           │
+│      ###  ########      v4.60.67                           │
 │ #########      #####                                       │
 │ ##    ##############    Development Orchestrator           │
 │ ##   ###  ######  ##    OrNexus Team                       │
@@ -205,8 +205,8 @@ This is the legacy skill-only fallback: never spawn a child subagent from
 
 A child `*yolo` terminal success, including a merge/status `done` result, stops
 only that child story. It is not a yoloop stop. After the child returns, the root
-Claude Code agent resumes ownership and re-invokes `*yoloop` when the latest
-yoloop metadata has `yoloopComplete === false` and `yoloopAborted === false`.
+Claude Code agent resumes ownership and re-invokes `*yoloop` unless the latest
+metadata says complete, aborted, or release-blocked.
 
 For architecture planning, a returned `kind: 'task'` directive authorizes only
 the single registered stage command in its `promptTemplate`. The child executes
@@ -277,9 +277,8 @@ For each `SkillDirective` with `skill === 'loop'`, invoke the Skill tool:
 - Skill name: `loop`
 - Args: the directive's `args` field, verbatim. Typical value:
   `@neocortex *yoloop @<dir>` (echoes the original user invocation).
-- Termination: pass the directive's `terminationTokens` as the loop's exit conditions.
-  The `/loop` skill watches for `[YOLOOP_COMPLETE]` (success path) and
-  `[YOLOOP_ABORTED]` (failure path); first match terminates.
+- Termination: pass `terminationTokens` as exit conditions. The first matching
+  complete, aborted, or release-blocked token stops the loop.
 
 Example invocation:
 
@@ -340,7 +339,7 @@ Server response (abbreviated):
         "kind": "skill",
         "skill": "loop",
         "args": "@neocortex *yoloop @docs/epics/",
-        "terminationTokens": ["[YOLOOP_COMPLETE]", "[YOLOOP_ABORTED]"]
+        "terminationTokens": ["[YOLOOP_COMPLETE]", "[YOLOOP_ABORTED]", "[YOLOOP_RELEASE_BLOCKED]"]
       },
       {
         "kind": "task",
@@ -360,7 +359,7 @@ Agent (correct):
 3. For the first iteration, runs child profile `neocortex` with prompt
    `*yolo @docs/stories/P122.01.story.md`.
 4. Child execution completes; agent re-invokes the loop with the next iteration.
-5. Continues until response body contains `[YOLOOP_COMPLETE]` or `[YOLOOP_ABORTED]`.
+5. Continues until response body contains `[YOLOOP_COMPLETE]`, `[YOLOOP_ABORTED]`, or `[YOLOOP_RELEASE_BLOCKED]`.
 
 Agent (INCORRECT -- pre-P122 behavior):
 

package/targets-stubs/codex/AGENTS.md

@@ -28,7 +28,7 @@ Codex built-in commands or actions.
 
 <!-- END: Plugin Conflict Prevention -->
 
-# Neocortex v4.60.65 | OrNexus Team
+# Neocortex v4.60.67 | OrNexus Team
 
 You are a Development Orchestrator. All orchestration logic is delivered by the remote Neocortex server.
 
@@ -311,11 +311,11 @@ while true; do
   echo "$RESPONSE"
   echo "$RESPONSE" | grep -q '\[YOLOOP_COMPLETE\]' && break
   echo "$RESPONSE" | grep -q '\[YOLOOP_ABORTED\]' && break
+  echo "$RESPONSE" | grep -q '\[YOLOOP_RELEASE_BLOCKED\]' && exit 1
 done
 ```
 
-The loop terminates on `[YOLOOP_COMPLETE]` (success) or `[YOLOOP_ABORTED]` (failure).
-For full details see `docs/arquitetura-software/loop-usage-guide.md`.
+Stops: `[YOLOOP_COMPLETE]`, `[YOLOOP_ABORTED]`, or `[YOLOOP_RELEASE_BLOCKED]`.
 
 When public metadata includes `epicTerminalGitDirective`, the root executes it
 before re-invoking yoloop. The recorded origin is authoritative; never assume

package/targets-stubs/cursor/agent.md

@@ -1,6 +1,6 @@
 ---
 name: neocortex
-description: "🧠 Neocortex v4.60.65 | OrNexus Team"
+description: "🧠 Neocortex v4.60.67 | OrNexus Team"
 model: inherit
 readonly: false
 is_background: false
@@ -64,7 +64,7 @@ SEMPRE que este agente for invocado, imprima o banner abaixo como PRIMEIRO outpu
 ┌────────────────────────────────────────────────────────────┐
 │                                                            │
 │       #######           N E O C O R T E X                  │
-│      ###  ########      v4.60.65                           │
+│      ###  ########      v4.60.67                           │
 │ #########      #####                                       │
 │ ##    ##############    Development Orchestrator           │
 │ ##   ###  ######  ##    OrNexus Team                       │
@@ -221,10 +221,11 @@ while true; do
   echo "$RESPONSE"
   echo "$RESPONSE" | grep -q '\[YOLOOP_COMPLETE\]' && break
   echo "$RESPONSE" | grep -q '\[YOLOOP_ABORTED\]' && break
+  echo "$RESPONSE" | grep -q '\[YOLOOP_RELEASE_BLOCKED\]' && exit 1
 done
 ```
 
-Termination tokens: `[YOLOOP_COMPLETE]` (success) and `[YOLOOP_ABORTED]` (failure).
+Termination tokens: `[YOLOOP_COMPLETE]` (success), `[YOLOOP_ABORTED]` (failure), and `[YOLOOP_RELEASE_BLOCKED]` (terminal non-success).
 
 See `docs/arquitetura-software/loop-usage-guide.md` (Platform Matrix section) for the
 full pattern, including operator guidance for long overnight sessions.

package/targets-stubs/gemini-cli/agent.md

@@ -1,6 +1,6 @@
 ---
 name: neocortex-root
-description: "🧠 Neocortex v4.60.65 | OrNexus Team"
+description: "🧠 Neocortex v4.60.67 | OrNexus Team"
 kind: local
 tools:
   # File operations (Gemini CLI built-ins)
@@ -62,7 +62,7 @@ SEMPRE que este agente for invocado, imprima o banner abaixo como PRIMEIRO outpu
 ┌────────────────────────────────────────────────────────────┐
 │                                                            │
 │       #######           N E O C O R T E X                  │
-│      ###  ########      v4.60.65                           │
+│      ###  ########      v4.60.67                           │
 │ #########      #####                                       │
 │ ##    ##############    Development Orchestrator           │
 │ ##   ###  ######  ##    OrNexus Team                       │
@@ -165,7 +165,7 @@ This is the legacy skill-only fallback: never spawn a child subagent from
 A child `*yolo` terminal success, including a merge/status `done` result, stops
 only that child story. It is not a yoloop stop. After the child returns, the root
 Gemini CLI agent resumes ownership and re-invokes `*yoloop` when the latest
-yoloop metadata has `yoloopComplete === false` and `yoloopAborted === false`.
+yoloop metadata has `yoloopComplete === false`, `yoloopAborted === false`, and `yoloopReleaseBlocked !== true`.
 
 ## Exemplos
 
@@ -234,8 +234,9 @@ while true; do
   echo "$RESPONSE"
   echo "$RESPONSE" | grep -q '\[YOLOOP_COMPLETE\]' && break
   echo "$RESPONSE" | grep -q '\[YOLOOP_ABORTED\]' && break
+  echo "$RESPONSE" | grep -q '\[YOLOOP_RELEASE_BLOCKED\]' && exit 1
 done
 ```
 
-The loop terminates on `[YOLOOP_COMPLETE]` (success) or `[YOLOOP_ABORTED]` (failure).
+The loop terminates on `[YOLOOP_COMPLETE]` (success), `[YOLOOP_ABORTED]` (failure), or `[YOLOOP_RELEASE_BLOCKED]` (terminal non-success).
 For full details see `docs/arquitetura-software/loop-usage-guide.md`.

package/targets-stubs/opencode/neocortex-root.md

@@ -58,7 +58,7 @@ explicit server opt-in rather than a local assumption.
 ┌────────────────────────────────────────────────────────────┐
 │                                                            │
 │       #######           N E O C O R T E X                  │
-│      ###  ########      v4.60.65                           │
+│      ###  ########      v4.60.67                           │
 │ #########      #####                                       │
 │ ##    ##############    Development Orchestrator           │
 │ ##   ###  ######  ##    OrNexus Team                       │
@@ -180,7 +180,7 @@ not a Neocortex server trigger. Never pass `@neocortex *yoloop ...` or
 A child `*yolo` terminal success, including a merge/status `done` result, stops
 only that child story. It is not a yoloop stop. After the child returns, I
 resume ownership as the root agent and re-invoke `*yoloop` when the latest
-yoloop metadata has `yoloopComplete === false` and `yoloopAborted === false`.
+yoloop metadata has `yoloopComplete === false`, `yoloopAborted === false`, and `yoloopReleaseBlocked !== true`.
 
 ## Examples
 
@@ -223,7 +223,7 @@ Per iteration, when a `kind: 'task'` directive is returned:
    prompt only.
 3. Wait for the child execution to return.
 4. Re-invoke `*yoloop <args>` only when the latest response metadata has all
-    of: `yoloopComplete === false`, `yoloopAborted === false`,
+    of: `yoloopComplete === false`, `yoloopAborted === false`, `yoloopReleaseBlocked !== true`,
     `safeToContinueYoloop !== false`, and the latest scoped CI merge decision,
     when present, has `blockingChecks=[]` after safe bounded remediation has
     been attempted and revalidated. Otherwise STOP and report the outcome to

package/targets-stubs/vscode/neocortex.agent.md

@@ -1,6 +1,6 @@
 ---
 name: "neocortex"
-description: "Neocortex v4.60.65 | OrNexus Team"
+description: "Neocortex v4.60.67 | OrNexus Team"
 tools:
   # Read / Edit (built-in tool sets)
   - read
@@ -68,7 +68,7 @@ SEMPRE que este agente for invocado, imprima o banner abaixo como PRIMEIRO outpu
 ┌────────────────────────────────────────────────────────────┐
 │                                                            │
 │       #######           N E O C O R T E X                  │
-│      ###  ########      v4.60.65                           │
+│      ###  ########      v4.60.67                           │
 │ #########      #####                                       │
 │ ##    ##############    Development Orchestrator           │
 │ ##   ###  ######  ##    OrNexus Team                       │
@@ -175,7 +175,7 @@ This is the legacy skill-only fallback: never spawn a child subagent from
 A child `*yolo` terminal success, including a merge/status `done` result, stops
 only that child story. It is not a yoloop stop. After the child returns, the root
 VS Code/Copilot agent resumes ownership and re-invokes `*yoloop` when the latest
-yoloop metadata has `yoloopComplete === false` and `yoloopAborted === false`.
+yoloop metadata has `yoloopComplete === false`, `yoloopAborted === false`, and `yoloopReleaseBlocked !== true`.
 
 ## Exemplos
 
@@ -250,10 +250,11 @@ while true; do
   echo "$RESPONSE"
   echo "$RESPONSE" | grep -q '\[YOLOOP_COMPLETE\]' && break
   echo "$RESPONSE" | grep -q '\[YOLOOP_ABORTED\]' && break
+  echo "$RESPONSE" | grep -q '\[YOLOOP_RELEASE_BLOCKED\]' && exit 1
 done
 ```
 
-The loop terminates on `[YOLOOP_COMPLETE]` (success) or `[YOLOOP_ABORTED]` (failure).
+The loop terminates on `[YOLOOP_COMPLETE]` (success), `[YOLOOP_ABORTED]` (failure), or `[YOLOOP_RELEASE_BLOCKED]` (terminal non-success).
 For full details see `docs/arquitetura-software/loop-usage-guide.md`.
 
 At the root only, `epicTerminalGitDirective` uses the recorded origin and