strray-ai 1.9.0 → 1.10.0

package/.opencode/OpenCode.json

@@ -0,0 +1,58 @@
+{
+  "agent": {
+    "orchestrator": {
+      "mode": "subagent"
+    },
+    "enforcer": {
+      "mode": "subagent"
+    },
+    "architect": {
+      "mode": "subagent"
+    },
+    "testing-lead": {
+      "mode": "subagent"
+    },
+    "bug-triage-specialist": {
+      "mode": "subagent"
+    },
+    "code-reviewer": {
+      "mode": "subagent"
+    },
+    "security-auditor": {
+      "mode": "subagent"
+    },
+    "refactorer": {
+      "mode": "subagent"
+    },
+    "researcher": {
+      "mode": "subagent"
+    },
+    "log-monitor": {
+      "mode": "subagent"
+    },
+    "strategist": {
+      "mode": "subagent"
+    },
+    "tech-writer": {
+      "mode": "subagent"
+    },
+    "code-analyzer": {
+      "mode": "subagent"
+    },
+    "frontend-ui-ux-engineer": {
+      "mode": "subagent"
+    },
+    "seo-consultant": {
+      "mode": "subagent"
+    },
+    "content-creator": {
+      "mode": "subagent"
+    },
+    "growth-strategist": {
+      "mode": "subagent"
+    },
+    "multimodal-looker": {
+      "mode": "subagent"
+    }
+  }
+}

package/.opencode/agents/architect.yml

@@ -14,6 +14,40 @@ mode: subagent
 # - Term 3: Do Not Over-Engineer - simple solutions over complex
 # - Term 17: YAGNI - don't build what isn't needed
 
+# =============================================================================
+# INTEGRATION RESPONSIBILITIES
+# =============================================================================
+# When designing new components or features, the architect MUST:
+#
+# 1. FULL APPLICATION INTEGRATION:
+#    - Identify ALL files that need modification across the entire codebase
+#    - Update imports, exports, and references throughout the application
+#    - Ensure new code integrates seamlessly with existing patterns
+#    - Check for circular dependencies and break them appropriately
+#    - Verify all integration points work together
+#
+# 2. DOCUMENTATION UPDATES (MANDATORY):
+#    - Update README.md when adding new features or changing behavior
+#    - Update AGENTS.md when adding/modifying agent capabilities
+#    - Update CHANGELOG.md with architectural changes
+#    - Add/update architecture documentation in docs/
+#    - Update API documentation when endpoints change
+#    - Cross-reference all affected documentation
+#
+# 3. CONFIGURATION UPDATES:
+#    - Update routing configurations
+#    - Update feature flags when adding new capabilities
+#    - Update environment configurations if needed
+#    - Check opencode.json and config files
+#
+# 4. TEST INTEGRATION:
+#    - Ensure tests exist for new integration points
+#    - Update existing tests that may be affected
+#    - Add integration tests for cross-component functionality
+#
+# NEVER leave documentation or integration incomplete. All changes must be
+# fully integrated and documented before marking work as complete.
+
 # State Management Configuration
 state_management:
   enabled: true

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

@@ -13,6 +13,40 @@ version: "1.0.0"
 # - Term 5: Surgical Fixes - targeted API changes, minimal breaking changes
 # - Term 7: Resolve All Errors - zero tolerance for API errors
 
+# =============================================================================
+# INTEGRATION & DOCUMENTATION RESPONSIBILITIES
+# =============================================================================
+# When implementing backend changes, you MUST:
+#
+# 1. FULL APPLICATION INTEGRATION:
+#    - Update ALL files that reference the changed API
+#    - Update routes, controllers, services consistently
+#    - Update database migrations if schema changes
+#    - Update environment configurations
+#    - Check for broken imports or exports
+#    - Verify all integration tests pass
+#
+# 2. API DOCUMENTATION (MANDATORY):
+#    - Update README.md with new endpoints or changes
+#    - Update AGENTS.md when agent capabilities change
+#    - Document request/response schemas
+#    - Update API examples in documentation
+#    - Document authentication changes
+#    - Mark deprecated endpoints
+#
+# 3. CONFIGURATION UPDATES:
+#    - Update routing tables
+#    - Update environment variables documentation
+#    - Update feature flags if adding new capabilities
+#    - Check docker-compose.yml if services change
+#
+# 4. DEPENDENCY CHECKS:
+#    - Update package.json if new dependencies added
+#    - Document new dependencies in README
+#    - Check for version compatibility
+#
+# NEVER leave API changes undocumented or partially integrated.
+
 mode: subagent
 
 # Logging Configuration

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

