@yemi33/minions 0.1.249 → 0.1.251

package/CHANGELOG.md

@@ -1,10 +1,14 @@
 # Changelog
 
-## 0.1.249 (2026-04-03)
+## 0.1.251 (2026-04-03)
 
 ### Features
+-  add 'pin' action to CC — pin critical context to all agents
 -  mandatory test validation before PR creation in implement and fix playbooks
 
+### Fixes
+-  don't hardcode npm test — agents must read project conventions
+
 ## 0.1.248 (2026-04-03)
 
 ### Fixes

package/dashboard/js/command-center.js

@@ -279,6 +279,16 @@ async function ccExecuteAction(action) {
         status.style.color = 'var(--green)';
         break;
       }
+      case 'pin': {
+        await fetch('/api/pinned', {
+          method: 'POST', headers: { 'Content-Type': 'application/json' },
+          body: JSON.stringify({ title: action.title, content: action.content || action.description, level: action.level || '' })
+        });
+        status.innerHTML = '&#x1F4CC; Pinned: <strong>' + escHtml(action.title) + '</strong> — visible to all agents';
+        status.style.color = 'var(--green)';
+        refresh();
+        break;
+      }
       case 'plan': {
         await fetch('/api/plan', {
           method: 'POST', headers: { 'Content-Type': 'application/json' },

package/dashboard.js

@@ -378,7 +378,8 @@ If no actions are needed (just answering a question, or you handled it directly)
 
 Available action types:
 - **dispatch**: Create a work item for an agent. Fields: title, workType (ask/explore/fix/review/test/implement/verify), priority (low/medium/high), agents (array of IDs, optional), project, description. Use \`verify\` when the user wants to build PRs locally, merge branches together, start a dev server, and get a localhost URL to test.
-- **note**: Save a note/decision. Fields: title, content
+- **note**: Save a note/decision to the inbox. Fields: title, content
+- **pin**: Pin critical context visible to ALL agents on every task. Use when the user says "remember", "pin", "always", "from now on". Fields: title, content, level (optional: "critical" or "warning")
 - **plan**: Create a multi-step plan. Fields: title, description, project, branchStrategy (parallel/shared-branch)
 - **cancel**: Cancel a running agent. Fields: agent (agent ID), reason
 - **retry**: Retry failed work items. Fields: ids (array of work item IDs)

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@yemi33/minions",
-  "version": "0.1.249",
+  "version": "0.1.251",
   "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/fix.md

@@ -47,8 +47,8 @@ If you encounter merge conflicts (e.g., during `git pull` or when the PR shows c
 
 Before pushing your fix, run the project's test suite:
 
-1. Find the test command (check `package.json` scripts, CLAUDE.md, or README — usually `npm test`)
-2. Run the full test suite
+1. Find the test command by reading the project's own documentation — check CLAUDE.md, agent.md, README, or package.json scripts in the project root. Every project defines its own conventions.
+2. Run the full test suite using whatever command the project specifies
 3. If any tests fail due to your changes, fix them before pushing
 4. Do NOT push code that breaks existing tests
 

package/playbooks/implement.md

@@ -73,8 +73,8 @@ After building, verify the build succeeded. If the build fails:
 
 Before creating a PR, you MUST run the project's test suite and ensure all existing tests pass:
 
-1. Find the test command (check `package.json` scripts, CLAUDE.md, or README — usually `npm test`)
-2. Run the full test suite
+1. Find the test command by reading the project's own documentation — check CLAUDE.md, agent.md, README, or package.json scripts in the project root. Every project defines its own conventions.
+2. Run the full test suite using whatever command the project specifies
 3. If any tests fail:
    - Determine if YOUR changes caused the failure (compare with the failing test's assertions)
    - Fix any regressions you introduced