taskbrew 1.0.0__tar.gz

taskbrew-1.0.0/.env.example

@@ -0,0 +1,17 @@
+# Required — at least one provider API key
+ANTHROPIC_API_KEY=your-anthropic-api-key-here
+
+# Optional — Gemini provider
+GOOGLE_API_KEY=your-google-api-key-here
+
+# Optional — Server
+AI_TEAM_API_URL=http://127.0.0.1:8420
+AI_TEAM_DB_PATH=~/.ai-team/data/ai-team.db
+
+# Optional — Logging
+LOG_LEVEL=INFO
+LOG_FORMAT=dev
+
+# Optional — Auth
+AUTH_ENABLED=false
+CORS_ORIGINS=http://localhost:8000,http://localhost:3000

taskbrew-1.0.0/.githooks/pre-commit

@@ -0,0 +1,79 @@
+#!/usr/bin/env bash
+# .githooks/pre-commit
+# =====================================================================
+# Validates that commits are made to the correct task branch.
+#
+# This hook prevents commits with the wrong task ID from being created,
+# catching contamination at the source before it reaches the repository.
+#
+# Exit codes:
+#   0 = PASS - commit task matches branch task
+#   1 = FAIL - commit task doesn't match branch task (abort commit)
+# =====================================================================
+
+set -euo pipefail
+
+# Get current branch
+BRANCH=$(git rev-parse --abbrev-ref HEAD 2>/dev/null || echo "")
+
+# Early exit if not on a feature branch (e.g., on main, in detached state)
+if [[ ! "$BRANCH" =~ ^feat/ ]]; then
+    exit 0
+fi
+
+# Extract task ID from branch name
+# Examples: feat/rv-220 → RV-220, feat/cd-088 → CD-088
+BRANCH_TASK=$(echo "$BRANCH" | sed -E 's/feat\/([a-z]+-[0-9]+).*/\1/' | tr '[:lower:]' '[:upper:]')
+if [ "$BRANCH_TASK" = "$BRANCH" ]; then
+    BRANCH_TASK=""
+fi
+
+# Get the commit message being staged
+COMMIT_MSG_FILE="${1:-}"
+if [ -z "$COMMIT_MSG_FILE" ] || [ ! -f "$COMMIT_MSG_FILE" ]; then
+    exit 0
+fi
+
+COMMIT_MSG=$(cat "$COMMIT_MSG_FILE")
+
+# Extract task ID from commit message
+# Looking for pattern like "(RV-220)" or "(CD-088)" in the message
+MSG_TASK=$(echo "$COMMIT_MSG" | grep -oE "\((CD|RV|TS|AR|DEBUG)-[0-9]+\)" | sed -E 's/[()]+//g' | head -1 || true)
+
+# If we have both task IDs, validate they match
+if [ -n "$BRANCH_TASK" ] && [ -n "$MSG_TASK" ]; then
+    if [ "$BRANCH_TASK" != "$MSG_TASK" ]; then
+        cat >&2 <<EOF
+ERROR: Commit task ID mismatch
+  Branch: $BRANCH (task: $BRANCH_TASK)
+  Commit: $MSG_TASK
+
+Each feature branch must contain commits for only one task.
+Update your commit message to use the correct task ID: ($BRANCH_TASK)
+
+Current message:
+  $COMMIT_MSG
+
+Expected format:
+  $BRANCH_TASK message here ($(echo $BRANCH_TASK | cut -d- -f1)-NNN)
+
+EOF
+        exit 1
+    fi
+elif [ -n "$BRANCH_TASK" ] && [ -z "$MSG_TASK" ]; then
+    # Branch suggests a task but commit message doesn't mention any task
+    cat >&2 <<EOF
+WARNING: Commit message missing task ID
+  Branch: $BRANCH (task: $BRANCH_TASK)
+  Commit message has no task ID
+
+Consider adding the task ID to your commit message: ($BRANCH_TASK)
+
+Current message:
+  $COMMIT_MSG
+
+EOF
+    # This is a warning, not a hard error - let it pass
+fi
+
+exit 0

taskbrew-1.0.0/.githooks/pre-merge-commit

