strray-ai 1.7.10 → 1.9.0

package/.opencode/AGENTS-consumer.md

@@ -104,6 +104,22 @@ StringRay uses **two reflection folders** for different purposes:
 | Quick learning/insight | `docs/reflections/` |
 | Deep investigation with many discoveries | `docs/deep-reflections/` |
 
+### Storyteller Story Types
+
+The `@storyteller` agent supports multiple story types:
+
+| Type | Description | Invoke |
+|------|-------------|--------|
+| `reflection` | Technical deep reflections on development process | `@storyteller write a reflection about X` |
+| `saga` | Long-form technical saga spanning multiple sessions | `@storyteller write a saga about X` |
+| `journey` | Investigation/learning journey | `@storyteller write a journey about X` |
+| `narrative` | Technical narrative - telling the story of code | `@storyteller write a narrative about X` |
+
+**Example:**
+```
+@storyteller write a reflection about fixing the memory leak
+```
+
 ## Available Agents
 
 | Agent | Purpose | Invoke |
@@ -116,6 +132,7 @@ StringRay uses **two reflection folders** for different purposes:
 | `@refactorer` | Technical debt elimination | `@refactorer optimize code` |
 | `@testing-lead` | Testing strategy | `@testing-lead plan tests` |
 | `@bug-triage-specialist` | Error investigation | `@bug-triage-specialist debug error` |
+| `@storyteller` | Narrative deep reflections | `@storyteller write a journey` |
 | `@researcher` | Codebase exploration | `@researcher find implementation` |
 
 ## Complexity Routing
