Files
Profa 2253d05618 feat: flatten project structure — archive v2, promote v3 to root
Remove the nested v3/ subdirectory by moving all active source code,
tests, configs, and assets directly to the project root. Archive v2/
(dead code, 847MB) to v2-archive.tar.gz.

Key changes:
- Move v3/src/ → src/, v3/tests/ → tests/, v3/packages/ → packages/
- Move v3/tsconfig.json, v3/vitest.config.ts to root
- Merge v3/package.json into root package.json (ESM, scripts, deps, exports)
- Merge v3/scripts/ into scripts/, v3/implementation/ into docs/implementation/
- Update all CI workflows to remove "cd v3 &&" and v3/ path prefixes
- Fix all init installer path resolution (3-level-up → 2-level-up)
- Fix hooks to use "node ./dist/cli/bundle.js" instead of bare "aqe"
- Update settings.json ADR/DDD directories to docs/implementation/
- Fix helper scripts (statusline, adr-compliance, ddd-tracker, guidance-hooks)
- Update 58 agent definitions: aqe/v3/ → aqe/ memory namespaces
- Update 15 guidance shards: v3/src/ → src/ path references
- Fix sync interfaces: remove v3/ and v2/ path references
- Fix test path calculations (process.cwd() + '..' no longer needed)
- Fix flaky perf test threshold (500ms → 1000ms for CI environments)
- Fix complexity-analyzer test to match ADR-051 keyword-based eligibility

Build passes, 17,901 tests pass, CLI and MCP bundles verified.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
2026-03-01 11:35:41 +00:00

1.7 KiB

SPEC-{ADR-ID}-{Letter}: {Title}

Field Value
Specification ID SPEC-{ADR-ID}-{Letter}
Parent ADR ADR-{ADR-ID}
Version 1.0
Status Draft
Last Updated {YYYY-MM-DD}
Author {Author Name}

Overview

{Brief description of what this specification covers. 2-3 sentences explaining the scope and purpose.}


Specification Details

{Main technical content. This is where implementation details belong:

  • Code examples
  • Configuration templates
  • API definitions
  • Schema definitions
  • Architecture diagrams
  • Migration scripts
  • Deployment procedures }

Section 1: {Topic}

{Detailed content}

Section 2: {Topic}

{Detailed content}


Examples

{Concrete examples showing how to use or implement this specification}

Example 1: {Description}

// Code example

Example 2: {Description}

# Configuration example

Validation Rules

Rule ID Description Severity
{SPEC-ID}-001 {Rule description} Error / Warning / Info
{SPEC-ID}-002 {Rule description} Error / Warning / Info

Spec ID Title Relationship
SPEC-{xxx}-{x} {Title} {How they relate}

Changelog

Version Date Author Changes
1.0 {YYYY-MM-DD} {Author} Initial specification

References