@@ -0,0 +1,115 @@
+#!/usr/bin/env bash
+# .githooks/pre-merge-commit
+# -------------------------------------------------------
+# Git pre-merge-commit hook — scope-checks the inbound branch
+# before a merge lands on the current branch.
+#
+# Exit codes from scripts/check-merge-scope.sh:
+#   0 = PASS  — merge proceeds silently
+#   1 = WARN  — warning printed, merge still proceeds
+#   2 = BLOCK — merge is aborted
+#
+# This hook ONLY fires during `git merge` (the pre-merge-commit
+# hook is not invoked for normal commits).
+# -------------------------------------------------------
+
+set -euo pipefail
+
+REPO_ROOT="$(git rev-parse --show-toplevel)"
+SCOPE_SCRIPT="${REPO_ROOT}/scripts/check-merge-scope.sh"
+
+# ------------------------------------------------------------------
+# 1. Detect the branch being merged
+# ------------------------------------------------------------------
+# During a merge, MERGE_HEAD contains the tip commit of the branch
+# being merged. We resolve it back to a branch name.
+# ------------------------------------------------------------------
+GIT_DIR="$(git rev-parse --git-dir)"
+MERGE_HEAD_FILE="${GIT_DIR}/MERGE_HEAD"
+
+if [ ! -f "${MERGE_HEAD_FILE}" ]; then
+    # No MERGE_HEAD means this isn't a merge — nothing to check.
+    # (Defensive guard; pre-merge-commit shouldn't fire otherwise.)
+    exit 0
+fi
+
+MERGE_SHA="$(cat "${MERGE_HEAD_FILE}")"
+
+# Try to resolve the SHA to a branch name.
+# `git name-rev` returns e.g. "abc1234 remotes/origin/feature/foo" or "abc1234 feature/foo"
+BRANCH_NAME="$(git name-rev --name-only --refs='refs/heads/*' "${MERGE_SHA}" 2>/dev/null || true)"
+
+# If name-rev couldn't resolve against local branches, try remote tracking branches
+if [ -z "${BRANCH_NAME}" ] || [ "${BRANCH_NAME}" = "undefined" ]; then
+    BRANCH_NAME="$(git name-rev --name-only --refs='refs/remotes/*' "${MERGE_SHA}" 2>/dev/null || true)"
+    # Strip the leading "remotes/origin/" prefix if present
+    BRANCH_NAME="${BRANCH_NAME#remotes/origin/}"
+    BRANCH_NAME="${BRANCH_NAME#remotes/*/}"
+fi
+
+# Fallback: parse GIT_REFLOG_ACTION (set by git during merge)
+# Typically: "merge <branch-name>" or "merge origin/<branch-name>"
+if [ -z "${BRANCH_NAME}" ] || [ "${BRANCH_NAME}" = "undefined" ]; then
+    if [ -n "${GIT_REFLOG_ACTION:-}" ]; then
+        # Extract branch name from "merge <branch>" pattern
+        BRANCH_NAME="$(echo "${GIT_REFLOG_ACTION}" | sed -n 's/^merge \(.*\)/\1/p')"
+    fi
+fi
+
+# Last resort: use the raw SHA (the scope script can still count commits)
+if [ -z "${BRANCH_NAME}" ] || [ "${BRANCH_NAME}" = "undefined" ]; then
+    BRANCH_NAME="${MERGE_SHA}"
+fi
+
+# ------------------------------------------------------------------
+# 2. Verify the scope-check script exists
+# ------------------------------------------------------------------
+if [ ! -x "${SCOPE_SCRIPT}" ]; then
+    echo "pre-merge-commit: WARNING — scope-check script not found or not executable:"
+    echo "  ${SCOPE_SCRIPT}"
+    echo "Skipping pre-merge scope validation. Run 'make setup-hooks' to verify setup."
+    exit 0
+fi
+
+# ------------------------------------------------------------------
+# 3. Run the scope check
+# ------------------------------------------------------------------
+echo "pre-merge-commit: checking merge scope for '${BRANCH_NAME}' ..."
+
+set +e
+"${SCOPE_SCRIPT}" "${BRANCH_NAME}"
+EXIT_CODE=$?
+set -e
+
+case ${EXIT_CODE} in
+    0)
+        # PASS — proceed silently
+        ;;
+    1)
+        # WARN — message already printed by the script; allow merge
+        echo "pre-merge-commit: scope warning detected (see above). Merge will proceed."
+        ;;
+    2)
+        # BLOCK — abort the merge
+        echo ""
+        echo "============================================================"
+        echo "  MERGE BLOCKED by pre-merge scope check"
+        echo "  Branch: ${BRANCH_NAME}"
+        echo "============================================================"
+        echo ""
+        echo "The inbound branch exceeds the allowed commit-count threshold."
+        echo "Please rebase or split the branch before merging."
+        echo ""
+        echo "To bypass this check (use with caution):"
+        echo "  git merge --no-verify <branch>"
+        echo ""
+        exit 1   # non-zero exits abort the merge
+        ;;
+    *)
+        # Unexpected exit code — treat as warning, don't block
+        echo "pre-merge-commit: scope script exited with unexpected code ${EXIT_CODE}."
+        echo "Allowing merge to proceed."
+        ;;
+esac
+
+exit 0

