@yemi33/minions 0.1.1889 → 0.1.1891

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@yemi33/minions",
-  "version": "0.1.1889",
+  "version": "0.1.1891",
   "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/meeting-debate.md

@@ -20,16 +20,20 @@ You are {{agent_name}} ({{agent_role}}) in Round 2 of a team meeting.
 
 ## Your Task
 
-You've read everyone's investigation findings above. Now:
+You've read everyone's investigation findings above. Your response MUST begin with the `Disagreements:` section below — in that order — before any other content.
 
-1. **What do you agree with?** Which points are strongest?
-2. **What do you disagree with?** Challenge weak arguments directly.
+1. **Disagreements:** (required, FIRST section) — at least one bullet naming a specific Round 1 claim you reject. Each bullet MUST identify the participant by name, quote or paraphrase the claim, give your reason for rejecting it, and cite evidence as `path:line` (for code claims) or a transcript quote (for meeting claims). If after honest review you genuinely cannot disagree with anything, the section MUST take this exact form instead:
+
+   ```
+   Disagreements: none — explicit agreement with <participant>'s claim that <claim> after verifying <evidence: path:line or transcript quote>
+   ```
+
+   "None" with no verification target is not acceptable.
+2. **What do you agree with?** (max 3 bullets) — which points are strongest, and why.
 3. **Play devil's advocate** — what's the strongest counterargument to your OWN position?
 4. **What's missing?** What did everyone overlook?
 5. **What should the team decide?**
 
-Be direct. Constructive disagreement is encouraged — don't just agree with everyone.
-
 ## Output Format
 
 Write your debate response as markdown. Reference other agents' findings by name.

package/docs/archive/distribution.md

@@ -1,97 +0,0 @@
-# Distribution & Publishing
-
-> **ARCHIVED 2026-05-12.** This document describes a defunct two-repo "personal vs. origin" architecture (`yemishin_microsoft/minions` → `yemi33/minions`) and a manual `/sync-to-personal` workflow that no longer exists. The current model is single-repo: `yemi33/minions` publishes itself to npm via `.github/workflows/publish.yml` on every push to `master`. The doc also incorrectly claims package contents are gated by a `files` field in `package.json` — they are actually gated by `.npmignore`. Kept for historical reference; do not follow these steps.
-
-Minions is distributed as an npm package (`@yemi33/minions`) from a sanitized copy of the main repo.
-
-## Two-Repo Architecture
-
-| Repo | Purpose | What's included |
-|------|---------|----------------|
-| **origin** (`yemishin_microsoft/minions`) | Full working repo with all session state | Everything — history, notes, decisions, work items, CLAUDE.md |
-| **personal** (`yemi33/minions`) | Clean distribution for others | Engine, dashboard, playbooks, charters, skills, docs, npm package files |
-
-## What Gets Stripped
-
-These files are removed during sync to personal:
-
-| Category | Pattern | Reason |
-|----------|---------|--------|
-| Agent history | `agents/*/history.md` | Session-specific task logs |
-| Notes archive | `notes/archive/*` | Historical agent findings |
-| Notes inbox | `notes/inbox/*` | Pending agent findings |
-| Notes summary | `notes.md` | Consolidated knowledge (runtime) |
-| Work items | `work-items.json` | Runtime dispatch tracking |
-| Project instructions | `CLAUDE.md` | Org-specific context |
-
-## npm Package
-
-**Package:** `@yemi33/minions`
-**Registry:** https://www.npmjs.com/package/@yemi33/minions
-
-### What's in the package
-
-Controlled by the `files` field in `package.json`:
-- `bin/minions.js` — CLI entry point
-- `engine.js`, `dashboard.js`, `dashboard/` (fragments), `minions.js` — core scripts
-- `engine/spawn-agent.js`, `engine/ado-mcp-wrapper.js` — engine helpers
-- `agents/*/charter.md` — agent role definitions
-- `playbooks/*.md` — task templates
-- `config.template.json` — starter config
-- `routing.md`, `team.md` — editable team config
-- `skills/`, `docs/` — documentation and workflows
-
-### How `minions init` works
-
-1. Copies all package files from `node_modules/@yemi33/minions/` to `~/.minions/`
-2. Creates `config.json` from `config.template.json` if it doesn't exist
-3. Creates runtime directories (`engine/`, `notes/inbox/`, `notes/archive/`, etc.)
-4. Runs `minions.js init` to populate config with default agents
-5. On `--force`, overwrites `.js` and `.html` files but preserves user-modified `.md` files
-
-### How updates work
-
-- Users run `npm update -g @yemi33/minions` then `minions init --force` to update engine code
-- `npx @yemi33/minions` always fetches the latest version
-
-## Auto-Publishing
-
-A GitHub Action on the personal repo auto-publishes to npm on every push to master.
-
-### How it works
-
-1. Push to `yemi33/minions` master triggers `.github/workflows/publish.yml`
-2. Action queries npm for the current published version
-3. Bumps patch version (e.g., `0.1.5` → `0.1.6`)
-4. Publishes to npm with the new version
-5. Commits the version bump back to the repo with `[skip ci]` to prevent loops
-
-### Why version comes from npm, not the repo
-
-The sync-to-personal workflow force-pushes, which overwrites any version bump commits from previous action runs. So the action reads the latest version from the npm registry and bumps from there.
-
-### Setup requirements
-
-- `NPM_TOKEN` secret on `yemi33/minions` — a granular access token with publish permissions and 2FA bypass enabled
-- The workflow file (`.github/workflows/publish.yml`) is gitignored on the org repo and force-added during sync
-
-## Sync Workflow
-
-Run `/sync-to-personal` or manually:
-
-```bash
-# 1. Create dist branch, strip files, add workflow, force-push
-git checkout -b dist-clean
-git rm --cached agents/*/history.md notes.md work-items.json CLAUDE.md
-git rm -r --cached notes/archive/ notes/inbox/ notes/
-# ... add .gitkeep files, .gitignore entries, workflow file
-git add -f .github/workflows/publish.yml
-git commit -m "Strip for distribution"
-git push personal dist-clean:master --force
-
-# 2. Return to master
-git checkout master
-git branch -D dist-clean
-```
-
-