sinapse-ai 7.7.2 → 7.7.4

package/.codex/scripts/generate-codex-greeting.js

@@ -0,0 +1,101 @@
+#!/usr/bin/env node
+'use strict';
+
+const fs = require('fs');
+const path = require('path');
+const { spawnSync } = require('child_process');
+
+const PROJECT_ROOT = path.resolve(__dirname, '..', '..');
+const SHARED_GREETING_SCRIPT = path.join(
+  PROJECT_ROOT,
+  '.sinapse-ai',
+  'development',
+  'scripts',
+  'generate-greeting.js',
+);
+
+function generateFallbackGreeting(agentId) {
+  return '## Activation\n\n' +
+    `\`${agentId}\` ready\n\n` +
+    'Type `*help` to see available commands.';
+}
+
+function isGenericSharedFallback(output, agentId) {
+  const normalized = String(output || '').trim();
+  if (!normalized) return true;
+
+  const genericPatterns = [
+    `\u2705 ${agentId} Agent ready\n\nType \`*help\` to see available commands.`,
+    `\u2705 Agent ${agentId} loaded`,
+    `\ud83d\udc51 ${agentId} Agent ready`,
+  ];
+  const looksLikeGenericActivation = genericPatterns.some((pattern) => normalized.includes(pattern));
+  const hasHelpPrompt = normalized.includes('Type `*help` to see available commands.');
+  const hasRichCodexGreeting = normalized.includes('AI Agent Squads for Claude Code');
+
+  return (looksLikeGenericActivation && hasHelpPrompt && !hasRichCodexGreeting);
+}
+
+function trySharedGreeting(agentId) {
+  if (!fs.existsSync(SHARED_GREETING_SCRIPT)) return '';
+
+  const result = spawnSync(process.execPath, [SHARED_GREETING_SCRIPT, agentId], {
+    cwd: PROJECT_ROOT,
+    encoding: 'utf8',
+  });
+
+  const output = String(result.stdout || '').trim();
+  if (!output || isGenericSharedFallback(output, agentId)) {
+    return '';
+  }
+
+  return output;
+}
+
+function extractStaticGreeting(agentId) {
+  const agentPath = path.join(PROJECT_ROOT, '.codex', 'agents', `${agentId}.md`);
+  if (!fs.existsSync(agentPath)) return '';
+
+  const content = fs.readFileSync(agentPath, 'utf8');
+  const firstBlock = content.match(
+    /When this agent is activated, you MUST display this greeting EXACTLY as your first output[\s\S]*?```([\s\S]*?)```/i,
+  );
+  const secondBlock = content.match(/Then display:\s*```([\s\S]*?)```/i);
+
+  const parts = [];
+  if (firstBlock && firstBlock[1]) {
+    parts.push(firstBlock[1].trim());
+  }
+  if (secondBlock && secondBlock[1]) {
+    parts.push(secondBlock[1].trim());
+  }
+
+  return parts.join('\n\n').trim();
+}
+
+function generateCodexGreeting(agentId) {
+  return trySharedGreeting(agentId) ||
+    extractStaticGreeting(agentId) ||
+    generateFallbackGreeting(agentId);
+}
+
+function main() {
+  const agentId = process.argv[2];
+  if (!agentId) {
+    console.error('Usage: node .codex/scripts/generate-codex-greeting.js <agent-id>');
+    process.exit(1);
+  }
+
+  console.log(generateCodexGreeting(agentId));
+}
+
+if (require.main === module) {
+  main();
+}
+
+module.exports = {
+  generateCodexGreeting,
+  extractStaticGreeting,
+  trySharedGreeting,
+  isGenericSharedFallback,
+};

package/.codex/scripts/resolve-codex-command.js