taskbrew-1.0.0/.github/workflows/ci.yml

@@ -0,0 +1,50 @@
+name: CI
+
+on:
+  push:
+    branches: [main]
+  pull_request:
+    branches: [main]
+
+concurrency:
+  group: ${{ github.workflow }}-${{ github.ref }}
+  cancel-in-progress: true
+
+jobs:
+  test:
+    name: "CI - Python ${{ matrix.python-version }}"
+    runs-on: ubuntu-latest
+    strategy:
+      fail-fast: false
+      matrix:
+        python-version: ["3.10", "3.12"]
+
+    steps:
+      - name: Checkout repository
+        uses: actions/checkout@v4
+
+      - name: Set up Python ${{ matrix.python-version }}
+        uses: actions/setup-python@v5
+        with:
+          python-version: ${{ matrix.python-version }}
+
+      - name: Cache pip dependencies
+        uses: actions/cache@v4
+        with:
+          path: ~/.cache/pip
+          key: ${{ runner.os }}-pip-${{ matrix.python-version }}-${{ hashFiles('pyproject.toml') }}
+          restore-keys: |
+            ${{ runner.os }}-pip-${{ matrix.python-version }}-
+            ${{ runner.os }}-pip-
+
+      - name: Install dependencies
+        run: pip install -e ".[dev]"
+
+      - name: Lint with ruff
+        run: ruff check src/ tests/
+
+      - name: Run tests
+        run: pytest tests/ -x -q --no-header
+
+      - name: Security scan with bandit
+        run: bandit -r src/taskbrew/ -c pyproject.toml

taskbrew-1.0.0/.gitignore

@@ -0,0 +1,54 @@
+# Python
+__pycache__/
+*.egg-info/
+.eggs/
+dist/
+build/
+*.pyc
+*.pyo
+
+# Virtual environments
+.venv/
+env/
+
+# Data (user-specific)
+data/
+*.db
+artifacts/
+.worktrees/
+
+# IDE
+.vscode/
+.idea/
+*.swp
+*.swo
+
+# OS
+.DS_Store
+Thumbs.db
+
+# Environment
+.env
+
+# Node
+node_modules/
+
+# Coverage
+.coverage
+htmlcov/
+
+# Logs
+*.log
+
+# Claude Code
+.claude/
+
+# QA reports (internal)
+qa-reports/
+
+# Test output
+test_output*
+
+# Tool caches
+.pytest_cache/
+.ruff_cache/

taskbrew-1.0.0/ARCH-COMPLIANCE-CD153.md

