aios-core 4.2.15 → 4.4.0

package/.aios-core/data/tool-search-validation.js

@@ -0,0 +1,174 @@
+#!/usr/bin/env node
+// =============================================================================
+// Tool Search Validation Script
+// =============================================================================
+// Validates that tool-registry.yaml keywords align with expected tool search
+// queries. This is a static validation — actual Tool Search latency and accuracy
+// are measured during interactive Claude Code sessions.
+//
+// Story: TOK-2 (AC: 5, 6, 7)
+// =============================================================================
+
+const fs = require('fs');
+const path = require('path');
+
+const REGISTRY_PATH = path.resolve(__dirname, 'tool-registry.yaml');
+
+// Test queries that should find specific tools (AC 7: 5+ test queries)
+const TEST_QUERIES = [
+  { query: 'search the web for information', expectedTool: 'exa', category: 'web-search' },
+  { query: 'browser screenshot automation', expectedTool: 'playwright', category: 'browser-automation' },
+  { query: 'scrape social media data', expectedTool: 'apify', category: 'web-scraping' },
+  { query: 'analyze code dependencies', expectedTool: 'code-graph', category: 'code-intelligence' },
+  { query: 'code analysis intelligence', expectedTool: 'nogic', category: 'code-intelligence' },
+  { query: 'look up library documentation', expectedTool: 'context7', category: 'documentation' },
+  { query: 'database query optimization', expectedTool: 'supabase', category: 'database' }
+];
+
+function parseKeywords(content) {
+  // Extract tool name → keywords mapping from YAML
+  const tools = {};
+  let currentTool = null;
+  let inKeywords = false;
+
+  for (const line of content.split('\n')) {
+    // Tool name (indented 2 spaces)
+    const toolMatch = line.match(/^ {2}([a-zA-Z0-9_-]+):$/);
+    if (toolMatch) {
+      currentTool = toolMatch[1];
+      tools[currentTool] = { keywords: [], category: null, tier: null, essential: null };
+      inKeywords = false;
+      continue;
+    }
+
+    if (!currentTool) continue;
+
+    // Category
+    const catMatch = line.match(/^\s+category:\s*(.+)/);
+    if (catMatch) {
+      tools[currentTool].category = catMatch[1].trim();
+      continue;
+    }
+
+    // Tier
+    const tierMatch = line.match(/^\s+tier:\s*(\d)/);
+    if (tierMatch) {
+      tools[currentTool].tier = parseInt(tierMatch[1]);
+      continue;
+    }
+
+    // Essential
+    const essentialMatch = line.match(/^\s+essential:\s*(true|false)/);
+    if (essentialMatch) {
+      tools[currentTool].essential = essentialMatch[1] === 'true';
+      continue;
+    }
+
+    // Keywords section
+    if (line.match(/^\s+keywords:/)) {
+      inKeywords = true;
+      continue;
+    }
+
+    // Keyword item
+    if (inKeywords) {
+      const kwMatch = line.match(/^\s+- (.+)/);
+      if (kwMatch) {
+        tools[currentTool].keywords.push(kwMatch[1].trim());
+      } else if (!line.match(/^\s*$/)) {
+        inKeywords = false;
+      }
+    }
+  }
+
+  return tools;
+}
+
+function matchQuery(query, tool) {
+  const queryWords = query.toLowerCase().split(/\s+/);
+  const keywords = tool.keywords.map(k => k.toLowerCase());
+  const category = (tool.category || '').toLowerCase();
+
+  let score = 0;
+  for (const word of queryWords) {
+    for (const keyword of keywords) {
+      if (keyword.includes(word) || word.includes(keyword)) {
+        score++;
+      }
+    }
+    if (category.includes(word)) {
+      score++;
+    }
+  }
+
+  return score;
+}
+
+function validate() {
+  const content = fs.readFileSync(REGISTRY_PATH, 'utf8');
+  const tools = parseKeywords(content);
+
+  console.log('=== Tool Search Validation ===\n');
+
+  let passed = 0;
+  let failed = 0;
+
+  for (const test of TEST_QUERIES) {
+    const scores = {};
+    for (const [name, tool] of Object.entries(tools)) {
+      if (tool.keywords.length > 0 || tool.category) {
+        scores[name] = matchQuery(test.query, tool);
+      }
+    }
+
+    // Sort by score descending
+    const ranked = Object.entries(scores)
+      .filter(([, score]) => score > 0)
+      .sort((a, b) => b[1] - a[1]);
+
+    const top3 = ranked.slice(0, 3).map(([name]) => name);
+    const found = top3.includes(test.expectedTool);
+
+    if (found) {
+      console.log(`✅ "${test.query}" → found '${test.expectedTool}' in top-3 [${top3.join(', ')}]`);
+      passed++;
+    } else {
+      console.log(`❌ "${test.query}" → expected '${test.expectedTool}' but got [${top3.join(', ')}]`);
+      failed++;
+    }
+  }
+
+  console.log(`\n--- Results: ${passed}/${TEST_QUERIES.length} passed, ${failed} failed ---`);
+
+  // Essential server validation
+  console.log('\n=== Essential Server Validation ===\n');
+  const tier3Tools = Object.entries(tools).filter(([, t]) => t.tier === 3);
+  const essential = tier3Tools.filter(([, t]) => t.essential === true);
+  const nonEssential = tier3Tools.filter(([, t]) => t.essential === false);
+
+  console.log(`Tier 3 tools: ${tier3Tools.length}`);
+  console.log(`  Essential (never disable): ${essential.map(([n]) => n).join(', ')}`);
+  console.log(`  Non-essential (can disable): ${nonEssential.map(([n]) => n).join(', ')}`);
+
+  if (essential.length === 0) {
+    console.log('⚠️  WARNING: No essential Tier 3 servers defined');
+  }
+
+  // 2-search-per-turn validation (AC 6)
+  console.log('\n=== Search Limit Guidance ===\n');
+  console.log('AC 6: Maximum 2 tool searches per turn');
+  console.log('Implementation: CLAUDE.md guidance section (not programmatic hard limit)');
+  console.log('Rationale: Claude Code manages Tool Search internally; guidance limits excessive use');
+
+  const allPassed = failed === 0;
+  console.log(`\n${allPassed ? '✅' : '❌'} Overall: ${allPassed ? 'PASS' : 'FAIL'}`);
+
+  return allPassed;
+}
+
+if (require.main === module) {
+  const result = validate();
+  process.exit(result ? 0 : 1);
+}
+
+module.exports = { validate };