@@ -0,0 +1,147 @@
+#!/usr/bin/env node
+'use strict';
+
+const fs = require('fs');
+const path = require('path');
+
+const PROJECT_ROOT = path.resolve(__dirname, '..', '..');
+const REGISTRY_PATH = path.join(PROJECT_ROOT, '.codex', 'command-registry.json');
+
+function loadCommandRegistry(projectRoot = PROJECT_ROOT) {
+  const registryPath = path.join(projectRoot, '.codex', 'command-registry.json');
+  const raw = fs.readFileSync(registryPath, 'utf8');
+  return JSON.parse(raw);
+}
+
+function normalizeAgentInput(value) {
+  return String(value || '').trim().replace(/^@/, '').toLowerCase();
+}
+
+function normalizeCommandInput(value) {
+  return String(value || '').trim().replace(/^\*/, '').toLowerCase();
+}
+
+function resolveAgent(registry, agentInput) {
+  const normalized = normalizeAgentInput(agentInput);
+  const matches = [];
+
+  for (const [agentId, agentSpec] of Object.entries(registry.agents || {})) {
+    const aliases = [agentId, ...(agentSpec.aliases || [])]
+      .map((alias) => normalizeAgentInput(alias));
+    if (aliases.includes(normalized)) {
+      matches.push({ agentId, agentSpec });
+    }
+  }
+
+  if (matches.length > 1) {
+    throw new Error(`Ambiguous Codex agent "${agentInput}"`);
+  }
+
+  return matches[0] || null;
+}
+
+function resolveCommand(agentSpec, commandInput) {
+  const normalized = normalizeCommandInput(commandInput);
+  const matches = [];
+
+  for (const [commandId, commandSpec] of Object.entries(agentSpec.commands || {})) {
+    const aliases = [commandId, ...(commandSpec.aliases || [])]
+      .map((alias) => normalizeCommandInput(alias));
+    if (aliases.includes(normalized)) {
+      matches.push({ commandId, commandSpec });
+    }
+  }
+
+  if (matches.length > 1) {
+    throw new Error(`Ambiguous Codex command "${commandInput}"`);
+  }
+
+  return matches[0] || null;
+}
+
+function resolveCodexCommand(agentInput, commandInput, projectRoot = PROJECT_ROOT) {
+  const registry = loadCommandRegistry(projectRoot);
+  const agent = resolveAgent(registry, agentInput);
+  if (!agent) {
+    throw new Error(`Unknown Codex agent "${agentInput}"`);
+  }
+
+  const command = resolveCommand(agent.agentSpec, commandInput);
+  if (!command) {
+    throw new Error(`Unknown Codex command "${commandInput}" for agent "${agent.agentId}"`);
+  }
+
+  return {
+    agentId: agent.agentId,
+    skillId: agent.agentSpec.skillId,
+    commandId: command.commandId,
+    kind: command.commandSpec.kind,
+    target: command.commandSpec.target,
+    resources: command.commandSpec.resources || [],
+    sourceOfTruth: agent.agentSpec.sourceOfTruth,
+  };
+}
+
+function parseArgs(argv = process.argv.slice(2)) {
+  const args = argv.filter((arg) => !arg.startsWith('--'));
+  const flags = new Set(argv.filter((arg) => arg.startsWith('--')));
+  return {
+    agent: args[0],
+    command: args[1],
+    json: flags.has('--json'),
+  };
+}
+
+function formatHumanResult(result) {
+  const lines = [
+    `Agent: ${result.agentId}`,
+    `Skill: ${result.skillId}`,
+    `Command: ${result.commandId}`,
+    `Kind: ${result.kind}`,
+    `Target: ${result.target}`,
+    `Source: ${result.sourceOfTruth}`,
+  ];
+
+  if (result.resources.length > 0) {
+    lines.push('Resources:');
+    lines.push(...result.resources.map((resource) => `- ${resource}`));
+  }
+
+  return lines.join('\n');
+}
+
+function main() {
+  const args = parseArgs();
+  if (!args.agent || !args.command) {
+    console.error('Usage: node .codex/scripts/resolve-codex-command.js <agent> <command> [--json]');
+    process.exit(1);
+  }
+
+  try {
+    const result = resolveCodexCommand(args.agent, args.command);
+    if (args.json) {
+      console.log(JSON.stringify(result, null, 2));
+    } else {
+      console.log(formatHumanResult(result));
+    }
+  } catch (error) {
+    console.error(error.message);
+    process.exit(1);
+  }
+}
+
+if (require.main === module) {
+  main();
+}
+
+module.exports = {
+  REGISTRY_PATH,
+  loadCommandRegistry,
+  normalizeAgentInput,
+  normalizeCommandInput,
+  resolveAgent,
+  resolveCommand,
+  resolveCodexCommand,
+  parseArgs,
+  formatHumanResult,
+};

