chore(aiwg): adopt shared BT6 maintainer workflow (#148)

* docs(policy): allow low-impact contributor courtesy cleanup

* chore(aiwg): migrate to shared BT6 maintainer plugin

* chore: reconcile delivery validation

.aiwg/reports/abm-gate-report.md

@@ -1,15 +1,42 @@
 # Architecture Baseline Milestone Gate Report
 
-**Status:** PASS  
-**Date:** 2026-07-20
+## Gate Metadata
 
-| Criterion | Status | Evidence |
-| --- | --- | --- |
-| SAD exists and is baselined | PASS | `architecture/software-architecture-doc.md`; current-state, >1,000 words |
-| At least three ADRs | PASS | ADR-001 through ADR-005 |
-| Use-case architectural coverage | PASS | SAD traceability covers UC-001 through UC-005 |
-| Test strategy exists | PASS | `testing/test-strategy.md` |
-| No unmitigated blocking architecture risk | PASS | R-01 has enforced controls; weakening them is explicitly release-blocking |
-| Vision/current-state separation | PASS | ADR-005 and `architecture/vision-alignment.md` |
+- **Decision:** PASS WITH CONDITIONS
+- **Evaluation date:** 2026-07-21
+- **Scope:** Current-state brownfield architecture and construction-readiness evidence
+- **Evaluator:** Artifact standards audit; named maintainer approval pending
 
-The architecture is baselined for maintenance and controlled evolution. “Construction ready” means the brownfield team can prioritize alignment work; it does not relabel experimental features as stable.
+## Criteria and Evidence
+
+| Criterion | Threshold | Status | Citable evidence |
+| --- | --- | --- | --- |
+| SAD completeness | v3 sections, context/container/component/data/sequences/API/deployment/cross-cutting/technology/traceability/open questions | PASS | Software Architecture Document |
+| Architectural decisions | At least three decisions with context, alternatives, consequences, risks, implementation/tests, references | PASS | ADR-001 through ADR-005 |
+| Requirement architecture coverage | Every UC, story group, and NFR maps to a component/tactic and verification | PASS | SAD §§12–14 |
+| Test strategy | Levels, environments, metrics, risk mapping, and blocking gates are explicit | PASS | Test strategy |
+| Risk control | No accepted release path weakens blocking safety controls | PASS | R-001/R-002/R-008; ADR-003 |
+| Vision/current-state separation | Maturity evidence and promotion gates are explicit | PASS | ADR-005 and vision alignment |
+| Review approval | Named architecture/safety/evaluation approval recorded | CONDITION | Roles defined; named sign-off pending |
+| Open architecture work | Gaps have owners/target phase and do not masquerade as implemented claims | PASS | SAD Appendix B; Iteration 001 |
+
+## Conditions
+
+1. Maintainers must review the SAD/ADRs and record named accept/amend/supersede outcomes.
+2. Complete the adapter safety inventory and maturity-consistency automation before claiming those controls are complete.
+3. Establish measured workload/startup/shutdown baselines before making performance or disposability claims.
+
+## Decision Rationale
+
+The current-state architecture is sufficiently detailed and traceable for controlled brownfield construction. “Pass” does not promote experimental features, prove hosted-service readiness, or fabricate stakeholder approval. The conditions are explicit construction work and release-review prerequisites where applicable.
+
+## References
+
+- @.aiwg/architecture/software-architecture-doc.md — Architecture baseline and matrices.
+- @.aiwg/architecture/adr-001.md — Local-first modular structure.
+- @.aiwg/architecture/adr-003.md — Deterministic safety boundary.
+- @.aiwg/architecture/adr-005.md — Maturity boundary.
+- @.aiwg/architecture/vision-alignment.md — Evidence and promotion criteria.
+- @.aiwg/testing/test-strategy.md — Verification strategy.
+- @.aiwg/planning/iteration-001-plan.md — Condition closure plan.
+- @.aiwg/team/team-profile.md — Pending named ownership.