@bradygaster/squad-sdk 0.9.0 → 0.9.2-insider.1

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@bradygaster/squad-sdk",
-  "version": "0.9.0",
+  "version": "0.9.2-insider.1",
   "description": "Squad SDK — Programmable multi-agent runtime for GitHub Copilot",
   "type": "module",
   "main": "./dist/index.js",
@@ -185,6 +185,34 @@
     "./config/models": {
       "types": "./dist/config/models.d.ts",
       "import": "./dist/config/models.js"
+    },
+    "./storage": {
+      "types": "./dist/storage/index.d.ts",
+      "import": "./dist/storage/index.js"
+    },
+    "./platform": {
+      "types": "./dist/platform/index.d.ts",
+      "import": "./dist/platform/index.js"
+    },
+    "./remote": {
+      "types": "./dist/remote/index.d.ts",
+      "import": "./dist/remote/index.js"
+    },
+    "./roles": {
+      "types": "./dist/roles/index.d.ts",
+      "import": "./dist/roles/index.js"
+    },
+    "./state": {
+      "types": "./dist/state/index.d.ts",
+      "import": "./dist/state/index.js"
+    },
+    "./streams": {
+      "types": "./dist/streams/index.d.ts",
+      "import": "./dist/streams/index.js"
+    },
+    "./upstream": {
+      "types": "./dist/upstream/index.d.ts",
+      "import": "./dist/upstream/index.js"
     }
   },
   "files": [
@@ -213,11 +241,15 @@
     "@opentelemetry/sdk-trace-base": "^1.30.0",
     "@opentelemetry/sdk-trace-node": "^1.30.0",
     "@opentelemetry/semantic-conventions": "^1.28.0",
+    "sql.js": "^1.14.1",
     "ws": "^8.18.0"
   },
   "devDependencies": {
     "@types/node": "^22.0.0",
+    "@types/sql.js": "^1.4.10",
     "@types/ws": "^8.5.13",
+    "typedoc": "~0.28.18",
+    "typedoc-plugin-markdown": "~4.11.0",
     "typescript": "^5.7.0"
   },
   "keywords": [

package/templates/scribe-charter.md

@@ -15,6 +15,10 @@
 - `.squad/decisions.md` — the shared decision log all agents read (canonical, merged)
 - `.squad/decisions/inbox/` — decision drop-box (agents write here, I merge)
 - Cross-agent context propagation — when one agent's decision affects another
+- Decision archival — **HARD GATE**: enforce two-tier ceiling on decisions.md before every merge:
+  - **Tier 1 (30-day):** If >20KB, archive entries older than 30 days
+  - **Tier 2 (7-day):** If still >50KB after Tier 1, archive entries older than 7 days
+  - Emit HEALTH REPORT to session log after archival runs
 
 ## How I Work
 

package/templates/skills/cross-machine-coordination/SKILL.md

@@ -0,0 +1,434 @@
+# Skill: Cross-Machine Coordination Pattern
+
+**Skill ID:** `cross-machine-coordination`  
+**Owner:** Ralph (Work Monitor)  
+**Squad Integration:** All agents  
+**Status:** Specification (ready for implementation)  
+
+---
+
+## Overview
+
+Enables squad agents running on different machines (laptop, DevBox, Azure VM) to securely share work, coordinate execution, and pass results without manual intervention.
+
+**Pattern:** Git-based task queuing + GitHub Issues supplement
+
+---
+
+## Usage
+
+### For Task Sources (Orchestrating Machine)
+
+**To assign work to DevBox:**
+
+```bash
+# Create task file
+cat > .squad/cross-machine/tasks/2026-03-14T1530Z-laptop-gpu-voice-clone.yaml << 'EOF'
+id: gpu-voice-clone-001
+source_machine: laptop-machine
+target_machine: devbox
+priority: high
+created_at: 2026-03-14T15:30:00Z
+task_type: gpu_workload
+payload:
+  command: "python scripts/voice-clone.py --input voice.wav --output cloned.wav"
+  expected_duration_min: 15
+  resources:
+    gpu: true
+    memory_gb: 8
+status: pending
+EOF
+
+# Commit & push
+git add .squad/cross-machine/tasks/
+git commit -m "Cross-machine task: GPU voice cloning [squad:machine-devbox]"
+git push origin main
+```
+
+Ralph on DevBox will:
+1. Pull the task on next cycle (5-10 min)
+2. Validate schema & command whitelist
+3. Execute the GPU workload
+4. Write result to `.squad/cross-machine/results/gpu-voice-clone-001.yaml`
+5. Commit & push the result
+
+---
+
+### For Task Executors (DevBox, Azure VMs)
+
+Ralph automatically watches `.squad/cross-machine/tasks/` for work targeted at this machine.
+
+**On each cycle (5-10 min):**
+
+```python
+# Pseudo-code (Ralph implementation)
+1. git pull origin main
+2. Load all .yaml files in .squad/cross-machine/tasks/
+3. Filter for status=pending AND target_machine=HOSTNAME
+4. For each task:
+   a. Validate schema (must have: id, source_machine, target_machine, payload)
+   b. Validate command against whitelist
+   c. Execute task (with timeout)
+   d. Write result to .squad/cross-machine/results/{id}.yaml
+   e. Commit & push result
+```
+
+---
+
+### For Urgent/Ad-Hoc Tasks
+
+**Use GitHub Issues with `squad:machine-{name}` label:**
+
+```bash
+# Create issue
+gh issue create \
+  --title "GPU: Clone voice profile from sample.wav" \
+  --body "Execute voice cloning on DevBox. Input: /path/to/voice-input.wav" \
+  --label "squad:machine-devbox" \
+  --label "urgent"
+```
+
+Ralph on DevBox will:
+1. Detect issue with `squad:machine-devbox` label
+2. Parse task from issue body
+3. Execute task
+4. Comment with result
+5. Close issue
+
+---
+
+## File Formats
+
+### Task File (YAML)
+
+**Location:** `.squad/cross-machine/tasks/{timestamp}-{machine}-{task-id}.yaml`
+
+**Required Fields:**
+```yaml
+id: {task-id}                      # Unique identifier (alphanumeric + dash)
+source_machine: {hostname}         # Where task was created
+target_machine: {hostname}         # Where task will execute
+priority: high|normal|low          # Execution priority
+created_at: 2026-03-14T15:30:00Z   # ISO 8601 timestamp
+task_type: gpu_workload|script|... # Category
+payload:
+  command: "..."                   # Shell command to execute
+  expected_duration_min: 15        # Timeout (minutes)
+  resources:
+    gpu: true|false
+    memory_gb: 8
+    cpu_cores: 4
+status: pending|executing|completed|failed
+```
+
+**Optional Fields:**
+```yaml
+description: "Human-readable task description"
+timeout_override_min: 120          # Override default timeout
+retry_count: 3                     # Retry failed tasks
+```
+
+### Result File (YAML)
+
+**Location:** `.squad/cross-machine/results/{task-id}.yaml`
+
+```yaml
+id: {task-id}                          # Links back to task
+target_machine: devbox                 # Executed on
+completed_at: 2026-03-14T15:45:00Z    # When it finished
+status: completed|failed|timeout       # Outcome
+exit_code: 0                           # Shell exit code
+stdout: "..."                          # Captured output
+stderr: "..."                          # Captured errors
+duration_seconds: 900                  # How long it took
+artifacts:
+  - path: "/path/to/artifacts/..."   # Location of results
+    type: audio|text|model|...
+    size_mb: 2.5
+```
+
+---
+
+## Security Model
+
+### Validation Pipeline
+
+All tasks go through:
+
+1. **Schema Validation**
+   - YAML structure matches spec
+   - Required fields present
+   - No unexpected fields (reject)
+
+2. **Command Whitelist**
+   - Only approved commands allowed
+   - Path validation (no `../../` escapes)
+   - Environment variable sanitization
+   - No inline shell operators (`&&`, `|`, `>`)
+
+3. **Resource Limits**
+   - Timeout enforced (default: 60 min)
+   - Memory cap: 16GB (adjustable)
+   - CPU threads: 4 (adjustable)
+   - Disk write: 100GB (adjustable)
+
+4. **Execution Isolation**
+   - Runs as unprivileged user
+   - Temp directory cleaned after execution
+   - Network access: read-only (no outbound writes)
+
+5. **Audit Trail**
+   - All executions logged to git
+   - Commit signed with Ralph's key
+   - Result stored immutably
+
+### Threat Mitigations
+
+| Threat | Mitigation |
+|--------|-----------|
+| **Malicious task injection** | Branch protection + PR review before merge |
+| **Credential leakage** | Pre-commit secret scan + environment scrubbing |
+| **Resource exhaustion** | Timeout + memory limits |
+| **Code injection** | Command whitelist + no shell evaluation |
+| **Result tampering** | Git commit history is immutable |
+
+---
+
+## Configuration
+
+Ralph reads config from `.squad/config.json`:
+
+```json
+{
+  "cross_machine": {
+    "enabled": true,
+    "poll_interval_seconds": 300,
+    "this_machine": "devbox",
+    "max_concurrent_tasks": 2,
+    "task_timeout_minutes": 60,
+    "command_whitelist": [
+      "python scripts/voice-clone.py",
+      "python scripts/data-process.py",
+      "bash scripts/cleanup.sh"
+    ],
+    "result_ttl_days": 30
+  }
+}
+```
+
+---
+
+## Examples
+
+### Example 1: GPU Voice Cloning (Laptop → DevBox)
+
+**1. Laptop creates task:**
+
+```yaml
+# .squad/cross-machine/tasks/2026-03-14T1530Z-laptop-gpu-001.yaml
+id: gpu-voice-clone-001
+source_machine: laptop-machine
+target_machine: devbox
+priority: high
+created_at: 2026-03-14T15:30:00Z
+task_type: gpu_workload
+payload:
+  command: "python scripts/voice-clone.py --input voice.wav --output cloned.wav"
+  expected_duration_min: 15
+  resources:
+    gpu: true
+    memory_gb: 8
+status: pending
+```
+
+**2. Laptop commits & pushes:**
+
+```bash
+git add .squad/cross-machine/tasks/
+git commit -m "Task: GPU voice cloning [squad:machine-devbox]"
+git push origin main
+```
+
+**3. DevBox Ralph (5 min later):**
+
+```
+[Ralph Watch Cycle]
+- Pulled origin/main
+- Detected: gpu-voice-clone-001 (status: pending, target: devbox)
+- Validation: ✅ Schema OK, command whitelisted
+- Executing: python scripts/voice-clone.py ...
+- [15 minutes of processing]
+- Completed: exit code 0
+- Writing result...
+- Committing & pushing...
+```
+
+**4. Laptop Ralph (next cycle) sees result:**
+
+```yaml
+# .squad/cross-machine/results/gpu-voice-clone-001.yaml
+id: gpu-voice-clone-001
+target_machine: devbox
+completed_at: 2026-03-14T15:45:00Z
+status: completed
+exit_code: 0
+stdout: "Voice cloning completed. Output written to /tmp/cloned.wav"
+stderr: ""
+duration_seconds: 900
+artifacts:
+  - path: "/path/to/artifacts/voice-clone-001/output.wav"
+    type: audio
+    size_mb: 2.5
+```
+
+---
+
+### Example 2: Urgent Debug Request (Human → DevBox via Issue)
+
+**Create issue:**
+
+```bash
+gh issue create \
+  --title "DevBox: Debug voice model failure" \
+  --body "Error: Model failed to load on last run. Please check /tmp/model.log and report findings." \
+  --label "squad:machine-devbox" \
+  --label "urgent"
+```
+
+**DevBox Ralph detects → executes → comments:**
+
+```
+✅ Executed on devbox at 2026-03-14 15:47:00
+Command: python scripts/debug-model.py
+
+Result:
+------
+Model file: /tmp/model-v2.bin (OK)
+Checksum: a1b2c3d4e5f6 (matches expected)
+Memory available: 12 GB (sufficient)
+
+ERROR FOUND: Config file permission issue
+  - File: ~/.config/voice/model.yaml
+  - Permissions: -rw------- (owner-only)
+  - Expected: -rw-r--r-- (world-readable for service)
+
+FIX: Run: chmod 644 ~/.config/voice/model.yaml
+```
+
+---
+
+## Error Handling
+
+### Task Execution Failures
+
+If a task fails (exit code != 0):
+
+1. Result written with `status: failed` + exit code
+2. stderr captured in result
+3. Committed to git for audit
+4. Source machine can retry by re-pushing task with `status: pending`
+
+### Stalled Tasks
+
+If a task doesn't complete within timeout:
+
+1. Process killed
+2. Result written with `status: timeout`
+3. stderr: "Execution exceeded X minutes"
+4. Source can investigate or retry
+
+### Network Failures
+
+If git push/pull fails:
+
+- Ralph retries on next cycle
+- Tasks queue locally until connectivity restored
+- No tasks lost (stored in local repo)
+
+---
+
+## Monitoring & Debugging
+
+### Check Task Queue
+
+```bash
+ls -la .squad/cross-machine/tasks/
+cat .squad/cross-machine/tasks/*.yaml | grep -E "^(id|status|target_machine):"
+```
+
+### Check Results
+
+```bash
+ls -la .squad/cross-machine/results/
+cat .squad/cross-machine/results/{task-id}.yaml
+```
+
+### View Execution History
+
+```bash
+git log --oneline .squad/cross-machine/ | head -20
+```
+
+### Monitor Ralph Cycles
+
+```bash
+tail -f .squad/log/ralph-watch.log | grep "cross-machine"
+```
+
+---
+
+## Integration with Ralph Watch
+
+Ralph automatically includes this pattern in its watch loop:
+
+```
+Ralph Watch Cycle (every 5-10 min):
+1. Fetch GitHub issues with squad:machine-* labels
+2. Poll .squad/cross-machine/tasks/
+3. For each matching task:
+   - Validate
+   - Execute
+   - Write result
+   - Commit & push
+4. Update status in issue (if applicable)
+5. Sleep until next cycle
+```
+
+No manual Ralph configuration needed — just create task files or issues with the right labels.
+
+---
+
+## Migration from Manual Handoff
+
+**Before (today):**
+- Laptop → user manually copies file to Teams chat
+- user pastes into target terminal
+- user copies output back
+- user pastes result manually
+
+**After (with this pattern):**
+- Laptop Ralph writes task file → git push
+- DevBox Ralph auto-executes → git push result
+- Laptop Ralph auto-reads result
+- 0 human intervention needed
+
+---
+
+## Future Enhancements
+
+Potential expansions (Phase 2+):
+
+1. **Task Priorities:** Execution order based on priority field
+2. **Serial Pipelines:** Machine A → B → C task chains
+3. **GPU Availability Polling:** Query DevBox before submitting work
+4. **Cost Tracking:** Log resource usage per task
+5. **Notification Webhooks:** Alert on task completion
+6. **Web Dashboard:** Real-time task status visualization
+
+---
+
+## Questions?
+
+Refer to research report: `research/active/cross-machine-agents/README.md`
+
+Contact: Seven (Research & Docs) or Ralph (Work Monitor)

package/templates/skills/error-recovery/SKILL.md

@@ -0,0 +1,99 @@
+---
+name: "error-recovery"
+description: "Standard recovery patterns for all squad agents. When something fails, adapt — don't just report the failure."
+domain: "reliability, agent-coordination"
+confidence: "high"
+license: MIT
+---
+
+# Error Recovery Patterns
+
+Standard recovery patterns for all squad agents. When something fails, **adapt** — don't just report the failure.
+
+---
+
+## 1. Retry with Backoff
+
+**When:** Transient failures — API timeouts, rate limits, network errors, temporary service unavailability.
+
+**Pattern:**
+1. Wait briefly, then retry (start at 2s, double each attempt)
+2. Maximum 3 retries before escalating
+3. Log each attempt with the error received
+
+**Example:** API call returns 429 Too Many Requests → wait 2s → retry → wait 4s → retry → wait 8s → retry → escalate if still failing.
+
+---
+
+## 2. Fallback Alternatives
+
+**When:** Primary tool or approach fails and an alternative exists.
+
+**Pattern:**
+1. Attempt primary approach
+2. On failure, identify alternative tool/method
+3. Try the alternative with the same intent
+4. Document which alternative was used and why
+
+**Example:** Primary CLI tool fails → fall back to direct API call for the same operation.
+
+---
+
+## 3. Diagnose-and-Fix
+
+**When:** Build failures, test failures, linting errors — structured errors with actionable output.
+
+**Pattern:**
+1. Read the full error output carefully
+2. Identify the root cause from error messages
+3. Attempt a targeted fix
+4. Re-run to verify the fix
+5. Maximum 3 fix-retry cycles before escalating
+
+**Example:** Build fails with a type error → check for missing import → add it → rebuild.
+
+---
+
+## 4. Escalate with Context
+
+**When:** Recovery attempts have been exhausted, or the failure requires human judgment.
+
+**Pattern:**
+1. Summarize what was attempted and what failed
+2. Include the exact error messages
+3. State what you believe the root cause is
+4. Suggest next steps or who might be able to help
+5. Hand off to the coordinator or the appropriate specialist
+
+**Example:** After 3 failed build attempts → "Build fails on line 42 with null reference. Tried X, Y, Z. Likely a design issue in the Foo module. Recommend the code owner review."
+
+---
+
+## 5. Graceful Degradation
+
+**When:** A non-critical step fails but the overall task can still deliver value.
+
+**Pattern:**
+1. Determine if the failed step is critical to the task outcome
+2. If non-critical, log the failure and continue
+3. Deliver partial results with a clear note of what was skipped
+4. Offer to retry the skipped step separately
+
+**Example:** Generating a report with 5 sections — section 3 data source is unavailable → produce the report with 4 sections, note that section 3 was skipped and why.
+
+---
+
+## Applying These Patterns
+
+Each agent should reference these patterns in their charter's `## Error Recovery` section, tailored to their domain. The charter should list the agent's most common failure modes and map each to the appropriate pattern above.
+
+**Selection guide:**
+
+| Failure Type | Primary Pattern | Fallback Pattern |
+|---|---|---|
+| Network/API transient | Retry with Backoff | Escalate with Context |
+| Tool/dependency missing | Fallback Alternatives | Escalate with Context |
+| Build/test error | Diagnose-and-Fix | Escalate with Context |
+| Auth/permissions | Retry with Backoff | Escalate with Context |
+| Non-critical data missing | Graceful Degradation | — |
+| Unknown/novel error | Escalate with Context | — |