Fix 30 KB errors: ExaCS storage 3-10x wrong, ECPU transition, IOPS limits, missing shapes

Cross-referenced all 70+ KB files against official Oracle docs. Critical fixes:
- ExaCS: storage was flash cache not usable disk (76.8→190.8 TB QR), added X11M, removed X10M
- ADB-S: OCPU→ECPU migration, 26ai as default, cross-region RTO 15→10 min
- Compute: E5 max 94→126, A2 80→78, added E6/A4/BM shapes, 11 GPU shapes
- Storage: Higher Perf IOPS 35K→50K, UHP 450K→300K, File Storage 25K→50K
- DBCS: E5.Flex max 94→64, storage 80→150 TB, added 26ai
- Networking: FastConnect +400 Gbps, NSG max 120 rules

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

kb/sizing/adb-scaling-behavior.yaml

@@ -4,9 +4,10 @@ description: ADB-S auto-scaling behavior, timing, and sizing implications.
 ---
 
 auto_scaling:
+  notes: "OCPU is legacy billing. ECPU is now default. 1 OCPU ≈ 4 ECPUs."
   ocpu_scaling:
     trigger: "CPU demand exceeds current allocation"
-    max_scale: "3x base OCPUs (up to 128 OCPU maximum)"
+    max_scale: "3x base OCPUs/ECPUs (up to 128 OCPU / 512 ECPU maximum)"
     ramp_up_time: "2-3 minutes to begin scaling"
     ramp_down_time: "After sustained low utilization (5-10 minutes)"
     billing: "Only billed during active scaling period, per OCPU per second"