@yemi33/minions 0.1.991 → 0.1.993

package/CHANGELOG.md

@@ -1,6 +1,6 @@
 # Changelog
 
-## 0.1.991 (2026-04-15)
+## 0.1.993 (2026-04-15)
 
 ### Features
 - fix doc-chat Clear chat not persisting session deletion to localStorage (#1102)
@@ -25,6 +25,8 @@
 - add PR/build status CLI shim and agent guidance
 
 ### Fixes
+-  remove dead 'meeting' row from routing.md — orchestrated by engine/meeting.js directly
+- gate review auto-dispatch on adoPollEnabled and evalLoop (#1116)
 -  updatePrAfterReview preserves fixedAt when writing minionsReview
 - replace undefined PROJECTS with config.projects in checkWatches (#1104)
 - fix syncPrsFromOutput skipping tool_result lines where PR URLs live (#1100)
@@ -43,10 +45,9 @@
 -  set lastPushedAt on fix completion to unblock re-review without poller
 -  restore ADO throttle test functions deleted during merge conflict resolution
 -  trigger second-pass re-review after fix agent completes
--  update ccInFlightAborts when retry LLM replaces original
--  skip orphaned LLM retry when client disconnected during CC stream
 
 ### Other
+- chore: harden prompt posture
 - refactor(watches): rename maxTriggers→stopAfter, add onNotMet per-poll action
 - refactor(dashboard): extract _releaseCCTab helper and CC_LOCK_WAIT_MS constant
 - merge: resolve conflicts with master on PR-1065

package/engine.js

@@ -2033,8 +2033,9 @@ async function discoverFromPrs(config, project) {
     }
 
     // PRs with changes requested → route back to author for fix
+    // Gate on evalLoopEnabled — the review→fix cycle is the eval loop
     let fixDispatched = false;
-    if (reviewStatus === 'changes-requested' && !awaitingReReview && !evalEscalated) {
+    if (evalLoopEnabled && reviewStatus === 'changes-requested' && !awaitingReReview && !evalEscalated) {
       const key = `fix-${project?.name || 'default'}-${pr.id}`;
       if (isAlreadyDispatched(key) || isOnCooldown(key, cooldownMs)) continue;
       const agentId = resolveAgent('fix', config, pr.agent);

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@yemi33/minions",
-  "version": "0.1.991",
+  "version": "0.1.993",
   "description": "Multi-agent AI dev team that runs from ~/.minions/ — five autonomous agents share a single engine, dashboard, and knowledge base",
   "bin": {
     "minions": "bin/minions.js"

package/playbooks/shared-rules.md

@@ -2,6 +2,14 @@
 
 Codex will review your changes — make sure your implementation is thorough and not lazy.
 
+## Reasoning and Teaching Posture
+
+- Act like you've already explained this yesterday. Do not ramble, re-teach obvious basics, or pad the answer. Get to the point fast.
+- You are an IQ 150 software engineering specialist. If the reasoning is average, vague, or hand-wavy, it is wrong.
+- Explain concepts like you are teaching a packed auditorium. If the structure is weak or the example is forgettable, the explanation failed.
+- Treat every answer like there is $100 on the line. Sloppy logic, missed edge cases, and fake confidence lose the bet.
+- Assume another CLI is going to review the code and try to prove you wrong. Close every hole before you answer.
+
 ## Context Window Awareness
 
 Your context window may be compacted or summarized mid-task by Claude's automatic context management. This is normal and expected for long-running tasks. Do NOT interpret compacted or truncated context as a signal to stop early, wrap up prematurely, or skip remaining work. Continue working toward your stated objective regardless of context window state — re-read key files if needed to recover context.

package/prompts/cc-system.md

@@ -5,6 +5,14 @@ You have full CLI power (read, write, edit, shell, builds) plus minions-specific
 
 Codex will review your changes — make sure your implementation is thorough and not lazy.
 
+## Reasoning and Teaching Posture
+
+- Act like you've already explained this yesterday. Do not ramble, re-teach obvious basics, or pad the answer. Get to the point fast.
+- You are an IQ 150 software engineering specialist. If the reasoning is average, vague, or hand-wavy, it is wrong.
+- Explain concepts like you are teaching a packed auditorium. If the structure is weak or the example is forgettable, the explanation failed.
+- Treat every answer like there is $100 on the line. Sloppy logic, missed edge cases, and fake confidence lose the bet.
+- Assume another CLI is going to review the code and try to prove you wrong. Close every hole before you answer.
+
 ## Guardrails
 READ ONLY — never write/edit: `engine.js`, `engine/*.js`, `dashboard.js`, `dashboard/**`, `minions.js`, `bin/*.js`, `engine/control.json`, `engine/dispatch.json`, `config.json`.
 CAN modify: notes, plans, knowledge, work items, pull-requests.json, routing.md, charters, skills, playbooks, project repos.

package/routing.md

@@ -18,7 +18,6 @@ How the engine decides who handles what. Parsed by engine.js — keep the table
 | ask | ripley | rebecca |
 | verify | dallas | ralph |
 | decompose | ripley | rebecca |
-| meeting | ripley | rebecca |
 
 Notes:
 - `_author_` means route to the PR author