aios-core 2.1.0

package/.aios-core/product/data/test-priorities-matrix.md

@@ -0,0 +1,175 @@
+<!-- Powered by AIOS™ Core -->
+
+# Test Priorities Matrix
+
+Guide for prioritizing test scenarios based on risk, criticality, and business impact.
+
+## Priority Levels
+
+### P0 - Critical (Must Test)
+
+**Criteria:**
+
+- Revenue-impacting functionality
+- Security-critical paths
+- Data integrity operations
+- Regulatory compliance requirements
+- Previously broken functionality (regression prevention)
+
+**Examples:**
+
+- Payment processing
+- Authentication/authorization
+- User data creation/deletion
+- Financial calculations
+- GDPR/privacy compliance
+
+**Testing Requirements:**
+
+- Comprehensive coverage at all levels
+- Both happy and unhappy paths
+- Edge cases and error scenarios
+- Performance under load
+
+### P1 - High (Should Test)
+
+**Criteria:**
+
+- Core user journeys
+- Frequently used features
+- Features with complex logic
+- Integration points between systems
+- Features affecting user experience
+
+**Examples:**
+
+- User registration flow
+- Search functionality
+- Data import/export
+- Notification systems
+- Dashboard displays
+
+**Testing Requirements:**
+
+- Primary happy paths required
+- Key error scenarios
+- Critical edge cases
+- Basic performance validation
+
+### P2 - Medium (Nice to Test)
+
+**Criteria:**
+
+- Secondary features
+- Admin functionality
+- Reporting features
+- Configuration options
+- UI polish and aesthetics
+
+**Examples:**
+
+- Admin settings panels
+- Report generation
+- Theme customization
+- Help documentation
+- Analytics tracking
+
+**Testing Requirements:**
+
+- Happy path coverage
+- Basic error handling
+- Can defer edge cases
+
+### P3 - Low (Test if Time Permits)
+
+**Criteria:**
+
+- Rarely used features
+- Nice-to-have functionality
+- Cosmetic issues
+- Non-critical optimizations
+
+**Examples:**
+
+- Advanced preferences
+- Legacy feature support
+- Experimental features
+- Debug utilities
+
+**Testing Requirements:**
+
+- Smoke tests only
+- Can rely on manual testing
+- Document known limitations
+
+## Risk-Based Priority Adjustments
+
+### Increase Priority When:
+
+- High user impact (affects >50% of users)
+- High financial impact (>$10K potential loss)
+- Security vulnerability potential
+- Compliance/legal requirements
+- Customer-reported issues
+- Complex implementation (>500 LOC)
+- Multiple system dependencies
+
+### Decrease Priority When:
+
+- Feature flag protected
+- Gradual rollout planned
+- Strong monitoring in place
+- Easy rollback capability
+- Low usage metrics
+- Simple implementation
+- Well-isolated component
+
+## Test Coverage by Priority
+
+| Priority | Unit Coverage | Integration Coverage | E2E Coverage       |
+| -------- | ------------- | -------------------- | ------------------ |
+| P0       | >90%          | >80%                 | All critical paths |
+| P1       | >80%          | >60%                 | Main happy paths   |
+| P2       | >60%          | >40%                 | Smoke tests        |
+| P3       | Best effort   | Best effort          | Manual only        |
+
+## Priority Assignment Rules
+
+1. **Start with business impact** - What happens if this fails?
+2. **Consider probability** - How likely is failure?
+3. **Factor in detectability** - Would we know if it failed?
+4. **Account for recoverability** - Can we fix it quickly?
+
+## Priority Decision Tree
+
+```
+Is it revenue-critical?
+├─ YES → P0
+└─ NO → Does it affect core user journey?
+    ├─ YES → Is it high-risk?
+    │   ├─ YES → P0
+    │   └─ NO → P1
+    └─ NO → Is it frequently used?
+        ├─ YES → P1
+        └─ NO → Is it customer-facing?
+            ├─ YES → P2
+            └─ NO → P3
+```
+
+## Test Execution Order
+
+1. Execute P0 tests first (fail fast on critical issues)
+2. Execute P1 tests second (core functionality)
+3. Execute P2 tests if time permits
+4. P3 tests only in full regression cycles
+
+## Continuous Adjustment
+
+Review and adjust priorities based on:
+
+- Production incident patterns
+- User feedback and complaints
+- Usage analytics
+- Test failure history
+- Business priority changes
+ 

package/.aios-core/product/templates/1mcp-config.yaml

