Files
Dragan Spiridonov bd938c5597 release: v3.6.8 — MCP auto-init, experience persistence, DB isolation (#263)
* fix(kernel): resolve relative dbPath to prevent split-brain dual-database writes

UnifiedPersistenceManager and HybridMemoryBackend pass static relative path
'.agentic-qe/memory.db' to UnifiedMemoryManager, which overrides the resolved
absolute path in the constructor via spread. When CWD differs from project root
(e.g. tests running from v3/), this creates a duplicate database at
v3/.agentic-qe/memory.db, splitting dream/concept data from patterns/KV data.

Fix: resolve any relative dbPath through findProjectRoot() in the constructor,
ensuring all callers converge on the single project-root database.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

* release(v3.6.8): fix MCP auto-init, experience persistence, DB isolation, and missing deps

- Fleet auto-initializes on MCP server startup (no manual fleet_init needed)
- ExperienceReplay unified to read from captured_experiences table
- Data migrator writes to captured_experiences instead of removed experiences table
- Added fast-json-patch and jose to root package.json (fixes #262)
- Wrapped MinCut dispose saveSnapshot in try/catch for test resilience
- Kernel initializes UnifiedPersistence with temp DB for in-memory backend
- All 6 MCP handler test files use memoryBackend:'memory' and resetUnifiedPersistence()
- domain-handlers and wrapped-domain-handlers use beforeAll to prevent OOM

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

* docs: add RVF integration plan, ADRs, and benchmark script

- RVF integration implementation plan and Six Hats analyses
- Phase 0 gate report for RVF integration readiness
- ADR-065: RVF integration hybrid architecture
- ADR-066: RVF pattern store progressive HNSW
- ADR-067: Agent memory branching with RVF copy-on-write
- AQE baseline benchmark script

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

* fix(tests): restore fleet after dispose in wrapped-domain-handlers beforeAll tests

The "not initialized" tests call disposeFleet() but with beforeAll the
fleet is only initialized once. Subsequent tests failed because the
fleet was never re-initialized. Add handleFleetInit() after each
dispose-based test to restore state for later tests.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

---------

Co-authored-by: Claude Opus 4.6 <noreply@anthropic.com>
2026-02-16 08:20:10 +01:00
..

Agentic QE v3 Implementation Documentation

This directory contains all implementation documentation, planning, and research for Agentic QE v3.

Directory Structure

implementation/
├── adrs/                    # Architecture Decision Records
├── architecture/            # Architecture diagrams & analysis
├── planning/                # Master plans & implementation strategies
├── security/                # Security considerations
└── agents/                  # Agent specifications

Document Index

ADRs (Architecture Decision Records)

Document Description
v3-adrs.md All 10 ADRs (001-010) master document

Planning

Document Description
AQE-V3-MASTER-PLAN.md Complete v3 master plan with DDD architecture

Key Concepts

Domain-Driven Design for QE

Agentic QE v3 uses DDD with 6 bounded contexts:

  1. Test Generation - AI-powered test creation
  2. Test Execution - Parallel execution and retry
  3. Coverage Analysis - O(log n) gap detection
  4. Quality Assessment - Quality gates and metrics
  5. Defect Intelligence - Prediction and analysis
  6. Learning Optimization - Pattern learning and transfer

Agent Hierarchy

21 specialized v3 agents organized hierarchically:

  • Queen Coordinator (orchestration)
  • Test Generation Group (4 agents)
  • Quality Gates Group (3 agents)
  • Intelligence Group (3 agents)
  • Execution Group (3 agents)
  • Coverage Group (3 agents)
  • Learning Group (4 agents)

Key ADRs

ADR Decision
ADR-001 Adopt DDD for QE bounded contexts
ADR-002 Event-driven domain communication
ADR-003 Sublinear O(log n) coverage analysis
ADR-004 Plugin architecture for extensions
ADR-005 AI-first test generation

Getting Started

# Use v3 DDD skill
Task("Analyze QE architecture",
     "Design DDD bounded contexts for quality engineering",
     "system-architect")

# Use v3 Queen Coordinator
Task("Orchestrate QE workflow",
     "Coordinate full quality engineering workflow",
     "v3-qe-queen-coordinator")

# Use v3 Test Architect
Task("Generate tests",
     "Create AI-powered test suite for UserService",
     "v3-qe-test-architect")

Last Updated: 2026-01-07 Version: 1.0.0