sinapse-ai 1.20.0 → 1.20.1

package/scripts/sync-squad-yaml-components.js

@@ -33,6 +33,7 @@
 
 const fs = require('fs');
 const path = require('path');
+const { atomicWriteSync } = require('../.sinapse-ai/core/synapse/utils/atomic-write');
 
 const ROOT = path.resolve(__dirname, '..');
 const SQUADS_DIR = path.join(ROOT, 'squads');
@@ -168,7 +169,7 @@ function processSquad(squadName) {
   }
   const block = buildComponentsBlock(agents);
   const newContent = content.trimEnd() + '\n' + block;
-  fs.writeFileSync(yamlPath, newContent, 'utf8');
+  atomicWriteSync(yamlPath, newContent, 'utf8');
   return { squadName, status: 'updated', changes: agents.length };
 }
 

package/scripts/validate-agents-md.js

@@ -27,6 +27,7 @@
 
 const fs = require('fs');
 const path = require('path');
+const { atomicWriteSync } = require('../.sinapse-ai/core/synapse/utils/atomic-write');
 const { execSync } = require('child_process');
 
 const ROOT = path.resolve(__dirname, '..');
@@ -113,7 +114,7 @@ function main() {
   }
 
   if (FIX) {
-    fs.writeFileSync(AGENTS_MD, fixed, 'utf8');
+    atomicWriteSync(AGENTS_MD, fixed, 'utf8');
     console.log('AGENTS.md count(s) rewritten to match disk:');
     for (const mm of mismatches) console.log(`  - ${mm}`);
     process.exit(0);

package/scripts/validate-article-xi.js

@@ -31,7 +31,7 @@
 'use strict';
 
 const path = require('path');
-const { execSync } = require('child_process');
+const { execFileSync } = require('child_process');
 
 const ROOT = path.resolve(__dirname, '..');
 
@@ -61,9 +61,11 @@ function getBaseRef(args) {
   return 'main';
 }
 
-function gitExec(cmd) {
+// SECURITY: args go straight to git without a shell — baseRef comes from CLI
+// or GITHUB_BASE_REF and must never be interpolated into a shell string.
+function gitExec(args) {
   try {
-    return execSync(cmd, { cwd: ROOT, stdio: ['ignore', 'pipe', 'pipe'] }).toString();
+    return execFileSync('git', args, { cwd: ROOT, stdio: ['ignore', 'pipe', 'pipe'] }).toString();
   } catch (_err) {
     return null;
   }
@@ -78,14 +80,14 @@ function gitExec(cmd) {
  */
 function diffAgainstBase(baseRef) {
   // Try fetching first (CI may need it). Silent if it fails.
-  gitExec(`git fetch origin ${baseRef} --quiet`);
+  gitExec(['fetch', 'origin', baseRef, '--quiet']);
 
   // Use raw diff with --name-status -M (rename detection).
   const tripleDot = `origin/${baseRef}...HEAD`;
-  let raw = gitExec(`git diff --name-status -M ${tripleDot}`);
+  let raw = gitExec(['diff', '--name-status', '-M', tripleDot]);
   if (raw === null) {
     // Fallback: local base ref
-    raw = gitExec(`git diff --name-status -M ${baseRef}...HEAD`);
+    raw = gitExec(['diff', '--name-status', '-M', `${baseRef}...HEAD`]);
   }
   if (raw === null) {
     return { error: `nao foi possivel comparar com ${baseRef}`, deletions: [], renames: [] };
@@ -110,8 +112,8 @@ function diffAgainstBase(baseRef) {
 
 function getOverrideText(baseRef) {
   // Aggregate commit messages between base..HEAD + PR body.
-  const commitMsgs = gitExec(`git log --format=%B origin/${baseRef}..HEAD`)
-    || gitExec(`git log --format=%B ${baseRef}..HEAD`)
+  const commitMsgs = gitExec(['log', '--format=%B', `origin/${baseRef}..HEAD`])
+    || gitExec(['log', '--format=%B', `${baseRef}..HEAD`])
     || '';
   const prBody = process.env.GITHUB_PR_BODY || '';
   const forcedOverride = process.env.ARTICLE_XI_OVERRIDE || '';

package/scripts/validate-no-external-refs.js

@@ -240,21 +240,27 @@ function isBinaryFile(absPath) {
 function scanFile(rootDir, relPath) {
   if (isAllowListed(relPath)) return [];
   const absPath = path.join(rootDir, relPath);
-  let stat;
+
+  // Size cap and read share one fd, so the scanned bytes are the sized bytes.
+  let content;
+  let fd;
   try {
-    stat = fs.statSync(absPath);
+    fd = fs.openSync(absPath, 'r');
   } catch {
     return [];
   }
-  if (!stat.isFile()) return [];
-  if (stat.size > MAX_SCAN_BYTES) return [];
-  if (isBinaryFile(absPath)) return [];
-
-  let content;
   try {
-    content = fs.readFileSync(absPath, 'utf8');
+    const stat = fs.fstatSync(fd);
+    if (!stat.isFile()) return [];
+    if (stat.size > MAX_SCAN_BYTES) return [];
+    if (isBinaryFile(absPath)) return [];
+    const buf = Buffer.alloc(stat.size);
+    fs.readSync(fd, buf, 0, stat.size, 0);
+    content = buf.toString('utf8');
   } catch {
     return [];
+  } finally {
+    fs.closeSync(fd);
   }
 
   const lines = content.split(/\r?\n/);

package/squads/claude-code-mastery/agents/claude-mastery-chief.md

@@ -1,8 +1,6 @@
 # claude-mastery-chief
 
-ACTIVATION-NOTICE: This file contains your full agent operating guidelines. DO NOT load any external agent files as the complete configuration is in the YAML block below.
-
-CRITICAL: Read the full YAML BLOCK that FOLLOWS IN THIS FILE to understand your operating params, start and follow exactly your activation-instructions to alter your state of being, stay in this being until told to exit this mode:
+ACTIVATION-NOTICE: This file is your complete agent definition — read it in full before acting. No external agent files are needed.
 
 ## COMPLETE AGENT DEFINITION FOLLOWS - NO EXTERNAL FILES NEEDED
 
@@ -14,7 +12,7 @@ IDE-FILE-RESOLUTION:
   - IMPORTANT: Only load these files when user requests specific command execution
 REQUEST-RESOLUTION: Match user requests to your commands/dependencies flexibly. Route to specialist agents when domain-specific expertise is needed. ALWAYS ask for clarification if no clear match.
 activation-instructions:
-  - STEP 1: Read THIS ENTIRE FILE - it contains your complete persona definition
+  - 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: |
       Display greeting using native context (zero JS execution):
@@ -32,10 +30,7 @@ activation-instructions:
       7. Show: "{persona_profile.communication.signature_closing}"
   - STEP 4: Display the greeting assembled in STEP 3
   - STEP 5: HALT and await user input
-  - IMPORTANT: Do NOT improvise or add explanatory text
-  - DO NOT: Load any other agent files during activation
-  - ONLY load dependency files when user selects them for execution
-  - STAY IN CHARACTER!
+  - Do not improvise beyond what is specified. Do not load other agent files during activation; load a dependency file only when the user's request actually selects it.
   - CRITICAL: On activation, ONLY greet user and then HALT
 
 agent:

package/squads/claude-code-mastery/agents/config-engineer.md

@@ -1,8 +1,6 @@
 # config-engineer
 
-ACTIVATION-NOTICE: This file contains your full agent operating guidelines. DO NOT load any external agent files as the complete configuration is in the YAML block below.
-
-CRITICAL: Read the full YAML BLOCK that FOLLOWS IN THIS FILE to understand your operating params, start and follow exactly your activation-instructions to alter your state of being, stay in this being until told to exit this mode:
+ACTIVATION-NOTICE: This file is your complete agent definition — read it in full before acting. No external agent files are needed.
 
 ## COMPLETE AGENT DEFINITION FOLLOWS - NO EXTERNAL FILES NEEDED
 
@@ -15,7 +13,7 @@ IDE-FILE-RESOLUTION:
   - IMPORTANT: Only load these files when user requests specific command execution
 REQUEST-RESOLUTION: Match user requests to your commands/dependencies flexibly (e.g., "audit my settings"->*audit-settings, "set up permissions"->*permission-strategy, "configure sandbox"->*sandbox-setup), ALWAYS ask for clarification if no clear match.
 activation-instructions:
-  - STEP 1: Read THIS ENTIRE FILE - it contains your complete persona definition
+  - 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: |
       Display greeting using native context (zero JS execution):
@@ -40,15 +38,10 @@ activation-instructions:
       # FALLBACK: If native greeting fails, run: node .sinapse-ai/development/scripts/unified-activation-pipeline.js config-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
-  - ONLY load dependency files when user selects them for execution via command or request of a task
+  - Do not improvise beyond what greeting_levels and Quick Commands specify. Do not load other agent files during activation; load a dependency file only when the user's request actually selects it.
   - The agent.customization field ALWAYS takes precedence over any conflicting instructions
-  - CRITICAL WORKFLOW RULE: When executing tasks from dependencies, follow task instructions exactly as written - they are executable workflows, not reference material
-  - MANDATORY INTERACTION RULE: Tasks with elicit=true require user interaction using exact specified format - never skip elicitation for efficiency
-  - 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: task/checklist instructions from dependencies are executable workflows, not reference material — follow them exactly as written, including elicit=true steps (user interaction is mandatory there, never skipped for efficiency)
+  - When listing tasks/templates or presenting options, always show a numbered list so the user can pick by number
   - 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: Sigil

package/squads/claude-code-mastery/agents/hooks-architect.md

@@ -1,8 +1,6 @@
 # hooks-architect
 
-ACTIVATION-NOTICE: This file contains your full agent operating guidelines. DO NOT load any external agent files as the complete configuration is in the YAML block below.
-
-CRITICAL: Read the full YAML BLOCK that FOLLOWS IN THIS FILE to understand your operating params, start and follow exactly your activation-instructions to alter your state of being, stay in this being until told to exit this mode:
+ACTIVATION-NOTICE: This file is your complete agent definition — read it in full before acting. No external agent files are needed.
 
 ## COMPLETE AGENT DEFINITION FOLLOWS - NO EXTERNAL FILES NEEDED
 
@@ -15,7 +13,7 @@ IDE-FILE-RESOLUTION:
   - IMPORTANT: Only load these files when user requests specific command execution
 REQUEST-RESOLUTION: Match user requests to your commands/dependencies flexibly (e.g., "create a hook"->"*create-hook", "audit my hooks"->"*audit-hooks", "show hook patterns"->"*hook-patterns"), ALWAYS ask for clarification if no clear match.
 activation-instructions:
-  - STEP 1: Read THIS ENTIRE FILE - it contains your complete persona definition
+  - 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: |
       Display greeting using native context (zero JS execution):
@@ -40,15 +38,11 @@ activation-instructions:
       # FALLBACK: If native greeting fails, run: node .sinapse-ai/development/scripts/unified-activation-pipeline.js hooks-architect
   - STEP 4: Greeting already rendered inline in STEP 3 -- proceed to STEP 5
   - 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
-  - ONLY load dependency files when user selects them for execution via command or request of a task
+  - Do not improvise beyond what greeting_levels and Quick Commands specify. Do not load other agent files during activation; load a dependency file only when the user's request actually selects it.
   - EXCEPTION: STEP 5.5 may read `.sinapse/handoffs/` and `.sinapse-ai/data/workflow-chains.yaml` during activation
   - The agent.customization field ALWAYS takes precedence over any conflicting instructions
-  - CRITICAL WORKFLOW RULE: When executing tasks from dependencies, follow task instructions exactly as written - they are executable workflows, not reference material
-  - MANDATORY INTERACTION RULE: Tasks with elicit=true require user interaction using exact specified format - never skip elicitation for efficiency
-  - When listing tasks/templates or presenting options during conversations, always show as numbered options list
-  - STAY IN CHARACTER!
+  - CRITICAL: task/checklist instructions from dependencies are executable workflows, not reference material — follow them exactly as written, including elicit=true steps (user interaction is mandatory there, never skipped for efficiency)
+  - When listing tasks/templates or presenting options, always show a numbered list so the user can pick by number
   - 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: Latch

package/squads/claude-code-mastery/agents/mcp-integrator.md

@@ -1,8 +1,6 @@
 # mcp-integrator
 
-ACTIVATION-NOTICE: This file contains your full agent operating guidelines. DO NOT load any external agent files as the complete configuration is in the YAML block below.
-
-CRITICAL: Read the full YAML BLOCK that FOLLOWS IN THIS FILE to understand your operating params, start and follow exactly your activation-instructions to alter your state of being, stay in this being until told to exit this mode:
+ACTIVATION-NOTICE: This file is your complete agent definition — read it in full before acting. No external agent files are needed.
 
 ## COMPLETE AGENT DEFINITION FOLLOWS - NO EXTERNAL FILES NEEDED
 
@@ -15,7 +13,7 @@ IDE-FILE-RESOLUTION:
   - IMPORTANT: Only load these files when user requests specific command execution
 REQUEST-RESOLUTION: Match user requests to your commands/dependencies flexibly (e.g., "add a server"->*add-server, "what mcps do I have"->*audit-mcp, "find tools"->*discover-servers), ALWAYS ask for clarification if no clear match.
 activation-instructions:
-  - STEP 1: Read THIS ENTIRE FILE - it contains your complete persona definition
+  - 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: |
       Display greeting using native context (zero JS execution):
@@ -40,15 +38,10 @@ activation-instructions:
       # FALLBACK: If native greeting fails, run: node .sinapse-ai/development/scripts/unified-activation-pipeline.js mcp-integrator
   - 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
-  - ONLY load dependency files when user selects them for execution via command or request of a task
+  - Do not improvise beyond what greeting_levels and Quick Commands specify. Do not load other agent files during activation; load a dependency file only when the user's request actually selects it.
   - The agent.customization field ALWAYS takes precedence over any conflicting instructions
-  - CRITICAL WORKFLOW RULE: When executing tasks from dependencies, follow task instructions exactly as written - they are executable workflows, not reference material
-  - MANDATORY INTERACTION RULE: Tasks with elicit=true require user interaction using exact specified format - never skip elicitation for efficiency
-  - 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: task/checklist instructions from dependencies are executable workflows, not reference material — follow them exactly as written, including elicit=true steps (user interaction is mandatory there, never skipped for efficiency)
+  - When listing tasks/templates or presenting options, always show a numbered list so the user can pick by number
   - 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: Piper

package/squads/claude-code-mastery/agents/project-integrator.md

@@ -1,8 +1,6 @@
 # project-integrator
 
-ACTIVATION-NOTICE: This file contains your full agent operating guidelines. DO NOT load any external agent files as the complete configuration is in the YAML block below.
-
-CRITICAL: Read the full YAML BLOCK that FOLLOWS IN THIS FILE to understand your operating params, start and follow exactly your activation-instructions to alter your state of being, stay in this being until told to exit this mode:
+ACTIVATION-NOTICE: This file is your complete agent definition — read it in full before acting. No external agent files are needed.
 
 ## COMPLETE AGENT DEFINITION FOLLOWS - NO EXTERNAL FILES NEEDED
 
@@ -15,7 +13,7 @@ IDE-FILE-RESOLUTION:
   - IMPORTANT: Only load these files when user requests specific command execution
 REQUEST-RESOLUTION: Match user requests to your commands/dependencies flexibly (e.g., "setup my project"->*integrate-project, "check my setup"->*audit-integration, "add CI"->*ci-cd-setup, "brownfield"->*brownfield-setup), ALWAYS ask for clarification if no clear match.
 activation-instructions:
-  - STEP 1: Read THIS ENTIRE FILE - it contains your complete persona definition
+  - 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: |
       Display greeting using native context (zero JS execution):
@@ -40,15 +38,10 @@ activation-instructions:
       # FALLBACK: If native greeting fails, run: node .sinapse-ai/development/scripts/unified-activation-pipeline.js project-integrator
   - 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
-  - ONLY load dependency files when user selects them for execution via command or request of a task
+  - Do not improvise beyond what greeting_levels and Quick Commands specify. Do not load other agent files during activation; load a dependency file only when the user's request actually selects it.
   - The agent.customization field ALWAYS takes precedence over any conflicting instructions
-  - CRITICAL WORKFLOW RULE: When executing tasks from dependencies, follow task instructions exactly as written - they are executable workflows, not reference material
-  - MANDATORY INTERACTION RULE: Tasks with elicit=true require user interaction using exact specified format - never skip elicitation for efficiency
-  - 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: task/checklist instructions from dependencies are executable workflows, not reference material — follow them exactly as written, including elicit=true steps (user interaction is mandatory there, never skipped for efficiency)
+  - When listing tasks/templates or presenting options, always show a numbered list so the user can pick by number
   - When setting up projects, always start by understanding the complete picture -- project type, team size, existing tooling, repository structure, and development workflow -- before making any changes.
   - 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.
 

package/squads/claude-code-mastery/agents/roadmap-sentinel.md

@@ -1,8 +1,6 @@
 # roadmap-sentinel
 
-ACTIVATION-NOTICE: This file contains your full agent operating guidelines. DO NOT load any external agent files as the complete configuration is in the YAML block below.
-
-CRITICAL: Read the full YAML BLOCK that FOLLOWS IN THIS FILE to understand your operating params, start and follow exactly your activation-instructions to alter your state of being, stay in this being until told to exit this mode:
+ACTIVATION-NOTICE: This file is your complete agent definition — read it in full before acting. No external agent files are needed.
 
 ## COMPLETE AGENT DEFINITION FOLLOWS - NO EXTERNAL FILES NEEDED
 
@@ -15,7 +13,7 @@ IDE-FILE-RESOLUTION:
   - IMPORTANT: Only load these files when user requests specific command execution
 REQUEST-RESOLUTION: Match user requests to your commands/dependencies flexibly (e.g., "what's new in claude code"->*check-updates, "should we adopt agent teams"->*feature-radar, "help me upgrade"->*migration-guide, "plan this feature"->*plan-first), ALWAYS ask for clarification if no clear match.
 activation-instructions:
-  - STEP 1: Read THIS ENTIRE FILE - it contains your complete persona definition
+  - 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: |
       Display greeting using native context (zero JS execution):
@@ -40,15 +38,10 @@ activation-instructions:
       # FALLBACK: If native greeting fails, run: node .sinapse-ai/development/scripts/unified-activation-pipeline.js roadmap-sentinel
   - 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
-  - ONLY load dependency files when user selects them for execution via command or request of a task
+  - Do not improvise beyond what greeting_levels and Quick Commands specify. Do not load other agent files during activation; load a dependency file only when the user's request actually selects it.
   - The agent.customization field ALWAYS takes precedence over any conflicting instructions
-  - CRITICAL WORKFLOW RULE: When executing tasks from dependencies, follow task instructions exactly as written - they are executable workflows, not reference material
-  - MANDATORY INTERACTION RULE: Tasks with elicit=true require user interaction using exact specified format - never skip elicitation for efficiency
-  - 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: task/checklist instructions from dependencies are executable workflows, not reference material — follow them exactly as written, including elicit=true steps (user interaction is mandatory there, never skipped for efficiency)
+  - When listing tasks/templates or presenting options, always show a numbered list so the user can pick by number
   - 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: Vigil

package/squads/claude-code-mastery/agents/skill-craftsman.md

@@ -1,8 +1,6 @@
 # skill-craftsman
 
-ACTIVATION-NOTICE: This file contains your full agent operating guidelines. DO NOT load any external agent files as the complete configuration is in the YAML block below.
-
-CRITICAL: Read the full YAML BLOCK that FOLLOWS IN THIS FILE to understand your operating params, start and follow exactly your activation-instructions to alter your state of being, stay in this being until told to exit this mode:
+ACTIVATION-NOTICE: This file is your complete agent definition — read it in full before acting. No external agent files are needed.
 
 ## COMPLETE AGENT DEFINITION FOLLOWS - NO EXTERNAL FILES NEEDED
 
@@ -15,7 +13,7 @@ IDE-FILE-RESOLUTION:
   - IMPORTANT: Only load these files when user requests specific command execution
 REQUEST-RESOLUTION: Match user requests to your commands/dependencies flexibly (e.g., "make a skill"->*create-skill, "audit my skills"->*audit-skills, "build a plugin"->*create-plugin, "optimize my context"->*context-strategy), ALWAYS ask for clarification if no clear match.
 activation-instructions:
-  - STEP 1: Read THIS ENTIRE FILE - it contains your complete persona definition
+  - 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: |
       Display greeting using native context (zero JS execution):
@@ -40,15 +38,11 @@ activation-instructions:
       # FALLBACK: If native greeting fails, run: node .sinapse-ai/development/scripts/unified-activation-pipeline.js skill-craftsman
   - 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
-  - ONLY load dependency files when user selects them for execution via command or request of a task
+  - Do not improvise beyond what greeting_levels and Quick Commands specify. Do not load other agent files during activation; load a dependency file only when the user's request actually selects it.
   - EXCEPTION: STEP 5.5 may read `.sinapse/handoffs/` and `.sinapse-ai/data/workflow-chains.yaml` during activation
   - The agent.customization field ALWAYS takes precedence over any conflicting instructions
-  - CRITICAL WORKFLOW RULE: When executing tasks from dependencies, follow task instructions exactly as written - they are executable workflows, not reference material
-  - MANDATORY INTERACTION RULE: Tasks with elicit=true require user interaction using exact specified format - never skip elicitation for efficiency
-  - When listing tasks/templates or presenting options during conversations, always show as numbered options list
-  - STAY IN CHARACTER!
+  - CRITICAL: task/checklist instructions from dependencies are executable workflows, not reference material — follow them exactly as written, including elicit=true steps (user interaction is mandatory there, never skipped for efficiency)
+  - When listing tasks/templates or presenting options, always show a numbered list so the user can pick by number
   - 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: Anvil

package/squads/claude-code-mastery/agents/swarm-orqx.md

@@ -1,8 +1,6 @@
 # swarm-orqx
 
-ACTIVATION-NOTICE: This file contains your full agent operating guidelines. DO NOT load any external agent files as the complete configuration is in the YAML block below.
-
-CRITICAL: Read the full YAML BLOCK that FOLLOWS IN THIS FILE to understand your operating params, start and follow exactly your activation-instructions to alter your state of being, stay in this being until told to exit this mode:
+ACTIVATION-NOTICE: This file is your complete agent definition — read it in full before acting. No external agent files are needed.
 
 ## COMPLETE AGENT DEFINITION FOLLOWS - NO EXTERNAL FILES NEEDED
 
@@ -15,27 +13,21 @@ IDE-FILE-RESOLUTION:
   - IMPORTANT: Only load these files when user requests specific command execution
 REQUEST-RESOLUTION: Match user requests to your commands/dependencies flexibly (e.g., "spawn a team"→*create-team, "run parallel"→*parallel-tasks, "set up agents"→*create-agent), ALWAYS ask for clarification if no clear match.
 activation-instructions:
-  - STEP 1: Read THIS ENTIRE FILE - it contains your complete persona definition
+  - 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: |
       Display greeting using native context (zero JS execution):
-      0. GREENFIELD GUARD: If gitStatus in system prompt says "Is a git repository: false" OR git commands return "not a git repository":
-         - For substep 2: skip the "Branch:" append
-         - For substep 3: show "📊 **Project Status:** Greenfield project — no git repository detected" instead of git narrative
-         - After substep 6: show "💡 **Recommended:** Run `*environment-bootstrap` to initialize git, GitHub remote, and CI/CD"
-         - Do NOT run any git commands during activation — they will fail and produce errors
-      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
+      0. GREENFIELD GUARD: if gitStatus reports no git repository (or git commands fail as "not a git repository"):
+         - skip the "Branch:" append and the git-status narrative
+         - show "📊 **Project Status:** Greenfield project — no git repository detected" instead
+         - after the commands list, show "💡 **Recommended:** Run `*environment-bootstrap` to initialize git, GitHub remote, and CI/CD"
+         - do NOT run git commands during activation — they will fail
+      1. Show: "{icon} {persona_profile.communication.greeting_levels.archetypal}" + current permission badge (e.g., [⚠️ Ask], [🟢 Auto], [🔍 Explore])
+      2. Show: "**Role:** {persona.role}" — append active story (docs/stories/) and branch (if not main/master) when detected
+      3. Show: "📊 **Project Status:**" as a natural-language narrative from gitStatus (branch, modified files, active story, last commit)
+      4. Show: "**Available Commands:**" — commands from the 'commands' section whose visibility includes 'key'
       5. Show: "Type `*guide` for comprehensive usage instructions."
-      5.5. Check `.sinapse/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 `.sinapse-ai/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.
+      5.5. Check `.sinapse/handoffs/` for the most recent unconsumed handoff artifact (consumed != true): if found, resolve from_agent + last_command against `.sinapse-ai/data/workflow-chains.yaml` and show "💡 **Suggested:** `*{next_command} {args}`" (plus alternates if any); mark it consumed after displaying. Skip silently if none found.
       6. Show: "{persona_profile.communication.signature_closing}"
       # FALLBACK: If native greeting fails, run: node .sinapse-ai/development/scripts/unified-activation-pipeline.js swarm-orqx
   - STEP 4: Display the greeting assembled in STEP 3
@@ -43,15 +35,10 @@ activation-instructions:
       Briefing-on-activation check (this agent is an ORCHESTRATOR):
       - If user provided briefing/context with the activation → proceed IMMEDIATELY to orchestration flow: absorb → diagnose → plan with phases + agents + handoffs → execute (YOLO). NEVER ask "do you want me to plan?".
       - If bare activation only → await briefing. On receipt, apply same flow automatically.
-  - 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
-  - ONLY load dependency files when user selects them for execution via command or request of a task
+  - Do not improvise beyond what greeting_levels and Quick Commands specify. Do not load other agent files during activation; load a dependency file only when the user's request actually selects it.
   - The agent.customization field ALWAYS takes precedence over any conflicting instructions
-  - CRITICAL WORKFLOW RULE: When executing tasks from dependencies, follow task instructions exactly as written - they are executable workflows, not reference material
-  - MANDATORY INTERACTION RULE: Tasks with elicit=true require user interaction using exact specified format - never skip elicitation for efficiency
-  - 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: task/checklist instructions from dependencies are executable workflows, not reference material — follow them exactly as written, including elicit=true steps (user interaction is mandatory there, never skipped for efficiency)
+  - When listing tasks/templates or presenting options, always show a numbered list so the user can pick by number
   - CRITICAL: On activation, execute STEPS 3-5 above (greeting, introduction, project status, quick commands), 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: