@paths.design/caws-cli 10.2.0 → 11.1.0

package/templates/docs/README.md

@@ -1,151 +0,0 @@
-# CAWS Project Documentation
-
-## Overview
-This project is built with the **Coding Agent Workflow System (CAWS)** - an engineering-grade framework that ensures quality, reliability, and maintainability in AI-assisted development.
-
-## Key Features
-- **Quality Gates**: Automated validation of scope, budget, and standards
-- **Comprehensive Testing**: Unit, contract, integration, and mutation testing
-- **Observability**: Structured logging, metrics, and tracing
-- **Rollback Ready**: Feature flags and migration support
-- **Provenance Tracking**: SBOM and SLSA attestation generation
-
-## Getting Started
-
-### 1. Project Setup
-The project is already scaffolded with CAWS. Review and customize:
-- `.caws/specs/<spec-id>.yaml` - Canonical feature specification and requirements
-- `.caws/working-spec.yaml` - Compatibility mirror for legacy paths
-- `.caws/policy.yaml` - Risk tier definitions
-- `.github/workflows/caws.yml` - CI/CD quality gates
-
-### 2. Development Workflow
-1. **Plan**: Update the active feature spec with requirements and scope
-2. **Implement**: Follow agent conduct rules and mode constraints
-3. **Verify**: Run tests and quality gates locally
-4. **Document**: Update documentation and generate provenance
-
-### 3. Quality Assurance
-- Run `npm run test` for all tests
-- Check trust score with CAWS tools
-- Validate against working specification
-- Ensure rollback capabilities
-
-## Architecture
-
-### Directory Structure
-```
-src/                    # Source code
-├── core/              # Core business logic
-├── api/               # API endpoints
-├── models/            # Data models
-└── utils/             # Utilities
-
-tests/                 # Test suites
-├── unit/             # Unit tests
-├── contract/         # Contract tests
-├── integration/      # Integration tests
-└── e2e/              # End-to-end tests
-
-apps/tools/caws/       # CAWS utilities
-└── prompt-lint.js    # Prompt validation
-└── attest.js         # SBOM/attestation generation
-```
-
-### Key Patterns
-- **Dependency Injection**: For testability and determinism
-- **Interface Segregation**: Clean boundaries and contracts
-- **Observability**: Structured logging and metrics
-- **Property Testing**: Edge cases and invariants
-
-## Development Guidelines
-
-### Agent Conduct Rules
-1. **Spec Adherence**: Stay within declared scope and mode
-2. **Determinism**: Inject time, UUID, and random dependencies
-3. **Comprehensive Testing**: Unit + property + integration tests
-4. **Observability**: Log, metric, and trace key operations
-5. **Rollback Ready**: Feature flags and migration support
-
-### Code Quality
-- **Type Safety**: Full TypeScript coverage
-- **Test Coverage**: 80%+ branch coverage, 50%+ mutation score
-- **Performance**: API p95 < 250ms, accessibility compliance
-- **Security**: Input validation, rate limiting, secret scanning
-
-## Deployment
-
-### CI/CD Pipeline
-The project includes automated quality gates:
-- Static analysis and security scanning
-- Unit and integration testing
-- Performance and accessibility validation
-- Provenance and attestation generation
-
-### Environment Setup
-1. Configure environment variables
-2. Set up monitoring and alerting
-3. Establish rollback procedures
-4. Document operational runbooks
-
-## Monitoring & Observability
-
-### Metrics
-- Request latency and throughput
-- Error rates and types
-- Resource utilization
-- Business metrics
-
-### Logging
-- Structured logs with correlation IDs
-- Error tracking and alerting
-- Performance monitoring
-- Security event logging
-
-### Tracing
-- Distributed request tracing
-- Performance profiling
-- Dependency analysis
-- Root cause identification
-
-## Troubleshooting
-
-### Common Issues
-1. **Trust Score Low**: Check test coverage and quality gates
-2. **Scope Violations**: Ensure changes align with the active spec
-3. **Budget Exceeded**: Review change size and complexity
-4. **Flaky Tests**: Use property testing and proper mocking
-
-### Support
-- Check `agents.md` for comprehensive documentation
-- Review CI/CD logs for quality gate failures
-- Use CAWS tools for validation and debugging
-- Follow agent conduct rules for collaboration
-
-## Contributing
-
-### Development Process
-1. Update the active feature specification
-2. Create comprehensive tests
-3. Implement with quality gates
-4. Generate provenance artifacts
-5. Document changes thoroughly
-
-### Code Review
-- Review against the active feature spec
-- Check trust score and quality gates
-- Validate observability and rollback
-- Ensure documentation completeness
-
-## Resources
-
-- **[CAWS Framework](agents.md)**: Complete system documentation
-- **[Canonical Specs](.caws/specs/)**: Project requirements
-- **[Quality Gates](.github/workflows/caws.yml)**: CI/CD pipeline
-- **[Tools](apps/tools/caws/)**: Development utilities
-
----
-
-**Maintainer**: @darianrosebrook
-**Framework**: CAWS v1.0
-**Updated**: $(date)

