Profa
2253d05618
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>
3.6 KiB
MADR-{ID}: {Strategic Initiative Title}
| Field | Value |
|---|---|
| Decision ID | MADR-{ID} |
| Type | Master ADR |
| Initiative | {Programme/Project Name} |
| Proposed By | {Author} |
| Date | {YYYY-MM-DD} |
| Aggregate Status | {Calculated from children} |
WH(Y) Decision Statement
In the context of {strategic context - the overarching system or programme},
facing {strategic challenge - the high-level problem or opportunity},
we decided for {strategic direction - the approach or initiative},
and neglected {alternative strategies considered},
to achieve {strategic benefits - high-level outcomes},
accepting that {strategic trade-offs - complexity, cost, coordination required}.
Strategic Context
{Detailed description of the business or technical drivers behind this initiative. What market forces, technical constraints, or organizational goals motivated this?}
Scope Boundary
In Scope
- {Decision area 1}
- {Decision area 2}
- {Decision area 3}
Out of Scope
- {Excluded area 1}
- {Excluded area 2}
Child ADR Registry
| ADR ID | Title | Status | Phase | Owner |
|---|---|---|---|---|
| ADR-{xxx} | {Title} | Proposed / Approved / Implemented | {Phase number} | {Team} |
| ADR-{xxx} | {Title} | {Status} | {Phase} | {Team} |
| ADR-{xxx} | {Title} | {Status} | {Phase} | {Team} |
Decision Sequencing
Phase 1: {Phase Name} (Foundation)
{Description of this phase's objectives}
Included ADRs:
- ADR-{xxx}: {Title}
- ADR-{xxx}: {Title}
Prerequisites: None
Phase 2: {Phase Name}
{Description}
Included ADRs:
- ADR-{xxx}: {Title}
- ADR-{xxx}: {Title}
Prerequisites: Phase 1 complete
Phase 3: {Phase Name}
{Description}
Included ADRs:
- ADR-{xxx}: {Title}
Prerequisites: Phase 1 and 2 complete
Progress Dashboard
MADR-{ID}: {Title}
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
Aggregate Status: {Status} ({X}/{Y} approved)
Phase 1: {Name}
[✓] ADR-xxx: {Title} (Implemented)
[✓] ADR-xxx: {Title} (Approved)
Phase 2: {Name}
[~] ADR-xxx: {Title} (Under Review)
[ ] ADR-xxx: {Title} (Proposed)
Progress: ████████░░░░░░░░ {X}%
Aggregate Status History
| Status | Date | Notes |
|---|---|---|
| Proposed | {YYYY-MM-DD} | Initial creation |
| In Progress | {YYYY-MM-DD} | First child ADR approved |
Governance
| Review Board | Date | Outcome | Next Review |
|---|---|---|---|
| {Board Name} | {Date} | {Outcome} | {Date} |
References
| Reference ID | Title | Type | Location |
|---|---|---|---|
| {REF-ID} | {Title} | {Type} | {Location} |
Definition of Done
This Master ADR is complete when:
- All child ADRs identified and registered
- Phase sequencing defined with dependencies
- All Phase 1 (Foundation) ADRs approved
- Progress dashboard reflects current state
- Governance review scheduled