Style depth labels as pills in section subsection-summary tables

The 5-lifecycle and 6-decision-making sections each open with a
"Sub-section / Focus / Depth" overview table listing all numbered
sub-sections. The depth column was using plain text "Recommended" /
"Minimum" / "Comprehensive" while the rest of the site uses the
colour-coded <span class="maturity-indicator"> pills.

Converted those table cells to use the same pill styling as elsewhere
on the standard pages — Cheat Sheet, sub-section headers, and the
how-to-use page. Visually consistent across the site now.

20 cells changed (10 in 5-lifecycle, 10 in 6-decision-making).

Build verified: 154 pages, no errors.

Author: andibing

src/content/docs/standard/5-lifecycle.mdx

@@ -14,16 +14,16 @@ Lifecycle Management describes how the solution is developed, deployed, operated
 
 | Sub-section | Focus | Depth |
 |------------|-------|-------|
-| 5.1 Software Development & CI/CD | Build and deploy pipelines | Recommended |
-| 5.2 Service Transition & Migration | Migration strategy and cutover | Recommended |
-| 5.3 Test Strategy | Architecturally significant testing | Recommended |
-| 5.4 Release Management | Release frequency and process | Recommended |
-| 5.5 Operations & Support | Support model and SLAs | Recommended |
-| 5.6 Resourcing & Skills | Team capability and readiness | Recommended |
-| 5.7 Service Start | Start-up sequence and dependencies | Comprehensive |
-| 5.8 Maintainability | Patching, certificates, dependencies | Recommended |
-| 5.9 Decommissioning & Legacy Removal | End-of-life and disposal | Recommended |
-| 5.10 Exit Planning | Vendor lock-in and exit strategy | Recommended |
+| 5.1 Software Development & CI/CD | Build and deploy pipelines | <span class="maturity-indicator maturity-recommended">Recommended</span> |
+| 5.2 Service Transition & Migration | Migration strategy and cutover | <span class="maturity-indicator maturity-recommended">Recommended</span> |
+| 5.3 Test Strategy | Architecturally significant testing | <span class="maturity-indicator maturity-recommended">Recommended</span> |
+| 5.4 Release Management | Release frequency and process | <span class="maturity-indicator maturity-recommended">Recommended</span> |
+| 5.5 Operations & Support | Support model and SLAs | <span class="maturity-indicator maturity-recommended">Recommended</span> |
+| 5.6 Resourcing & Skills | Team capability and readiness | <span class="maturity-indicator maturity-recommended">Recommended</span> |
+| 5.7 Service Start | Start-up sequence and dependencies | <span class="maturity-indicator maturity-comprehensive">Comprehensive</span> |
+| 5.8 Maintainability | Patching, certificates, dependencies | <span class="maturity-indicator maturity-recommended">Recommended</span> |
+| 5.9 Decommissioning & Legacy Removal | End-of-life and disposal | <span class="maturity-indicator maturity-recommended">Recommended</span> |
+| 5.10 Exit Planning | Vendor lock-in and exit strategy | <span class="maturity-indicator maturity-recommended">Recommended</span> |
 
 ## 5.1 Software Development & CI/CD
 

src/content/docs/standard/6-decision-making.mdx

@@ -18,16 +18,16 @@ This section captures the decision-making context for the architecture:
 
 | Sub-section | Focus | Depth |
 |------------|-------|-------|
-| 6.1 Constraints | Fixed limitations shaping the design | Minimum |
-| 6.2 Assumptions | Factors believed true but not verified | Minimum |
-| 6.3 Risks | Potential events that could affect the design | Minimum |
-| 6.4 Dependencies | External factors the design relies upon | Minimum |
-| 6.5 Issues | Problems that have already materialised | Recommended |
-| 6.6 Technical Debt Register | Debt introduced or inherited | Recommended |
-| 6.7 Guardrail Exceptions | Exceptions to policies and standards | Recommended |
-| 6.8 Architectural Decisions Log | Summary index of ADRs | Recommended |
-| 6.9 Compliance Traceability | Mapping to standards and principles | Comprehensive |
-| 6.10 Approval Sign-Off | Governance approval record | Minimum |
+| 6.1 Constraints | Fixed limitations shaping the design | <span class="maturity-indicator maturity-minimum">Minimum</span> |
+| 6.2 Assumptions | Factors believed true but not verified | <span class="maturity-indicator maturity-minimum">Minimum</span> |
+| 6.3 Risks | Potential events that could affect the design | <span class="maturity-indicator maturity-minimum">Minimum</span> |
+| 6.4 Dependencies | External factors the design relies upon | <span class="maturity-indicator maturity-minimum">Minimum</span> |
+| 6.5 Issues | Problems that have already materialised | <span class="maturity-indicator maturity-recommended">Recommended</span> |
+| 6.6 Technical Debt Register | Debt introduced or inherited | <span class="maturity-indicator maturity-recommended">Recommended</span> |
+| 6.7 Guardrail Exceptions | Exceptions to policies and standards | <span class="maturity-indicator maturity-recommended">Recommended</span> |
+| 6.8 Architectural Decisions Log | Summary index of ADRs | <span class="maturity-indicator maturity-recommended">Recommended</span> |
+| 6.9 Compliance Traceability | Mapping to standards and principles | <span class="maturity-indicator maturity-comprehensive">Comprehensive</span> |
+| 6.10 Approval Sign-Off | Governance approval record | <span class="maturity-indicator maturity-minimum">Minimum</span> |
 
 Sections 6.1 through 6.5 collectively form the **RAID log** (Risks, Assumptions, Issues, Dependencies) — a standard project governance tool — extended with **Constraints** to capture fixed limitations. Each element has its own sub-section for clarity, but they should be maintained together as a single, living governance artefact.