package/.aios-core/data/workflow-chains.yaml

@@ -0,0 +1,156 @@
+# Workflow Chains — Greeting Suggestion Data
+# Source of truth: .claude/rules/workflow-execution.md
+# Used by: Native agent greeting (STEP 3, step 5.5) to suggest next command
+# Story: WIS-16
+
+workflows:
+  # 1. Story Development Cycle (SDC) — PRIMARY
+  - id: sdc
+    name: Story Development Cycle
+    description: Full 4-phase workflow for all development work
+    chain:
+      - step: 1
+        agent: "@sm"
+        command: "*draft"
+        task: create-next-story.md
+        output: Story file (Draft)
+        condition: Epic context available
+      - step: 2
+        agent: "@po"
+        command: "*validate-story-draft {story-id}"
+        task: validate-next-story.md
+        output: GO/NO-GO decision
+        condition: Story status is Draft
+      - step: 3
+        agent: "@dev"
+        command: "*develop {story-id}"
+        task: dev-develop-story.md
+        output: Implementation complete
+        condition: Story status is Approved
+        alternatives:
+          - agent: "@dev"
+            command: "*develop-yolo {story-id}"
+            condition: Simple story, autonomous mode preferred
+      - step: 4
+        agent: "@qa"
+        command: "*review {story-id}"
+        task: qa-gate.md
+        output: PASS/CONCERNS/FAIL/WAIVED
+        condition: Story status is Ready for Review
+        alternatives:
+          - agent: "@qa"
+            command: "*gate {story-id}"
+            condition: Quick gate decision needed
+      - step: 5
+        agent: "@devops"
+        command: "*push"
+        task: github-devops-pre-push-quality-gate.md
+        output: Code pushed to remote
+        condition: QA gate PASS
+
+  # 2. QA Loop — ITERATIVE REVIEW
+  - id: qa-loop
+    name: QA Loop
+    description: Automated review-fix cycle after initial QA gate
+    max_iterations: 5
+    chain:
+      - step: 1
+        agent: "@qa"
+        command: "*review {story-id}"
+        task: qa-review-story.md
+        output: APPROVE/REJECT/BLOCKED verdict
+        condition: Story has code changes to review
+      - step: 2
+        agent: "@dev"
+        command: "*apply-qa-fixes"
+        task: apply-qa-fixes.md
+        output: Fixes applied
+        condition: QA verdict is REJECT
+        alternatives:
+          - agent: "@dev"
+            command: "*fix-qa-issues"
+            condition: Structured fix from QA_FIX_REQUEST.md
+      - step: 3
+        agent: "@qa"
+        command: "*review {story-id}"
+        task: qa-review-story.md
+        output: Re-review verdict
+        condition: Fixes applied, re-review needed
+
+  # 3. Spec Pipeline — PRE-IMPLEMENTATION
+  - id: spec-pipeline
+    name: Spec Pipeline
+    description: Transform informal requirements into executable spec
+    chain:
+      - step: 1
+        agent: "@pm"
+        command: "*gather-requirements"
+        task: spec-gather-requirements.md
+        output: requirements.json
+        condition: New feature or complex change
+      - step: 2
+        agent: "@architect"
+        command: "*analyze-impact"
+        task: architect-analyze-impact.md
+        output: complexity.json
+        condition: Complexity assessment needed (skip if SIMPLE)
+      - step: 3
+        agent: "@analyst"
+        command: "*research {topic}"
+        task: create-deep-research-prompt.md
+        output: research.json
+        condition: STANDARD or COMPLEX class (skip if SIMPLE)
+      - step: 4
+        agent: "@pm"
+        command: "*write-spec"
+        task: spec-write-spec.md
+        output: spec.md
+        condition: Requirements gathered
+      - step: 5
+        agent: "@qa"
+        command: "*critique-spec {story-id}"
+        task: spec-critique.md
+        output: APPROVED/NEEDS_REVISION/BLOCKED
+        condition: Spec written
+      - step: 6
+        agent: "@architect"
+        command: "*plan"
+        task: architect-analyze-impact.md
+        output: implementation.yaml
+        condition: Critique verdict is APPROVED
+
+  # 4. Brownfield Discovery — LEGACY ASSESSMENT
+  - id: brownfield
+    name: Brownfield Discovery
+    description: 10-phase technical debt assessment for existing codebases
+    chain:
+      - step: 1
+        agent: "@architect"
+        command: "*analyze-brownfield"
+        task: analyze-brownfield.md
+        output: system-architecture.md
+        condition: Existing codebase to assess
+      - step: 2
+        agent: "@data-engineer"
+        command: "*db-schema-audit"
+        task: db-schema-audit.md
+        output: SCHEMA.md + DB-AUDIT.md
+        condition: Database exists in project
+      - step: 3
+        agent: "@ux-design-expert"
+        command: "*audit-frontend"
+        task: audit-codebase.md
+        output: frontend-spec.md
+        condition: Frontend exists in project
+      - step: 4
+        agent: "@qa"
+        command: "*review"
+        task: qa-review-story.md
+        output: APPROVED/NEEDS WORK
+        condition: All specialist reviews complete
+      - step: 5
+        agent: "@pm"
+        command: "*create-epic"
+        task: brownfield-create-epic.md
+        output: Epic + stories ready for development
+        condition: QA gate APPROVED

