docs: fill the untested items and record why the B layer has no graphs

The forward upgrade to 26.7.3 was zero downtime across 87 samples, and since databasechangelog stayed at 210 the rollback to 26.7.0 also succeeded, which narrows D-2's conclusion: rolling back fails when the schema moved, not because of the version number. The row count is the check.

Role changes never reach the upstream through request repetition; the session is a snapshot taken at login and only a new session picks up the new claim. Auditing the docs also surfaced that Prometheus scrapes only keycloak, kubelet, node-exporter and itself, so the B-layer experiments have no metrics to screenshot rather than missing screenshots.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

docs/evidence/followup/01-d2-forward-upgrade.txt

@@ -0,0 +1,32 @@
+=== D-1 절차대로 먼저 백업 ===
+  백업: 395375 bytes
+  마이그레이션 전: 210
+  세션 전: 3
+
+=== ★ 정방향 업그레이드 + 1초 간격 가용성 측정 ===
+  시작: 15:22:59
+partitioned roll out complete: 2 new pods have been updated...
+  완료: 15:24:26
+
+=== 업그레이드 중 외부 응답 시계열 ===
+  200 200 200 200 200 200 200 200 200 200 200 200 200 200 200 200 200 200 200 200 
+  200 200 200 200 200 200 200 200 200 200 200 200 200 200 200 200 200 200 200 200 
+  200 200 200 200 200 200 200 200 200 200 200 200 200 200 200 200 200 200 200 200 
+  200 200 200 200 200 200 200 200 200 200 200 200 200 200 200 200 200 200 200 200 
+  200 200 200 200 200 200 200 
+  200 응답: 87 회
+  비200   : 0
+0 회
+=== 업그레이드 후 ===
+quay.io/keycloak/keycloak:26.7.3
+  Keycloak 26.7.3
+  마이그레이션 후: 210  (전: 210)
+  세션 후:        3  (전: 3)
+
+=== 스키마 마이그레이션이 실제로 있었는가 ===
+  (없으면 26.7.0→26.7.3 에 스키마 변경이 없다는 뜻)
+
+=== 파드 상태와 클러스터 ===
+  keycloak-0   1/1 Running restarts=0
+  keycloak-1   1/1 Running restarts=0
+  cluster: [keycloak-1-11418(v=16.0.14)|47] (2) [keycloak-1-11418(v=16.0.14), keycloak-0-58996(v=16.0.14)]