@@ -0,0 +1,178 @@
+# Architecture Compliance Verification — CD-153
+
+**Task:** CD-153 — Fix feat/cd-129 architecture misalignment - ground rendering constants
+**Type:** Revision | **Priority:** High | **Group:** GRP-010
+**Date Verified:** 2026-02-25
+**Reviewer:** Coder-4
+
+---
+
+## Overview
+
+This document verifies that all architectural misalignments identified in code review **RV-176** have been resolved and that the codebase complies with the **AR-040** architecture decision for ground rendering.
+
+---
+
+## Critical Issues — Verification Status
+
+### 1. GROUND_HASH_SPACING Value Mismatch ✅ RESOLVED
+
+**Requirement:** `GROUND_HASH_SPACING = 20` (per AR-040 specification)
+
+**Verification:**
+```javascript
+// File: flappy-bird/game.js (line 9)
+const GROUND_HASH_SPACING = 20;  // px — distance between vertical hash lines in ground texture
+```
+
+**Status:** ✅ CORRECT
+**Evidence:** Value is 20, matches AR-040 specification for proper ground texture scaling
+
+---
+
+### 2. updateGround() Function Extraction ✅ RESOLVED
+
+**Requirement:** Ground offset logic extracted into dedicated `updateGround(dt)` function
+
+**Verification:**
+```javascript
+// File: flappy-bird/game.js (lines 397-401)
+function updateGround(dt) {
+    groundOffset += PIPE_SPEED * dt;
+    groundOffset = groundOffset % CANVAS_WIDTH;
+}
+```
+
+**Usage in STATE_IDLE (line 411):**
+```javascript
+case STATE_IDLE:
+    bobTimer += dt;
+    bird.y = BIRD_START_Y + Math.sin(bobTimer * BOB_FREQUENCY * Math.PI * 2) * BOB_AMPLITUDE;
+    updateGround(dt);  // ✅ Calls function
+    break;
+```
+
+**Usage in STATE_PLAYING (line 429):**
+```javascript
+case STATE_PLAYING:
+    updateBird(dt);
+    updatePipes(dt);
+    checkCollisions();
+    if (gameState !== STATE_PLAYING) break;
+    updateScore();
+    updateGround(dt);  // ✅ Calls function
+    break;
+```
+
+**Status:** ✅ CORRECT
+**Evidence:**
+- Function properly extracted with clear documentation
+- Called in both STATE_IDLE and STATE_PLAYING as required
+- Proper floating-point overflow prevention with CANVAS_WIDTH modulus
+
+---
+
+### 3. Undocumented Pipe Color Changes ✅ RESOLVED
+
+**Requirement:** Pipe color changes documented or reverted to original
+
+**Verification:**
+```javascript
+// File: flappy-bird/game.js (line 250)
+ctx.fillStyle = '#2ECC71';  // Green  ✅ Original color with clear comment
+
+// File: flappy-bird/game.js (line 259)
+ctx.fillStyle = '#27AE60'; // Darker green  ✅ Original color with clear comment
+```
+
+**Status:** ✅ CORRECT
+**Evidence:**
+- Pipe body color: `#2ECC71` (original, documented)
+- Pipe caps color: `#27AE60` (original, documented)
+- No undocumented color changes
+- Both colors have clear inline comments
+
+---
+
+### 4. GROUND_HASH_SPACING Constant Usage ✅ RESOLVED
+
+**Requirement:** All ground offset calculations use GROUND_HASH_SPACING constant consistently
+
+**Verification:**
+```javascript
+// File: flappy-bird/game.js (lines 460-461)
+const startX = -(groundOffset % GROUND_HASH_SPACING);
+for (let x = startX; x < CANVAS_WIDTH; x += GROUND_HASH_SPACING) {
+    ctx.beginPath();
+    ctx.moveTo(x, groundY + 10);
+    ctx.lineTo(x, groundY + GROUND_HEIGHT);
+    ctx.stroke();
+}
+```
+
+**Status:** ✅ CORRECT
+**Evidence:**
+- No magic numbers in ground offset calculations
+- Consistent use of GROUND_HASH_SPACING constant
+- Prevents future maintenance issues
+
+---
+
+### 5. System Files ✅ RESOLVED
+
+**Requirement:** .DS_Store files removed; added to .gitignore
+
+**Verification:**
+```bash
+$ find . -name ".DS_Store" 2>/dev/null
+(no output — no .DS_Store files found)
+```
+
+**Status:** ✅ CORRECT
+**Evidence:** No system files present in repository
+
+---
+
+## Acceptance Criteria Checklist
+
+- ✅ GROUND_HASH_SPACING = 20 in game.js
+- ✅ updateGround(dt) function extracted with proper implementation
+- ✅ All ground offset updates use the function
+- ✅ Color changes documented or reverted
+- ✅ .DS_Store removed
+- ✅ All critical constants properly defined
+
+---
+
+## Architecture Decision Reference
+
+This verification is based on the architecture decision **AR-040** which resolved the CD-097 ↔ CD-099 ground rendering conflict:
+
+**Key Decision:**
+- GROUND_HASH_SPACING: 20 (per CD-099's explicit specification rationale)
+- updateGround() function: Required for code organization and maintainability
+- Code architecture: Modern JavaScript practices (let vs var)
+
+**Reference Document:** `/flappy-bird/ARCH-DECISION-CD097-CD099-CONFLICT.md`
+
+---
+
+## Code Review Status
+
+**Previous Review:** RV-176 (identified persistent issues from RV-175)
+**Current Status:** All issues resolved and verified
+
+**Ready for:**
+- ✅ QA Verification (TS-200 baseline: 64/64 tests expected to pass)
+- ✅ Code Review
+
+---
+
+## Sign-Off
+
+**Verified By:** Coder-4
+**Verification Date:** 2026-02-25
+**Branch:** feat/cd-153
+**Status:** ✅ READY FOR QA AND REVIEW
+
+All critical architectural misalignments have been resolved. The codebase complies with AR-040 specification.

taskbrew-1.0.0/CD-164-VERIFICATION-CD-145-READY-TO-MERGE.md

@@ -0,0 +1,175 @@
+# CD-164 Verification Report: CD-145 Branching Policy Fixes Ready to Merge
+
+**Date:** 2026-02-25
+**Coder Instance:** coder-13
+**Branch:** feat/cd-164
+**Task:** CD-164 - Complete and merge branching-policy.md fixes (CD-145)
+**Status:** ✅ VERIFIED - READY FOR MERGE TO MAIN
+
+---
+
+## Executive Summary
+
+CD-145 successfully addresses all three critical issues flagged in the original RV-095 code review of CD-076. The fixes have been verified by QA (TS-226: PASSED) and all acceptance criteria are met. The branch is ready for merge to main.
+
+**Verification Results:**
+- ✅ All RV-095 issues fixed
+- ✅ QA verification passed (TS-226)
+- ✅ All artifacts in place
+- ✅ Documentation accurate and complete
+
+---
+
+## Issues Fixed - Verification Details
+
+### Issue #1: ✅ Commit Message Task ID Mismatch (CD-076)
+
+**Original Problem (RV-095):**
+- CD-076 commit message referenced wrong task ID (CD-060 instead of CD-076)
+- Violates commit message convention
+
+**Fix Applied (CD-145):**
+- Commit c3986eb documents that feat/cd-076 commit message was corrected
+- Task ID now properly reflects CD-076 branch naming
+
+**Verification:**
+```
+Commit: c3986eb
+Message: docs(CD-145): Fix branching-policy.md critical accuracy issues
+Content: "Fixed feat/cd-076 commit message to reference correct task ID (CD-076 instead of CD-060)"
+Status: ✅ FIXED
+```
+
+---
+
+### Issue #2: ✅ Inaccurate Example Citation (CD-067)
+
+**Original Problem (RV-095):**
+- Document claimed CD-067 was a compliant example
+- Actual CD-067 commit lacks the required `(direct-fix)` tag
+- This violated criterion #6 of the stated exemption criteria
+
+**Fix Applied (CD-145):**
+- Removed CD-067 as claimed example from docs/branching-policy.md
+- Added note: "A fully compliant, real-world example is being identified and will be added in a follow-up commit"
+- Guidance updated to clarify that all criteria must be met
+
+**Verification:**
+From fixed branching-policy.md:
+```
+> Note: A fully compliant, real-world example is being identified and will be added
+> in a follow-up commit. All future direct-fix commits must include the `(direct-fix)` tag
+> in the commit message to demonstrate compliance with all six criteria.
+```
+Status: ✅ FIXED
+
+---
+
+### Issue #3: ✅ Missing AR-017 Reference Artifact
+
+**Original Problem (RV-095):**
+- Document referenced `artifacts/ARCH-REVIEW-017-branching-policy-trivial-fix-exemptions.md`
+- File did not exist
+
+**Fix Applied (CD-145):**
+- Created comprehensive artifacts/ARCH-REVIEW-017-branching-policy-trivial-fix-exemptions.md
+- Document includes:
+  - Decision statement for trivial-fix exemption
+  - All six criteria with rationale
+  - Compliance verification process
+  - Reference examples and guidance
+
+**Verification:**
+```
+File Created: artifacts/ARCH-REVIEW-017-branching-policy-trivial-fix-exemptions.md
+Size: 159 lines
+Content: Comprehensive architecture review with full policy context
+Status: ✅ CREATED AND VERIFIED
+```
+
+---
+
+## QA Verification Results
+
+**Test Instance:** TS-226
+**Tester:** tester-2
+**Status:** ✅ **PASSED** - All 12 verification items
+
+Verification coverage:
+- ✅ Document accuracy: AR-017 artifact references correct
+- ✅ Example handling: CD-067 non-compliant reference removed
+- ✅ Artifact content: Six criteria comprehensively documented
+- ✅ feat/cd-076: Commit message corrected to reference CD-076
+- ✅ Cross-references: All consistent and accurate
+- ✅ No dangling references found
+- ✅ Document structure: Clear and navigable
+- ✅ Criteria: All measurable and testable
+
+---
+
+## Files Changed in CD-145
+
+**Commit:** c3986eb6571024d1d974011ae3e6e9aced1f2d62
+**Date:** Wed Feb 25 09:08:04 2026 +0530
+**Author:** Nikhil Chatragadda
+
+**Files Added/Modified:**
+1. `artifacts/ARCH-REVIEW-017-branching-policy-trivial-fix-exemptions.md` (+159 lines)
+   - New architecture review document
+   - Comprehensive policy documentation
+   - Compliance guidance and examples
+
+2. `docs/branching-policy.md` (+56 lines)
+   - Updated with accurate example handling
+   - Removed non-compliant CD-067 reference
+   - Added note about pending compliant example identification
+
+**Total Changes:** +215 lines, well-scoped and focused
+
+---
+
+## Acceptance Criteria Verification
+
+| Criterion | Status | Evidence |
+|-----------|--------|----------|
+| CD-145 addresses all RV-095 issues | ✅ YES | All 3 issues fixed (ID mismatch, example accuracy, artifact) |
+| docs/branching-policy.md accurate & complete | ✅ YES | QA TS-226 verification: PASSED |
+| All artifacts referenced in CD-145 are in place | ✅ YES | AR-017 artifact created and verified |
+| CD-145 is ready for merge to main | ✅ YES | Commit c3986eb verified and tested |
+| Downstream tasks (CD-078) can proceed | ✅ CONFIRMED | CD-145 ready to unblock CD-078 |
+
+---
+
+## Impact Assessment
+
+**Blocking Issue Resolution:**
+- CD-078 (exemption note for pipelines) depends on this completing
+- CD-145 merge unblocks CD-078 immediately
+
+**Policy Document Status:**
+- Establishes authoritative branching policy document for the project
+- Provides clear compliance criteria for exemption process
+- Enables consistent enforcement across all future branches
+
+**Quality Improvements:**
+- Document now has verified accuracy
+- Example handling clarified pending compliant reference
+- Architecture review artifact provides full decision context
+
+---
+
+## Recommendation
+
+✅ **APPROVED FOR MERGE TO MAIN**
+
+CD-145 successfully resolves all RV-095 issues and is fully tested and verified. The branch is ready for immediate merge to main. Upon merge completion:
+
+1. CD-145 will be officially merged to main
+2. CD-078 (unblocked by CD-164) can proceed
+3. Branching policy becomes authoritative reference for future exemption claims
+
+---
+
+**Verification Completed By:** coder-13
+**Timestamp:** 2026-02-25
+**Next Steps:** Merge feat/cd-145 to main, then confirm in CD-164

taskbrew-1.0.0/CHANGELOG.md

@@ -0,0 +1,29 @@
+# Changelog
+
+All notable changes to this project will be documented in this file.
+
+The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.1.0/),
+and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
+
+## [1.0.0] - 2026-02-27
+
+### Added
+- Multi-agent orchestration with PM, Architect, Coder, and Verifier roles
+- Claude Code and Gemini CLI provider support
+- Config-driven MCP tool server registration
+- Provider extensibility via YAML config and Python plugin interface
+- Hybrid agent routing (open discovery + restricted mode)
+- Task guardrails (depth limits, group limits, rejection cycle detection)
+- Plugin system with startup hooks and event bus integration
+- Web dashboard with real-time task monitoring
+- Multi-project support with per-project database isolation
+- `taskbrew init` command for project scaffolding
+- `taskbrew doctor` command for system diagnostics
+- Fail-fast startup validation with actionable error messages
+- MIT license for open-source distribution
+
+### Infrastructure
+- Comprehensive test suite (1250+ tests)
+- SQLite-based task persistence
+- FastAPI dashboard with WebSocket updates
+- Git worktree isolation for concurrent agent work