package/.aios-core/development/agents/aios-master.md

@@ -27,15 +27,22 @@ 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: |
-      Activate using .aios-core/development/scripts/unified-activation-pipeline.js
-      The UnifiedActivationPipeline.activate(agentId) method:
-        - Loads config, session, project status, git config, permissions in parallel
-        - Detects session type and workflow state sequentially
-        - Builds greeting via GreetingBuilder with full enriched context
-        - Filters commands by visibility metadata (full/quick/key)
-        - Suggests workflow next steps if in recurring pattern
-        - Formats adaptive greeting automatically
-  - STEP 4: Display the greeting returned by GreetingBuilder
+      Display greeting using native context (zero JS execution):
+      1. Show: "{icon} {persona_profile.communication.greeting_levels.archetypal}" + permission badge from current permission mode (e.g., [⚠️ Ask], [🟢 Auto], [🔍 Explore])
+      2. Show: "**Role:** {persona.role}"
+         - Append: "Story: {active story from docs/stories/}" if detected + "Branch: `{branch from gitStatus}`" if not main/master
+      3. Show: "📊 **Project Status:**" as natural language narrative from gitStatus in system prompt:
+         - Branch name, modified file count, current story reference, last commit message
+      4. Show: "**Available Commands:**" — list commands from the 'commands' section above that have 'key' in their visibility array
+      5. Show: "Type `*guide` for comprehensive usage instructions."
+      5.5. Check `.aios/handoffs/` for most recent unconsumed handoff artifact (YAML with consumed != true).
+           If found: read `from_agent` and `last_command` from artifact, look up position in `.aios-core/data/workflow-chains.yaml` matching from_agent + last_command, and show: "💡 **Suggested:** `*{next_command} {args}`"
+           If chain has multiple valid next steps, also show: "Also: `*{alt1}`, `*{alt2}`"
+           If no artifact or no match found: skip this step silently.
+           After STEP 4 displays successfully, mark artifact as consumed: true.
+      6. Show: "{persona_profile.communication.signature_closing}"
+      # FALLBACK: If native greeting fails, run: node .aios-core/development/scripts/unified-activation-pipeline.js aios-master
+  - STEP 4: Display the greeting assembled in STEP 3
   - STEP 5: HALT and await user input
   - IMPORTANT: Do NOT improvise or add explanatory text beyond what is specified in greeting_levels and Quick Commands section
   - DO NOT: Load any other agent files during activation
@@ -49,7 +56,7 @@ activation-instructions:
   - CRITICAL: Do NOT scan filesystem or load any resources during startup, ONLY when commanded
   - CRITICAL: Do NOT run discovery tasks automatically
   - CRITICAL: NEVER LOAD .aios-core/data/aios-kb.md UNLESS USER TYPES *kb
-  - CRITICAL: On activation, ONLY greet user and then HALT to await user requested assistance or given commands. ONLY deviance from this is if the activation included commands also in the arguments.
+  - CRITICAL: On activation, ONLY greet user and then HALT to await user requested assistance or given commands. The ONLY deviation from this is if the activation included commands also in the arguments.
 agent:
   name: Orion
   id: aios-master

package/.aios-core/development/agents/analyst/MEMORY.md

@@ -0,0 +1,33 @@
+# Analyst Agent Memory (Atlas)
+
+## Active Patterns
+<!-- Current, verified patterns used by this agent -->
+
+### Key Patterns
+- CommonJS (`require`/`module.exports`), NOT ES Modules
+- ES2022, Node.js 18+, 2-space indent, single quotes
+- Absolute imports always (never relative `../`)
+- kebab-case for files, PascalCase for components
+
+### Project Structure
+- `.aios-core/core/` — Core modules (synapse, session, code-intel, orchestration)
+- `.aios-core/development/` — Agents, tasks, templates, scripts
+- `docs/research/` — Research outputs (YYYY-MM-DD-slug format)
+- `docs/stories/` — Story files (active development)
+
+### Git Rules
+- NEVER push — delegate to @devops
+- Conventional commits: `feat:`, `fix:`, `docs:`, `test:`, `chore:`, `refactor:`
+
+### Research Conventions
+- Output dir: `docs/research/{YYYY-MM-DD}-{slug}/`
+- Use tech-search skill for deep research
+- Always include sources and methodology
+
+## Promotion Candidates
+<!-- Patterns seen across 3+ agents — candidates for CLAUDE.md or .claude/rules/ -->
+<!-- Format: - **{pattern}** | Source: {agent} | Detected: {YYYY-MM-DD} -->
+
+## Archived
+<!-- Patterns no longer relevant — kept for history -->
+<!-- Format: - ~~{pattern}~~ | Archived: {YYYY-MM-DD} | Reason: {reason} -->