package/.codex/skills/sinapse-analyst/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: sinapse-analyst
-description: Business Analyst (Atlas). Use for market research, competitive analysis, user research, brainstorming session facilitation, structured ideation workshops, feasibility studies, i...
+description: Business Analyst (Scope). Use for market research, competitive analysis, user research, brainstorming session facilitation, structured ideation workshops, feasibility studies, i...
 ---
 
 # SINAPSE Business Analyst Activator
@@ -10,9 +10,10 @@ Use for market research, competitive analysis, user research, brainstorming sess
 
 ## Activation Protocol
 1. Load `.sinapse-ai/development/agents/analyst.md` as source of truth (fallback: `.codex/agents/analyst.md`).
-2. Adopt this agent persona and command system.
-3. Generate greeting via `node .sinapse-ai/development/scripts/generate-greeting.js analyst` and show it first.
-4. Stay in this persona until the user asks to switch or exit.
+2. Generate greeting via `node .sinapse-ai/development/scripts/generate-greeting.js analyst` and show it first.
+3. Adopt this agent persona and command system.
+4. If a starred command is invoked in Codex, resolve it via `node .codex/scripts/resolve-codex-command.js sinapse-analyst <command>` when a registry mapping exists.
+5. Stay in this persona until the user asks to switch or exit.
 
 ## Starter Commands
 - `*help` - Show all available commands with descriptions

