These agents were updated in .claude/agents/v3/ for ADR-093 but the
corresponding files in assets/agents/v3/ (the directory shipped to
users via aqe init) still carried stale advisor model IDs
(claude-opus-4, claude-opus-4-6). Fresh installs would have received
the old model references.
Synced files:
qe-coverage-specialist, qe-fleet-commander, qe-pentest-validator,
qe-queen-coordinator, qe-risk-assessor, qe-root-cause-analyzer,
qe-security-auditor, qe-security-scanner, qe-test-architect
Verified in a fresh project: aqe init --auto now writes agent files
with claude-opus-4.7 / claude-opus-4-7 advisor models and the ADR-093
"effort: max" frontmatter for the three cyber-pinned agents.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Multi-model routing layer with circuit breaking, PII redaction, and
domain-specific prompts for the Queen coordinator.
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
- #361: opencode-installer uses package-relative path resolution with
resolveViaPackageJson() fallback, never uses CWD as source
- #362: permissions union-merged via _aqePermissions to preserve user entries
- #363: brain-checkpoint/statusline hooks use hardcoded projectRoot fallback
instead of `pwd` in $(git rev-parse ... || echo "<path>")
- #364: created .claude/helpers/validation-pipeline.cjs with 13-step
requirements pipeline, updated SKILL.md references
- #365: agents-installer bumps `updated:` frontmatter date when overlays
modify agent content
- #366: qe-security-scanner dependency on qe-dependency-mapper changed
from hard to soft
- #367: --steps parameter documented as comma-separated string consistently
Closes#361, closes#362, closes#363, closes#364, closes#365, closes#366, closes#367
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Fix MCP tool prefix mismatch in 8 agent files (mcp__agentic_qe_v3__ → mcp__agentic-qe__)
and permission pattern in settings.json/settings-merge.ts. Closes#357.
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Add three subsystems for fleet orchestration intelligence:
- Pre-spawn MCP validation scans agent files for tool references and
validates availability at install and spawn time (advisory only)
- Agent dependency graph with YAML frontmatter parsing, topological
sort, and phased spawn plans for multi-agent orchestration
- Co-execution repository tracks agent pair success rates, feeding
behavioral signals into the signal merger for routing decisions
Wire all subsystems into the queen coordinator: dependency graph built
on initialize(), MCP validation in requestAgentSpawn(), co-execution
recording in handleTaskCompletionCallback(), and getSpawnPlan()/
getDependencyGraph() exposed on the public interface.
Add structured dependencies frontmatter to 5 agent definitions and
475 passing tests including 7 end-to-end integration tests proving
the wiring works.
Closes#342
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Semgrep integration was well-written but only used as a fallback in the
coordination layer — never invoked when the regex scanner succeeded.
Now SASTScanner.scanWithRules() runs pattern scanning + semgrep in parallel
when semgrep is installed, merging and deduplicating results.
Also corrects agent documentation that falsely claimed OWASP ZAP, TruffleHog,
Gitleaks, ESLint Security, and Snyk integrations. The actual implementations
are: regex patterns + semgrep (SAST), OSV API (deps), custom fetch-based
scanner (DAST), and regex patterns (secrets).
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
- Fix MCP entry path resolution in mcp.ts (1 level up, not 2)
- Remove stale v3/ directory references in 10-workers.ts
- Fix CRLF line endings in 170+ skill files breaking frontmatter parsing
- Add CRLF→LF safety net in prepare-assets.sh
- Rewrite README.md for clarity (1097→280 lines, outcome-focused)
- Sync assets from .claude/skills via prepare-assets.sh
Fixes issues reported in v3.7.9 upgrade (skill-lint failures, MCP errors)
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Remove redundant /v3/ segment from agent memory namespace paths
(e.g., aqe/v3/accessibility/outcomes/* → aqe/accessibility/outcomes/*).
Namespace identifiers in memory.db remain unchanged — this only
affects the documentation references in agent markdown files.
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Dragan Spiridonov