package/.aios-core/development/agents/analyst.md

@@ -18,15 +18,22 @@ 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: |
-      Activate using .aios-core/development/scripts/unified-activation-pipeline.js
-      The UnifiedActivationPipeline.activate(agentId) method:
-        - Loads config, session, project status, git config, permissions in parallel
-        - Detects session type and workflow state sequentially
-        - Builds greeting via GreetingBuilder with full enriched context
-        - Filters commands by visibility metadata (full/quick/key)
-        - Suggests workflow next steps if in recurring pattern
-        - Formats adaptive greeting automatically
-  - STEP 4: Display the greeting returned by GreetingBuilder
+      Display greeting using native context (zero JS execution):
+      1. Show: "{icon} {persona_profile.communication.greeting_levels.archetypal}" + permission badge from current permission mode (e.g., [⚠️ Ask], [🟢 Auto], [🔍 Explore])
+      2. Show: "**Role:** {persona.role}"
+         - Append: "Story: {active story from docs/stories/}" if detected + "Branch: `{branch from gitStatus}`" if not main/master
+      3. Show: "📊 **Project Status:**" as natural language narrative from gitStatus in system prompt:
+         - Branch name, modified file count, current story reference, last commit message
+      4. Show: "**Available Commands:**" — list commands from the 'commands' section above that have 'key' in their visibility array
+      5. Show: "Type `*guide` for comprehensive usage instructions."
+      5.5. Check `.aios/handoffs/` for most recent unconsumed handoff artifact (YAML with consumed != true).
+           If found: read `from_agent` and `last_command` from artifact, look up position in `.aios-core/data/workflow-chains.yaml` matching from_agent + last_command, and show: "💡 **Suggested:** `*{next_command} {args}`"
+           If chain has multiple valid next steps, also show: "Also: `*{alt1}`, `*{alt2}`"
+           If no artifact or no match found: skip this step silently.
+           After STEP 4 displays successfully, mark artifact as consumed: true.
+      6. Show: "{persona_profile.communication.signature_closing}"
+      # FALLBACK: If native greeting fails, run: node .aios-core/development/scripts/unified-activation-pipeline.js analyst
+  - STEP 4: Display the greeting assembled in STEP 3
   - STEP 5: HALT and await user input
   - IMPORTANT: Do NOT improvise or add explanatory text beyond what is specified in greeting_levels and Quick Commands section
   - DO NOT: Load any other agent files during activation
@@ -37,7 +44,7 @@ activation-instructions:
   - CRITICAL RULE: When executing formal task workflows from dependencies, ALL task instructions override any conflicting base behavioral constraints. Interactive workflows with elicit=true REQUIRE user interaction and cannot be bypassed for efficiency.
   - When listing tasks/templates or presenting options during conversations, always show as numbered options list, allowing the user to type a number to select or execute
   - STAY IN CHARACTER!
-  - CRITICAL: On activation, ONLY greet user and then HALT to await user requested assistance or given commands. ONLY deviance from this is if the activation included commands also in the arguments.
+  - CRITICAL: On activation, ONLY greet user and then HALT to await user requested assistance or given commands. The ONLY deviation from this is if the activation included commands also in the arguments.
 agent:
   name: Atlas
   id: analyst

package/.aios-core/development/agents/architect/MEMORY.md