package/.codex/skills/sinapse-architect/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: sinapse-architect
-description: Architect (Aria). Use for system architecture (fullstack, backend, frontend, infrastructure), technology stack selection (technical evaluation), API design (REST/GraphQL/tRPC/We...
+description: Architect (Stratum). Use for system architecture (fullstack, backend, frontend, infrastructure), technology stack selection (technical evaluation), API design (REST/GraphQL/tRPC...
 ---
 
 # SINAPSE Architect Activator
@@ -10,9 +10,10 @@ Use for system architecture (fullstack, backend, frontend, infrastructure), tech
 
 ## Activation Protocol
 1. Load `.sinapse-ai/development/agents/architect.md` as source of truth (fallback: `.codex/agents/architect.md`).
-2. Adopt this agent persona and command system.
-3. Generate greeting via `node .sinapse-ai/development/scripts/generate-greeting.js architect` and show it first.
-4. Stay in this persona until the user asks to switch or exit.
+2. Generate greeting via `node .sinapse-ai/development/scripts/generate-greeting.js architect` and show it first.
+3. Adopt this agent persona and command system.
+4. If a starred command is invoked in Codex, resolve it via `node .codex/scripts/resolve-codex-command.js sinapse-architect <command>` when a registry mapping exists.
+5. Stay in this persona until the user asks to switch or exit.
 
 ## Starter Commands
 - `*help` - Show all available commands with descriptions

package/.codex/skills/sinapse-data-engineer/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: sinapse-data-engineer
-description: Database Architect & Operations Engineer (Dara). Use for database design, schema architecture, Supabase configuration, RLS policies, migrations, query optimization, data modelin...
+description: Database Architect & Operations Engineer (Tensor). Use for database design, schema architecture, Supabase configuration, RLS policies, migrations, query optimization, data model...
 ---
 
 # SINAPSE Database Architect & Operations Engineer Activator
@@ -10,9 +10,10 @@ Use for database design, schema architecture, Supabase configuration, RLS polici
 
 ## Activation Protocol
 1. Load `.sinapse-ai/development/agents/data-engineer.md` as source of truth (fallback: `.codex/agents/data-engineer.md`).
-2. Adopt this agent persona and command system.
-3. Generate greeting via `node .sinapse-ai/development/scripts/generate-greeting.js data-engineer` and show it first.
-4. Stay in this persona until the user asks to switch or exit.
+2. Generate greeting via `node .sinapse-ai/development/scripts/generate-greeting.js data-engineer` and show it first.
+3. Adopt this agent persona and command system.
+4. If a starred command is invoked in Codex, resolve it via `node .codex/scripts/resolve-codex-command.js sinapse-data-engineer <command>` when a registry mapping exists.
+5. Stay in this persona until the user asks to switch or exit.
 
 ## Starter Commands
 - `*help` - Show all available commands with descriptions

package/.codex/skills/sinapse-dev/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: sinapse-dev
-description: Full Stack Developer (Dex). Use for code implementation, debugging, refactoring, and development best practices
+description: Full Stack Developer (Pixel). Use for code implementation, debugging, refactoring, and development best practices
 ---
 
 # SINAPSE Full Stack Developer Activator
@@ -10,9 +10,10 @@ Use for code implementation, debugging, refactoring, and development best practi
 
 ## Activation Protocol
 1. Load `.sinapse-ai/development/agents/developer.md` as source of truth (fallback: `.codex/agents/developer.md`).
-2. Adopt this agent persona and command system.
-3. Generate greeting via `node .sinapse-ai/development/scripts/generate-greeting.js dev` and show it first.
-4. Stay in this persona until the user asks to switch or exit.
+2. Generate greeting via `node .sinapse-ai/development/scripts/generate-greeting.js dev` and show it first.
+3. Adopt this agent persona and command system.
+4. If a starred command is invoked in Codex, resolve it via `node .codex/scripts/resolve-codex-command.js sinapse-dev <command>` when a registry mapping exists.
+5. Stay in this persona until the user asks to switch or exit.
 
 ## Starter Commands
 - `*help` - Show all available commands with descriptions

package/.codex/skills/sinapse-devops/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: sinapse-devops
-description: GitHub Repository Manager & DevOps Specialist (Gage). Use for repository operations, version management, CI/CD, quality gates, and GitHub push operations. ONLY agent authorized...
+description: GitHub Repository Manager & DevOps Specialist (Pipeline). Use for repository operations, version management, CI/CD, quality gates, and GitHub push operations. ONLY agent authori...
 ---
 
 # SINAPSE GitHub Repository Manager & DevOps Specialist Activator
@@ -10,9 +10,10 @@ Use for repository operations, version management, CI/CD, quality gates, and Git
 
 ## Activation Protocol
 1. Load `.sinapse-ai/development/agents/devops.md` as source of truth (fallback: `.codex/agents/devops.md`).
-2. Adopt this agent persona and command system.
-3. Generate greeting via `node .sinapse-ai/development/scripts/generate-greeting.js devops` and show it first.
-4. Stay in this persona until the user asks to switch or exit.
+2. Generate greeting via `node .sinapse-ai/development/scripts/generate-greeting.js devops` and show it first.
+3. Adopt this agent persona and command system.
+4. If a starred command is invoked in Codex, resolve it via `node .codex/scripts/resolve-codex-command.js sinapse-devops <command>` when a registry mapping exists.
+5. Stay in this persona until the user asks to switch or exit.
 
 ## Starter Commands
 - `*help` - Show all available commands with descriptions

package/.codex/skills/sinapse-orqx/SKILL.md

@@ -1,28 +1,23 @@
 ---
 name: sinapse-orqx
-description: SINAPSE Master Orchestrator & Framework Developer (Orion). Use when you need comprehensive expertise across all domains, framework component creation/modification, workflow orchest...
+description: "Sinapse Master — Supreme Ecosystem Orchestrator" ("Imperator"). ALWAYS as the default agent. Imperator is the first point of contact for EVERY request. Routes directly to @spec...
 ---
 
-# SINAPSE SINAPSE Master Orchestrator & Framework Developer Activator
+# SINAPSE "Sinapse Master — Supreme Ecosystem Orchestrator" Activator
 
 ## When To Use
-Use when you need comprehensive expertise across all domains, framework component creation/modification, workflow orchestration, or running tasks that don't require a specialized persona.
+ALWAYS as the default agent. Imperator is the first point of contact for EVERY request. Routes directly to @specialist when clear, or to @{domain}-orqx when complex.
 
 ## Activation Protocol
-1. Load `.sinapse-ai/development/agents/sinapse-orqx.md` as source of truth (fallback: `.codex/agents/sinapse-orqx.md`).
-2. Adopt this agent persona and command system.
-3. Generate greeting via `node .sinapse-ai/development/scripts/generate-greeting.js sinapse-orqx` and show it first.
-4. Stay in this persona until the user asks to switch or exit.
+1. Load `.codex/agents/sinapse-orqx.md` as source of truth.
+2. Keep `.sinapse-ai/development/agents/sinapse-orqx.md` as the shared parity reference.
+3. Generate greeting via `node .codex/scripts/generate-codex-greeting.js sinapse-orqx` and show it first.
+4. Adopt this agent persona and command system.
+5. If a starred command is invoked in Codex, resolve it via `node .codex/scripts/resolve-codex-command.js sinapse-orqx <command>` when a registry mapping exists.
+6. Stay in this persona until the user asks to switch or exit.
 
 ## Starter Commands
-- `*help` - Show all available commands with descriptions
-- `*kb` - Toggle KB mode (loads SINAPSE Method knowledge)
-- `*status` - Show current context and progress
-- `*guide` - Show comprehensive usage guide for this agent
-- `*exit` - Exit agent mode
-- `*create` - Create new SINAPSE component (agent, task, workflow, template, checklist)
-- `*modify` - Modify existing SINAPSE component
-- `*update-manifest` - Update team manifest
+- `*help` - List available commands
 
 ## Non-Negotiables
 - Follow `.sinapse-ai/constitution.md`.

package/.codex/skills/sinapse-pm/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: sinapse-pm
-description: Product Manager (Morgan). Use for PRD creation (greenfield and brownfield), epic creation and management, product strategy and vision, feature prioritization (MoSCoW, RICE), roa...
+description: Product Manager (Beacon). Use for PRD creation (greenfield and brownfield), epic creation and management, product strategy and vision, feature prioritization (MoSCoW, RICE), roa...
 ---
 
 # SINAPSE Product Manager Activator
@@ -10,9 +10,10 @@ Use for PRD creation (greenfield and brownfield), epic creation and management,
 
 ## Activation Protocol
 1. Load `.sinapse-ai/development/agents/project-lead.md` as source of truth (fallback: `.codex/agents/project-lead.md`).
-2. Adopt this agent persona and command system.
-3. Generate greeting via `node .sinapse-ai/development/scripts/generate-greeting.js pm` and show it first.
-4. Stay in this persona until the user asks to switch or exit.
+2. Generate greeting via `node .sinapse-ai/development/scripts/generate-greeting.js pm` and show it first.
+3. Adopt this agent persona and command system.
+4. If a starred command is invoked in Codex, resolve it via `node .codex/scripts/resolve-codex-command.js sinapse-pm <command>` when a registry mapping exists.
+5. Stay in this persona until the user asks to switch or exit.
 
 ## Starter Commands
 - `*help` - Show all available commands with descriptions

package/.codex/skills/sinapse-po/SKILL.md

@@ -10,9 +10,10 @@ Use for backlog management, story refinement, acceptance criteria, sprint planni
 
 ## Activation Protocol
 1. Load `.sinapse-ai/development/agents/product-lead.md` as source of truth (fallback: `.codex/agents/product-lead.md`).
-2. Adopt this agent persona and command system.
-3. Generate greeting via `node .sinapse-ai/development/scripts/generate-greeting.js po` and show it first.
-4. Stay in this persona until the user asks to switch or exit.
+2. Generate greeting via `node .sinapse-ai/development/scripts/generate-greeting.js po` and show it first.
+3. Adopt this agent persona and command system.
+4. If a starred command is invoked in Codex, resolve it via `node .codex/scripts/resolve-codex-command.js sinapse-po <command>` when a registry mapping exists.
+5. Stay in this persona until the user asks to switch or exit.
 
 ## Starter Commands
 - `*help` - Show all available commands with descriptions

package/.codex/skills/sinapse-qa/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: sinapse-qa
-description: Test Architect & Quality Advisor (Quinn). Use for comprehensive test architecture review, quality gate decisions, and code improvement. Provides thorough analysis including requ...
+description: Test Architect & Quality Advisor (Litmus). Use for comprehensive test architecture review, quality gate decisions, and code improvement. Provides thorough analysis including req...
 ---
 
 # SINAPSE Test Architect & Quality Advisor Activator
@@ -10,19 +10,20 @@ Use for comprehensive test architecture review, quality gate decisions, and code
 
 ## Activation Protocol
 1. Load `.sinapse-ai/development/agents/quality-gate.md` as source of truth (fallback: `.codex/agents/quality-gate.md`).
-2. Adopt this agent persona and command system.
-3. Generate greeting via `node .sinapse-ai/development/scripts/generate-greeting.js qa` and show it first.
-4. Stay in this persona until the user asks to switch or exit.
+2. Generate greeting via `node .sinapse-ai/development/scripts/generate-greeting.js qa` and show it first.
+3. Adopt this agent persona and command system.
+4. If a starred command is invoked in Codex, resolve it via `node .codex/scripts/resolve-codex-command.js sinapse-qa <command>` when a registry mapping exists.
+5. Stay in this persona until the user asks to switch or exit.
 
 ## Starter Commands
 - `*help` - Show all available commands with descriptions
-- `*code-review {scope}` - Run automated review (scope: uncommitted or committed)
-- `*review {story}` - Comprehensive story review with gate decision
-- `*review-build {story}` - 10-phase structured QA review (Epic 6) - outputs qa_report.md
-- `*gate {story}` - Create quality gate decision
-- `*nfr-assess {story}` - Validate non-functional requirements
-- `*risk-profile {story}` - Generate risk assessment matrix
-- `*create-fix-request {story}` - Generate QA_FIX_REQUEST.md for @developer with issues to fix
+- `*code-review` - Run automated review (scope: uncommitted or committed)
+- `*review` - Comprehensive story review with gate decision
+- `*gate` - Create quality gate decision
+- `*nfr-assess` - Validate non-functional requirements
+- `*risk-profile` - Generate risk assessment matrix
+- `*security-check` - Run 8-point security vulnerability scan
+- `*test-design` - Create comprehensive test scenarios
 
 ## Non-Negotiables
 - Follow `.sinapse-ai/constitution.md`.

package/.codex/skills/sinapse-sm/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: sinapse-sm
-description: Scrum Master (River). Use for user story creation from PRD, story validation and completeness checking, acceptance criteria definition, story refinement, sprint planning, backlo...
+description: Scrum Master (Sync). Use for user story creation from PRD, story validation and completeness checking, acceptance criteria definition, story refinement, sprint planning, backlog...
 ---
 
 # SINAPSE Scrum Master Activator
@@ -10,9 +10,10 @@ Use for user story creation from PRD, story validation and completeness checking
 
 ## Activation Protocol
 1. Load `.sinapse-ai/development/agents/sprint-lead.md` as source of truth (fallback: `.codex/agents/sprint-lead.md`).
-2. Adopt this agent persona and command system.
-3. Generate greeting via `node .sinapse-ai/development/scripts/generate-greeting.js sm` and show it first.
-4. Stay in this persona until the user asks to switch or exit.
+2. Generate greeting via `node .sinapse-ai/development/scripts/generate-greeting.js sm` and show it first.
+3. Adopt this agent persona and command system.
+4. If a starred command is invoked in Codex, resolve it via `node .codex/scripts/resolve-codex-command.js sinapse-sm <command>` when a registry mapping exists.
+5. Stay in this persona until the user asks to switch or exit.
 
 ## Starter Commands
 - `*help` - Show all available commands with descriptions

package/.codex/skills/sinapse-squad-creator/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: sinapse-squad-creator
-description: Squad Creator (Craft). Use to create, validate, publish and manage squads
+description: Squad Creator (Loom). Use to create, validate, publish and manage squads
 ---
 
 # SINAPSE Squad Creator Activator
@@ -10,9 +10,10 @@ Use to create, validate, publish and manage squads
 
 ## Activation Protocol
 1. Load `.sinapse-ai/development/agents/squad-creator.md` as source of truth (fallback: `.codex/agents/squad-creator.md`).
-2. Adopt this agent persona and command system.
-3. Generate greeting via `node .sinapse-ai/development/scripts/generate-greeting.js squad-creator` and show it first.
-4. Stay in this persona until the user asks to switch or exit.
+2. Generate greeting via `node .sinapse-ai/development/scripts/generate-greeting.js squad-creator` and show it first.
+3. Adopt this agent persona and command system.
+4. If a starred command is invoked in Codex, resolve it via `node .codex/scripts/resolve-codex-command.js sinapse-squad-creator <command>` when a registry mapping exists.
+5. Stay in this persona until the user asks to switch or exit.
 
 ## Starter Commands
 - `*help` - Show all available commands with descriptions

package/.codex/skills/sinapse-ux-design-expert/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: sinapse-ux-design-expert
-description: UX/UI Designer & Design System Architect (Uma). Complete design workflow - user research, wireframes, design systems, token extraction, component building, and quality assurance
+description: UX/UI Designer & Design System Architect (Mosaic). Complete design workflow - user research, wireframes, design systems, token extraction, component building, and quality assurance
 ---
 
 # SINAPSE UX/UI Designer & Design System Architect Activator
@@ -10,9 +10,10 @@ Complete design workflow - user research, wireframes, design systems, token extr
 
 ## Activation Protocol
 1. Load `.sinapse-ai/development/agents/ux-design-expert.md` as source of truth (fallback: `.codex/agents/ux-design-expert.md`).
-2. Adopt this agent persona and command system.
-3. Generate greeting via `node .sinapse-ai/development/scripts/generate-greeting.js ux-design-expert` and show it first.
-4. Stay in this persona until the user asks to switch or exit.
+2. Generate greeting via `node .sinapse-ai/development/scripts/generate-greeting.js ux-design-expert` and show it first.
+3. Adopt this agent persona and command system.
+4. If a starred command is invoked in Codex, resolve it via `node .codex/scripts/resolve-codex-command.js sinapse-ux-design-expert <command>` when a registry mapping exists.
+5. Stay in this persona until the user asks to switch or exit.
 
 ## Starter Commands
 - `*help` - List available commands

package/.codex/tasks/convene-sinapse-council.md

@@ -0,0 +1,28 @@
+# Codex Council Task
+
+## Purpose
+
+Frame a strategic decision for council-style deliberation in Codex.
+
+## Required Inputs
+
+- Strategic question
+
+## Steps
+
+1. Read `.codex/catalog.json`, `.codex/agents/sinapse-orqx.md`, and `.codex/agents/council-orqx.md`.
+2. Restate the decision in a way that is actionable and falsifiable.
+3. Identify which strategic lenses or squads should weigh in.
+4. Summarize:
+   - core decision
+   - options
+   - tradeoffs
+   - recommended route
+5. If execution needs a concrete framework command, resolve it via `.codex/command-registry.json`.
+
+## Output Contract
+
+- Strategic decision frame
+- Options and tradeoffs
+- Recommended council/orqx route
+- Next action

package/.codex/tasks/create-sinapse-strategic-brief.md

@@ -0,0 +1,29 @@
+# Codex Strategic Brief Task
+
+## Purpose
+
+Generate a Codex-compatible strategic brief that pulls the minimum relevant squads into scope.
+
+## Required Inputs
+
+- Topic or initiative to brief
+
+## Steps
+
+1. Read `.codex/catalog.json` and `.codex/agents/sinapse-orqx.md`.
+2. Classify the topic by domains, urgency, and decision horizon.
+3. Identify the minimum relevant orqx set for the brief.
+4. If the brief depends on a framework workflow step, resolve the starred command via `.codex/command-registry.json`.
+5. Produce a concise brief with:
+   - objective
+   - squads/orqx to involve
+   - key unknowns
+   - risks
+   - recommended next action
+
+## Output Contract
+
+- Strategic brief
+- Recommended squad/orqx set
+- Key risks and unknowns
+- Immediate next step

package/.codex/tasks/onboard-sinapse-codex.md

@@ -0,0 +1,34 @@
+# Codex Onboard Task
+
+## Purpose
+
+Guide the user through the real Codex operating surface for SINAPSE in this repository.
+
+## Required Inputs
+
+- Optional focus area or domain
+
+## Steps
+
+1. Read `AGENTS.md` and `.codex/catalog.json`.
+2. Explain the preferred activation path in Codex:
+   - `/skills` -> `sinapse-<agent>`
+   - `@agent` aliases from `AGENTS.md`
+3. Explain the two Codex layers:
+   - `.codex/skills` for activation
+   - `.codex/agents` for expanded catalog and specialist context
+4. Explain the validated operator commands:
+   - `npm run sync:ide:codex`
+   - `npm run validate:codex-sync`
+   - `npm run validate:codex-integration`
+   - `npm run validate:codex-commands`
+   - `npm run validate:codex-skills`
+   - `npm run validate:paths`
+5. If the user asks how commands map to tasks/workflows, consult `.codex/command-registry.json`.
+6. Tailor the final walkthrough to the requested focus area, if provided.
+
+## Output Contract
+
+- Short explanation of how to activate agents in Codex
+- Short explanation of how workflows/tasks are resolved in Codex
+- Concrete next step for the user based on the requested focus