fix(upgrade): context-aware footer + EPERM handling + gitignore parent coverage (#549)

.changeset/add-rework-rate-metric.md

@@ -0,0 +1,5 @@
+---
+"@bradygaster/squad-sdk": minor
+---
+
+Add rework rate OTEL metrics (#265) — tracks PR revision patterns as the emerging 5th DORA metric

.changeset/add-session-recovery-skill.md

@@ -0,0 +1,4 @@
+---
+---
+
+Add session-recovery skill for detecting and resuming interrupted Copilot CLI sessions

.changeset/add-skill-script-loader.md

@@ -0,0 +1,5 @@
+---
+"@bradygaster/squad-sdk": minor
+---
+
+Add SkillScriptLoader, handler types, and applySkillHandlers for executable skill handler scripts

.changeset/ado-configurable-items.md

@@ -0,0 +1,14 @@
+---
+"@bradygaster/squad-sdk": minor
+---
+
+ADO configurable work item types, area paths, and iteration support (#240)
+
+- Add `getAvailableWorkItemTypes(org, project)` for process template introspection
+- Add `validateWorkItemType(org, project, typeName)` for pre-creation validation
+- Add `WorkItemTypeInfo` interface for type metadata
+- Enhance `AzureDevOpsAdapter` with instance-level `getAvailableWorkItemTypes()` and `validateWorkItemType()` methods
+- Support optional `validateType` flag in `createWorkItem()` to check type before creation
+- Enhance `squad init` to introspect available work item types and store `_availableTypes` hint in `.squad/config.json`
+- Support `adoConfig` in `InitOptions` for explicit work item type, area path, and iteration path during init
+- Graceful fallback to default types (User Story, Bug, Task) when az CLI is unavailable

.changeset/config.json

@@ -5,7 +5,7 @@
   "fixed": [],
   "linked": [],
   "access": "public",
-  "baseBranch": "main",
+  "baseBranch": "dev",
   "updateInternalDependencies": "patch",
   "ignore": []
 }

.changeset/cooperative-rate-limiting.md

@@ -0,0 +1,11 @@
+---
+"@bradygaster/squad-sdk": minor
+---
+
+feat: Cooperative rate limiting with predictive circuit breaker
+
+Added cooperative rate limiting patterns for multi-agent deployments:
+- Traffic Light, Predictive Circuit Breaker, Priority Retry Windows
+- Cooperative Token Pool for shared quota management
+
+Closes #515

.changeset/cross-squad-orchestration.md

@@ -0,0 +1,6 @@
+---
+"@bradygaster/squad-sdk": minor
+"@bradygaster/squad-cli": minor
+---
+
+Cross-squad orchestration — discovery, delegation, and manifest (#316). Adds manifest schema, `squad discover` / `squad delegate` commands, and runtime module for coordinating work across multiple Squad instances.

.changeset/fix-readme-migration-guide-link.md

@@ -0,0 +1,5 @@
+---
+"@bradygaster/squad-cli": patch
+---
+
+docs: point README migration guide links to the published docs site

.changeset/keda-scaler-docs.md

@@ -0,0 +1,10 @@
+---
+"@bradygaster/squad-cli": patch
+---
+
+docs: Add KEDA external scaler template for GitHub issue-driven autoscaling
+
+New template documenting how to use keda-copilot-scaler for scaling
+agent pods to zero when idle, with rate-limit-aware polling.
+
+Closes #516

.changeset/machine-capability-routing.md

@@ -0,0 +1,15 @@
+---
+"@bradygaster/squad-sdk": minor
+"@bradygaster/squad-cli": minor
+---
+
+feat: Machine capability discovery and `needs:*` label-based issue routing
+
+Added capability filtering to Ralph's watch command. Issues with `needs:*` labels
+(e.g., `needs:gpu`, `needs:browser`) are only processed by Ralph instances whose
+machine has those capabilities declared in `machine-capabilities.json`.
+
+This enables multi-machine Squad deployments where different machines handle
+different types of work based on their available tooling.
+
+Closes #514

.changeset/persistent-ralph.md

@@ -0,0 +1,11 @@
+---
+'@bradygaster/squad-sdk': minor
+'@bradygaster/squad-cli': minor
+---
+
+Enable persistent Ralph — heartbeat cron + healthCheck timer
+
+- Enable cron schedule in squad-heartbeat.yml (all 5 sync locations)
+- Enable RalphMonitor healthCheck timer (previously commented out pre-migration)
+- Add platform detection tests for getRalphScanCommands (GitHub/ADO/Planner)
+- Add healthCheck timer tests with fake timers (start/stop/interval/stale detection)

.changeset/sdk-parity-batch2-tests.md

@@ -0,0 +1,5 @@
+---
+"@bradygaster/squad-sdk": patch
+---
+
+Add SDK feature parity batch 2 — 64 tests covering manual ceremonies (#27), ceremony cooldown (#28), human team members (#36), constraint budget enforcement (#49 — rate limiter, file-write guards, shell restrictions, PII scrubbing), multi-agent artifact coordination (#50), and builder validation edge cases.

.changeset/sdk-parity-batch3-tests.md

@@ -0,0 +1,11 @@
+---
+"@bradygaster/squad-sdk": patch
+---
+
+test: SDK feature parity batch 3 — 46 tests for #31, #47, #45, #46
+
+Adds 46 automated tests covering 4 SDK features from the #341 parity matrix:
+- RalphMonitor idle-watch mode (#31): construction, event handling, stale session detection
+- Platform detection (#47): GitHub/Azure DevOps URL parsing, detectPlatformFromUrl
+- Reviewer lockout (#45): rejection protocol, per-artifact scope, persistence
+- Deadlock handling (#46): all-agents-locked detection, clearLockout escalation, recovery

.changeset/squad-scheduler.md

@@ -0,0 +1,6 @@
+---
+"@bradygaster/squad-sdk": minor
+"@bradygaster/squad-cli": minor
+---
+
+Generic, provider-agnostic scheduler for Squad (#296) — unified schedule.json manifest with LocalPolling and GitHubActions provider adapters, CLI commands (list, run, init, status), schema validation, and cron/interval trigger evaluation.

.copilot/skills/agent-collaboration/SKILL.md

@@ -0,0 +1,42 @@
+---
+name: "agent-collaboration"
+description: "Standard collaboration patterns for all squad agents — worktree awareness, decisions, cross-agent communication"
+domain: "team-workflow"
+confidence: "high"
+source: "extracted from charter boilerplate — identical content in 18+ agent charters"
+---
+
+## Context
+
+Every agent on the team follows identical collaboration patterns for worktree awareness, decision recording, and cross-agent communication. These were previously duplicated in every charter's Collaboration section (~300 bytes × 18 agents = ~5.4KB of redundant context). Now centralized here.
+
+The coordinator's spawn prompt already instructs agents to read decisions.md and their history.md. This skill adds the patterns for WRITING decisions and requesting help.
+
+## Patterns
+
+### Worktree Awareness
+Use the `TEAM ROOT` path provided in your spawn prompt. All `.squad/` paths are relative to this root. If TEAM ROOT is not provided (rare), run `git rev-parse --show-toplevel` as fallback. Never assume CWD is the repo root.
+
+### Decision Recording
+After making a decision that affects other team members, write it to:
+`.squad/decisions/inbox/{your-name}-{brief-slug}.md`
+
+Format:
+```
+### {date}: {decision title}
+**By:** {Your Name}
+**What:** {the decision}
+**Why:** {rationale}
+```
+
+### Cross-Agent Communication
+If you need another team member's input, say so in your response. The coordinator will bring them in. Don't try to do work outside your domain.
+
+### Reviewer Protocol
+If you have reviewer authority and reject work: the original author is locked out from revising that artifact. A different agent must own the revision. State who should revise in your rejection response.
+
+## Anti-Patterns
+- Don't read all agent charters — you only need your own context + decisions.md
+- Don't write directly to `.squad/decisions.md` — always use the inbox drop-box
+- Don't modify other agents' history.md files — that's Scribe's job
+- Don't assume CWD is the repo root — always use TEAM ROOT

.copilot/skills/agent-conduct/SKILL.md

@@ -0,0 +1,24 @@
+---
+name: "agent-conduct"
+description: "Shared hard rules enforced across all squad agents"
+domain: "team-governance"
+confidence: "high"
+source: "reskill extraction — Product Isolation Rule and Peer Quality Check appeared in all 20 agent charters"
+---
+
+## Context
+
+Every squad agent must follow these two hard rules. They were previously duplicated in every charter. Now they live here as a shared skill, loaded once.
+
+## Patterns
+
+### Product Isolation Rule (hard rule)
+Tests, CI workflows, and product code must NEVER depend on specific agent names from any particular squad. "Our squad" must not impact "the squad." No hardcoded references to agent names (Flight, EECOM, FIDO, etc.) in test assertions, CI configs, or product logic. Use generic/parameterized values. If a test needs agent names, use obviously-fake test fixtures (e.g., "test-agent-1", "TestBot").
+
+### Peer Quality Check (hard rule)
+Before finishing work, verify your changes don't break existing tests. Run the test suite for files you touched. If CI has been failing, check your changes aren't contributing to the problem. When you learn from mistakes, update your history.md.
+
+## Anti-Patterns
+- Don't hardcode dev team agent names in product code or tests
+- Don't skip test verification before declaring work done
+- Don't ignore pre-existing CI failures that your changes may worsen

.copilot/skills/ci-validation-gates/SKILL.md

@@ -0,0 +1,84 @@
+---
+name: "ci-validation-gates"
+description: "Defensive CI/CD patterns: semver validation, token checks, retry logic, draft detection — earned from v0.8.22"
+domain: "ci-cd"
+confidence: "high"
+source: "extracted from Drucker and Trejo charters — earned knowledge from v0.8.22 release incident"
+---
+
+## Context
+
+CI workflows must be defensive. These patterns were learned from the v0.8.22 release disaster where invalid semver, wrong token types, missing retry logic, and draft releases caused a multi-hour outage. Both Drucker (CI/CD) and Trejo (Release Manager) carried this knowledge in their charters — now centralized here.
+
+## Patterns
+
+### Semver Validation Gate
+Every publish workflow MUST validate version format before `npm publish`. 4-part versions (e.g., 0.8.21.4) are NOT valid semver — npm mangles them.
+
+```yaml
+- name: Validate semver
+  run: |
+    VERSION="${{ github.event.release.tag_name }}"
+    VERSION="${VERSION#v}"
+    if ! npx semver "$VERSION" > /dev/null 2>&1; then
+      echo "❌ Invalid semver: $VERSION"
+      echo "Only 3-part versions (X.Y.Z) or prerelease (X.Y.Z-tag.N) are valid."
+      exit 1
+    fi
+    echo "✅ Valid semver: $VERSION"
+```
+
+### NPM Token Type Verification
+NPM_TOKEN MUST be an Automation token, not a User token with 2FA:
+- User tokens require OTP — CI can't provide it → EOTP error
+- Create Automation tokens at npmjs.com → Settings → Access Tokens → Automation
+- Verify before first publish in any workflow
+
+### Retry Logic for npm Registry Propagation
+npm registry uses eventual consistency. After `npm publish` succeeds, the package may not be immediately queryable.
+- Propagation: typically 5-30s, up to 2min in rare cases
+- All verify steps: 5 attempts, 15-second intervals
+- Log each attempt: "Attempt 1/5: Checking package..."
+- Exit loop on success, fail after max attempts
+
+```yaml
+- name: Verify package (with retry)
+  run: |
+    MAX_ATTEMPTS=5
+    WAIT_SECONDS=15
+    for attempt in $(seq 1 $MAX_ATTEMPTS); do
+      echo "Attempt $attempt/$MAX_ATTEMPTS: Checking $PACKAGE@$VERSION..."
+      if npm view "$PACKAGE@$VERSION" version > /dev/null 2>&1; then
+        echo "✅ Package verified"
+        exit 0
+      fi
+      [ $attempt -lt $MAX_ATTEMPTS ] && sleep $WAIT_SECONDS
+    done
+    echo "❌ Failed to verify after $MAX_ATTEMPTS attempts"
+    exit 1
+```
+
+### Draft Release Detection
+Draft releases don't emit `release: published` event. Workflows MUST:
+- Trigger on `release: published` (NOT `created`)
+- If using workflow_dispatch: verify release is published via GitHub API before proceeding
+
+### Build Script Protection
+Set `SKIP_BUILD_BUMP=1` (or `$env:SKIP_BUILD_BUMP = "1"` on Windows) before ANY release build. bump-build.mjs is for dev builds ONLY — it silently mutates versions.
+
+## Known Failure Modes (v0.8.22 Incident)
+
+| # | What Happened | Root Cause | Prevention |
+|---|---------------|-----------|------------|
+| 1 | 4-part version published, npm mangled it | No semver validation gate | `npx semver` check before every publish |
+| 2 | CI failed 5+ times with EOTP | User token with 2FA | Automation token only |
+| 3 | Verify returned false 404 | No retry logic for propagation | 5 attempts, 15s intervals |
+| 4 | Workflow never triggered | Draft release doesn't emit event | Never create draft releases |
+| 5 | Version mutated during release | bump-build.mjs ran in release | SKIP_BUILD_BUMP=1 |
+
+## Anti-Patterns
+- ❌ Publishing without semver validation gate
+- ❌ Single-shot verification without retry
+- ❌ Hard-coded secrets in workflows
+- ❌ Silent CI failures — every error needs actionable output with remediation
+- ❌ Assuming npm publish is instantly queryable