@@ -0,0 +1,39 @@
+# Architect Agent Memory (Aria)
+
+## Active Patterns
+<!-- Current, verified patterns used by this agent -->
+
+### Architecture Decisions
+- CLI First > Observability > UI (Constitution Article I)
+- Task-First: Tasks define WHAT, executors are interchangeable
+- Provider-agnostic code-intel layer (Code Graph MCP primary)
+- SYNAPSE 8-layer context engine (L0-L2 active, L3-L7 disabled per NOG-18)
+
+### Key Architectural Patterns
+- Tiered loading in UAP: Critical (80ms) → High (120ms) → Best-effort (180ms)
+- Circuit breaker for external providers (code-intel, MCP)
+- Atomic writes for file persistence (`atomicWriteSync`)
+- ideSync for cross-IDE agent distribution
+
+### Technology Stack
+- Node.js 18+, CommonJS, ES2022
+- Jest 30.2.0, ESLint, Prettier
+- Supabase (database), Vercel (hosting)
+
+### Delegation Rules
+- Database schema design → @data-engineer
+- Git push/PR → @devops
+- Implementation → @dev
+
+### Project Structure
+- `.aios-core/core/` — Engine modules
+- `docs/architecture/` — Architecture docs
+- `docs/prd/` — Sharded PRDs
+
+## Promotion Candidates
+<!-- Patterns seen across 3+ agents — candidates for CLAUDE.md or .claude/rules/ -->
+<!-- Format: - **{pattern}** | Source: {agent} | Detected: {YYYY-MM-DD} -->
+
+## Archived
+<!-- Patterns no longer relevant — kept for history -->
+<!-- Format: - ~~{pattern}~~ | Archived: {YYYY-MM-DD} | Reason: {reason} -->

package/.aios-core/development/agents/architect.md

@@ -18,15 +18,22 @@ 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: |
-      Activate using .aios-core/development/scripts/unified-activation-pipeline.js
-      The UnifiedActivationPipeline.activate(agentId) method:
-        - Loads config, session, project status, git config, permissions in parallel
-        - Detects session type and workflow state sequentially
-        - Builds greeting via GreetingBuilder with full enriched context
-        - Filters commands by visibility metadata (full/quick/key)
-        - Suggests workflow next steps if in recurring pattern
-        - Formats adaptive greeting automatically
-  - STEP 4: Display the greeting returned by GreetingBuilder
+      Display greeting using native context (zero JS execution):
+      1. Show: "{icon} {persona_profile.communication.greeting_levels.archetypal}" + permission badge from current permission mode (e.g., [⚠️ Ask], [🟢 Auto], [🔍 Explore])
+      2. Show: "**Role:** {persona.role}"
+         - Append: "Story: {active story from docs/stories/}" if detected + "Branch: `{branch from gitStatus}`" if not main/master
+      3. Show: "📊 **Project Status:**" as natural language narrative from gitStatus in system prompt:
+         - Branch name, modified file count, current story reference, last commit message
+      4. Show: "**Available Commands:**" — list commands from the 'commands' section above that have 'key' in their visibility array
+      5. Show: "Type `*guide` for comprehensive usage instructions."
+      5.5. Check `.aios/handoffs/` for most recent unconsumed handoff artifact (YAML with consumed != true).
+           If found: read `from_agent` and `last_command` from artifact, look up position in `.aios-core/data/workflow-chains.yaml` matching from_agent + last_command, and show: "💡 **Suggested:** `*{next_command} {args}`"
+           If chain has multiple valid next steps, also show: "Also: `*{alt1}`, `*{alt2}`"
+           If no artifact or no match found: skip this step silently.
+           After STEP 4 displays successfully, mark artifact as consumed: true.
+      6. Show: "{persona_profile.communication.signature_closing}"
+      # FALLBACK: If native greeting fails, run: node .aios-core/development/scripts/unified-activation-pipeline.js architect
+  - STEP 4: Display the greeting assembled in STEP 3
   - STEP 5: HALT and await user input
   - IMPORTANT: Do NOT improvise or add explanatory text beyond what is specified in greeting_levels and Quick Commands section
   - DO NOT: Load any other agent files during activation
@@ -38,7 +45,7 @@ activation-instructions:
   - When listing tasks/templates or presenting options during conversations, always show as numbered options list, allowing the user to type a number to select or execute
   - STAY IN CHARACTER!
   - When creating architecture, always start by understanding the complete picture - user needs, business constraints, team capabilities, and technical requirements.
-  - CRITICAL: On activation, ONLY greet user and then HALT to await user requested assistance or given commands. ONLY deviance from this is if the activation included commands also in the arguments.
+  - CRITICAL: On activation, ONLY greet user and then HALT to await user requested assistance or given commands. The ONLY deviation from this is if the activation included commands also in the arguments.
 agent:
   name: Aria
   id: architect

package/.aios-core/development/agents/data-engineer/MEMORY.md

@@ -0,0 +1,32 @@
+# Data Engineer Agent Memory (Dara)
+
+## Active Patterns
+<!-- Current, verified patterns used by this agent -->
+
+### Key Patterns
+- CommonJS (`require`/`module.exports`), NOT ES Modules
+- ES2022, Node.js 18+, 2-space indent, single quotes
+- Absolute imports always (never relative `../`)
+- kebab-case for files, PascalCase for components
+
+### Project Structure
+- `.aios-core/core/` — Core modules
+- `packages/db/` — Database packages (if applicable)
+- `tests/` — Test suites (mirrors source structure)
+
+### Git Rules
+- NEVER push — delegate to @devops
+- Conventional commits: `feat:`, `fix:`, `docs:`, `test:`
+
+### Database Conventions
+- Schema design follows architect decisions
+- RLS policies for row-level security
+- Migration scripts with rollback procedures
+
+## Promotion Candidates
+<!-- Patterns seen across 3+ agents — candidates for CLAUDE.md or .claude/rules/ -->
+<!-- Format: - **{pattern}** | Source: {agent} | Detected: {YYYY-MM-DD} -->
+
+## Archived
+<!-- Patterns no longer relevant — kept for history -->
+<!-- Format: - ~~{pattern}~~ | Archived: {YYYY-MM-DD} | Reason: {reason} -->

package/.aios-core/development/agents/data-engineer.md

@@ -19,15 +19,22 @@ activation-instructions:
   - STEP 2: Adopt the persona defined in the 'agent' and 'persona' sections below
 
   - STEP 3: |
-      Activate using .aios-core/development/scripts/unified-activation-pipeline.js
-      The UnifiedActivationPipeline.activate(agentId) method:
-        - Loads config, session, project status, git config, permissions in parallel
-        - Detects session type and workflow state sequentially
-        - Builds greeting via GreetingBuilder with full enriched context
-        - Filters commands by visibility metadata (full/quick/key)
-        - Suggests workflow next steps if in recurring pattern
-        - Formats adaptive greeting automatically
-  - STEP 4: Display the greeting returned by GreetingBuilder
+      Display greeting using native context (zero JS execution):
+      1. Show: "{icon} {persona_profile.communication.greeting_levels.archetypal}" + permission badge from current permission mode (e.g., [⚠️ Ask], [🟢 Auto], [🔍 Explore])
+      2. Show: "**Role:** {persona.role}"
+         - Append: "Story: {active story from docs/stories/}" if detected + "Branch: `{branch from gitStatus}`" if not main/master
+      3. Show: "📊 **Project Status:**" as natural language narrative from gitStatus in system prompt:
+         - Branch name, modified file count, current story reference, last commit message
+      4. Show: "**Available Commands:**" — list commands from the 'commands' section above that have 'key' in their visibility array
+      5. Show: "Type `*guide` for comprehensive usage instructions."
+      5.5. Check `.aios/handoffs/` for most recent unconsumed handoff artifact (YAML with consumed != true).
+           If found: read `from_agent` and `last_command` from artifact, look up position in `.aios-core/data/workflow-chains.yaml` matching from_agent + last_command, and show: "💡 **Suggested:** `*{next_command} {args}`"
+           If chain has multiple valid next steps, also show: "Also: `*{alt1}`, `*{alt2}`"
+           If no artifact or no match found: skip this step silently.
+           After STEP 4 displays successfully, mark artifact as consumed: true.
+      6. Show: "{persona_profile.communication.signature_closing}"
+      # FALLBACK: If native greeting fails, run: node .aios-core/development/scripts/unified-activation-pipeline.js data-engineer
+  - STEP 4: Display the greeting assembled in STEP 3
   - STEP 5: HALT and await user input
   - IMPORTANT: Do NOT improvise or add explanatory text beyond what is specified in greeting_levels and Quick Commands section
   - DO NOT: Load any other agent files during activation