@@ -0,0 +1,225 @@
+# 1MCP Configuration Template for AIOS
+# Purpose: Define MCP servers and presets for AIOS agents
+# Location: ~/.1mcp/config.json (generated from this template)
+
+# ==============================================================================
+# MCP SERVERS
+# ==============================================================================
+mcps:
+  # Documentation & Research MCP
+  context7:
+    command: "npx"
+    args: ["-y", "@upstash/context7-mcp"]
+    enabled: true
+    description: "Library/framework documentation lookup"
+    use_cases:
+      - "Architecture research"
+      - "API reference lookup"
+      - "Learning new frameworks"
+    agents: ["architect", "analyst", "dev"]
+
+  # GitHub Operations MCP
+  github:
+    command: "npx"
+    args: ["-y", "@modelcontextprotocol/server-github"]
+    enabled: true
+    environment:
+      GITHUB_TOKEN: "${GITHUB_TOKEN}"  # Set in environment
+    description: "GitHub API operations (repos, issues, PRs)"
+    use_cases:
+      - "Story implementation"
+      - "Pull request creation"
+      - "Issue tracking"
+      - "Code review"
+    agents: ["dev", "qa", "sm", "po"]
+
+  # Browser Automation MCP
+  browser:
+    command: "npx"
+    args: ["-y", "@modelcontextprotocol/server-puppeteer"]
+    enabled: true
+    description: "Browser automation and web scraping"
+    use_cases:
+      - "UI testing"
+      - "Web scraping"
+      - "Screenshot generation"
+      - "Integration testing"
+    agents: ["qa", "dev", "analyst"]
+
+  # Docker & Containers MCP (disabled by default)
+  docker:
+    command: "npx"
+    args: ["-y", "@docker/mcp-server-docker-desktop"]
+    enabled: false  # Enable only when needed
+    description: "Docker container management"
+    use_cases:
+      - "Container operations"
+      - "Docker Compose management"
+      - "Image building"
+      - "Deployment automation"
+    agents: ["devops", "sm"]
+
+# ==============================================================================
+# PRESETS (Agent-Specific Configurations)
+# ==============================================================================
+presets:
+  # Development Preset (Default)
+  aios-dev:
+    filter: ["github", "browser"]
+    description: "Story implementation, PRs, development tasks"
+    token_budget: "25-40K"
+    agents: ["dev", "qa", "sm"]
+    use_cases:
+      - "Story implementation (docs/stories/*.md)"
+      - "Pull request creation"
+      - "Code review and validation"
+      - "Issue tracking and management"
+      - "Sprint planning"
+    recommended: true
+
+  # Research Preset
+  aios-research:
+    filter: ["context7", "browser"]
+    description: "Documentation-heavy research and learning"
+    token_budget: "40-60K"
+    agents: ["architect", "analyst"]
+    use_cases:
+      - "Architecture design and research"
+      - "Framework evaluation"
+      - "API reference lookup"
+      - "Best practices research"
+      - "Documentation writing"
+    recommended: false
+
+  # Docker Preset (On-Demand)
+  aios-docker:
+    filter: ["docker", "browser"]
+    description: "Container management and deployment"
+    token_budget: "15-20K"
+    agents: ["devops"]
+    use_cases:
+      - "Docker container operations"
+      - "Deployment automation"
+      - "Integration testing with containers"
+      - "Service orchestration"
+    recommended: false
+    enable_only_when_needed: true
+
+  # Full Preset (Rare Use)
+  aios-full:
+    filter: ["context7", "github", "browser"]
+    description: "Complex multi-domain tasks requiring all tools"
+    token_budget: "60-80K"
+    agents: ["all"]
+    use_cases:
+      - "Complex exploratory work"
+      - "Emergency debugging (need all tools)"
+      - "Multi-domain integration tasks"
+    recommended: false
+    warning: "Use sparingly - higher token cost"
+
+# ==============================================================================
+# SERVER CONFIGURATION
+# ==============================================================================
+server:
+  port: 3050
+  host: "127.0.0.1"  # Localhost only (security)
+  timeout: 30000     # 30 seconds
+  max_retries: 3
+
+# ==============================================================================
+# MONITORING & LOGGING
+# ==============================================================================
+monitoring:
+  enabled: true
+  metrics:
+    track_token_usage: true
+    track_preset_usage: true
+    track_mcp_errors: true
+  logging:
+    level: "info"  # "debug" | "info" | "warn" | "error"
+    file: "~/.1mcp/logs/server.log"
+
+# ==============================================================================
+# AIOS INTEGRATION
+# ==============================================================================
+aios_integration:
+  # Automatic preset selection based on agent
+  auto_preset_selection:
+    enabled: true
+    mappings:
+      dev: "aios-dev"
+      qa: "aios-dev"
+      sm: "aios-dev"
+      po: "aios-dev"
+      architect: "aios-research"
+      analyst: "aios-research"
+      devops: "aios-docker"
+
+  # Token budget alerts
+  token_budget_alerts:
+    enabled: true
+    warn_threshold: 50000   # Warn if > 50K tokens
+    error_threshold: 80000  # Error if > 80K tokens
+
+  # Automatic fallback
+  fallback:
+    enabled: true
+    if_preset_fails: "aios-dev"  # Fallback to dev preset
+    if_server_down: "direct_mcp"  # Fallback to direct MCPs
+
+# ==============================================================================
+# USAGE EXAMPLES
+# ==============================================================================
+examples:
+  # Example 1: Story Implementation (@dev agent)
+  story_implementation:
+    agent: "dev"
+    preset: "aios-dev"
+    mcps_used: ["github", "browser"]
+    token_budget: "~35K"
+    workflow:
+      - "Read story file (filesystem)"
+      - "Search related code (github.search_code)"
+      - "Implement changes (filesystem.write)"
+      - "Create PR (github.create_pr)"
+      - "Update story progress (filesystem.write)"
+
+  # Example 2: Architecture Research (@architect agent)
+  architecture_research:
+    agent: "architect"
+    preset: "aios-research"
+    mcps_used: ["context7", "browser"]
+    token_budget: "~50K"
+    workflow:
+      - "Look up framework docs (context7)"
+      - "Browse examples (browser.navigate)"
+      - "Research best practices (context7 + browser)"
+      - "Document findings (filesystem.write)"
+
+  # Example 3: Docker Deployment (@devops)
+  docker_deployment:
+    agent: "devops"
+    preset: "aios-docker"
+    mcps_used: ["docker", "browser"]
+    token_budget: "~18K"
+    workflow:
+      - "Build Docker image (docker.build)"
+      - "Run container (docker.run)"
+      - "Test deployment (browser.navigate)"
+      - "Verify health (browser.screenshot)"
+
+# ==============================================================================
+# NOTES
+# ==============================================================================
+notes:
+  token_reduction: "85% (280K → 40K with aios-dev)"
+  production_ready: true
+  validated_by: "AIOS Roundtable 2025-01-14"
+  experts:
+    - "Pedro Valério (Systems Architecture)"
+    - "Mitchell Hashimoto (Infrastructure)"
+    - "Andrej Karpathy (AI Systems)"
+    - "Guillermo Rauch (Developer Experience)"
+  decision: "Use 1MCP (Phase 1), defer TOON to Phase 2 pending benchmark"
+  documentation: "docs/guides/1mcp-implementation.md"

