chore: archive v1.14.22 milestone

.planning/milestones/v1.14.22-REQUIREMENTS.md

@@ -0,0 +1,29 @@
+# Requirements Archive: v1.14.22
+
+**Milestone:** Config Consolidation & Infrastructure
+**Status:** 100% COMPLETE
+
+---
+
+## 1. Functional Requirements (Archived)
+- [x] **R-01: Centralized Configuration**: All environment settings must live in the `config/` directory.
+- [x] **R-02: Secret Separation**: Production secrets must be stored in `secrets.yaml` and excluded from Git.
+- [x] **R-03: Multi-Domain Schema**: Config must be split into `backend`, `frontend`, `network`, and `docker` domains.
+- [x] **R-04: Python Tooling**: All deployment and management scripts must be implemented in Python with consistent logging.
+- [x] **R-05: Dynamic Topology**: The system must automatically calculate API endpoints from the `server_ip` defined in `network.yaml`.
+- [x] **R-06: Unified Auth Mgmt**: Admin UI must save LDAP settings directly to the YAML configuration.
+
+---
+
+## 2. Technical Quality Requirements
+- [x] **Q-01: Type Compliance**: No bold/medium font weights in the UI.
+- [x] **Q-02: Copywriting**: Contextual CTA labels for all destructive or safety-critical actions.
+- [x] **Q-03: Backward Compatibility**: Legacy `inventory.env` support maintained during the transition (deprecated).
+- [x] **Q-04: Security**: Masked secrets in logs and subprocess injection protection.
+
+---
+
+## 3. Requirement Outcomes
+- **Validated**: YAML configuration significantly improved developer experience and deployment reliability.
+- **Adjusted**: Initially planned to keep `inventory.env` as primary; adjusted to deprecate it immediately in favor of YAML.
+- **Dropped**: Scale testing with 10k items (Deferred to Phase 8).

.planning/milestones/v1.14.22-ROADMAP.md

@@ -0,0 +1,38 @@
+# Milestone Archive: v1.14.22 — Config Consolidation & Infrastructure
+
+**Shipped:** 2026-04-23
+**Git Tag:** v1.14.22
+**Audit Rating:** 10/10
+
+---
+
+## 1. Executive Summary
+Milestone v1.14.22 focused on the transition from legacy environment-variable-based configuration to a centralized, domain-driven YAML architecture. It established a Single Source of Truth (SSOT) for network topology and replaced all legacy shell scripts with a unified Python management suite.
+
+---
+
+## 2. Phase Breakdown (Phase 7)
+
+### Phase 7: Config Consolidation
+- **Plan 01: Folder Structure**: Created `config/` with YAML schemas and examples.
+- **Plan 02: Backend Refactor**: Migrated `config_loader.py` and `config_manager.py` to YAML.
+- **Plan 03: Script Unification**: Converted `deploy`, `run_standalone`, `install_service`, and `export` to Python.
+- **Plan 04: Docker Integration**: Integrated volume-mounted YAML configs and updated entrypoints.
+- **Hardening Pass**: Fixed typography (NO BOLD), contextual CTAs, and Port 80 SSL conflicts.
+
+---
+
+## 3. Key Accomplishments
+- ✓ **YAML-First Architecture**: Load order enforced (Env > YAML > Secrets > Defaults).
+- ✓ **Python Tooling Suite**: 100% removal of legacy `.sh` management scripts.
+- ✓ **Dynamic Client Discovery**: Frontend automatically finds backend via `network.json` sync.
+- ✓ **Premium UI Polish**: Full compliance with AI_RULES.md typography and copywriting standards.
+- ✓ **Infrastructure Stability**: Robust Caddy standalone proxy with SSL.
+
+---
+
+## 4. Statistics
+- **Phases**: 1
+- **Tasks Completed**: 19
+- **Files Modified**: 45+
+- **Commit Range**: 778d671a..e5bb14d9