@@ -13,6 +13,45 @@ version: "1.0.0"
 # - Term 48: Regression Prevention - preserve functionality
 # - Term 46: Import Consistency - consistent imports
 
+# =============================================================================
+# CODE REVIEW RESPONSIBILITIES
+# =============================================================================
+# When reviewing code changes, the code-reviewer MUST verify:
+#
+# 1. FULL INTEGRATION CHECK:
+#    - All files modified consistently across the codebase
+#    - No orphaned imports or exports
+#    - All integration points properly connected
+#    - Configuration files updated if needed
+#    - Routing and paths updated throughout
+#
+# 2. DOCUMENTATION UPDATES (BLOCKING ISSUE):
+#    - README.md updated for new features or behavioral changes
+#    - AGENTS.md updated when agent capabilities change
+#    - CHANGELOG.md updated with user-facing changes
+#    - API documentation updated for endpoint changes
+#    - Configuration docs updated if settings change
+#    - ALWAYS reject code that lacks required documentation updates
+#
+# 3. CROSS-REFERENCE VALIDATION:
+#    - Verify all referenced files exist
+#    - Check for broken links in documentation
+#    - Ensure consistent naming across docs and code
+#    - Validate code examples in documentation
+#
+# 4. COMPLETENESS CHECK:
+#    - No TODO comments in production code
+#    - No placeholder implementations
+#    - All functionality fully implemented
+#    - All error paths handled
+#
+# REJECTION CRITERIA:
+# - Code that changes behavior without updating README
+# - New features without documentation
+# - API changes without updating AGENTS.md or API docs
+# - Partial implementations
+# - Missing integration points
+
 mode: subagent
 
 # Logging Configuration

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

@@ -14,6 +14,40 @@ mode: subagent
 # - Term 3: Do Not Over-Engineer - clear, concise documentation
 # - Term 35: Version Control Best Practices - track document versions
 
+# =============================================================================
+# DOCUMENTATION INTEGRATION RESPONSIBILITIES
+# =============================================================================
+# When generating documentation, you MUST:
+#
+# 1. FULL DOCUMENTATION ECOSYSTEM:
+#    - Update README.md with new features or major changes
+#    - Update AGENTS.md when agent capabilities change
+#    - Update CHANGELOG.md for version changes
+#    - Cross-reference all related documentation
+#    - Maintain consistency across all docs
+#
+# 2. INTEGRATION VERIFICATION:
+#    - Check all internal links are valid
+#    - Verify code examples work
+#    - Ensure file paths are correct
+#    - Validate markdown formatting
+#    - Check image/asset references
+#
+# 3. COMPLETENESS REQUIREMENTS:
+#    - No placeholder text or incomplete sections
+#    - All features documented
+#    - API endpoints fully documented
+#    - Configuration options explained
+#    - Usage examples provided
+#
+# 4. MULTI-FILE COORDINATION:
+#    - Update all affected docs in single session
+#    - Ensure version numbers consistent
+#    - Sync changes across README, AGENTS, CHANGELOG
+#    - Update table of contents if structure changes
+#
+# NEVER submit partial documentation or leave docs inconsistent with code.
+
 # Logging Configuration
 logging:
   level: warn

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

@@ -13,6 +13,41 @@ version: "1.0.0"
 # - Term 5: Surgical Fixes - targeted UI changes, minimal re-renders
 # - Term 7: Resolve All Errors - zero tolerance for UI runtime errors
 
+# =============================================================================
+# INTEGRATION & DOCUMENTATION RESPONSIBILITIES
+# =============================================================================
+# When implementing frontend changes, you MUST:
+#
+# 1. FULL APPLICATION INTEGRATION:
+#    - Update ALL components that use the changed code
+#    - Update imports/exports consistently across the app
+#    - Update routing if new pages added
+#    - Update state management if store changes
+#    - Check for broken references or paths
+#    - Verify styling consistency
+#
+# 2. UI DOCUMENTATION (MANDATORY):
+#    - Update README.md with new features or UI changes
+#    - Update component documentation
+#    - Add/update usage examples
+#    - Document accessibility features
+#    - Update AGENTS.md if agent UI capabilities change
+#    - Screenshots for major UI changes
+#
+# 3. CONFIGURATION UPDATES:
+#    - Update build configuration if needed
+#    - Update environment variables
+#    - Check webpack/vite config changes
+#    - Update public assets if needed
+#
+# 4. STYLE & THEME INTEGRATION:
+#    - Update design system documentation
+#    - Ensure theme consistency
+#    - Update CSS variables if styling changes
+#    - Check responsive breakpoints
+#
+# NEVER leave UI changes undocumented or partially integrated.
+
 mode: subagent
 
 # Logging Configuration

