agileflow 3.3.0 → 3.4.1

package/src/core/experts/analytics/expertise.yaml

@@ -108,106 +108,12 @@ conventions:
   - "Document all events in event catalog"
   - "Test tracking in development before production"
 
-event_categories:
-  navigation:
-    - page_viewed
-    - navigation_clicked
-    - back_clicked
-    - search_performed
-
-  user_actions:
-    - button_clicked
-    - form_submitted
-    - feature_used
-    - content_shared
-
-  conversions:
-    - signup_started
-    - signup_completed
-    - trial_started
-    - purchase_completed
-    - upgrade_clicked
-
-  engagement:
-    - content_viewed
-    - video_played
-    - comment_added
-    - reaction_added
-
-  errors:
-    - error_occurred
-    - api_failed
-    - validation_failed
-
-key_metrics:
-  acquisition:
-    - daily_signups
-    - signup_conversion_rate
-    - acquisition_source
-
-  engagement:
-    - daily_active_users
-    - monthly_active_users
-    - session_duration
-    - feature_adoption_rate
-
-  retention:
-    - day_1_retention
-    - day_7_retention
-    - day_30_retention
-    - churn_rate
-
-  revenue:
-    - monthly_recurring_revenue
-    - average_revenue_per_user
-    - lifetime_value
-
-# Learnings are AUTO-UPDATED by self-improve.md
-# Do not edit manually - let the agent learn from experience
+# Learnings (trimmed - keep 2 most actionable)
 learnings:
   - date: 2025-12-21
-    context: AgileFlow metrics tracking patterns
-    learning: |
-      AgileFlow tracks expertise system metrics via scripts/expertise-metrics.sh script.
-      This script analyzes all expert expertise.yaml files to generate health metrics:
-      - Total number of experts
-      - Experts with learnings vs without
-      - Average learnings per expert
-      - Most active experts (by learning count)
-      - Stale experts (not updated recently)
-      Use this pattern for analyzing distributed knowledge across multiple expertise files.
-
-  - date: 2025-12-21
-    context: Validation script health metrics
-    learning: |
-      AgileFlow validation scripts (scripts/validate-*.sh) provide structured health metrics
-      with PASS/WARN/FAIL counts. Key patterns:
-      - Each validation script outputs structured results (not just exit codes)
-      - Metrics include: total checks, passed, warnings, failures
-      - validate-all.sh aggregates metrics from individual validators
-      - Health dashboard can be built by parsing validation output
-      This pattern enables tracking system health trends over time.
-
-  - date: 2025-12-21
-    context: Story completion metrics from status.json
-    learning: |
-      AgileFlow tracks project progress via docs/09-agents/status.json.
-      Key metrics available:
-      - Total stories vs completed stories (completion percentage)
-      - Stories by status: backlog, in_progress, blocked, completed
-      - WIP (work in progress) count
-      - Stories by epic (epic-level progress)
-      - Average story age (time in current status)
-      Parse status.json to generate project health dashboards and velocity metrics.
+    context: "Expertise metrics"
+    insight: "scripts/expertise-metrics.sh analyzes expertise.yaml files for health: total experts, learnings count, staleness distribution"
 
   - date: 2025-12-21
-    context: Agent activity tracking via log.jsonl
-    learning: |
-      AgileFlow tracks agent activity in docs/09-agents/bus/log.jsonl (append-only).
-      Each line is a JSON object with: timestamp, agent, action, metadata.
-      Key patterns:
-      - Append-only format (never edit existing lines)
-      - Parse line-by-line to analyze agent activity patterns
-      - Track agent invocation frequency, success rates, common errors
-      - Identify most active agents and underutilized agents
-      Use this for agent performance analytics and optimization insights.
+    context: "Story metrics from status.json"
+    insight: "Parse status.json for: completion %, stories by status/epic, WIP count, average story age"

package/src/core/experts/codebase-query/expertise.yaml

@@ -89,79 +89,10 @@ query_types:
       - input: "utils dependencies"
         translation: '--deps="src/lib/utils.js"'
 
-# Available tags (auto-detected from paths)
-available_tags:
-  api:
-    patterns: ["/api/", "/routes/", "/endpoints/", "/controllers/"]
-    description: "API endpoints and routes"
-  ui:
-    patterns: ["/components/", "/ui/", "/views/", "/pages/"]
-    description: "UI components and views"
-  database:
-    patterns: ["/db/", "/database/", "/models/", "/schema/", "/migrations/"]
-    description: "Database models and migrations"
-  auth:
-    patterns: ["/auth/", "/login/", "/session/", "/jwt/", "/oauth/"]
-    description: "Authentication logic"
-  test:
-    patterns: ["/test/", "/tests/", "/__tests__/", "/spec/", "/specs/"]
-    description: "Test files"
-  config:
-    patterns: ["/config/", "/settings/", "/env/"]
-    description: "Configuration files"
-  lib:
-    patterns: ["/lib/", "/utils/", "/helpers/", "/shared/"]
-    description: "Utility libraries"
-  docs:
-    patterns: ["/docs/", "/documentation/"]
-    description: "Documentation files"
-  scripts:
-    patterns: ["/scripts/", "/bin/", "/tools/"]
-    description: "Build and utility scripts"
-  types:
-    patterns: ["/types/", "/typings/", "/interfaces/"]
-    description: "Type definitions"
+# 10 auto-detected tags: api, ui, database, auth, test, config, lib, docs, scripts, types
+# Tag patterns defined in codebase-indexer.js:TAG_PATTERNS
 
-# Natural language patterns
-nl_patterns:
-  - pattern: "where is * defined"
-    query_type: export
-    extraction: "symbol from *"
-  - pattern: "what files use *"
-    query_type: export
-    extraction: "symbol from *"
-  - pattern: "* files"
-    query_type: query
-    extraction: "keyword from *"
-  - pattern: "files with *"
-    query_type: content
-    extraction: "regex from *"
-  - pattern: "* in the codebase"
-    query_type: query
-    extraction: "keyword from *"
-  - pattern: "dependencies of *"
-    query_type: deps
-    extraction: "file path from *"
-  - pattern: "what depends on *"
-    query_type: deps
-    extraction: "file path from *"
-
-# Fallback strategies
-fallbacks:
-  index_unavailable:
-    description: "When index cannot be built or is corrupted"
-    strategy:
-      - "Use Glob tool for file pattern matching"
-      - "Use Grep tool for content searching"
-      - "Combine results manually"
-
-  no_results:
-    description: "When query returns no matches"
-    strategy:
-      - "Try broader search terms"
-      - "Check for typos in symbol names"
-      - "Try content search instead of export search"
-      - "Suggest related tags"
+# NL patterns and fallback strategies handled by agent prompt (omitted for brevity)
 
 # Conventions
 conventions:

package/src/core/experts/compliance/expertise.yaml

@@ -88,80 +88,14 @@ conventions:
   - "Compliance cannot be compromised for convenience"
   - "Annual compliance audits required"
 
-regulations:
-  gdpr:
-    scope: "EU personal data"
-    requirements:
-      - "Explicit consent for processing"
-      - "Right to access, rectification, deletion"
-      - "Data portability"
-      - "72-hour breach notification"
-      - "Data Protection Impact Assessment"
+# Regulations: GDPR, CCPA, HIPAA, SOC2, PCI-DSS (models know details - omitted)
 
-  ccpa:
-    scope: "California residents"
-    requirements:
-      - "Right to know what data collected"
-      - "Right to deletion"
-      - "Right to opt-out of sale"
-      - "Non-discrimination"
-
-  hipaa:
-    scope: "Protected Health Information (PHI)"
-    requirements:
-      - "Access controls"
-      - "Audit trails"
-      - "Encryption"
-      - "Business Associate Agreements"
-
-  soc2:
-    scope: "Service organizations"
-    requirements:
-      - "Security controls"
-      - "Availability"
-      - "Processing integrity"
-      - "Confidentiality"
-      - "Privacy"
-
-  pci_dss:
-    scope: "Payment card data"
-    requirements:
-      - "Network security"
-      - "Cardholder data protection"
-      - "Vulnerability management"
-      - "Access control"
-      - "Monitoring and testing"
-
-# Learnings are AUTO-UPDATED by self-improve.md
+# Learnings (trimmed - keep 2 most actionable)
 learnings:
   - date: 2025-12-21
-    context: AgileFlow commit policy
-    learning: |
-      NO AI attribution in commits. CLAUDE.md explicitly forbids AI footers,
-      Co-Authored-By for AI, emoji robots, or any AI mentions in commit messages.
-      Commits must be clean conventional format (feat/fix/chore/docs).
-      This is a compliance requirement to maintain professional git history.
-
-  - date: 2025-12-21
-    context: AgileFlow secrets management
-    learning: |
-      Gitignored sensitive files include: .npmrc (npm token), .mcp.json (MCP secrets),
-      and CLAUDE.md (internal dev docs). NPM_TOKEN is stored in GitHub Secrets at
-      https://github.com/projectquestorg/AgileFlow/settings/secrets/actions and NEVER
-      committed to repository. This follows security best practices for credential storage.
-
-  - date: 2025-12-21
-    context: AgileFlow audit trail
-    learning: |
-      ADRs in docs/03-decisions/ document architecture decisions for audit trails.
-      status.json in docs/09-agents/ provides complete story tracking history with
-      timestamps, status changes, and agent communications. This creates immutable
-      audit trail of all project decisions and work progress.
+    context: "Commit and secrets policy"
+    insight: "NO AI attribution in commits (clean conventional format). Secrets: .npmrc, CLAUDE.md gitignored. NPM_TOKEN in GitHub Secrets only."
 
   - date: 2025-12-21
-    context: AgileFlow data retention
-    learning: |
-      Auto-archival system (scripts/archive-completed-stories.sh) automatically moves
-      completed stories older than 7 days to docs/09-agents/archive/YYYY-MM.json.
-      This implements data retention policy while keeping status.json lean. Archives
-      organized by month for compliance audits and historical retrieval.
+    context: "Audit trail and retention"
+    insight: "ADRs in docs/03-decisions/, story tracking in status.json. Auto-archival moves completed stories >7 days to archive/YYYY-MM.json."

package/src/core/experts/database/expertise.yaml

@@ -74,30 +74,7 @@ relationships:
 
 # Database patterns the expert should recognize and follow
 patterns:
-  - name: "Soft deletes"
-    description: "Use deleted_at timestamp instead of hard DELETE"
-    location: Tables with user data
-    applies_to: [users, posts, comments]
-
-  - name: "Timestamps"
-    description: "All tables have created_at and updated_at"
-    location: Every table
-    convention: "Auto-managed by ORM or triggers"
-
-  - name: "UUID primary keys"
-    description: "Use UUIDs instead of auto-increment for distributed systems"
-    location: Primary key columns
-    alternative: "Auto-increment for simpler setups"
-
-  - name: "Foreign key naming"
-    description: "Foreign keys follow <table_singular>_id pattern"
-    location: All relationship columns
-    example: "user_id, post_id, category_id"
-
-  - name: "Index naming"
-    description: "Indexes follow idx_<table>_<columns> pattern"
-    location: Index definitions
-    example: "idx_users_email, idx_posts_user_id_created_at"
+  # Generic SQL patterns (soft deletes, timestamps, UUID, FK/index naming) omitted - models know these
 
   - name: "JSON Single Source of Truth"
     description: "AgileFlow uses status.json as primary data store"
@@ -114,39 +91,19 @@ patterns:
     location: docs/09-agents/archive/YYYY-MM.json
     script: scripts/archive-completed-stories.sh
 
-# Conventions the database expert should follow
+# Conventions (AgileFlow-specific only; generic SQL conventions omitted)
 conventions:
-  - "Tables: lowercase, plural (users, posts, categories)"
-  - "Columns: lowercase, snake_case (first_name, created_at)"
-  - "Foreign keys: <table_singular>_id (user_id, post_id)"
-  - "Required columns: id, created_at, updated_at"
-  - "Soft delete column: deleted_at (nullable timestamp)"
-  - "All queries use parameterized statements (prevent SQL injection)"
-  - "Transactions for multi-table operations"
-  - "Migrations must be reversible (up and down)"
-  - "No SELECT * in production code"
-  - "Index columns used in WHERE, JOIN, ORDER BY"
   - "JSON stores: always update 'updated' timestamp when modifying"
   - "JSON Lines: append only, never modify existing lines"
+  - "All queries use parameterized statements (prevent SQL injection)"
+  - "Migrations must be reversible (up and down)"
 
-# Learned from AgileFlow codebase exploration
+# Learnings (trimmed - keep 2 most actionable)
 learnings:
   - date: 2025-12-21
-    context: "Analyzed AgileFlow data storage"
-    insight: "AgileFlow uses JSON files instead of SQL: status.json for tracking, log.jsonl for coordination, archive/ for historical data"
-    source: "docs/09-agents/"
-
-  - date: 2025-12-21
-    context: "Analyzed status.json schema"
-    insight: "Two main collections: epics (EP-ID keys) and stories (US-ID keys); stories have owner, status, priority, estimate, depends_on, test_status"
-    source: "docs/09-agents/status.json"
-
-  - date: 2025-12-21
-    context: "Analyzed archival pattern"
-    insight: "scripts/archive-completed-stories.sh moves done stories >7 days old to archive/YYYY-MM.json to keep status.json performant"
-    source: "scripts/archive-completed-stories.sh, CLAUDE.md"
+    context: "AgileFlow data storage"
+    insight: "JSON files not SQL: status.json (epics EP-ID, stories US-ID with owner/status/priority/estimate/depends_on/test_status), log.jsonl (coordination), archive/ (historical)"
 
   - date: 2025-12-21
-    context: "Analyzed JSON Lines pattern"
-    insight: "bus/log.jsonl uses append-only JSON Lines format for agent messages; each line is independent JSON object"
-    source: "docs/09-agents/bus/log.jsonl"
+    context: "Archival pattern"
+    insight: "archive-completed-stories.sh moves done stories >7 days to archive/YYYY-MM.json. Keeps status.json performant."

package/src/core/experts/documentation/expertise.yaml

@@ -111,149 +111,16 @@ conventions:
   - "Each folder should have README.md explaining its purpose"
   - "NO AI attribution in commits or documentation (see CLAUDE.md)"
 
-# Learned from AgileFlow codebase exploration
+# Learnings (trimmed - keep 3 most actionable)
 learnings:
-  - date: "2026-01-01"
-    auto_generated: true
-    context: "Test learning"
-    insight: "This is a test"
   - date: 2025-12-21
-    context: "Analyzed docs/ directory structure"
-    insight: "10 numbered directories (00-meta through 10-research) organize all project documentation"
-    source: "docs/"
-
-  - date: 2025-12-21
-    context: "Analyzed README structure"
-    insight: "Main README is 537 lines with collapsible sections; uses badges for quick stats"
-    source: "README.md"
-
-  - date: 2025-12-21
-    context: "Analyzed status tracking"
-    insight: "status.json in docs/09-agents/ tracks all stories with owner, status, dependencies, test_status"
-    source: "docs/09-agents/status.json"
-
-  - date: 2025-12-21
-    context: "Analyzed research pattern"
-    insight: "Research notes use YYYYMMDD-slug.md pattern in docs/10-research/"
-    source: "docs/10-research/"
-
-  - date: 2025-12-24
-    context: "Generated command documentation (batch 4 - operations)"
-    insight: "Created 6 comprehensive operation command docs (ci, deploy, changelog, packages, tests, compress) following template with quick start, parameters, examples, workflow, output, and related commands sections"
-    created_files:
-      - "apps/docs/content/docs/commands/ci.mdx (155 lines)"
-      - "apps/docs/content/docs/commands/deploy.mdx (324 lines)"
-      - "apps/docs/content/docs/commands/changelog.mdx (329 lines)"
-      - "apps/docs/content/docs/commands/packages.mdx (377 lines)"
-      - "apps/docs/content/docs/commands/tests.mdx (449 lines)"
-      - "apps/docs/content/docs/commands/compress.mdx (375 lines)"
-    total_lines: 2009
-    source: "packages/cli/src/core/commands/*.md"
-    notes: "All files follow consistent documentation template: frontmatter, quick start, purpose, parameters table, examples with explanations, workflow steps, output/files, and related commands"
-
-  - date: 2026-01-09
-    context: "Created IDE Integrations documentation for AgileFlow"
-    insight: "IDE handler system supports 4 IDEs (Claude Code, Cursor, Windsurf, OpenAI Codex) through plugin architecture. Each IDE has custom config directory (.claude/, .cursor/, .windsurf/, .codex/) and different installation models. Claude Code most advanced (damage control, spawnable agents), OpenAI Codex unique (per-repo skills, user-level prompts, AGENTS.md instructions)"
-    created_files:
-      - "apps/docs/content/docs/features/ide-integrations.mdx (700+ lines)"
-      - "apps/docs/content/docs/features/index.mdx (updated with IDE section)"
-    total_lines: 700
-    source: "packages/cli/tools/cli/installers/ide/ (_base-ide.js, claude-code.js, cursor.js, windsurf.js, codex.js, manager.js)"
-    coverage:
-      - "IDE overview table with config dirs, types, status"
-      - "Quick start for Claude Code (default IDE)"
-      - "Multi-IDE installation instructions"
-      - "Detailed setup for each IDE with directory structure"
-      - "Command access patterns by IDE"
-      - "Claude Code subagent spawning, damage control hooks"
-      - "Cursor unique features, differences from Claude Code"
-      - "Windsurf workflow management, VSCode integration"
-      - "OpenAI Codex dual installation model (per-repo skills, user-level prompts, AGENTS.md)"
-      - "Dynamic IDE handler system, extensibility guide"
-      - "Content injection system explanation"
-      - "Troubleshooting guide for common issues"
-      - "Best practices for IDE selection and multi-IDE usage"
-      - "Configuration management and version control"
-    notes: "Comprehensive 700+ line documentation covering all 4 IDEs with detailed setup, command access, and unique features. Includes handler architecture for IDE developers extending with new IDEs."
-
-  - date: 2026-02-03
-    context: "Generated command documentation (batch 9 - missing commands)"
-    insight: "Created 9 comprehensive command docs for audit, batch, choose, council, install, maintain, rlm, rpi, and workflow commands. All follow consistent template with quick start, parameters table, detailed explanations, usage examples, output formats, and related commands"
-    created_files:
-      - "apps/docs/content/docs/commands/audit.mdx (5.4K)"
-      - "apps/docs/content/docs/commands/batch.mdx (6.2K)"
-      - "apps/docs/content/docs/commands/choose.mdx (5.5K)"
-      - "apps/docs/content/docs/commands/council.mdx (9.3K)"
-      - "apps/docs/content/docs/commands/install.mdx (6.7K)"
-      - "apps/docs/content/docs/commands/maintain.mdx (6.5K)"
-      - "apps/docs/content/docs/commands/rlm.mdx (5.8K)"
-      - "apps/docs/content/docs/commands/rpi.mdx (8.0K)"
-      - "apps/docs/content/docs/commands/workflow.mdx (8.2K)"
-    total_lines: 61_700_characters
-    source: "packages/cli/src/core/commands/*.md (source command files)"
-    coverage:
-      - "audit: Story verification through GSD cycle (tests + acceptance criteria)"
-      - "batch: Functional processing patterns (map/pmap/filter/reduce with loop mode)"
-      - "choose: AI-directed decision making with structured options analysis"
-      - "council: Multi-perspective strategic decisions (3 council members in parallel)"
-      - "install: Post-installation validation with 6 check categories"
-      - "maintain: Periodic health checks (updates, config, status.json, sessions)"
-      - "rlm: Recursive document analysis without context rot (virtualized documents)"
-      - "rpi: Research-Plan-Implement workflow with phase transitions"
-      - "workflow: Parameterized workflow templates (built-in + custom)"
-    notes: "All 9 files follow consistent documentation template extracted from source .md files: quick start, parameters table, detailed descriptions, usage examples with output, status indicators, best practices, error handling, and related commands. Ready for docs site publication."
+    context: "Docs directory structure"
+    insight: "10 numbered directories (00-meta through 10-research); status.json is single source of truth for story tracking"
 
   - date: 2026-02-07