package/templates/scripts/new_feature.sh

@@ -1,80 +0,0 @@
-#!/bin/bash
-# Create a new CAWS feature spec + optional worktree
-#
-# Usage:
-#   scripts/new_feature.sh FEAT-001 "Feature description"
-#   scripts/new_feature.sh FEAT-001 "Feature description" --worktree
-#
-# This script:
-#   1. Creates a feature spec in .caws/specs/<ID>.yaml
-#   2. Optionally creates a git worktree for isolated development
-
-set -euo pipefail
-
-if [ $# -lt 2 ]; then
-  echo "usage: scripts/new_feature.sh <SPEC-ID> <title> [--worktree]" >&2
-  echo "  example: scripts/new_feature.sh FEAT-001 'Add user authentication'" >&2
-  exit 1
-fi
-
-SPEC_ID="$1"
-TITLE="$2"
-USE_WORKTREE="${3:-}"
-
-# Validate spec ID format (PREFIX-NUMBER, e.g., FEAT-001, AUTH-042)
-if ! echo "$SPEC_ID" | grep -qE '^[A-Z]+-[0-9]+$'; then
-  echo "error: spec ID must be in format PREFIX-NUMBER (e.g., FEAT-001, AUTH-042)" >&2
-  exit 1
-fi
-
-SPEC_FILE=".caws/specs/${SPEC_ID}.yaml"
-
-# Check if spec already exists
-if [ -f "$SPEC_FILE" ]; then
-  echo "error: spec $SPEC_ID already exists at $SPEC_FILE" >&2
-  exit 1
-fi
-
-# Create spec directory if needed
-mkdir -p .caws/specs
-
-# Generate spec scaffold
-TIMESTAMP=$(date -u +"%Y-%m-%dT%H:%M:%SZ")
-cat > "$SPEC_FILE" << EOF
-id: ${SPEC_ID}
-type: feature
-title: "${TITLE}"
-status: draft
-risk_tier: 2
-mode: development
-created_at: "${TIMESTAMP}"
-updated_at: "${TIMESTAMP}"
-blast_radius:
-  modules: []
-  data_migration: false
-operational_rollback_slo: 5m
-scope:
-  in: []
-  out:
-    - docs/reference/v1/
-    - .caws/
-threats: []
-invariants: []
-acceptance: []
-acceptance_criteria: []
-milestones: []
-EOF
-
-echo "Created feature spec: $SPEC_FILE"
-
-# Optionally create worktree
-if [ "$USE_WORKTREE" = "--worktree" ]; then
-  BRANCH_NAME="feat/${SPEC_ID,,}"  # lowercase
-  WORKTREE_DIR=".caws/worktrees/${SPEC_ID,,}"
-
-  git worktree add "$WORKTREE_DIR" -b "$BRANCH_NAME"
-  echo "Created worktree: $WORKTREE_DIR (branch: $BRANCH_NAME)"
-  echo ""
-  echo "To start working:"
-  echo "  cd $WORKTREE_DIR"
-fi

package/templates/scripts/quality-gates/check-god-objects.js

@@ -1,146 +0,0 @@
-#!/usr/bin/env node
-
-/**
- * God Object Detector
- * 
- * Checks for god objects (large files) in staged files only.
- * This script is automatically generated by CAWS scaffold.
- * 
- * @author @darianrosebrook
- */
-
-const fs = require('fs');
-const path = require('path');
-const { execSync } = require('child_process');
-
-// Configuration
-const CONFIG = {
-  godObjectThresholds: {
-    warning: 1750,
-    critical: 2000,
-  },
-};
-
-// Collect staged Rust files only
-function collectStagedRustFiles() {
-  try {
-    // Get staged files
-    const stagedFiles = execSync("git diff --cached --name-only", {
-      encoding: "utf8",
-    })
-      .trim()
-      .split("\n")
-      .filter((file) => file.trim() !== "");
-
-    // Filter for Rust files
-    const rustFiles = stagedFiles.filter((file) => file.endsWith(".rs"));
-
-    // Convert to absolute paths
-    const RUST_FILES = [];
-    for (const file of rustFiles) {
-      const fullPath = path.resolve(file);
-      if (fs.existsSync(fullPath)) {
-        RUST_FILES.push(fullPath);
-      }
-    }
-
-    console.log(`📁 Found ${rustFiles.length} staged Rust files to check`);
-    return RUST_FILES;
-  } catch (error) {
-    console.warn(`⚠️  Could not get staged files: ${error.message}`);
-    return [];
-  }
-}
-
-// Check for god objects
-function checkGodObjects() {
-  const RUST_FILES = collectStagedRustFiles();
-  
-  if (RUST_FILES.length === 0) {
-    console.log("✅ No staged Rust files to check for god objects");
-    return { violations: [], warnings: [] };
-  }
-
-  const violations = [];
-  const warnings = [];
-
-  for (const filePath of RUST_FILES) {
-    try {
-      const content = fs.readFileSync(filePath, 'utf8');
-      const lineCount = content.split('\n').length;
-      const relativePath = path.relative(process.cwd(), filePath);
-
-      if (lineCount >= CONFIG.godObjectThresholds.critical) {
-        violations.push({
-          file: relativePath,
-          lines: lineCount,
-          message: `CRITICAL: ${lineCount} LOC exceeds god object threshold (${CONFIG.godObjectThresholds.critical}+ LOC)`
-        });
-      } else if (lineCount >= CONFIG.godObjectThresholds.warning) {
-        warnings.push({
-          file: relativePath,
-          lines: lineCount,
-          message: `WARNING: ${lineCount} LOC approaches god object territory (${CONFIG.godObjectThresholds.warning}+ LOC)`
-        });
-      }
-    } catch (error) {
-      console.warn(`⚠️  Could not analyze ${filePath}: ${error.message}`);
-    }
-  }
-
-  return { violations, warnings };
-}
-
-// Check for god object regression
-function checkGodObjectRegression() {
-  const RUST_FILES = collectStagedRustFiles();
-  
-  if (RUST_FILES.length === 0) {
-    return { regression: false };
-  }
-
-  // This is a simplified check - in a real implementation,
-  // you might want to compare against previous commits
-  const results = checkGodObjects();
-  
-  return {
-    regression: results.violations.length > 0,
-    violations: results.violations,
-    warnings: results.warnings
-  };
-}
-
-// Main execution
-function main() {
-  console.log("🏗️  Checking god objects...");
-  
-  const results = checkGodObjects();
-  
-  if (results.violations.length > 0) {
-    console.log("   ❌ God object violations detected:");
-    results.violations.forEach(violation => {
-      console.log(`      ${violation.file}: ${violation.message}`);
-    });
-    process.exit(1);
-  } else {
-    console.log("   ✅ No blocking god object violations");
-  }
-  
-  if (results.warnings.length > 0) {
-    console.log("   ⚠️  God object warnings:");
-    results.warnings.forEach(warning => {
-      console.log(`      ${warning.file}: ${warning.message}`);
-    });
-  }
-}
-
-// Run if called directly
-if (require.main === module) {
-  main();
-}
-
-module.exports = {
-  checkGodObjects,
-  checkGodObjectRegression,
-  collectStagedRustFiles,
-};

package/templates/scripts/quality-gates/run-quality-gates.js

@@ -1,50 +0,0 @@
-#!/usr/bin/env node
-
-/**
- * Quality Gates Runner
- * 
- * Runs comprehensive quality gates on staged files only.
- * This script is automatically generated by CAWS scaffold.
- * 
- * @author @darianrosebrook
- */
-
-const { runQualityGates } = require('@paths.design/caws-cli/src/utils/quality-gates');
-
-// Parse command line arguments
-const args = process.argv.slice(2);
-const options = {
-  languages: ['rust'],
-  checkTodos: true,
-  checkGodObjects: true,
-  ci: args.includes('--ci') || args.includes('--ci-mode')
-};
-
-// Extract languages from arguments
-const langIndex = args.indexOf('--languages');
-if (langIndex !== -1 && args[langIndex + 1]) {
-  options.languages = args[langIndex + 1].split(',').map(lang => lang.trim());
-}
-
-// Check for disable flags
-if (args.includes('--no-todos')) {
-  options.checkTodos = false;
-}
-
-if (args.includes('--no-god-objects')) {
-  options.checkGodObjects = false;
-}
-
-// Run quality gates
-try {
-  const results = runQualityGates(options);
-  
-  if (!results.passed && options.ci) {
-    process.exit(1);
-  }
-} catch (error) {
-  console.error(`❌ Quality gates failed: ${error.message}`);
-  if (options.ci) {
-    process.exit(1);
-  }
-}