@bradygaster/squad-cli 0.9.2-insider.6 → 0.9.4-insider.1

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@bradygaster/squad-cli",
-  "version": "0.9.2-insider.6",
+  "version": "0.9.4-insider.1",
   "description": "Squad CLI — Command-line interface for the Squad multi-agent runtime",
   "type": "module",
   "bin": {
@@ -124,6 +124,10 @@
       "types": "./dist/cli/commands/watch/index.d.ts",
       "import": "./dist/cli/commands/watch/index.js"
     },
+    "./commands/watch/health": {
+      "types": "./dist/cli/commands/watch/health.d.ts",
+      "import": "./dist/cli/commands/watch/health.js"
+    },
     "./commands/start": {
       "types": "./dist/cli/commands/start.d.ts",
       "import": "./dist/cli/commands/start.js"
@@ -177,7 +181,7 @@
     "node": ">=22.5.0"
   },
   "dependencies": {
-    "@bradygaster/squad-sdk": "*",
+    "@bradygaster/squad-sdk": "0.9.4-insider.1",
     "ink": "^6.8.0",
     "react": "^19.2.4",
     "vscode-jsonrpc": "^8.2.1"

package/templates/casting-reference.md

@@ -1,104 +1,104 @@
-# Casting Reference
-
-On-demand reference for Squad's casting system. Loaded during Init Mode or when adding team members.
-
-## Universe Table
-
-| Universe | Capacity | Shape Tags | Resonance Signals |
-|---|---|---|---|
-| The Usual Suspects | 6 | small, noir, ensemble | crime, heist, mystery, deception |
-| Reservoir Dogs | 8 | small, noir, ensemble | crime, heist, tension, loyalty |
-| Alien | 8 | small, sci-fi, survival | space, isolation, threat, engineering |
-| Ocean's Eleven | 14 | medium, heist, ensemble | planning, coordination, roles, charm |
-| Arrested Development | 15 | medium, comedy, ensemble | dysfunction, business, family, satire |
-| Star Wars | 12 | medium, sci-fi, epic | conflict, mentorship, legacy, rebellion |
-| The Matrix | 10 | medium, sci-fi, cyberpunk | systems, reality, hacking, philosophy |
-| Firefly | 10 | medium, sci-fi, western | frontier, crew, independence, smuggling |
-| The Goonies | 8 | small, adventure, ensemble | exploration, treasure, kids, teamwork |
-| The Simpsons | 20 | large, comedy, ensemble | satire, community, family, absurdity |
-| Breaking Bad | 12 | medium, drama, tension | chemistry, transformation, consequence, power |
-| Lost | 18 | large, mystery, ensemble | survival, mystery, groups, leadership |
-| Marvel Cinematic Universe | 25 | large, action, ensemble | heroism, teamwork, powers, scale |
-| DC Universe | 18 | large, action, ensemble | justice, duality, powers, mythology |
-| Futurama | 12 | medium, sci-fi, comedy | future, robots, space, absurdity |
-
-**Total: 15 universes** — capacity range 6–25.
-
-## Selection Algorithm
-
-Universe selection is deterministic. Score each universe and pick the highest:
-
-```
-score = size_fit + shape_fit + resonance_fit + LRU
-```
-
-| Factor | Description |
-|---|---|
-| `size_fit` | How well the universe capacity matches the team size. Prefer universes where capacity ≥ agent_count with minimal waste. |
-| `shape_fit` | Match universe shape tags against the assignment shape derived from the project description. |
-| `resonance_fit` | Match universe resonance signals against session and repo context signals. |
-| `LRU` | Least-recently-used bonus — prefer universes not used in recent assignments (from `history.json`). |
-
-Same inputs → same choice (unless LRU changes between assignments).
-
-## Casting State File Schemas
-
-### policy.json
-
-Source template: `.squad/templates/casting-policy.json`
-Runtime location: `.squad/casting/policy.json`
-
-```json
-{
-  "casting_policy_version": "1.1",
-  "allowlist_universes": ["Universe Name", "..."],
-  "universe_capacity": {
-    "Universe Name": 10
-  }
-}
-```
-
-### registry.json
-
-Source template: `.squad/templates/casting-registry.json`
-Runtime location: `.squad/casting/registry.json`
-
-```json
-{
-  "agents": {
-    "agent-role-id": {
-      "persistent_name": "CharacterName",
-      "universe": "Universe Name",
-      "created_at": "ISO-8601",
-      "legacy_named": false,
-      "status": "active"
-    }
-  }
-}
-```
-
-### history.json
-
-Source template: `.squad/templates/casting-history.json`
-Runtime location: `.squad/casting/history.json`
-
-```json
-{
-  "universe_usage_history": [
-    {
-      "universe": "Universe Name",
-      "assignment_id": "unique-id",
-      "used_at": "ISO-8601"
-    }
-  ],
-  "assignment_cast_snapshots": {
-    "assignment-id": {
-      "universe": "Universe Name",
-      "agents": {
-        "role-id": "CharacterName"
-      },
-      "created_at": "ISO-8601"
-    }
-  }
-}
-```
+# Casting Reference
+
+On-demand reference for Squad's casting system. Loaded during Init Mode or when adding team members.
+
+## Universe Table
+
+| Universe | Capacity | Shape Tags | Resonance Signals |
+|---|---|---|---|
+| The Usual Suspects | 6 | small, noir, ensemble | crime, heist, mystery, deception |
+| Reservoir Dogs | 8 | small, noir, ensemble | crime, heist, tension, loyalty |
+| Alien | 8 | small, sci-fi, survival | space, isolation, threat, engineering |
+| Ocean's Eleven | 14 | medium, heist, ensemble | planning, coordination, roles, charm |
+| Arrested Development | 15 | medium, comedy, ensemble | dysfunction, business, family, satire |
+| Star Wars | 12 | medium, sci-fi, epic | conflict, mentorship, legacy, rebellion |
+| The Matrix | 10 | medium, sci-fi, cyberpunk | systems, reality, hacking, philosophy |
+| Firefly | 10 | medium, sci-fi, western | frontier, crew, independence, smuggling |
+| The Goonies | 8 | small, adventure, ensemble | exploration, treasure, kids, teamwork |
+| The Simpsons | 20 | large, comedy, ensemble | satire, community, family, absurdity |
+| Breaking Bad | 12 | medium, drama, tension | chemistry, transformation, consequence, power |
+| Lost | 18 | large, mystery, ensemble | survival, mystery, groups, leadership |
+| Marvel Cinematic Universe | 25 | large, action, ensemble | heroism, teamwork, powers, scale |
+| DC Universe | 18 | large, action, ensemble | justice, duality, powers, mythology |
+| Futurama | 12 | medium, sci-fi, comedy | future, robots, space, absurdity |
+
+**Total: 15 universes** — capacity range 6–25.
+
+## Selection Algorithm
+
+Universe selection is deterministic. Score each universe and pick the highest:
+
+```
+score = size_fit + shape_fit + resonance_fit + LRU
+```
+
+| Factor | Description |
+|---|---|
+| `size_fit` | How well the universe capacity matches the team size. Prefer universes where capacity ≥ agent_count with minimal waste. |
+| `shape_fit` | Match universe shape tags against the assignment shape derived from the project description. |
+| `resonance_fit` | Match universe resonance signals against session and repo context signals. |
+| `LRU` | Least-recently-used bonus — prefer universes not used in recent assignments (from `history.json`). |
+
+Same inputs → same choice (unless LRU changes between assignments).
+
+## Casting State File Schemas
+
+### policy.json
+
+Source template: `.squad/templates/casting-policy.json`
+Runtime location: `.squad/casting/policy.json`
+
+```json
+{
+  "casting_policy_version": "1.1",
+  "allowlist_universes": ["Universe Name", "..."],
+  "universe_capacity": {
+    "Universe Name": 10
+  }
+}
+```
+
+### registry.json
+
+Source template: `.squad/templates/casting-registry.json`
+Runtime location: `.squad/casting/registry.json`
+
+```json
+{
+  "agents": {
+    "agent-role-id": {
+      "persistent_name": "CharacterName",
+      "universe": "Universe Name",
+      "created_at": "ISO-8601",
+      "legacy_named": false,
+      "status": "active"
+    }
+  }
+}
+```
+
+### history.json
+
+Source template: `.squad/templates/casting-history.json`
+Runtime location: `.squad/casting/history.json`
+
+```json
+{
+  "universe_usage_history": [
+    {
+      "universe": "Universe Name",
+      "assignment_id": "unique-id",
+      "used_at": "ISO-8601"
+    }
+  ],
+  "assignment_cast_snapshots": {
+    "assignment-id": {
+      "universe": "Universe Name",
+      "agents": {
+        "role-id": "CharacterName"
+      },
+      "created_at": "ISO-8601"
+    }
+  }
+}
+```

package/templates/ceremonies.md

@@ -39,3 +39,31 @@
 2. Root cause analysis
 3. What should change?
 4. Action items for next iteration
+
+
+---
+
+## Retrospective with Enforcement
+
+| Field | Value |
+|-------|-------|
+| **Trigger** | auto |
+| **When** | weekly |
+| **Condition** | No *retrospective* log in .squad/log/ within the last 7 days |
+| **Facilitator** | lead |
+| **Participants** | all |
+| **Time budget** | focused |
+| **Enabled** | yes |
+| **Enforcement skill** | retro-enforcement |
+
+**Agenda:**
+1. What shipped this week? (closed issues, merged PRs)
+2. What did not ship? (open issues, blockers)
+3. Root cause on any failures
+4. Action items -- each MUST become a GitHub Issue labeled retro-action
+
+**Coordinator integration:**
+At round start, call Test-RetroOverdue (see skill retro-enforcement). If overdue, run this ceremony before the work queue.
+
+**Why GitHub Issues, not markdown:**
+Production data: 0% completion across 6 retros using markdown checklists, 100% after switching to GitHub Issues.

package/templates/fact-checker-charter.md

@@ -0,0 +1,83 @@
+# Fact Checker
+
+> Trust, but verify. Every claim gets a source check.
+
+## Identity
+
+- **Name:** Fact Checker
+- **Role:** Devil's Advocate & Verification Agent
+- **Style:** Rigorous but constructive. Flags issues clearly without being abrasive.
+- **Casting:** Gets a universe name like any other agent (not exempt like Scribe/Ralph).
+
+## What I Do
+
+Validate claims, detect hallucinations, and run counter-hypotheses on team output before it ships.
+
+## Verification Methodology
+
+For every claim or assertion I review:
+
+1. **Source Check:** What evidence supports this? Can I verify it?
+2. **Counter-Hypothesis:** What would disprove this? Is there an alternative explanation?
+3. **Existence Check:** Do the URLs, package names, API endpoints, file paths, and version numbers actually exist?
+4. **Consistency Check:** Does this contradict anything in `.squad/decisions.md` or prior team output?
+
+## Confidence Ratings
+
+Every verified item gets one of:
+
+| Rating | Meaning |
+|--------|---------|
+| ✅ Verified | Confirmed via source, test, or direct observation |
+| ⚠️ Unverified | Plausible but could not confirm — needs human review |
+| ❌ Contradicted | Found evidence that contradicts the claim |
+| 🔍 Needs Investigation | Requires deeper analysis beyond current scope |
+
+## When I'm Triggered
+
+- **Auto-trigger (via routing):** Tasks tagged with `review`, `verify`, `fact-check`, `audit`
+- **Pre-publish gate:** Before any artifact is delivered to the user, if configured
+- **Manual:** User says "fact-check this", "verify these claims", "double-check"
+- **Post-research:** After any agent produces research output or external references
+
+## How I Work
+
+1. **Read the artifact** — understand what's being claimed
+2. **Extract claims** — list every factual assertion (package versions, API behavior, file existence, etc.)
+3. **Verify each claim** — use available tools (grep, glob, web search, gh CLI) to check
+4. **Run counter-hypotheses** — for key assumptions, ask "what if this is wrong?"
+5. **Produce a verification report:**
+
+```markdown
+## Verification Report — {artifact name}
+
+### Claims Verified
+- ✅ {claim} — confirmed via {source}
+- ⚠️ {claim} — could not verify, {reason}
+- ❌ {claim} — contradicted by {evidence}
+
+### Counter-Hypotheses
+- {assumption} → Alternative: {counter}
+
+### Recommendation
+{proceed / revise / block with reasons}
+```
+
+6. **Write decision** if I found issues: `.squad/decisions/inbox/fact-checker-{slug}.md`
+
+## Boundaries
+
+**I handle:** Verification, fact-checking, counter-hypotheses, hallucination detection.
+
+**I don't handle:** Implementation, design, testing, or docs. I review, not create.
+
+**I am not a blocker by default.** My verification report is advisory unless the coordinator or a reviewer escalates it to a gate.
+
+## Project Context
+
+**Project:** {project_name}
+{project_description}
+
+## Learnings
+
+Initial setup complete. Ready for verification work.

package/templates/issue-lifecycle.md

@@ -231,7 +231,8 @@ Working as {member} ({role})
 **Update workflow:**
 ```bash
 # Make changes
-git add .
+# ⚠️ NEVER use `git add .` or `git add -A` — only stage files you intentionally changed
+git add -- {specific files you modified}
 git commit -m "fix: address review feedback"
 git push
 ```

package/templates/loop.md

@@ -0,0 +1,46 @@
+---
+configured: false
+interval: 10
+timeout: 30
+description: "My squad work loop"
+---
+
+# Squad Work Loop
+
+> ⚠️ Set `configured: true` in the frontmatter above to activate this loop.
+> Run with: `squad loop`
+
+## What to do each cycle
+
+Describe what your squad should do every time the loop wakes up. Be specific —
+the more context you give, the better your squad performs.
+
+Examples:
+- Check for new messages in a Teams channel and summarize action items
+- Review recent pull requests and flag anything needing attention
+- Run a health check on staging and report anomalies
+- Scan the inbox for anything that needs a response today
+
+<!-- Replace this section with your actual loop instructions. -->
+
+## Monitoring (optional)
+
+If you want your squad to watch external channels, enable monitor capabilities:
+
+```bash
+squad loop --monitor-email --monitor-teams
+```
+
+## Personality (optional)
+
+If your squad has a specific voice or style, describe it here so each cycle
+stays consistent.
+
+Example: "Be concise. Use bullet points. Flag blockers clearly."
+
+## Tips
+
+- **Be specific.** Vague prompts produce vague results.
+- **Set boundaries.** Tell the squad what NOT to do (e.g., "Don't send messages to anyone but me").
+- **Start small.** Begin with one task per cycle, then expand.
+- **Use frontmatter.** `interval` controls how often the loop runs. `timeout` caps each cycle.

package/templates/ralph-triage.js

@@ -55,6 +55,8 @@ function normalizeEol(content) {
   return content.replace(/\r\n/g, '\n').replace(/\r/g, '\n');
 }
 
+function slugify(text) { return text.toLowerCase().replace(/[^a-z0-9]+/g, '-').replace(/^-|-$/g, ''); }
+
 function parseRoutingRules(routingMd) {
   const table = parseTableSection(routingMd, /^##\s*work\s*type\s*(?:→|->)\s*agent\b/i);
   if (!table) return [];
@@ -124,7 +126,7 @@ function parseRoster(teamMd) {
     members.push({
       name,
       role,
-      label: `squad:${name.toLowerCase()}`,
+      label: `squad:${slugify(name)}`,
     });
   }
 

package/templates/scribe-charter.md

@@ -61,7 +61,26 @@ After every substantial work session:
    Do NOT embed newlines in `git commit -m` (backtick-n fails silently in PowerShell).
    Instead:
    - `cd` into the team root first.
-   - Stage all `.squad/` files: `git add .squad/`
+   - Stage only files Scribe actually modified in this session.
+     Use `git status --porcelain` to build an explicit file list filtered to allowed `.squad/` paths:
+     ```powershell
+     $allowed = @(
+       '.squad/decisions.md',
+       '.squad/decisions-archive.md'
+     )
+     $allowedPatterns = @(
+       '.squad/agents/*/history.md',
+       '.squad/agents/*/history-archive.md',
+       '.squad/log/*',
+       '.squad/orchestration-log/*'
+     )
+     $filesToStage = git status --porcelain | Where-Object { $_.Length -gt 3 } | ForEach-Object { $_.Substring(3) -replace '^.* -> ','' } | Where-Object {
+       $f = $_
+       ($f -in $allowed) -or ($allowedPatterns | Where-Object { $f -like $_ })
+     }
+     if ($filesToStage) { $filesToStage | Where-Object { $_ } | ForEach-Object { git add -- $_ } }
+     ```
+     ⚠️ NEVER use `git add .squad/` or broad globs — only stage specific files you wrote in this session.
    - Check for staged changes: `git diff --cached --quiet`
      If exit code is 0, no changes — skip silently.
    - Write the commit message to a temp file, then commit with `-F`: