amazingteam 3.0.0

package/.ai-team/memory/architect/module_map.md

@@ -0,0 +1,84 @@
+# Architect Memory - Module Map
+
+This file maintains a living map of the codebase modules and their relationships.
+
+---
+
+## Module Hierarchy
+
+### Core Modules
+
+| Module | Path | Purpose | Dependencies |
+|--------|------|---------|--------------|
+| Agents | `.opencode/agents/` | AI role definitions | None |
+| Skills | `.opencode/skills/` | Reusable AI skills | None |
+| Commands | `.opencode/commands/` | Workflow commands | None |
+| Memory | `.opencode/memory/` | Role-isolated memory | None |
+
+### Application Modules
+
+| Module | Path | Purpose | Dependencies |
+|--------|------|---------|--------------|
+| src | `src/` | Main application code | config, shared |
+| config | `src/config/` | Configuration management | None |
+| shared | `src/shared/` | Shared utilities | None |
+
+---
+
+## Dependency Graph
+
+```
+┌─────────────────────────────────────────────────────┐
+│                    GitHub Issues                     │
+└─────────────────────┬───────────────────────────────┘
+                      │
+                      ▼
+┌─────────────────────────────────────────────────────┐
+│                   Architect Agent                    │
+│  Memory: .opencode/memory/architect/                │
+└─────────────────────┬───────────────────────────────┘
+                      │
+                      ▼
+┌─────────────────────────────────────────────────────┐
+│                  Developer Agent                     │
+│  Memory: .opencode/memory/developer/                │
+└─────────────────────┬───────────────────────────────┘
+                      │
+                      ▼
+┌─────────────────────────────────────────────────────┐
+│                      QA Agent                        │
+│  Memory: .opencode/memory/qa/                       │
+└─────────────────────┬───────────────────────────────┘
+                      │
+                      ▼
+┌─────────────────────────────────────────────────────┐
+│                   Reviewer Agent                     │
+│  Memory: .opencode/memory/reviewer/                 │
+└─────────────────────────────────────────────────────┘
+```
+
+---
+
+## Integration Points
+
+| Integration | Type | Direction | Notes |
+|-------------|------|-----------|-------|
+| GitHub API | REST API | Inbound/Outbound | Issue/PR management |
+| GitHub Actions | Workflow | Inbound | Trigger execution |
+| OpenCode | CLI | Outbound | AI execution engine |
+
+---
+
+## Module Change History
+
+| Date | Module | Change Type | Notes |
+|------|--------|-------------|-------|
+| | | | |
+
+---
+
+## Notes
+
+- Update this file when modules are added, removed, or restructured
+- Keep dependency information accurate
+- Use this map when assessing change impact

package/.ai-team/memory/ci-analyst/failure_patterns.md

@@ -0,0 +1,102 @@
+# CI Analyst Memory - Failure Patterns
+
+This file stores CI failure patterns and resolution knowledge.
+
+---
+
+## Failure Classification
+
+### Build Failures
+
+| Type | Indicators | Quick Fix |
+|------|------------|-----------|
+| Compilation | Syntax/type errors | Fix errors |
+| Dependency | Package resolution | Check lock file |
+| Configuration | Missing config | Add config |
+
+### Test Failures
+
+| Type | Indicators | Quick Fix |
+|------|------------|-----------|
+| Assertion | Logic error | Fix code or test |
+| Timeout | Slow/hanging | Optimize or increase timeout |
+| Flaky | Intermittent | Fix race condition |
+| Environment | Missing resources | Add setup |
+
+### Infrastructure Failures
+
+| Type | Indicators | Quick Fix |
+|------|------------|-----------|
+| Resource | Out of memory/disk | Optimize or increase |
+| Network | Timeout/connection | Add retry or fix endpoint |
+| Permission | Access denied | Check permissions |
+
+---
+
+## Known CI Issues
+
+### Issue: [Issue Name]
+
+**Symptoms**: [What happens]
+
+**Cause**: [Root cause]
+
+**Resolution**: [How to fix]
+
+**Workaround**: [Temporary fix if any]
+
+**Status**: [Open/Fixed/Monitoring]
+
+---
+
+## Failure Log
+
+### [Date] - Build #[number]
+
+**Pipeline**: [Pipeline name]
+
+**Stage**: [Failed stage]
+
+**Error**: [Error message]
+
+**Root Cause**: [Determination]
+
+**Resolution**: [Fix applied]
+
+**Prevention**: [How to prevent recurrence]
+
+---
+
+## Flaky Test Registry
+
+| Test | Frequency | Last Seen | Suspected Cause | Status |
+|------|-----------|-----------|-----------------|--------|
+| | | | | |
+
+---
+
+## CI Infrastructure Notes
+
+### Resource Limits
+
+- Memory: [Limit]
+- Disk: [Limit]
+- Timeout: [Default]
+
+### Environment Variables
+
+- [Key variables to check]
+
+### Known External Dependencies
+
+| Service | Status Page | Last Issue |
+|---------|-------------|------------|
+| | | |
+
+---
+
+## Notes
+
+- Document all failures, patterns help identify root causes faster
+- Keep flaky test registry updated
+- Note infrastructure issues separately from code issues

package/.ai-team/memory/ci-analyst/runbook_references.md

@@ -0,0 +1,87 @@
+# CI Analyst Memory - Runbook References
+
+This file stores references to CI runbooks and investigation procedures.
+
+---
+
+## Runbook Quick Links
+
+### Build Issues
+
+| Problem | Runbook | Location |
+|---------|---------|----------|
+| Compilation failure | Build Debug | docs/runbooks/ci/build-debug.md |
+| Dependency issues | Dependency Resolution | docs/runbooks/ci/dependencies.md |
+| Out of memory | Memory Issues | docs/runbooks/ci/memory.md |
+
+### Test Issues
+
+| Problem | Runbook | Location |
+|---------|---------|----------|
+| Flaky tests | Flaky Test Investigation | docs/runbooks/ci/flaky-tests.md |
+| Test timeout | Timeout Investigation | docs/runbooks/ci/timeouts.md |
+| Test environment | Environment Setup | docs/runbooks/ci/environment.md |
+
+### Infrastructure Issues
+
+| Problem | Runbook | Location |
+|---------|---------|----------|
+| Resource limits | Resource Management | docs/runbooks/ci/resources.md |
+| Network issues | Network Debug | docs/runbooks/ci/network.md |
+| Permission errors | Access Control | docs/runbooks/ci/permissions.md |
+
+---
+
+## Investigation Procedures
+
+### Standard CI Failure Investigation
+
+1. Check error message and logs
+2. Identify failure type (build/test/infra)
+3. Check known issues in failure library
+4. Review recent changes
+5. Attempt local reproduction
+6. Apply fix or escalate
+7. Document resolution
+
+### Flaky Test Investigation
+
+1. Identify failing test
+2. Check failure history
+3. Look for race conditions
+4. Check test isolation
+5. Review mock setup
+6. Add retry or fix
+7. Add to flaky test registry
+
+---
+
+## Common Fixes Quick Reference
+
+| Error Type | Common Fix |
+|------------|------------|
+| Type error | Add type, fix type mismatch |
+| Import error | Fix import path, add to dependencies |
+| Test assertion | Fix logic in code or test |
+| Timeout | Increase timeout, optimize code |
+| Out of memory | Reduce memory usage, split job |
+| Permission | Update CI permissions |
+
+---
+
+## Escalation Paths
+
+| Issue Type | Escalate To |
+|------------|-------------|
+| Code bug | Developer |
+| Test bug | QA |
+| Infrastructure | DevOps |
+| External service | Contact provider |
+
+---
+
+## Notes
+
+- Keep runbook references up to date
+- Add new runbooks as they are created
+- Document any temporary workarounds

package/.ai-team/memory/developer/bug_investigation.md

@@ -0,0 +1,102 @@
+# Developer Memory - Bug Investigation
+
+This file records bug investigation patterns and common issues discovered by the Developer agent.
+
+---
+
+## Bug Categories
+
+### Common Bug Types
+
+| Type | Symptoms | Common Causes | Fix Pattern |
+|------|----------|---------------|-------------|
+| Null/Undefined | Runtime errors | Missing checks | Add null guards |
+| Logic Error | Wrong output | Incorrect conditions | Fix condition logic |
+| Race Condition | Intermittent failures | Async timing | Add synchronization |
+| State Bug | UI inconsistent | Stale state | Force re-render/reload |
+
+---
+
+## Investigation Process
+
+### Step 1: Reproduce
+
+1. Get exact reproduction steps
+2. Create minimal reproduction case
+3. Verify bug exists in current version
+4. Document environment details
+
+### Step 2: Locate
+
+1. Use stack traces to find location
+2. Search for error messages
+3. Trace execution flow
+4. Identify affected files
+
+### Step 3: Analyze
+
+1. Understand expected behavior
+2. Compare with actual behavior
+3. Identify root cause
+4. Consider similar issues
+
+### Step 4: Fix
+
+1. Write failing test
+2. Make minimal fix
+3. Verify fix resolves issue
+4. Check for regressions
+
+---
+
+## Bug Investigation Log
+
+### [Date] - [Bug Title]
+
+**Issue**: [Issue number]
+
+**Symptoms**: [What was observed]
+
+**Root Cause**: [Why it happened]
+
+**Location**: `file:line`
+
+**Fix**: [What was changed]
+
+**Lessons Learned**: [What can be applied elsewhere]
+
+---
+
+## Recurring Issues
+
+| Issue | Frequency | Pattern | Prevention |
+|-------|-----------|---------|------------|
+| | | | |
+
+---
+
+## Debugging Tools
+
+### Useful Commands
+
+```bash
+# Run specific test
+npm test -- --testNamePattern="test name"
+
+# Debug with Node
+node --inspect-brk dist/index.js
+
+# Check types
+npm run typecheck
+
+# Lint
+npm run lint
+```
+
+---
+
+## Notes
+
+- Document bugs that reveal patterns
+- Note investigation techniques that work well
+- Track recurring issues for prevention

package/.ai-team/memory/developer/build_issues.md

@@ -0,0 +1,115 @@
+# Developer Memory - Build Issues
+
+This file records build system knowledge and common issues encountered by the Developer agent.
+
+---
+
+## Build System Overview
+
+### Technology Stack
+
+| Tool | Version | Purpose |
+|------|---------|---------|
+| Node.js | 20+ | Runtime |
+| TypeScript | 5.x | Language |
+| npm | 10.x | Package manager |
+| Jest | 29.x | Testing |
+| ESLint | 8.x | Linting |
+
+### Build Commands
+
+| Command | Purpose |
+|---------|---------|
+| `npm run build` | Compile TypeScript |
+| `npm test` | Run tests |
+| `npm run lint` | Check code style |
+| `npm run typecheck` | Type checking |
+
+---
+
+## Build Issues Log
+
+### [Date] - [Issue Title]
+
+**Error**: [Error message or description]
+
+**Cause**: [What caused the issue]
+
+**Solution**: [How it was resolved]
+
+**Prevention**: [How to avoid in future]
+
+---
+
+## Common Build Issues
+
+### TypeScript Errors
+
+| Error | Cause | Solution |
+|-------|-------|----------|
+| Cannot find module | Missing import or path | Check import path |
+| Type not assignable | Wrong type | Add type assertion or fix type |
+| Property not exists | Missing property | Add property or use optional chaining |
+
+### Test Failures
+
+| Error | Cause | Solution |
+|-------|-------|----------|
+| Timeout | Async operation slow | Increase timeout or fix async |
+| Mock not working | Incorrect mock setup | Check mock configuration |
+| Snapshot mismatch | Output changed | Update snapshot if expected |
+
+### Dependency Issues
+
+| Issue | Cause | Solution |
+|-------|-------|----------|
+| Version conflict | Incompatible versions | Use resolutions or update |
+| Missing peer dependency | Not installed | Install peer dependency |
+| Security vulnerability | Outdated package | Update to secure version |
+
+---
+
+## Build Configuration
+
+### tsconfig.json Key Settings
+
+```json
+{
+  "compilerOptions": {
+    "strict": true,
+    "esModuleInterop": true,
+    "skipLibCheck": true
+  }
+}
+```
+
+### Jest Configuration
+
+```javascript
+module.exports = {
+  preset: 'ts-jest',
+  testEnvironment: 'node',
+  coverageThreshold: {
+    global: { branches: 80, functions: 80, lines: 80 }
+  }
+};
+```
+
+---
+
+## CI/CD Notes
+
+### GitHub Actions Workflow
+
+- Build runs on: `ubuntu-latest`
+- Node version: 20
+- Cache: npm
+- Steps: install → lint → typecheck → test → build
+
+---
+
+## Notes
+
+- Document any build issues and their solutions
+- Keep track of configuration changes
+- Note performance optimization opportunities

package/.ai-team/memory/developer/implementation_notes.md

@@ -0,0 +1,83 @@
+# Developer Memory - Implementation Notes
+
+This file stores implementation-specific knowledge and observations from the Developer agent.
+
+---
+
+## Implementation Patterns
+
+### Preferred Patterns
+
+| Pattern | Use Case | Example |
+|---------|----------|---------|
+| Repository | Data access abstraction | `user.repository.ts` |
+| Service | Business logic | `user.service.ts` |
+| Factory | Complex object creation | `factory.ts` |
+
+### Code Organization
+
+```
+module/
+├── index.ts              # Public API
+├── module.service.ts     # Business logic
+├── module.repository.ts  # Data access
+├── module.types.ts       # Types/interfaces
+└── __tests__/            # Tests
+    ├── module.service.test.ts
+    └── module.repository.test.ts
+```
+
+---
+
+## Implementation Log
+
+### [Date] - [Feature/Bug]
+
+**Task**: [Issue number or description]
+
+**Approach**: [How it was implemented]
+
+**Challenges**: [What was difficult]
+
+**Resolution**: [How challenges were addressed]
+
+---
+
+## Common Implementation Tasks
+
+### Adding a New Feature
+
+1. Create feature branch: `feat/issue-N-description`
+2. Create types/interfaces in `*.types.ts`
+3. Implement business logic in `*.service.ts`
+4. Add data access in `*.repository.ts` if needed
+5. Write unit tests in `__tests__/`
+6. Update documentation
+
+### Fixing a Bug
+
+1. Create fix branch: `fix/issue-N-description`
+2. Write failing test that reproduces the bug
+3. Make minimal fix
+4. Verify test passes
+5. Check for similar issues elsewhere
+6. Update regression tests
+
+---
+
+## Code Quality Checklist
+
+- [ ] Code follows naming conventions
+- [ ] Functions are small and focused
+- [ ] No code duplication
+- [ ] Error handling is appropriate
+- [ ] Tests cover edge cases
+- [ ] Documentation is updated
+
+---
+
+## Notes
+
+- Update this file when learning new patterns or encountering common issues
+- Keep track of implementation strategies that work well
+- Note any recurring challenges

package/.ai-team/memory/failures/failure_library.md

@@ -0,0 +1,103 @@
+# Failure Library
+
+This file stores recurring failure patterns for quick reference and prevention.
+
+**Important**: This is shared operational memory, not global project truth. It captures patterns that recur across tasks to improve response time and prevent repeated mistakes.
+
+---
+
+## Build Failures
+
+### Pattern: [Pattern Name]
+
+**Symptoms**: [What you see]
+
+**Root Cause**: [Why it happens]
+
+**Resolution**: [How to fix]
+
+**Prevention**: [How to prevent]
+
+**Last Occurrence**: [Date/Issue]
+
+---
+
+## Test Failures
+
+### Pattern: [Pattern Name]
+
+**Symptoms**: [What you see]
+
+**Root Cause**: [Why it happens]
+
+**Resolution**: [How to fix]
+
+**Prevention**: [How to prevent]
+
+**Last Occurrence**: [Date/Issue]
+
+---
+
+## Flaky Tests
+
+| Test Name | Symptoms | Suspected Cause | Mitigation |
+|-----------|----------|-----------------|------------|
+| | | | |
+
+---
+
+## Infrastructure Failures
+
+### Pattern: [Pattern Name]
+
+**Symptoms**: [What you see]
+
+**Root Cause**: [Why it happens]
+
+**Resolution**: [How to fix]
+
+**Prevention**: [How to prevent]
+
+**Last Occurrence**: [Date/Issue]
+
+---
+
+## Environment Issues
+
+| Environment | Issue | Cause | Resolution |
+|-------------|-------|-------|------------|
+| Development | | | |
+| CI | | | |
+| Staging | | | |
+| Production | | | |
+
+---
+
+## Recurring Bugs
+
+### Bug Class: [Class Name]
+
+**Pattern**: [Description of the pattern]
+
+**Example**: [Specific occurrence]
+
+**Fix Pattern**: [How to fix this class of bugs]
+
+**Prevention**: [Coding practices to prevent]
+
+---
+
+## Dependency Issues
+
+| Dependency | Version | Issue | Resolution |
+|------------|---------|-------|------------|
+| | | | |
+
+---
+
+## Notes
+
+- Update after each failure investigation
+- Look for patterns before adding new entries
+- Cross-reference with CI analyst memory
+- Use for post-mortem analysis