chore: rename _bmad-output to _sdlc and stop tracking _bmad

.gitignore

@@ -34,9 +34,9 @@ coverage*.json
 *.db-wal
 data/
 
-# BMAD generated render/cache artifacts; keep source skills, docs, and planning artifacts
-_bmad/render/
-_bmad-output/implementation-artifacts/
-_bmad-output/test-artifacts/
+# BMAD tooling is installed locally (installer-managed, per-user config); keep planning artifacts in _sdlc/
+_bmad/
+_sdlc/implementation-artifacts/
+_sdlc/test-artifacts/
 **/.agents/
 **/.claude/

CONTRIBUTING.md

@@ -5,7 +5,7 @@ Thanks for your interest. This project is in early development, so the most help
 ## Before you start
 
 - For anything beyond a small fix, **open an issue first** so we can agree on the approach.
-- Read the [architecture spine](_bmad-output/planning-artifacts/architecture/architecture-agenticexperience.net-2026-09-06/ARCHITECTURE-SPINE.md) and [reuse boundaries](_bmad-output/specs/spec-agentexperience-net/reuse-boundaries.md). They define rules the code must keep.
+- Read the [architecture spine](_sdlc/planning-artifacts/architecture/architecture-agenticexperience.net-2026-09-06/ARCHITECTURE-SPINE.md) and [reuse boundaries](_sdlc/specs/spec-agentexperience-net/reuse-boundaries.md). They define rules the code must keep.
 
 ## Ground rules
 

README.md

@@ -72,7 +72,7 @@ tests/
   AgentExperience.MicrosoftAgentFramework.Tests/  real ChatClientAgent runs against a scripted fake model
   AgentExperience.CompatibilityProof/       executable proofs for MAF hooks, context providers, pgvector, redaction
 docs/                                       original production architecture research
-_bmad-output/                               product brief, PRD, architecture, epics, and specs
+_sdlc/                                      product brief, PRD, architecture, epics, and specs
 ```
 
 ## Build and test
@@ -98,14 +98,14 @@ dotnet test --filter "FullyQualifiedName!~CompatibilityProof"
 3. **Govern experience safely:** sharing grants, audited lifecycle transitions, evidence-based confidence updates
 4. **Operate and measure the learning loop:** OpenTelemetry instrumentation, an end-to-end demo, measured reuse against a baseline, data deletion and expiry
 
-Full requirements and acceptance criteria are in [`_bmad-output/planning-artifacts/epics.md`](_bmad-output/planning-artifacts/epics.md).
+Full requirements and acceptance criteria are in [`_sdlc/planning-artifacts/epics.md`](_sdlc/planning-artifacts/epics.md).
 
 ## How this project is built
 
 Development is spec-driven with the [BMAD Method](https://github.com/bmad-code-org/BMAD-METHOD) and AI-assisted implementation. The planning trail is versioned alongside the code:
 
-- **Product brief, PRD, architecture, and epics:** [`_bmad-output/planning-artifacts/`](_bmad-output/planning-artifacts/)
-- **MVP spec and reuse-boundary decisions:** [`_bmad-output/specs/`](_bmad-output/specs/)
+- **Product brief, PRD, architecture, and epics:** [`_sdlc/planning-artifacts/`](_sdlc/planning-artifacts/)
+- **MVP spec and reuse-boundary decisions:** [`_sdlc/specs/`](_sdlc/specs/)
 
 Each story is planned against the architecture, implemented against explicit acceptance criteria, and then reviewed by independent adversarial, edge-case, and verification-gap passes before it is committed.