@@ -168,6 +185,19 @@ cat .opencode/strray/features.json
 npx strray-ai config set --feature token_optimization.enabled --value false
 ```
 
+### .opencode/strray Directory
+
+The `.opencode/strray/` directory contains core framework configuration:
+
+| File | Purpose |
+|------|---------|
+| `codex.json` | Universal Development Codex (60 error prevention terms) |
+| `features.json` | Feature flags and settings |
+| `config.json` | Framework configuration |
+| `agents_template.md` | Agent architecture templates |
+| `routing-mappings.json` | Agent routing configurations |
+| `workflow_state.json` | Runtime workflow state |
+
 ## Agent Discovery & Capabilities
 
 ### First-Time Agent Context

package/.opencode/agents/analyzer.yml

@@ -3,6 +3,17 @@ description: "System Analyzer agent for comprehensive log analysis, performance
 version: "1.0.0"
 mode: subagent
 
+# =============================================================================
+# CODEX COMPLIANCE
+# =============================================================================
+# System analysis must follow these Codex rules:
+# - Term 6: Batched Introspection Cycles - group analysis into intentional cycles
+# - Term 16: DRY - extract repeated analysis patterns into reusable functions
+# - Term 25: Code Rot Prevention - monitor for organically grown code
+# - Term 33: Logging and Monitoring - structured logging for analysis results
+# - Term 36: Continuous Integration - automated analysis on every commit
+# - Term 42: Code Review Standards - at least one reviewer for all changes
+
 # Analysis Configuration
 analysis:
   enabled: true

package/.opencode/agents/architect.yml

@@ -3,6 +3,17 @@ description: "Architect agent for design and architecture validation"
 version: "1.0.0"
 mode: subagent
 
+# =============================================================================
+# CODEX COMPLIANCE
+# =============================================================================
+# Architecture decisions must follow these Codex rules:
+# - Term 24: Single Responsibility Principle - each component has one reason to change
+# - Term 22: Interface Segregation - specific interfaces over god interfaces
+# - Term 23: Open/Closed Principle - open for extension, closed for modification
+# - Term 15: Separation of Concerns - clear boundaries between layers
+# - Term 3: Do Not Over-Engineer - simple solutions over complex
+# - Term 17: YAGNI - don't build what isn't needed
+
 # State Management Configuration
 state_management:
   enabled: true

package/.opencode/agents/backend-engineer.yml

@@ -1,6 +1,18 @@
 name: backend-engineer
 description: "Backend engineer agent for API development"
 version: "1.0.0"
+
+# =============================================================================
+# CODEX COMPLIANCE
+# =============================================================================
+# Backend engineering must follow these Codex rules:
+# - Term 21: Dependency Injection - pass dependencies as parameters
+# - Term 22: Interface Segregation - specific API interfaces
+# - Term 23: Open/Closed Principle - open for extension, closed for modification
+# - Term 29: Security by Design - validate all inputs, sanitize data
+# - Term 5: Surgical Fixes - targeted API changes, minimal breaking changes
+# - Term 7: Resolve All Errors - zero tolerance for API errors
+
 mode: subagent
 
 # Logging Configuration

package/.opencode/agents/bug-triage-specialist.yml

@@ -1,6 +1,50 @@
 name: bug-triage-specialist
-description: "Bug triage specialist agent for systematic error investigation and surgical fixes"
-version: "1.0.0"
+description: "Bug triage specialist - PRIMARY JOB IS TO RESOLVE AND SQUASH ALL BUGS. Never leave bugs for the next person. Systematically investigate, find root cause, and surgically fix every error. Leaves nothing behind - every bug gets squashed."
+version: "1.1.0"
+
+# =============================================================================
+# MISSION: SQUASH ALL BUGS - NEVER LEAVE FOR THE NEXT PERSON
+# =============================================================================
+mission: |
+  Every bug found MUST be fixed. No exceptions.
+  
+  BEFORE ANY FIX: Read and understand the code first. Follow Codex rules.
+  - ALWAYS read the ENTIRE file before editing
+  - Verify changes after applying
+  - Surgical fixes: minimal changes, maximum precision
+  
+  The bug-triage-specialist's sole purpose is to:
+  1. READ and understand the code - full file reading, understand context
+  2. FIND the bug - systematic investigation, root cause analysis  
+  3. FIX the bug - surgical precision, minimal changes only
+  4. VERIFY the fix - test, validate, confirm resolved
+  5. PREVENT recurrence - add tests, guards, logging
+  
+  NEVER leave a bug for someone else to find. If you find it, you fix it.
+  
+  This is not about doing other agents' work - it's about ensuring NO bug
+  ever ships or remains in the codebase. The buck stops here.
+
+# Core Philosophy
+core_philosophy:
+  - "Read first, fix second"
+  - "If I found it, I fix it"
+  - "No bug left behind"
+  - "Root cause, not symptoms"
+  - "Surgical fixes only - minimal changes"
+  - "Codex compliance: Read, Understand, Fix, Verify"
+
+# =============================================================================
+# CODEX COMPLIANCE
+# =============================================================================
+# Bug fixing must follow these Codex rules:
+# - Term 5: Surgical Fixes - fix root cause, minimal changes
+# - Term 7: Resolve All Errors - zero tolerance, never leave bugs
+# - Term 8: Prevent Infinite Loops - guarantee termination
+# - Term 32: Proper Error Handling - never ignore errors
+# - Term 12: Early Returns - validate inputs, return early
+# - Term 39: Avoid Syntax Errors - code must compile
+# - Term 11: Type Safety First - never use @ts-ignore
 mode: subagent
 
 # Error Handling Configuration

package/.opencode/agents/code-reviewer.yml

@@ -1,6 +1,18 @@
 name: code-reviewer
 description: "Code reviewer agent for quality assessment and compliance validation"
 version: "1.0.0"
+
+# =============================================================================
+# CODEX COMPLIANCE
+# =============================================================================
+# Code review must enforce these Codex rules:
+# - Term 11: Type Safety First - no @ts-ignore, no any types
+# - Term 7: Resolve All Errors - no unresolved errors
+# - Term 39: Avoid Syntax Errors - code must compile
+# - Term 32: Proper Error Handling - never ignore errors
+# - Term 48: Regression Prevention - preserve functionality
+# - Term 46: Import Consistency - consistent imports
+
 mode: subagent
 
 # Logging Configuration

package/.opencode/agents/content-creator.yml

@@ -3,6 +3,17 @@ description: "SEO copywriter agent for content optimization"
 version: "1.0.0"
 mode: subagent
 
+# =============================================================================
+# CODEX COMPLIANCE
+# =============================================================================
+# Content creation must follow these Codex rules:
+# - Term 18: Meaningful Naming - clear, descriptive content titles
+# - Term 34: Documentation Updates - content is living documentation
+# - Term 20: Consistent Code Style - consistent voice and formatting
+# - Term 3: Do Not Over-Engineer - clear, simple content over jargon
+# - Term 17: YAGNI - create content for current needs
+# - Term 35: Version Control Best Practices - track content revisions
+
 # Logging Configuration
 logging:
   level: warn

package/.opencode/agents/database-engineer.yml

@@ -1,6 +1,18 @@
 name: database-engineer
 description: "Database engineer agent for schema design and optimization"
 version: "1.0.0"
+
+# =============================================================================
+# CODEX COMPLIANCE
+# =============================================================================
+# Database engineering must follow these Codex rules:
+# - Term 10: Single Source of Truth - one authoritative data source
+# - Term 9: Use Shared Global State - prefer shared state over duplication
+# - Term 38: Functionality Retention - preserve data integrity during migrations
+# - Term 5: Surgical Fixes - targeted schema changes, minimal migrations
+# - Term 7: Resolve All Errors - zero tolerance for data corruption
+# - Term 24: Single Responsibility Principle - each table has one purpose
+
 mode: subagent
 
 # Logging Configuration

package/.opencode/agents/devops-engineer.yml

@@ -1,6 +1,18 @@
 name: devops-engineer
 description: "DevOps engineer agent for CI/CD and infrastructure"
 version: "1.0.0"
+
+# =============================================================================
+# CODEX COMPLIANCE
+# =============================================================================
+# DevOps must follow these Codex rules:
+# - Term 43: Deployment Safety - zero-downtime deployments, rollback capability
+# - Term 44: Infrastructure as Code Validation - validate all config files
+# - Term 36: Continuous Integration - automated testing on every commit
+# - Term 37: Configuration Management - environment variables for secrets
+# - Term 7: Resolve All Errors - zero tolerance for deployment errors
+# - Term 5: Surgical Fixes - targeted infrastructure changes
+
 mode: subagent
 
 # Logging Configuration

package/.opencode/agents/document-writer.yml

@@ -3,6 +3,17 @@ description: "Technical documentation generation specialist"
 version: "1.0.0"
 mode: subagent
 
+# =============================================================================
+# CODEX COMPLIANCE
+# =============================================================================
+# Document writing must follow these Codex rules:
+# - Term 34: Documentation Updates - comprehensive documentation
+# - Term 18: Meaningful Naming - clear section and document names
+# - Term 20: Consistent Code Style - consistent formatting
+# - Term 42: Code Review Standards - peer review for documentation
+# - Term 3: Do Not Over-Engineer - clear, concise documentation
+# - Term 35: Version Control Best Practices - track document versions
+
 # Logging Configuration
 logging:
   level: warn

package/.opencode/agents/enforcer.yml

@@ -1,6 +1,18 @@
 name: enforcer
 description: "Enforcer agent for codex compliance and error prevention"
 version: "1.0.0"
+
+# =============================================================================
+# CODEX COMPLIANCE
+# =============================================================================
+# Enforcement must apply these Codex rules:
+# - Term 7: Resolve All Errors - zero tolerance blocking
+# - Term 29: Security by Design - validate all inputs
+# - Term 39: Avoid Syntax Errors - blocking
+# - Term 11: Type Safety First - blocking
+# - Term 46: Import Consistency - blocking
+# - Term 47: Module System Consistency - no mixing ESM/CJS
+
 mode: subagent
 
 # Logging Configuration

package/.opencode/agents/frontend-engineer.yml

@@ -1,6 +1,18 @@
 name: frontend-engineer
 description: "Frontend engineer agent for UI development"
 version: "1.0.0"
+
+# =============================================================================
+# CODEX COMPLIANCE
+# =============================================================================
+# Frontend engineering must follow these Codex rules:
+# - Term 28: Performance Budget Enforcement - bundle size limits, lazy loading
+# - Term 30: Accessibility First - semantic HTML, ARIA labels, keyboard nav
+# - Term 15: Separation of Concerns - keep UI separate from business logic
+# - Term 3: Do Not Over-Engineer - simple component architecture
+# - Term 5: Surgical Fixes - targeted UI changes, minimal re-renders
+# - Term 7: Resolve All Errors - zero tolerance for UI runtime errors
+
 mode: subagent
 
 # Logging Configuration

package/.opencode/agents/frontend-ui-ux-engineer.yml

@@ -3,6 +3,17 @@ description: "Frontend UI/UX Engineer - UI/UX design and user experience special
 version: "1.0.0"
 mode: subagent
 
+# =============================================================================
+# CODEX COMPLIANCE
+# =============================================================================
+# UI/UX engineering must follow these Codex rules:
+# - Term 30: Accessibility First - semantic HTML, ARIA labels, keyboard navigation
+# - Term 28: Performance Budget Enforcement - lazy load non-critical components
+# - Term 15: Separation of Concerns - keep UI separate from business logic
+# - Term 3: Do Not Over-Engineer - simple, intuitive interfaces
+# - Term 35: Version Control Best Practices - atomic commits for UI changes
+# - Term 20: Consistent Code Style - follow design system patterns
+
 # Logging Configuration
 logging:
   level: warn

package/.opencode/agents/growth-strategist.yml

@@ -3,6 +3,17 @@ description: "Marketing expert agent for strategy and campaigns"
 version: "1.0.0"
 mode: subagent
 
+# =============================================================================
+# CODEX COMPLIANCE
+# =============================================================================
+# Growth strategy must follow these Codex rules:
+# - Term 18: Meaningful Naming - clear strategy names and metrics
+# - Term 34: Documentation Updates - document strategy and results
+# - Term 20: Consistent Code Style - consistent framework for analysis
+# - Term 3: Do Not Over-Engineer - simple strategies over complex
+# - Term 17: YAGNI - focus on current growth needs
+# - Term 6: Batched Introspection Cycles - group analysis into cycles
+
 # Logging Configuration
 logging:
   level: warn

package/.opencode/agents/librarian-agents-updater.yml

@@ -3,6 +3,17 @@ description: "Agent for updating and synchronizing agent definitions"
 version: "1.0.0"
 mode: subagent
 
+# =============================================================================
+# CODEX COMPLIANCE
+# =============================================================================
+# Agent management must follow these Codex rules:
+# - Term 10: Single Source of Truth - one authoritative agent definition
+# - Term 35: Version Control Best Practices - track agent changes
+# - Term 42: Code Review Standards - review all agent updates
+# - Term 34: Documentation Updates - document agent changes
+# - Term 20: Consistent Code Style - consistent agent definitions
+# - Term 9: Use Shared Global State - shared agent registry
+
 # Logging Configuration
 logging:
   level: warn

package/.opencode/agents/log-monitor.yml

@@ -3,6 +3,17 @@ description: "Log monitoring agent for system observability"
 version: "1.0.0"
 mode: subagent
 
+# =============================================================================
+# CODEX COMPLIANCE
+# =============================================================================
+# Log monitoring must follow these Codex rules:
+# - Term 33: Logging and Monitoring - structured logging, important events
+# - Term 35: Version Control Best Practices - track log analysis versions
+# - Term 36: Continuous Integration - automated log analysis
+# - Term 7: Resolve All Errors - zero tolerance for monitoring failures
+# - Term 13: Error Boundaries - provide fallback when monitoring fails
+# - Term 51: Graceful Degradation - continue operating during log issues
+
 # Logging Configuration
 logging:
   level: warn

package/.opencode/agents/mobile-developer.yml

@@ -3,6 +3,17 @@ description: "Mobile developer agent for iOS/Android apps"
 version: "1.0.0"
 mode: subagent
 
+# =============================================================================
+# CODEX COMPLIANCE
+# =============================================================================
+# Mobile development must follow these Codex rules:
+# - Term 28: Performance Budget Enforcement - mobile-optimized performance
+# - Term 30: Accessibility First - screen reader compatibility, touch targets
+# - Term 3: Do Not Over-Engineer - simple mobile solutions
+# - Term 15: Separation of Concerns - separate mobile UI from logic
+# - Term 35: Version Control Best Practices - atomic commits
+# - Term 20: Consistent Code Style - follow platform conventions
+
 # Logging Configuration
 logging:
   level: warn

package/.opencode/agents/multimodal-looker.yml

@@ -3,6 +3,17 @@ description: "Multimodal file analysis and interpretation specialist for images,
 version: "1.0.0"
 mode: subagent
 
+# =============================================================================
+# CODEX COMPLIANCE
+# =============================================================================
+# Multimodal analysis must follow these Codex rules:
+# - Term 3: Do Not Over-Engineer - focused analysis of media
+# - Term 17: YAGNI - analyze only what's needed
+# - Term 18: Meaningful Naming - clear descriptions of visual elements
+# - Term 20: Consistent Code Style - consistent interpretation patterns
+# - Term 33: Logging and Monitoring - log analysis results
+# - Term 34: Documentation Updates - document findings
+
 # Logging Configuration
 logging:
   level: warn

package/.opencode/agents/orchestrator.yml

@@ -3,6 +3,17 @@ description: "Orchestrator agent for workflow coordination and task delegation"
 version: "2.0.0"
 mode: primary
 
+# =============================================================================
+# CODEX COMPLIANCE
+# =============================================================================
+# Orchestration must enforce these Codex rules:
+# - Term 52: Agent Spawn Governance - all spawns through AgentSpawnGovernor
+# - Term 53: Subagent Spawning Prevention - subagents cannot spawn other subagents
+# - Term 54: Concurrent Agent Limits - max 8 concurrent, enforce rate limits
+# - Term 59: Multi-Agent Coordination - complex tasks through orchestrator
+# - Term 7: Resolve All Errors - all errors must be resolved before proceeding
+# - Term 8: Prevent Infinite Loops - guarantee termination in all workflows
+
 # State Management Configuration
 state_management:
   enabled: true

package/.opencode/agents/performance-engineer.yml

@@ -3,6 +3,17 @@ description: "Performance engineer agent for optimization"
 version: "1.0.0"
 mode: subagent
 
+# =============================================================================
+# CODEX COMPLIANCE
+# =============================================================================
+# Performance engineering must follow these Codex rules:
+# - Term 28: Performance Budget Enforcement - bundle <2MB, FCP <2s, TTI <5s
+# - Term 33: Logging and Monitoring - log performance metrics, structured logging
+# - Term 7: Resolve All Errors - zero tolerance for performance regressions
+# - Term 5: Surgical Fixes - targeted optimizations, minimal changes
+# - Term 25: Code Rot Prevention - monitor for performance degradation
+# - Term 36: Continuous Integration - automated performance testing
+
 # Logging Configuration
 logging:
   level: warn

package/.opencode/agents/refactorer.yml

@@ -1,6 +1,18 @@
 name: refactorer
 description: "Refactorer agent for technical debt elimination and surgical code improvements"
 version: "1.0.0"
+
+# =============================================================================
+# CODEX COMPLIANCE
+# =============================================================================
+# Refactoring must follow these Codex rules:
+# - Term 5: Surgical Fixes - minimal changes, fix root cause
+# - Term 16: DRY - extract repeated logic into reusable functions
+# - Term 25: Code Rot Prevention - monitor and refactor organically grown code
+# - Term 38: Functionality Retention - preserve existing functionality
+# - Term 7: Resolve All Errors - zero tolerance for refactoring errors
+# - Term 48: Regression Prevention - ensure no regressions from refactoring
+
 mode: subagent
 
 # Error Handling Configuration

package/.opencode/agents/researcher.yml

@@ -3,6 +3,17 @@ description: "Codebase and documentation search specialist"
 version: "1.0.0"
 mode: subagent
 
+# =============================================================================
+# CODEX COMPLIANCE
+# =============================================================================
+# Research must follow these Codex rules:
+# - Term 3: Do Not Over-Engineer - simple, focused searches
+# - Term 17: YAGNI - research only what's needed now
+# - Term 18: Meaningful Naming - clear search terms and results
+# - Term 6: Batched Introspection Cycles - group research into batches
+# - Term 9: Use Shared Global State - prefer shared knowledge over duplication
+# - Term 10: Single Source of Truth - one authoritative source for each fact
+
 # Logging Configuration
 logging:
   level: warn

package/.opencode/agents/security-auditor.yml

@@ -1,6 +1,18 @@
 name: security-auditor
 description: "Security auditor agent for vulnerability detection and compliance"
 version: "1.0.0"
+
+# =============================================================================
+# CODEX COMPLIANCE
+# =============================================================================
+# Security auditing must enforce these Codex rules:
+# - Term 29: Security by Design - validate all inputs, sanitize data, never expose secrets
+# - Term 32: Proper Error Handling - never ignore security errors, provide context
+# - Term 7: Resolve All Errors - zero tolerance for vulnerabilities, all must be resolved
+# - Term 5: Surgical Fixes - targeted security patches, minimal changes
+# - Term 39: Avoid Syntax Errors - code must compile after security fixes
+# - Term 11: Type Safety First - prevent injection attacks via strict types
+
 mode: subagent
 
 # Logging Configuration

package/.opencode/agents/seo-consultant.yml

@@ -3,6 +3,17 @@ description: "SEO specialist agent for technical SEO optimization"
 version: "1.0.0"
 mode: subagent
 
+# =============================================================================
+# CODEX COMPLIANCE
+# =============================================================================
+# SEO optimization must follow these Codex rules:
+# - Term 28: Performance Budget Enforcement - fast page loads improve SEO
+# - Term 30: Accessibility First - semantic HTML improves crawlability
+# - Term 35: Version Control Best Practices - track SEO changes
+# - Term 34: Documentation Updates - document SEO strategy changes
+# - Term 18: Meaningful Naming - clear meta descriptions and titles
+# - Term 20: Consistent Code Style - follow SEO best practices consistently
+
 # Logging Configuration
 logging:
   level: warn