@yemi33/minions 0.1.994 → 0.1.996

package/CHANGELOG.md

@@ -1,6 +1,6 @@
 # Changelog
 
-## 0.1.994 (2026-04-15)
+## 0.1.996 (2026-04-15)
 
 ### Features
 - fix stopAfter=0 watch expiry — run forever for all conditions (#1117)
@@ -25,6 +25,7 @@
 - gate auto-fix conflict dispatch behind autoFixConflicts flag
 
 ### Fixes
+-  restore WATCH_ABSOLUTE_CONDITIONS import in watches.js lost in #1117 squash merge
 -  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
@@ -44,9 +45,9 @@
 -  loop queue flush so messages queued during combined send aren't orphaned
 -  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
 
 ### Other
+- chore: strengthen prompts and routing
 - 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

package/engine/watches.js

@@ -11,7 +11,7 @@
 const path = require('path');
 const shared = require('./shared');
 const { safeJson, mutateJsonFileLocked, ts, uid, log, writeToInbox,
-  WATCH_STATUS, WATCH_TARGET_TYPE, WATCH_CONDITION } = shared;
+  WATCH_STATUS, WATCH_TARGET_TYPE, WATCH_CONDITION, WATCH_ABSOLUTE_CONDITIONS } = shared;
 
 // Dynamic path — respects MINIONS_TEST_DIR for test isolation
 function _watchesPath() { return path.join(shared.MINIONS_DIR, 'engine', 'watches.json'); }

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@yemi33/minions",
-  "version": "0.1.994",
+  "version": "0.1.996",
   "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

@@ -6,9 +6,12 @@ Codex will review your changes — make sure your implementation is thorough and
 
 - 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.
+- You have a student who is eagerly trying to learn from you. Display model behavior: be rigorous, teach cleanly, and show what good engineering thinking looks like.
 - Explain concepts like you are teaching a packed auditorium. If the structure is weak or the example is forgettable, the explanation failed.
+- Always verify your claims. If you state something as true, earn it.
 - 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.
+- Leave no stone unturned when implementing or explaining. Half-checks, shallow analysis, and partial reasoning are not acceptable.
 
 ## Context Window Awareness
 

package/prompts/cc-system.md

@@ -9,9 +9,12 @@ Codex will review your changes — make sure your implementation is thorough and
 
 - 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.
+- You have a student who is eagerly trying to learn from you. Display model behavior: be rigorous, teach cleanly, and show what good engineering thinking looks like.
 - Explain concepts like you are teaching a packed auditorium. If the structure is weak or the example is forgettable, the explanation failed.
+- Always verify your claims. If you state something as true, earn it.
 - 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.
+- Leave no stone unturned when implementing or explaining. Half-checks, shallow analysis, and partial reasoning are not acceptable.
 
 ## 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`.

package/routing.md

@@ -18,6 +18,7 @@ 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 | lambert |
 
 Notes:
 - `_author_` means route to the PR author