-    context: "Audited and fixed command documentation drift"
-    insight: "Systematically compared all 50 source commands against their documentation counterparts. Found critical drift in configure.mdx (50% outdated) and babysit.mdx (missing Smart Detection, Story Claiming, Logic Audit features). Fixed both with comprehensive updates preserving all source details."
-    modified_files:
-      - "apps/docs/content/docs/commands/configure.mdx (major rewrite - 200+ lines added)"
-      - "apps/docs/content/docs/commands/babysit.mdx (200+ lines added)"
-    drift_issues_fixed:
-      - "configure.mdx: Added 5 profile types (full, basic, minimal, experimental, none)"
-      - "configure.mdx: Added hierarchical menu system documentation (5 categories, 4 max options)"
-      - "configure.mdx: Added custom profiles (save, export, import, delete)"
-      - "configure.mdx: Added all available features (8 total: SessionStart, PreCompact, RalphLoop, SelfImprove, Archival, StatusLine, AskUserQuestion, Tmux, Shell Aliases, Auto-Update, CLAUDE.md Rules)"
-      - "configure.mdx: Added maintenance commands (detect, migrate, upgrade, repair, list-scripts)"
-      - "configure.mdx: Added troubleshooting section with solutions"
-      - "babysit.mdx: Added Smart Detection section (auto-enable Loop/Visual/Coverage/Conditions modes)"
-      - "babysit.mdx: Added Story Claiming section (multi-session coordination, prevent conflicts)"
-      - "babysit.mdx: Added Logic Audit integration (post-implementation quality check)"
-      - "babysit.mdx: Updated Loop Mode to show auto-detection instead of explicit parameters"
-    verified_good:
-      - "council.mdx: Comprehensive and current"
-      - "audit.mdx: Good alignment with source"
-      - "choose.mdx: Good alignment with source"
-    quality_gates:
-      - "Description matches source frontmatter ✓"
-      - "Parameters documented with types and defaults ✓"
-      - "Examples are copy-paste ready ✓"
-      - "Usage patterns match source implementation ✓"
-      - "Links to related commands accurate ✓"
-      - "No outdated information remains ✓"
-      - "All new features from source documented ✓"
-      - "Formatting consistent (tables, code blocks, bullets) ✓"
-    source: "packages/cli/src/core/commands/*.md vs apps/docs/content/docs/commands/*.mdx"
-    notes: "Used systematic comparison approach: extracted descriptions, parameters, and features from 50 source commands against documentation. Prioritized commands with most feature additions: babysit (Smart Detection, Story Claiming, Logic Audit), configure (profiles, hierarchical menus). All changes preserve source accuracy while making docs more discoverable and comprehensive."
+    context: "Documentation drift detection"
+    insight: "Source commands drift from docs site; systematic comparison needed. configure.mdx and babysit.mdx had 50%+ outdated content"
 
   - date: 2026-02-14