package/.aios-core/product/templates/activation-instructions-inline-greeting.yaml

@@ -0,0 +1,63 @@
+# Activation Instructions Template with Inline Greeting Logic
+# Version: 2.0 (Story 6.1.2.5-T1 - Option A Implementation)
+# Date: 2025-11-16
+
+# This template provides inline greeting logic that works reliably without
+# external JavaScript execution. It implements the greeting-builder.js logic
+# directly in YAML activation-instructions.
+
+activation-instructions:
+  - STEP 1: Read THIS ENTIRE FILE - it contains your complete persona definition
+
+  - STEP 2: Adopt the persona defined in the 'agent' and 'persona' sections below
+
+  - STEP 3: Generate contextual greeting using inline logic
+    # Session Type Detection (simplified inline version)
+    - If this is first message in conversation → session_type = "new"
+    - If conversation has history → session_type = "existing"
+    - Default to "new" if uncertain
+
+    # Greeting Components
+    - Start with greeting from persona_profile.greeting_levels.named
+    - Add role description from persona.role
+
+    # Project Status (check git)
+    - Use Bash tool to get: git branch --show-current
+    - Use Bash tool to get: git status --short | wc -l (count modified files)
+    - Use Bash tool to get: git log -1 --pretty=format:"%s" (recent commit)
+    - Format as:
+      📊 **Project Status:**
+      - 🌿 **Branch:** [branch_name]
+      - 📝 **Modified:** [count] files
+      - 📖 **Recent:** [commit_message]
+
+    # Command Filtering by Session Type
+    - If session_type = "new":
+      - Show commands with visibility: ["full", "quick", "key"] (up to 12)
+      - Header: "**Available Commands:**"
+    - If session_type = "existing":
+      - Show commands with visibility: ["quick", "key"] (6-8 commands)
+      - Header: "**Quick Commands:**"
+
+    # Command Formatting
+    - For each command:
+      - Format as: "   - `*{command.name}`: {command.description}"
+
+    # Footer
+    - Add: "Type `*guide` for comprehensive usage instructions."
+
+  - STEP 4: Display the greeting you generated in STEP 3
+
+  - STEP 5: HALT and await user input
+
+# Important Notes:
+# - This approach sacrifices DRY for reliability
+# - All 11 agents will have similar inline logic
+# - Changes require updating all agents (use batch script)
+# - No external dependencies = no execution failures
+# - Works 100% of the time in Claude Code environment
+
+# Maintenance:
+# - Use .aios-core/scripts/batch-update-greetings.js to update all agents
+# - Keep this template synchronized with actual agent files
+# - Document any greeting logic changes in ADR-001-IMPLEMENTATION-SUMMARY.md