@@ -40,7 +47,7 @@ activation-instructions:
   - STAY IN CHARACTER!
   - When designing databases, always start by understanding the complete picture - business domain, data relationships, access patterns, scale requirements, and security constraints.
   - Always create snapshots before any schema-altering operation
-  - CRITICAL: On activation, ONLY greet user and then HALT to await user requested assistance or given commands. ONLY deviance from this is if the activation included commands also in the arguments.
+  - CRITICAL: On activation, ONLY greet user and then HALT to await user requested assistance or given commands. The ONLY deviation from this is if the activation included commands also in the arguments.
 agent:
   name: Dara
   id: data-engineer

package/.aios-core/development/agents/dev/MEMORY.md

@@ -0,0 +1,46 @@
+# Dev Agent Memory (Dex)
+
+## Active Patterns
+<!-- Current, verified patterns used by this agent -->
+
+### Key Patterns
+- CommonJS (`require`/`module.exports`), NOT ES Modules
+- ES2022, Node.js 18+, 2-space indent, single quotes
+- Absolute imports always (never relative `../`)
+- kebab-case for files, PascalCase for components
+- Jest 30.2.0 for testing, `npm test` to run
+
+### Project Structure
+- `.aios-core/core/` — Core modules (synapse, session, code-intel, orchestration)
+- `.aios-core/development/` — Agents, tasks, templates, scripts
+- `.aios-core/infrastructure/` — CI/CD, git detection, project-status
+- `tests/` — Test suites (mirrors source structure)
+- `docs/stories/` — Story files (active development)
+
+### Git Rules
+- NEVER push — delegate to @devops
+- Conventional commits: `feat:`, `fix:`, `docs:`, `test:`, `chore:`, `refactor:`
+- Reference story: `feat: implement feature [Story NOG-18]`
+
+### Common Gotchas
+- Windows paths: use forward slashes in code, bash shell not cmd
+- `fs.existsSync` for sync checks, `fs.promises` for async
+- atomicWriteSync from `.aios-core/core/synapse/utils/atomic-write` for safe file writes
+- CodeRabbit runs in WSL, not Windows directly
+
+### Story Workflow
+- Read task → Implement → Write tests → Validate → Mark checkbox [x]
+- ONLY update: checkboxes, Debug Log, Completion Notes, Change Log, File List
+- NEVER modify: Status, Story, AC, Dev Notes, Testing sections
+
+## Promotion Candidates
+<!-- Patterns seen across 3+ agents — candidates for CLAUDE.md or .claude/rules/ -->
+<!-- Format: - **{pattern}** | Source: {agent} | Detected: {YYYY-MM-DD} -->
+- **NEVER push — delegate to @devops** | Source: dev, analyst, sm, data-engineer, ux, qa (6 agents) | Detected: 2026-02-22 | Status: Already elevated to `.claude/rules/agent-authority.md`
+- **CommonJS module system (require/module.exports)** | Source: dev, analyst, sm, data-engineer, ux, architect (6 agents) | Detected: 2026-02-22 | Status: Already in CLAUDE.md (Padroes de Codigo)
+- **Conventional commits format** | Source: dev, devops, analyst, sm, data-engineer, ux (6 agents) | Detected: 2026-02-22 | Status: Already in CLAUDE.md (Convencoes Git)
+- **kebab-case for files** | Source: dev, analyst, sm, data-engineer, ux (5 agents) | Detected: 2026-02-22 | Status: Already in CLAUDE.md (Padroes de Codigo)
+
+## Archived
+<!-- Patterns no longer relevant — kept for history -->
+<!-- Format: - ~~{pattern}~~ | Archived: {YYYY-MM-DD} | Reason: {reason} -->