-    context: "Audited README files for v3.0.2 - IDE config locations and badge accuracy"
-    insight: "Found and fixed 2 discrepancies between root and npm README files: (1) Cursor IDE config was .cursor/rules/ instead of .cursor/commands/ (verified against cursor.js installer), (2) OpenAI Codex location was incomplete - missing ~/.codex/prompts/ directory for user-level prompts. Both files now synchronized and identical."
-    fixed_issues:
-      - "packages/cli/README.md line 42: Updated Cursor from .cursor/rules/agileflow/ to .cursor/commands/agileflow/"
-      - "packages/cli/README.md line 44: Updated Codex from .codex/skills/ to .codex/skills/ and ~/.codex/prompts/"
-    verified:
-      - "Badge counts: 93 commands (correct), 45 agents (correct), dynamic skills (correct)"
-      - "All 11 referenced documentation files exist"
-      - "All 6 example commands/agents exist in source"
-      - "External links functional: npm (HTTP 200), GitHub (HTTP 200), docs site (HTTP 200)"
-      - "README files now identical (diff shows no differences)"
-    quality_gates:
-      - "Documentation current with v3.0.2 code ✓"
-      - "Counts verified against actual source files ✓"
-      - "IDE config verified against installers ✓"
-      - "All example commands/agents exist ✓"
-      - "No deprecated information remains ✓"
-      - "Two README files synchronized ✓"
-    source: "README.md, packages/cli/README.md, packages/cli/tools/cli/installers/ide/*.js"
-    notes: "Learned that IDE config locations can drift from documentation. Always verify against actual installer code (cursor.js, codex.js, etc.) not assumptions. OpenAI Codex has dual installation model (per-repo .codex/skills/ + user-level ~/.codex/prompts/) - this must be documented completely."
+    context: "IDE config documentation accuracy"
+    insight: "Always verify IDE config paths against installer code (cursor.js, codex.js), not assumptions. Codex has dual model (per-repo + user-level)"

package/src/core/experts/integrations/expertise.yaml

@@ -102,132 +102,12 @@ conventions:
   - "Mock external services in tests"
   - "Document all required environment variables"
 
-integrations_catalog:
-  payment:
-    - name: Stripe
-      env_vars: [STRIPE_API_KEY, STRIPE_WEBHOOK_SECRET]
-      webhooks: [payment.completed, subscription.updated, refund.created]
-    - name: PayPal
-      env_vars: [PAYPAL_CLIENT_ID, PAYPAL_CLIENT_SECRET]
-    - name: Square
-      env_vars: [SQUARE_ACCESS_TOKEN]
-
-  email:
-    - name: SendGrid
-      env_vars: [SENDGRID_API_KEY]
-      webhooks: [email.delivered, email.bounced, email.complained]
-    - name: Mailgun
-      env_vars: [MAILGUN_API_KEY, MAILGUN_DOMAIN]
-
-  auth:
-    - name: Auth0
-      env_vars: [AUTH0_DOMAIN, AUTH0_CLIENT_ID, AUTH0_CLIENT_SECRET]
-    - name: Google OAuth
-      env_vars: [GOOGLE_CLIENT_ID, GOOGLE_CLIENT_SECRET]
-    - name: GitHub OAuth
-      env_vars: [GITHUB_CLIENT_ID, GITHUB_CLIENT_SECRET]
-
-  messaging:
-    - name: Twilio
-      env_vars: [TWILIO_ACCOUNT_SID, TWILIO_AUTH_TOKEN]
-      webhooks: [message.delivered, message.failed]
-
-  storage:
-    - name: AWS S3
-      env_vars: [AWS_ACCESS_KEY_ID, AWS_SECRET_ACCESS_KEY, AWS_S3_BUCKET]
-    - name: Google Cloud Storage
-      env_vars: [GCS_PROJECT_ID, GCS_BUCKET]
-
-# Learnings are AUTO-UPDATED by self-improve.md
-# Do not edit manually - let the agent learn from experience
+# Learnings (trimmed - keep 2 most actionable)
 learnings:
-  - title: "IDE Integration Pattern: Multi-Platform Configuration"
-    date: 2025-12-21
-    context: "AgileFlow supports 3 different IDEs (Claude Code, Cursor, Windsurf) with different config directory structures"
-    learning: |
-      IDE integrations require platform-specific installers that handle different configuration locations:
-      - Claude Code: `.claude/commands/` for slash commands
-      - Cursor: `.cursor/commands/` for slash commands
-      - Windsurf: `.windsurf/commands/` for slash commands
-
-      Implementation approach:
-      1. Create IDE-specific installer scripts in `installers/ide/` directory
-      2. Each installer knows its target config directory structure
-      3. Use shared installation logic with IDE-specific paths
-      4. Test each installer independently
-
-      Key files: `installers/ide/install-claude-code.js`, `install-cursor.js`, `install-windsurf.js`
-    impact: "Enables AgileFlow to work across multiple development environments without manual configuration"
-
-  - title: "npm Registry Integration via GitHub Actions"
-    date: 2025-12-21
-    context: "AgileFlow automates publishing to npm registry when git tags are pushed"
-    learning: |
-      GitHub Actions can automate npm publishing with proper token management:
-      1. Store NPM_TOKEN in GitHub Secrets (repo settings)
-      2. Create workflow triggered by tag push pattern `v*.*.*`
-      3. Verify version consistency before publishing
-      4. Use `npm publish --access public` for public packages
-
-      Critical checks in workflow:
-      - Extract version from git tag
-      - Verify package.json version matches tag
-      - Verify CHANGELOG.md has release notes for version
-      - Install dependencies if package-lock.json exists
-      - Publish with NPM_TOKEN authentication
-
-      Key file: `.github/workflows/npm-publish.yml`
-    impact: "Eliminates manual publishing errors and ensures consistent release process"
-
-  - title: "Dynamic Content Injection at Install Time"
-    date: 2025-12-21
-    context: "AgileFlow uses placeholders in source files that get replaced with current content during installation"
-    learning: |
-      Dynamic content injection pattern avoids maintenance overhead for lists that change frequently:
-
-      Source files use placeholders:
-      - `<!-- {{AGENT_LIST}} -->` - Gets replaced with current agent list
-      - `<!-- {{COMMAND_LIST}} -->` - Gets replaced with current command list
-      - `<!-- {{SKILL_LIST}} -->` - Gets replaced with current skill list
-
-      Installer scans source files during installation and:
-      1. Detects placeholder patterns
-      2. Generates current list from filesystem (e.g., scan agents/ directory)
-      3. Replaces placeholder with formatted list
-      4. Writes installed file with injected content
-
-      Benefits:
-      - Zero maintenance overhead (no manual list updates)
-      - Always current (generated at install time)
-      - Source files stay clean and simple
-      - Installed files have complete information
-
-      Used in: babysit.md, expert.md, and other command files
-    impact: "Reduces maintenance burden and prevents stale documentation"
-
-  - title: "CI/CD Integration: Automated Release Workflow"
-    date: 2025-12-21
-    context: "AgileFlow uses release script + GitHub Actions for end-to-end release automation"
-    learning: |
-      Complete CI/CD integration requires coordinating multiple systems:
-
-      1. Local automation (release.sh script):
-         - Version bumping across multiple package.json files
-         - Git commit and tag creation
-         - GitHub release creation via `gh` CLI
-
-      2. Remote automation (GitHub Actions):
-         - Triggered by tag push
-         - Version verification (tag matches package.json)
-         - CHANGELOG verification (release notes exist)
-         - npm publishing with token authentication
-
-      3. Integration points:
-         - Git tags trigger GitHub Actions workflows
-         - GitHub Secrets provide secure token storage
-         - Workflow status appears in GitHub UI
-         - npm registry reflects published version
+  - date: 2025-12-21
+    context: "IDE integration pattern"
+    insight: "IDE-specific installers in installers/ide/ handle different config dirs (.claude/, .cursor/, .windsurf/). Shared logic in _base-ide.js, overrides per IDE."
 
-      Key insight: Split concerns between local (developer workflow) and remote (publishing) automation
-      Key files: `scripts/release.sh`, `.github/workflows/npm-publish.yml`
-    impact: "Provides reliable, repeatable release process that reduces human error"
+  - date: 2025-12-21
+    context: "Content injection"
+    insight: "Placeholders ({{AGENT_LIST}}, {{COMMAND_LIST}}) in source files replaced at install time. Zero runtime overhead."