package/.opencode/agents/refactorer.yml

@@ -13,6 +13,39 @@ version: "1.0.0"
 # - Term 7: Resolve All Errors - zero tolerance for refactoring errors
 # - Term 48: Regression Prevention - ensure no regressions from refactoring
 
+# =============================================================================
+# REFACTORING INTEGRATION RESPONSIBILITIES
+# =============================================================================
+# When refactoring code, you MUST:
+#
+# 1. FULL APPLICATION UPDATES:
+#    - Update ALL files that reference the refactored code
+#    - Update imports/exports throughout the application
+#    - Check for broken references or dependencies
+#    - Update tests to match refactored code
+#    - Verify no orphaned code remains
+#
+# 2. DOCUMENTATION UPDATES (CRITICAL):
+#    - Update README.md if public APIs changed
+#    - Update AGENTS.md if agent interfaces changed
+#    - Update API documentation for signature changes
+#    - Update code comments explaining new structure
+#    - Document breaking changes in CHANGELOG.md
+#
+# 3. CROSS-REFERENCE VALIDATION:
+#    - Check all files importing the changed module
+#    - Verify configuration files still valid
+#    - Check documentation examples still work
+#    - Validate agent references are correct
+#
+# 4. INTEGRATION TESTING:
+#    - Run all tests after refactoring
+#    - Test integration points manually if needed
+#    - Verify no functionality lost
+#    - Check performance not degraded
+#
+# NEVER leave refactoring incomplete or break existing integrations.
+
 mode: subagent
 
 # Error Handling Configuration

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

@@ -14,6 +14,43 @@ mode: subagent
 # - Term 3: Do Not Over-Engineer - simple, clear documentation
 # - Term 35: Version Control Best Practices - track doc changes
 
+# =============================================================================
+# DOCUMENTATION INTEGRATION RESPONSIBILITIES
+# =============================================================================
+# When creating or updating documentation, you MUST:
+#
+# 1. CROSS-REFERENCE ALL DOCUMENTATION:
+#    - Update README.md with new features/changes
+#    - Update AGENTS.md when agent capabilities change
+#    - Update CHANGELOG.md for user-facing changes
+#    - Update API documentation for endpoint changes
+#    - Update configuration docs if settings change
+#    - Check docs/ folder for related documentation
+#    - Ensure consistency across all docs
+#
+# 2. INTEGRATION VERIFICATION:
+#    - Verify all links work (internal and external)
+#    - Check code examples compile/run
+#    - Ensure file paths are correct
+#    - Validate agent references
+#    - Cross-check with actual code implementation
+#
+# 3. REQUIRED DOCUMENTATION FILES:
+#    - README.md - main project documentation
+#    - AGENTS.md - agent capabilities and usage
+#    - CHANGELOG.md - version history
+#    - API docs - endpoint documentation
+#    - Configuration docs - setup instructions
+#
+# 4. COMPLETENESS CHECK:
+#    - No placeholder text ("TODO", "FIXME", "coming soon")
+#    - All sections have content
+#    - Code examples are complete
+#    - Screenshots/images are included if needed
+#    - All features documented
+#
+# NEVER leave documentation incomplete or inconsistent with code.
+
 # Logging Configuration
 logging:
   level: warn

package/.opencode/codex.codex

@@ -1,5 +1,5 @@
 {
-  "version": "1.7.5",
+  "version": "1.10.0",
   "terms": [
     1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 20, 21, 22, 23, 24, 25, 26, 27, 28, 29, 30, 31, 32, 33, 34, 35, 36, 37, 38, 39, 40, 41, 42, 43, 44, 45, 46, 47, 48, 49, 50, 51, 52, 53, 54, 55, 56, 57, 58, 59, 60
   ],

package/.opencode/enforcer-config.json

@@ -1,6 +1,6 @@
 {
   "framework": "StringRay 1.0.0",
-  "version": "1.7.5",
+  "version": "1.10.0",
   "description": "Codex-compliant framework configuration for Credible UI project",
   "thresholds": {
     "bundleSize": {
@@ -174,7 +174,7 @@
       }
     },
     "codex": {
-      "version": "1.7.5",
+      "version": "1.10.0",
       "terms": [1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 15, 24, 29, 32, 38, 42, 43],
       "principles": [
         "progressive-prod-ready-code",