docs: B-0 — deploy the BFF and read what autoconfiguration actually chose

The authorized client repository is AuthenticatedPrincipalOAuth2AuthorizedClientRepository, keyed by principal with no session id in it, which is the mechanism behind the sharing problem Q1 and Q3 describe. Sharing a store does not fix a lookup key.

Five problems on the way in: only build output was committed under bff/, a duplicate YAML key broke the image build and was invisible until the full log was captured, env placeholders without defaults broke the tests, actuator was behind the login redirect so a 200 was the login page, and the 117KB beans response failed through the proxy.

Deploying two replicas made the login itself fail before any experiment started, because the authorization request lives in per-instance memory and the callback lands elsewhere.

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

.playwright-mcp/console-2026-09-04T03-23-15-961Z.log

@@ -18,3 +18,108 @@
 [   98008ms] [ERROR] WebSocket connection to 'wss://app2.hyeonworks.com/api/live/ws' failed: Error during WebSocket handshake: Unexpected response code: 400 @ https://app2.hyeonworks.com/public/build/1518.a3f1f690c084a37f01c7.js:362
 [  104458ms] [ERROR] WebSocket connection to 'wss://app2.hyeonworks.com/api/live/ws' failed: Error during WebSocket handshake: Unexpected response code: 400 @ https://app2.hyeonworks.com/public/build/1518.a3f1f690c084a37f01c7.js:362
 [  123816ms] [ERROR] WebSocket connection to 'wss://app2.hyeonworks.com/api/live/ws' failed: Error during WebSocket handshake: Unexpected response code: 400 @ https://app2.hyeonworks.com/public/build/1518.a3f1f690c084a37f01c7.js:362
+[  142764ms] [ERROR] WebSocket connection to 'wss://app2.hyeonworks.com/api/live/ws' failed: Error during WebSocket handshake: Unexpected response code: 400 @ https://app2.hyeonworks.com/public/build/1518.a3f1f690c084a37f01c7.js:362
+[  157198ms] [ERROR] WebSocket connection to 'wss://app2.hyeonworks.com/api/live/ws' failed: Error during WebSocket handshake: Unexpected response code: 400 @ https://app2.hyeonworks.com/public/build/1518.a3f1f690c084a37f01c7.js:362
+[  175220ms] [ERROR] WebSocket connection to 'wss://app2.hyeonworks.com/api/live/ws' failed: Error during WebSocket handshake: Unexpected response code: 400 @ https://app2.hyeonworks.com/public/build/1518.a3f1f690c084a37f01c7.js:362
+[  182187ms] [ERROR] WebSocket connection to 'wss://app2.hyeonworks.com/api/live/ws' failed: Error during WebSocket handshake: Unexpected response code: 400 @ https://app2.hyeonworks.com/public/build/1518.a3f1f690c084a37f01c7.js:362
+[  183411ms] [ERROR] WebSocket connection to 'wss://app2.hyeonworks.com/api/live/ws' failed: Error during WebSocket handshake: Unexpected response code: 400 @ https://app2.hyeonworks.com/public/build/1518.a3f1f690c084a37f01c7.js:362
+[  190581ms] [ERROR] WebSocket connection to 'wss://app2.hyeonworks.com/api/live/ws' failed: Error during WebSocket handshake: Unexpected response code: 400 @ https://app2.hyeonworks.com/public/build/1518.a3f1f690c084a37f01c7.js:362
+[  199499ms] [ERROR] WebSocket connection to 'wss://app2.hyeonworks.com/api/live/ws' failed: Error during WebSocket handshake: Unexpected response code: 400 @ https://app2.hyeonworks.com/public/build/1518.a3f1f690c084a37f01c7.js:362
+[  209995ms] [ERROR] WebSocket connection to 'wss://app2.hyeonworks.com/api/live/ws' failed: Error during WebSocket handshake: Unexpected response code: 400 @ https://app2.hyeonworks.com/public/build/1518.a3f1f690c084a37f01c7.js:362
+[  214849ms] [ERROR] WebSocket connection to 'wss://app2.hyeonworks.com/api/live/ws' failed: Error during WebSocket handshake: Unexpected response code: 400 @ https://app2.hyeonworks.com/public/build/1518.a3f1f690c084a37f01c7.js:362
+[  233084ms] [ERROR] WebSocket connection to 'wss://app2.hyeonworks.com/api/live/ws' failed: Error during WebSocket handshake: Unexpected response code: 400 @ https://app2.hyeonworks.com/public/build/1518.a3f1f690c084a37f01c7.js:362
+[  242910ms] [ERROR] WebSocket connection to 'wss://app2.hyeonworks.com/api/live/ws' failed: Error during WebSocket handshake: Unexpected response code: 400 @ https://app2.hyeonworks.com/public/build/1518.a3f1f690c084a37f01c7.js:362
+[  257975ms] [ERROR] WebSocket connection to 'wss://app2.hyeonworks.com/api/live/ws' failed: Error during WebSocket handshake: Unexpected response code: 400 @ https://app2.hyeonworks.com/public/build/1518.a3f1f690c084a37f01c7.js:362
+[  277220ms] [ERROR] WebSocket connection to 'wss://app2.hyeonworks.com/api/live/ws' failed: Error during WebSocket handshake: Unexpected response code: 400 @ https://app2.hyeonworks.com/public/build/1518.a3f1f690c084a37f01c7.js:362
+[  290806ms] [ERROR] WebSocket connection to 'wss://app2.hyeonworks.com/api/live/ws' failed: Error during WebSocket handshake: Unexpected response code: 400 @ https://app2.hyeonworks.com/public/build/1518.a3f1f690c084a37f01c7.js:362
+[  292674ms] [ERROR] WebSocket connection to 'wss://app2.hyeonworks.com/api/live/ws' failed: Error during WebSocket handshake: Unexpected response code: 400 @ https://app2.hyeonworks.com/public/build/1518.a3f1f690c084a37f01c7.js:362
+[  300013ms] [ERROR] WebSocket connection to 'wss://app2.hyeonworks.com/api/live/ws' failed: Error during WebSocket handshake: Unexpected response code: 400 @ https://app2.hyeonworks.com/public/build/1518.a3f1f690c084a37f01c7.js:362
+[  309267ms] [ERROR] WebSocket connection to 'wss://app2.hyeonworks.com/api/live/ws' failed: Error during WebSocket handshake: Unexpected response code: 400 @ https://app2.hyeonworks.com/public/build/1518.a3f1f690c084a37f01c7.js:362
+[  323998ms] [ERROR] WebSocket connection to 'wss://app2.hyeonworks.com/api/live/ws' failed: Error during WebSocket handshake: Unexpected response code: 400 @ https://app2.hyeonworks.com/public/build/1518.a3f1f690c084a37f01c7.js:362
+[  328620ms] [ERROR] WebSocket connection to 'wss://app2.hyeonworks.com/api/live/ws' failed: Error during WebSocket handshake: Unexpected response code: 400 @ https://app2.hyeonworks.com/public/build/1518.a3f1f690c084a37f01c7.js:362
+[  339787ms] [ERROR] WebSocket connection to 'wss://app2.hyeonworks.com/api/live/ws' failed: Error during WebSocket handshake: Unexpected response code: 400 @ https://app2.hyeonworks.com/public/build/1518.a3f1f690c084a37f01c7.js:362
+[  355959ms] [ERROR] WebSocket connection to 'wss://app2.hyeonworks.com/api/live/ws' failed: Error during WebSocket handshake: Unexpected response code: 400 @ https://app2.hyeonworks.com/public/build/1518.a3f1f690c084a37f01c7.js:362
+[  361079ms] [ERROR] WebSocket connection to 'wss://app2.hyeonworks.com/api/live/ws' failed: Error during WebSocket handshake: Unexpected response code: 400 @ https://app2.hyeonworks.com/public/build/1518.a3f1f690c084a37f01c7.js:362
+[  369272ms] [ERROR] WebSocket connection to 'wss://app2.hyeonworks.com/api/live/ws' failed: Error during WebSocket handshake: Unexpected response code: 400 @ https://app2.hyeonworks.com/public/build/1518.a3f1f690c084a37f01c7.js:362
+[  381866ms] [ERROR] WebSocket connection to 'wss://app2.hyeonworks.com/api/live/ws' failed: Error during WebSocket handshake: Unexpected response code: 400 @ https://app2.hyeonworks.com/public/build/1518.a3f1f690c084a37f01c7.js:362
+[  397120ms] [ERROR] WebSocket connection to 'wss://app2.hyeonworks.com/api/live/ws' failed: Error during WebSocket handshake: Unexpected response code: 400 @ https://app2.hyeonworks.com/public/build/1518.a3f1f690c084a37f01c7.js:362
+[  400712ms] [ERROR] WebSocket connection to 'wss://app2.hyeonworks.com/api/live/ws' failed: Error during WebSocket handshake: Unexpected response code: 400 @ https://app2.hyeonworks.com/public/build/1518.a3f1f690c084a37f01c7.js:362
+[  412579ms] [ERROR] WebSocket connection to 'wss://app2.hyeonworks.com/api/live/ws' failed: Error during WebSocket handshake: Unexpected response code: 400 @ https://app2.hyeonworks.com/public/build/1518.a3f1f690c084a37f01c7.js:362
+[  431630ms] [ERROR] WebSocket connection to 'wss://app2.hyeonworks.com/api/live/ws' failed: Error during WebSocket handshake: Unexpected response code: 400 @ https://app2.hyeonworks.com/public/build/1518.a3f1f690c084a37f01c7.js:362
+[  440746ms] [ERROR] WebSocket connection to 'wss://app2.hyeonworks.com/api/live/ws' failed: Error during WebSocket handshake: Unexpected response code: 400 @ https://app2.hyeonworks.com/public/build/1518.a3f1f690c084a37f01c7.js:362
+[  447809ms] [ERROR] WebSocket connection to 'wss://app2.hyeonworks.com/api/live/ws' failed: Error during WebSocket handshake: Unexpected response code: 400 @ https://app2.hyeonworks.com/public/build/1518.a3f1f690c084a37f01c7.js:362
+[  461741ms] [ERROR] WebSocket connection to 'wss://app2.hyeonworks.com/api/live/ws' failed: Error during WebSocket handshake: Unexpected response code: 400 @ https://app2.hyeonworks.com/public/build/1518.a3f1f690c084a37f01c7.js:362
+[  475459ms] [ERROR] WebSocket connection to 'wss://app2.hyeonworks.com/api/live/ws' failed: Error during WebSocket handshake: Unexpected response code: 400 @ https://app2.hyeonworks.com/public/build/1518.a3f1f690c084a37f01c7.js:362
+[  482723ms] [ERROR] WebSocket connection to 'wss://app2.hyeonworks.com/api/live/ws' failed: Error during WebSocket handshake: Unexpected response code: 400 @ https://app2.hyeonworks.com/public/build/1518.a3f1f690c084a37f01c7.js:362
+[  494299ms] [ERROR] WebSocket connection to 'wss://app2.hyeonworks.com/api/live/ws' failed: Error during WebSocket handshake: Unexpected response code: 400 @ https://app2.hyeonworks.com/public/build/1518.a3f1f690c084a37f01c7.js:362
+[  513174ms] [ERROR] WebSocket connection to 'wss://app2.hyeonworks.com/api/live/ws' failed: Error during WebSocket handshake: Unexpected response code: 400 @ https://app2.hyeonworks.com/public/build/1518.a3f1f690c084a37f01c7.js:362
+[  521541ms] [ERROR] WebSocket connection to 'wss://app2.hyeonworks.com/api/live/ws' failed: Error during WebSocket handshake: Unexpected response code: 400 @ https://app2.hyeonworks.com/public/build/1518.a3f1f690c084a37f01c7.js:362
+[  532145ms] [ERROR] WebSocket connection to 'wss://app2.hyeonworks.com/api/live/ws' failed: Error during WebSocket handshake: Unexpected response code: 400 @ https://app2.hyeonworks.com/public/build/1518.a3f1f690c084a37f01c7.js:362
+[  551129ms] [ERROR] WebSocket connection to 'wss://app2.hyeonworks.com/api/live/ws' failed: Error during WebSocket handshake: Unexpected response code: 400 @ https://app2.hyeonworks.com/public/build/1518.a3f1f690c084a37f01c7.js:362
+[  556250ms] [ERROR] WebSocket connection to 'wss://app2.hyeonworks.com/api/live/ws' failed: Error during WebSocket handshake: Unexpected response code: 400 @ https://app2.hyeonworks.com/public/build/1518.a3f1f690c084a37f01c7.js:362
+[  574381ms] [ERROR] WebSocket connection to 'wss://app2.hyeonworks.com/api/live/ws' failed: Error during WebSocket handshake: Unexpected response code: 400 @ https://app2.hyeonworks.com/public/build/1518.a3f1f690c084a37f01c7.js:362
+[  586190ms] [ERROR] WebSocket connection to 'wss://app2.hyeonworks.com/api/live/ws' failed: Error during WebSocket handshake: Unexpected response code: 400 @ https://app2.hyeonworks.com/public/build/1518.a3f1f690c084a37f01c7.js:362
+[  595782ms] [ERROR] WebSocket connection to 'wss://app2.hyeonworks.com/api/live/ws' failed: Error during WebSocket handshake: Unexpected response code: 400 @ https://app2.hyeonworks.com/public/build/1518.a3f1f690c084a37f01c7.js:362
+[  610555ms] [ERROR] WebSocket connection to 'wss://app2.hyeonworks.com/api/live/ws' failed: Error during WebSocket handshake: Unexpected response code: 400 @ https://app2.hyeonworks.com/public/build/1518.a3f1f690c084a37f01c7.js:362
+[  630695ms] [ERROR] WebSocket connection to 'wss://app2.hyeonworks.com/api/live/ws' failed: Error during WebSocket handshake: Unexpected response code: 400 @ https://app2.hyeonworks.com/public/build/1518.a3f1f690c084a37f01c7.js:362
+[  633257ms] [ERROR] WebSocket connection to 'wss://app2.hyeonworks.com/api/live/ws' failed: Error during WebSocket handshake: Unexpected response code: 400 @ https://app2.hyeonworks.com/public/build/1518.a3f1f690c084a37f01c7.js:362
+[  652194ms] [ERROR] WebSocket connection to 'wss://app2.hyeonworks.com/api/live/ws' failed: Error during WebSocket handshake: Unexpected response code: 400 @ https://app2.hyeonworks.com/public/build/1518.a3f1f690c084a37f01c7.js:362
+[  671361ms] [ERROR] WebSocket connection to 'wss://app2.hyeonworks.com/api/live/ws' failed: Error during WebSocket handshake: Unexpected response code: 400 @ https://app2.hyeonworks.com/public/build/1518.a3f1f690c084a37f01c7.js:362
+[  677606ms] [ERROR] WebSocket connection to 'wss://app2.hyeonworks.com/api/live/ws' failed: Error during WebSocket handshake: Unexpected response code: 400 @ https://app2.hyeonworks.com/public/build/1518.a3f1f690c084a37f01c7.js:362
+[  692444ms] [ERROR] WebSocket connection to 'wss://app2.hyeonworks.com/api/live/ws' failed: Error during WebSocket handshake: Unexpected response code: 400 @ https://app2.hyeonworks.com/public/build/1518.a3f1f690c084a37f01c7.js:362
+[  696949ms] [ERROR] WebSocket connection to 'wss://app2.hyeonworks.com/api/live/ws' failed: Error during WebSocket handshake: Unexpected response code: 400 @ https://app2.hyeonworks.com/public/build/1518.a3f1f690c084a37f01c7.js:362
+[  700122ms] [ERROR] WebSocket connection to 'wss://app2.hyeonworks.com/api/live/ws' failed: Error during WebSocket handshake: Unexpected response code: 400 @ https://app2.hyeonworks.com/public/build/1518.a3f1f690c084a37f01c7.js:362
+[  709954ms] [ERROR] WebSocket connection to 'wss://app2.hyeonworks.com/api/live/ws' failed: Error during WebSocket handshake: Unexpected response code: 400 @ https://app2.hyeonworks.com/public/build/1518.a3f1f690c084a37f01c7.js:362
+[  723992ms] [ERROR] WebSocket connection to 'wss://app2.hyeonworks.com/api/live/ws' failed: Error during WebSocket handshake: Unexpected response code: 400 @ https://app2.hyeonworks.com/public/build/1518.a3f1f690c084a37f01c7.js:362
+[  743173ms] [ERROR] WebSocket connection to 'wss://app2.hyeonworks.com/api/live/ws' failed: Error during WebSocket handshake: Unexpected response code: 400 @ https://app2.hyeonworks.com/public/build/1518.a3f1f690c084a37f01c7.js:362
+[  745075ms] [ERROR] WebSocket connection to 'wss://app2.hyeonworks.com/api/live/ws' failed: Error during WebSocket handshake: Unexpected response code: 400 @ https://app2.hyeonworks.com/public/build/1518.a3f1f690c084a37f01c7.js:362
+[  753299ms] [ERROR] WebSocket connection to 'wss://app2.hyeonworks.com/api/live/ws' failed: Error during WebSocket handshake: Unexpected response code: 400 @ https://app2.hyeonworks.com/public/build/1518.a3f1f690c084a37f01c7.js:362
+[  766683ms] [ERROR] WebSocket connection to 'wss://app2.hyeonworks.com/api/live/ws' failed: Error during WebSocket handshake: Unexpected response code: 400 @ https://app2.hyeonworks.com/public/build/1518.a3f1f690c084a37f01c7.js:362
+[  767855ms] [ERROR] WebSocket connection to 'wss://app2.hyeonworks.com/api/live/ws' failed: Error during WebSocket handshake: Unexpected response code: 400 @ https://app2.hyeonworks.com/public/build/1518.a3f1f690c084a37f01c7.js:362
+[  787261ms] [ERROR] WebSocket connection to 'wss://app2.hyeonworks.com/api/live/ws' failed: Error during WebSocket handshake: Unexpected response code: 400 @ https://app2.hyeonworks.com/public/build/1518.a3f1f690c084a37f01c7.js:362
+[  789725ms] [ERROR] WebSocket connection to 'wss://app2.hyeonworks.com/api/live/ws' failed: Error during WebSocket handshake: Unexpected response code: 400 @ https://app2.hyeonworks.com/public/build/1518.a3f1f690c084a37f01c7.js:362
+[  800680ms] [ERROR] WebSocket connection to 'wss://app2.hyeonworks.com/api/live/ws' failed: Error during WebSocket handshake: Unexpected response code: 400 @ https://app2.hyeonworks.com/public/build/1518.a3f1f690c084a37f01c7.js:362
+[  811324ms] [ERROR] WebSocket connection to 'wss://app2.hyeonworks.com/api/live/ws' failed: Error during WebSocket handshake: Unexpected response code: 400 @ https://app2.hyeonworks.com/public/build/1518.a3f1f690c084a37f01c7.js:362
+[  814096ms] [ERROR] WebSocket connection to 'wss://app2.hyeonworks.com/api/live/ws' failed: Error during WebSocket handshake: Unexpected response code: 400 @ https://app2.hyeonworks.com/public/build/1518.a3f1f690c084a37f01c7.js:362
+[  829045ms] [ERROR] WebSocket connection to 'wss://app2.hyeonworks.com/api/live/ws' failed: Error during WebSocket handshake: Unexpected response code: 400 @ https://app2.hyeonworks.com/public/build/1518.a3f1f690c084a37f01c7.js:362
+[  848506ms] [ERROR] WebSocket connection to 'wss://app2.hyeonworks.com/api/live/ws' failed: Error during WebSocket handshake: Unexpected response code: 400 @ https://app2.hyeonworks.com/public/build/1518.a3f1f690c084a37f01c7.js:362
+[  857716ms] [ERROR] WebSocket connection to 'wss://app2.hyeonworks.com/api/live/ws' failed: Error during WebSocket handshake: Unexpected response code: 400 @ https://app2.hyeonworks.com/public/build/1518.a3f1f690c084a37f01c7.js:362
+[  866212ms] [ERROR] WebSocket connection to 'wss://app2.hyeonworks.com/api/live/ws' failed: Error during WebSocket handshake: Unexpected response code: 400 @ https://app2.hyeonworks.com/public/build/1518.a3f1f690c084a37f01c7.js:362
+[  873174ms] [ERROR] WebSocket connection to 'wss://app2.hyeonworks.com/api/live/ws' failed: Error during WebSocket handshake: Unexpected response code: 400 @ https://app2.hyeonworks.com/public/build/1518.a3f1f690c084a37f01c7.js:362
+[  876033ms] [ERROR] WebSocket connection to 'wss://app2.hyeonworks.com/api/live/ws' failed: Error during WebSocket handshake: Unexpected response code: 400 @ https://app2.hyeonworks.com/public/build/1518.a3f1f690c084a37f01c7.js:362
+[  895198ms] [ERROR] WebSocket connection to 'wss://app2.hyeonworks.com/api/live/ws' failed: Error during WebSocket handshake: Unexpected response code: 400 @ https://app2.hyeonworks.com/public/build/1518.a3f1f690c084a37f01c7.js:362
+[  898884ms] [ERROR] WebSocket connection to 'wss://app2.hyeonworks.com/api/live/ws' failed: Error during WebSocket handshake: Unexpected response code: 400 @ https://app2.hyeonworks.com/public/build/1518.a3f1f690c084a37f01c7.js:362
+[  918642ms] [ERROR] WebSocket connection to 'wss://app2.hyeonworks.com/api/live/ws' failed: Error during WebSocket handshake: Unexpected response code: 400 @ https://app2.hyeonworks.com/public/build/1518.a3f1f690c084a37f01c7.js:362
+[  930133ms] [ERROR] WebSocket connection to 'wss://app2.hyeonworks.com/api/live/ws' failed: Error during WebSocket handshake: Unexpected response code: 400 @ https://app2.hyeonworks.com/public/build/1518.a3f1f690c084a37f01c7.js:362
+[  934008ms] [ERROR] WebSocket connection to 'wss://app2.hyeonworks.com/api/live/ws' failed: Error during WebSocket handshake: Unexpected response code: 400 @ https://app2.hyeonworks.com/public/build/1518.a3f1f690c084a37f01c7.js:362
+[  948541ms] [ERROR] WebSocket connection to 'wss://app2.hyeonworks.com/api/live/ws' failed: Error during WebSocket handshake: Unexpected response code: 400 @ https://app2.hyeonworks.com/public/build/1518.a3f1f690c084a37f01c7.js:362
+[  956860ms] [ERROR] WebSocket connection to 'wss://app2.hyeonworks.com/api/live/ws' failed: Error during WebSocket handshake: Unexpected response code: 400 @ https://app2.hyeonworks.com/public/build/1518.a3f1f690c084a37f01c7.js:362
+[  959397ms] [ERROR] WebSocket connection to 'wss://app2.hyeonworks.com/api/live/ws' failed: Error during WebSocket handshake: Unexpected response code: 400 @ https://app2.hyeonworks.com/public/build/1518.a3f1f690c084a37f01c7.js:362
+[  968406ms] [ERROR] WebSocket connection to 'wss://app2.hyeonworks.com/api/live/ws' failed: Error during WebSocket handshake: Unexpected response code: 400 @ https://app2.hyeonworks.com/public/build/1518.a3f1f690c084a37f01c7.js:362
+[  971788ms] [ERROR] WebSocket connection to 'wss://app2.hyeonworks.com/api/live/ws' failed: Error during WebSocket handshake: Unexpected response code: 400 @ https://app2.hyeonworks.com/public/build/1518.a3f1f690c084a37f01c7.js:362
+[  982746ms] [ERROR] WebSocket connection to 'wss://app2.hyeonworks.com/api/live/ws' failed: Error during WebSocket handshake: Unexpected response code: 400 @ https://app2.hyeonworks.com/public/build/1518.a3f1f690c084a37f01c7.js:362
+[  997394ms] [ERROR] WebSocket connection to 'wss://app2.hyeonworks.com/api/live/ws' failed: Error during WebSocket handshake: Unexpected response code: 400 @ https://app2.hyeonworks.com/public/build/1518.a3f1f690c084a37f01c7.js:362
+[ 1005078ms] [ERROR] WebSocket connection to 'wss://app2.hyeonworks.com/api/live/ws' failed: Error during WebSocket handshake: Unexpected response code: 400 @ https://app2.hyeonworks.com/public/build/1518.a3f1f690c084a37f01c7.js:362
+[ 1009269ms] [ERROR] WebSocket connection to 'wss://app2.hyeonworks.com/api/live/ws' failed: Error during WebSocket handshake: Unexpected response code: 400 @ https://app2.hyeonworks.com/public/build/1518.a3f1f690c084a37f01c7.js:362
+[ 1021453ms] [ERROR] WebSocket connection to 'wss://app2.hyeonworks.com/api/live/ws' failed: Error during WebSocket handshake: Unexpected response code: 400 @ https://app2.hyeonworks.com/public/build/1518.a3f1f690c084a37f01c7.js:362
+[ 1026674ms] [ERROR] WebSocket connection to 'wss://app2.hyeonworks.com/api/live/ws' failed: Error during WebSocket handshake: Unexpected response code: 400 @ https://app2.hyeonworks.com/public/build/1518.a3f1f690c084a37f01c7.js:362
+[ 1042137ms] [ERROR] WebSocket connection to 'wss://app2.hyeonworks.com/api/live/ws' failed: Error during WebSocket handshake: Unexpected response code: 400 @ https://app2.hyeonworks.com/public/build/1518.a3f1f690c084a37f01c7.js:362
+[ 1057497ms] [ERROR] WebSocket connection to 'wss://app2.hyeonworks.com/api/live/ws' failed: Error during WebSocket handshake: Unexpected response code: 400 @ https://app2.hyeonworks.com/public/build/1518.a3f1f690c084a37f01c7.js:362
+[ 1059851ms] [ERROR] WebSocket connection to 'wss://app2.hyeonworks.com/api/live/ws' failed: Error during WebSocket handshake: Unexpected response code: 400 @ https://app2.hyeonworks.com/public/build/1518.a3f1f690c084a37f01c7.js:362
+[ 1061855ms] [ERROR] WebSocket connection to 'wss://app2.hyeonworks.com/api/live/ws' failed: Error during WebSocket handshake: Unexpected response code: 400 @ https://app2.hyeonworks.com/public/build/1518.a3f1f690c084a37f01c7.js:362
+[ 1071317ms] [ERROR] WebSocket connection to 'wss://app2.hyeonworks.com/api/live/ws' failed: Error during WebSocket handshake: Unexpected response code: 400 @ https://app2.hyeonworks.com/public/build/1518.a3f1f690c084a37f01c7.js:362
+[ 1078179ms] [ERROR] WebSocket connection to 'wss://app2.hyeonworks.com/api/live/ws' failed: Error during WebSocket handshake: Unexpected response code: 400 @ https://app2.hyeonworks.com/public/build/1518.a3f1f690c084a37f01c7.js:362
+[ 1084940ms] [ERROR] WebSocket connection to 'wss://app2.hyeonworks.com/api/live/ws' failed: Error during WebSocket handshake: Unexpected response code: 400 @ https://app2.hyeonworks.com/public/build/1518.a3f1f690c084a37f01c7.js:362
+[ 1093950ms] [ERROR] WebSocket connection to 'wss://app2.hyeonworks.com/api/live/ws' failed: Error during WebSocket handshake: Unexpected response code: 400 @ https://app2.hyeonworks.com/public/build/1518.a3f1f690c084a37f01c7.js:362
+[ 1112279ms] [ERROR] WebSocket connection to 'wss://app2.hyeonworks.com/api/live/ws' failed: Error during WebSocket handshake: Unexpected response code: 400 @ https://app2.hyeonworks.com/public/build/1518.a3f1f690c084a37f01c7.js:362
+[ 1124360ms] [ERROR] WebSocket connection to 'wss://app2.hyeonworks.com/api/live/ws' failed: Error during WebSocket handshake: Unexpected response code: 400 @ https://app2.hyeonworks.com/public/build/1518.a3f1f690c084a37f01c7.js:362
+[ 1139110ms] [ERROR] WebSocket connection to 'wss://app2.hyeonworks.com/api/live/ws' failed: Error during WebSocket handshake: Unexpected response code: 400 @ https://app2.hyeonworks.com/public/build/1518.a3f1f690c084a37f01c7.js:362
+[ 1157981ms] [ERROR] WebSocket connection to 'wss://app2.hyeonworks.com/api/live/ws' failed: Error during WebSocket handshake: Unexpected response code: 400 @ https://app2.hyeonworks.com/public/build/1518.a3f1f690c084a37f01c7.js:362
+[ 1163071ms] [ERROR] WebSocket connection to 'wss://app2.hyeonworks.com/api/live/ws' failed: Error during WebSocket handshake: Unexpected response code: 400 @ https://app2.hyeonworks.com/public/build/1518.a3f1f690c084a37f01c7.js:362
+[ 1179032ms] [ERROR] WebSocket connection to 'wss://app2.hyeonworks.com/api/live/ws' failed: Error during WebSocket handshake: Unexpected response code: 400 @ https://app2.hyeonworks.com/public/build/1518.a3f1f690c084a37f01c7.js:362
+[ 1181195ms] [ERROR] WebSocket connection to 'wss://app2.hyeonworks.com/api/live/ws' failed: Error during WebSocket handshake: Unexpected response code: 400 @ https://app2.hyeonworks.com/public/build/1518.a3f1f690c084a37f01c7.js:362
+[ 1191955ms] [ERROR] WebSocket connection to 'wss://app2.hyeonworks.com/api/live/ws' failed: Error during WebSocket handshake: Unexpected response code: 400 @ https://app2.hyeonworks.com/public/build/1518.a3f1f690c084a37f01c7.js:362
+[ 1201472ms] [ERROR] WebSocket connection to 'wss://app2.hyeonworks.com/api/live/ws' failed: Error during WebSocket handshake: Unexpected response code: 400 @ https://app2.hyeonworks.com/public/build/1518.a3f1f690c084a37f01c7.js:362
+[ 1218261ms] [ERROR] WebSocket connection to 'wss://app2.hyeonworks.com/api/live/ws' failed: Error during WebSocket handshake: Unexpected response code: 400 @ https://app2.hyeonworks.com/public/build/1518.a3f1f690c084a37f01c7.js:362
+[ 1221169ms] [ERROR] WebSocket connection to 'wss://app2.hyeonworks.com/api/live/ws' failed: Error during WebSocket handshake: Unexpected response code: 400 @ https://app2.hyeonworks.com/public/build/1518.a3f1f690c084a37f01c7.js:362
+[ 1229430ms] [ERROR] WebSocket connection to 'wss://app2.hyeonworks.com/api/live/ws' failed: Error during WebSocket handshake: Unexpected response code: 400 @ https://app2.hyeonworks.com/public/build/1518.a3f1f690c084a37f01c7.js:362

.playwright-mcp/console-2026-09-04T03-43-55-141Z.log

@@ -0,0 +1,50 @@
+[     199ms] [ERROR] WebSocket connection to 'wss://app2.hyeonworks.com/api/live/ws' failed: Error during WebSocket handshake: Unexpected response code: 400 @ https://app2.hyeonworks.com/public/build/1518.a3f1f690c084a37f01c7.js:362
+[     297ms] [WARNING] <meta name="apple-mobile-web-app-capable" content="yes"> is deprecated. Please include <meta name="mobile-web-app-capable" content="yes"> @ https://app2.hyeonworks.com/explore?schemaVersion=1&orgId=1&panes=%7B%22a%22%3A%7B%22datasource%22%3A%22PBFA97CFB590B2093%22%2C%22queries%22%3A%5B%7B%22refId%22%3A%22A%22%2C%22expr%22%3A%22vendor_cluster_size%22%2C%22range%22%3Atrue%2C%22instant%22%3Afalse%2C%22editorMode%22%3A%22code%22%2C%22legendFormat%22%3A%22%7B%7Bpod%7D%7D%22%2C%22datasource%22%3A%7B%22type%22%3A%22prometheus%22%2C%22uid%22%3A%22PBFA97CFB590B2093%22%7D%7D%5D%2C%22range%22%3A%7B%22from%22%3A%22now-25m%22%2C%22to%22%3A%22now%22%7D%7D%7D:0
+[    1000ms] [ERROR] WebSocket connection to 'wss://app2.hyeonworks.com/api/live/ws' failed: Error during WebSocket handshake: Unexpected response code: 400 @ https://app2.hyeonworks.com/public/build/1518.a3f1f690c084a37f01c7.js:362
+[    2023ms] [ERROR] WebSocket connection to 'wss://app2.hyeonworks.com/api/live/ws' failed: Error during WebSocket handshake: Unexpected response code: 400 @ https://app2.hyeonworks.com/public/build/1518.a3f1f690c084a37f01c7.js:362
+[    3559ms] [ERROR] WebSocket connection to 'wss://app2.hyeonworks.com/api/live/ws' failed: Error during WebSocket handshake: Unexpected response code: 400 @ https://app2.hyeonworks.com/public/build/1518.a3f1f690c084a37f01c7.js:362
+[    7749ms] [ERROR] WebSocket connection to 'wss://app2.hyeonworks.com/api/live/ws' failed: Error during WebSocket handshake: Unexpected response code: 400 @ https://app2.hyeonworks.com/public/build/1518.a3f1f690c084a37f01c7.js:362
+[   16364ms] [ERROR] WebSocket connection to 'wss://app2.hyeonworks.com/api/live/ws' failed: Error during WebSocket handshake: Unexpected response code: 400 @ https://app2.hyeonworks.com/public/build/1518.a3f1f690c084a37f01c7.js:362
+[   25781ms] [ERROR] WebSocket connection to 'wss://app2.hyeonworks.com/api/live/ws' failed: Error during WebSocket handshake: Unexpected response code: 400 @ https://app2.hyeonworks.com/public/build/1518.a3f1f690c084a37f01c7.js:362
+[   42158ms] [ERROR] WebSocket connection to 'wss://app2.hyeonworks.com/api/live/ws' failed: Error during WebSocket handshake: Unexpected response code: 400 @ https://app2.hyeonworks.com/public/build/1518.a3f1f690c084a37f01c7.js:362
+[   59672ms] [ERROR] WebSocket connection to 'wss://app2.hyeonworks.com/api/live/ws' failed: Error during WebSocket handshake: Unexpected response code: 400 @ https://app2.hyeonworks.com/public/build/1518.a3f1f690c084a37f01c7.js:362
+[   77090ms] [ERROR] WebSocket connection to 'wss://app2.hyeonworks.com/api/live/ws' failed: Error during WebSocket handshake: Unexpected response code: 400 @ https://app2.hyeonworks.com/public/build/1518.a3f1f690c084a37f01c7.js:362
+[   87426ms] [ERROR] WebSocket connection to 'wss://app2.hyeonworks.com/api/live/ws' failed: Error during WebSocket handshake: Unexpected response code: 400 @ https://app2.hyeonworks.com/public/build/1518.a3f1f690c084a37f01c7.js:362
+[   89952ms] [ERROR] WebSocket connection to 'wss://app2.hyeonworks.com/api/live/ws' failed: Error during WebSocket handshake: Unexpected response code: 400 @ https://app2.hyeonworks.com/public/build/1518.a3f1f690c084a37f01c7.js:362
+[  104743ms] [ERROR] WebSocket connection to 'wss://app2.hyeonworks.com/api/live/ws' failed: Error in connection establishment: net::ERR_NAME_NOT_RESOLVED @ https://app2.hyeonworks.com/public/build/1518.a3f1f690c084a37f01c7.js:362
+[ 1573121ms] [WARNING] WebSocket connection to 'wss://app2.hyeonworks.com/api/live/ws' failed: WebSocket is closed before the connection is established. @ https://app2.hyeonworks.com/public/build/1518.a3f1f690c084a37f01c7.js:362
+[ 1584038ms] [ERROR] WebSocket connection to 'wss://app2.hyeonworks.com/api/live/ws' failed: HTTP Authentication failed; no valid credentials available @ https://app2.hyeonworks.com/public/build/1518.a3f1f690c084a37f01c7.js:362
+[ 1601626ms] [ERROR] WebSocket connection to 'wss://app2.hyeonworks.com/api/live/ws' failed: HTTP Authentication failed; no valid credentials available @ https://app2.hyeonworks.com/public/build/1518.a3f1f690c084a37f01c7.js:362
+[ 1613280ms] [ERROR] WebSocket connection to 'wss://app2.hyeonworks.com/api/live/ws' failed: HTTP Authentication failed; no valid credentials available @ https://app2.hyeonworks.com/public/build/1518.a3f1f690c084a37f01c7.js:362
+[ 1630173ms] [ERROR] WebSocket connection to 'wss://app2.hyeonworks.com/api/live/ws' failed: HTTP Authentication failed; no valid credentials available @ https://app2.hyeonworks.com/public/build/1518.a3f1f690c084a37f01c7.js:362
+[ 1634776ms] [ERROR] WebSocket connection to 'wss://app2.hyeonworks.com/api/live/ws' failed: HTTP Authentication failed; no valid credentials available @ https://app2.hyeonworks.com/public/build/1518.a3f1f690c084a37f01c7.js:362
+[ 1654205ms] [ERROR] WebSocket connection to 'wss://app2.hyeonworks.com/api/live/ws' failed: HTTP Authentication failed; no valid credentials available @ https://app2.hyeonworks.com/public/build/1518.a3f1f690c084a37f01c7.js:362
+[ 1661576ms] [ERROR] WebSocket connection to 'wss://app2.hyeonworks.com/api/live/ws' failed: HTTP Authentication failed; no valid credentials available @ https://app2.hyeonworks.com/public/build/1518.a3f1f690c084a37f01c7.js:362
+[ 1665269ms] [ERROR] WebSocket connection to 'wss://app2.hyeonworks.com/api/live/ws' failed: HTTP Authentication failed; no valid credentials available @ https://app2.hyeonworks.com/public/build/1518.a3f1f690c084a37f01c7.js:362
+[ 1682669ms] [ERROR] WebSocket connection to 'wss://app2.hyeonworks.com/api/live/ws' failed: HTTP Authentication failed; no valid credentials available @ https://app2.hyeonworks.com/public/build/1518.a3f1f690c084a37f01c7.js:362
+[ 1689435ms] [ERROR] WebSocket connection to 'wss://app2.hyeonworks.com/api/live/ws' failed: HTTP Authentication failed; no valid credentials available @ https://app2.hyeonworks.com/public/build/1518.a3f1f690c084a37f01c7.js:362
+[ 1704385ms] [ERROR] WebSocket connection to 'wss://app2.hyeonworks.com/api/live/ws' failed: HTTP Authentication failed; no valid credentials available @ https://app2.hyeonworks.com/public/build/1518.a3f1f690c084a37f01c7.js:362
+[ 1706314ms] [ERROR] WebSocket connection to 'wss://app2.hyeonworks.com/api/live/ws' failed: HTTP Authentication failed; no valid credentials available @ https://app2.hyeonworks.com/public/build/1518.a3f1f690c084a37f01c7.js:362
+[ 1724551ms] [ERROR] WebSocket connection to 'wss://app2.hyeonworks.com/api/live/ws' failed: HTTP Authentication failed; no valid credentials available @ https://app2.hyeonworks.com/public/build/1518.a3f1f690c084a37f01c7.js:362
+[ 1743701ms] [ERROR] WebSocket connection to 'wss://app2.hyeonworks.com/api/live/ws' failed: HTTP Authentication failed; no valid credentials available @ https://app2.hyeonworks.com/public/build/1518.a3f1f690c084a37f01c7.js:362
+[ 1758339ms] [ERROR] WebSocket connection to 'wss://app2.hyeonworks.com/api/live/ws' failed: HTTP Authentication failed; no valid credentials available @ https://app2.hyeonworks.com/public/build/1518.a3f1f690c084a37f01c7.js:362
+[ 1769299ms] [ERROR] WebSocket connection to 'wss://app2.hyeonworks.com/api/live/ws' failed: HTTP Authentication failed; no valid credentials available @ https://app2.hyeonworks.com/public/build/1518.a3f1f690c084a37f01c7.js:362
+[ 1789478ms] [ERROR] WebSocket connection to 'wss://app2.hyeonworks.com/api/live/ws' failed: HTTP Authentication failed; no valid credentials available @ https://app2.hyeonworks.com/public/build/1518.a3f1f690c084a37f01c7.js:362
+[ 1795415ms] [ERROR] WebSocket connection to 'wss://app2.hyeonworks.com/api/live/ws' failed: HTTP Authentication failed; no valid credentials available @ https://app2.hyeonworks.com/public/build/1518.a3f1f690c084a37f01c7.js:362
+[ 1815382ms] [ERROR] WebSocket connection to 'wss://app2.hyeonworks.com/api/live/ws' failed: HTTP Authentication failed; no valid credentials available @ https://app2.hyeonworks.com/public/build/1518.a3f1f690c084a37f01c7.js:362
+[ 1820392ms] [ERROR] WebSocket connection to 'wss://app2.hyeonworks.com/api/live/ws' failed: HTTP Authentication failed; no valid credentials available @ https://app2.hyeonworks.com/public/build/1518.a3f1f690c084a37f01c7.js:362
+[ 1822445ms] [ERROR] WebSocket connection to 'wss://app2.hyeonworks.com/api/live/ws' failed: HTTP Authentication failed; no valid credentials available @ https://app2.hyeonworks.com/public/build/1518.a3f1f690c084a37f01c7.js:362
+[ 1839035ms] [ERROR] WebSocket connection to 'wss://app2.hyeonworks.com/api/live/ws' failed: HTTP Authentication failed; no valid credentials available @ https://app2.hyeonworks.com/public/build/1518.a3f1f690c084a37f01c7.js:362
+[ 1840162ms] [ERROR] WebSocket connection to 'wss://app2.hyeonworks.com/api/live/ws' failed: HTTP Authentication failed; no valid credentials available @ https://app2.hyeonworks.com/public/build/1518.a3f1f690c084a37f01c7.js:362
+[ 1847739ms] [ERROR] WebSocket connection to 'wss://app2.hyeonworks.com/api/live/ws' failed: HTTP Authentication failed; no valid credentials available @ https://app2.hyeonworks.com/public/build/1518.a3f1f690c084a37f01c7.js:362
+[ 1861419ms] [ERROR] WebSocket connection to 'wss://app2.hyeonworks.com/api/live/ws' failed: HTTP Authentication failed; no valid credentials available @ https://app2.hyeonworks.com/public/build/1518.a3f1f690c084a37f01c7.js:362
+[ 1880381ms] [ERROR] WebSocket connection to 'wss://app2.hyeonworks.com/api/live/ws' failed: HTTP Authentication failed; no valid credentials available @ https://app2.hyeonworks.com/public/build/1518.a3f1f690c084a37f01c7.js:362
+[ 1893315ms] [ERROR] WebSocket connection to 'wss://app2.hyeonworks.com/api/live/ws' failed: HTTP Authentication failed; no valid credentials available @ https://app2.hyeonworks.com/public/build/1518.a3f1f690c084a37f01c7.js:362
+[ 1911434ms] [ERROR] WebSocket connection to 'wss://app2.hyeonworks.com/api/live/ws' failed: HTTP Authentication failed; no valid credentials available @ https://app2.hyeonworks.com/public/build/1518.a3f1f690c084a37f01c7.js:362
+[ 1922701ms] [ERROR] WebSocket connection to 'wss://app2.hyeonworks.com/api/live/ws' failed: HTTP Authentication failed; no valid credentials available @ https://app2.hyeonworks.com/public/build/1518.a3f1f690c084a37f01c7.js:362
+[ 1933868ms] [ERROR] WebSocket connection to 'wss://app2.hyeonworks.com/api/live/ws' failed: HTTP Authentication failed; no valid credentials available @ https://app2.hyeonworks.com/public/build/1518.a3f1f690c084a37f01c7.js:362
+[ 1944951ms] [ERROR] WebSocket connection to 'wss://app2.hyeonworks.com/api/live/ws' failed: Error during WebSocket handshake: Unexpected response code: 400 @ https://app2.hyeonworks.com/public/build/1518.a3f1f690c084a37f01c7.js:362
+[ 1948001ms] [ERROR] WebSocket connection to 'wss://app2.hyeonworks.com/api/live/ws' failed: Error during WebSocket handshake: Unexpected response code: 400 @ https://app2.hyeonworks.com/public/build/1518.a3f1f690c084a37f01c7.js:362
+[ 1952503ms] [ERROR] WebSocket connection to 'wss://app2.hyeonworks.com/api/live/ws' failed: Error during WebSocket handshake: Unexpected response code: 400 @ https://app2.hyeonworks.com/public/build/1518.a3f1f690c084a37f01c7.js:362
+[ 1953320ms] [ERROR] WebSocket connection to 'wss://app2.hyeonworks.com/api/live/ws' failed: Error during WebSocket handshake: Unexpected response code: 400 @ https://app2.hyeonworks.com/public/build/1518.a3f1f690c084a37f01c7.js:362
+[ 1955369ms] [ERROR] WebSocket connection to 'wss://app2.hyeonworks.com/api/live/ws' failed: Error during WebSocket handshake: Unexpected response code: 400 @ https://app2.hyeonworks.com/public/build/1518.a3f1f690c084a37f01c7.js:362

.playwright-mcp/console-2026-09-04T04-16-32-330Z.log

@@ -0,0 +1,20 @@
+[     585ms] [ERROR] WebSocket connection to 'wss://app2.hyeonworks.com/api/live/ws' failed: Error during WebSocket handshake: Unexpected response code: 400 @ https://app2.hyeonworks.com/public/build/1518.a3f1f690c084a37f01c7.js:362
+[    1132ms] [WARNING] <meta name="apple-mobile-web-app-capable" content="yes"> is deprecated. Please include <meta name="mobile-web-app-capable" content="yes"> @ https://app2.hyeonworks.com/explore?schemaVersion=1&panes=%7B%22o68%22%3A%7B%22datasource%22%3A%22PBFA97CFB590B2093%22%2C%22queries%22%3A%5B%7B%22refId%22%3A%22A%22%2C%22expr%22%3A%22agroal_blocking_time_max_milliseconds%22%2C%22range%22%3Atrue%2C%22instant%22%3Afalse%2C%22editorMode%22%3A%22code%22%2C%22legendFormat%22%3A%22blocking+max+-+%7B%7Bpod%7D%7D%22%2C%22datasource%22%3A%7B%22type%22%3A%22prometheus%22%2C%22uid%22%3A%22PBFA97CFB590B2093%22%7D%7D%5D%2C%22range%22%3A%7B%22from%22%3A%22now-30m%22%2C%22to%22%3A%22now%22%7D%7D%7D&orgId=1:0
+[    1555ms] [ERROR] WebSocket connection to 'wss://app2.hyeonworks.com/api/live/ws' failed: Error during WebSocket handshake: Unexpected response code: 400 @ https://app2.hyeonworks.com/public/build/1518.a3f1f690c084a37f01c7.js:362
+[    3604ms] [ERROR] WebSocket connection to 'wss://app2.hyeonworks.com/api/live/ws' failed: Error during WebSocket handshake: Unexpected response code: 400 @ https://app2.hyeonworks.com/public/build/1518.a3f1f690c084a37f01c7.js:362
+[    6373ms] [ERROR] WebSocket connection to 'wss://app2.hyeonworks.com/api/live/ws' failed: Error during WebSocket handshake: Unexpected response code: 400 @ https://app2.hyeonworks.com/public/build/1518.a3f1f690c084a37f01c7.js:362
+[    9135ms] [ERROR] WebSocket connection to 'wss://app2.hyeonworks.com/api/live/ws' failed: Error during WebSocket handshake: Unexpected response code: 400 @ https://app2.hyeonworks.com/public/build/1518.a3f1f690c084a37f01c7.js:362
+[   19066ms] [ERROR] WebSocket connection to 'wss://app2.hyeonworks.com/api/live/ws' failed: Error during WebSocket handshake: Unexpected response code: 400 @ https://app2.hyeonworks.com/public/build/1518.a3f1f690c084a37f01c7.js:362
+[   24595ms] [ERROR] WebSocket connection to 'wss://app2.hyeonworks.com/api/live/ws' failed: Error during WebSocket handshake: Unexpected response code: 400 @ https://app2.hyeonworks.com/public/build/1518.a3f1f690c084a37f01c7.js:362
+[   47125ms] [ERROR] WebSocket connection to 'wss://app2.hyeonworks.com/api/live/ws' failed: Error during WebSocket handshake: Unexpected response code: 400 @ https://app2.hyeonworks.com/public/build/1518.a3f1f690c084a37f01c7.js:362
+[   52154ms] [ERROR] WebSocket connection to 'wss://app2.hyeonworks.com/api/live/ws' failed: Error during WebSocket handshake: Unexpected response code: 400 @ https://app2.hyeonworks.com/public/build/1518.a3f1f690c084a37f01c7.js:362
+[   67608ms] [ERROR] WebSocket connection to 'wss://app2.hyeonworks.com/api/live/ws' failed: Error during WebSocket handshake: Unexpected response code: 400 @ https://app2.hyeonworks.com/public/build/1518.a3f1f690c084a37f01c7.js:362
+[   86965ms] [ERROR] WebSocket connection to 'wss://app2.hyeonworks.com/api/live/ws' failed: Error during WebSocket handshake: Unexpected response code: 400 @ https://app2.hyeonworks.com/public/build/1518.a3f1f690c084a37f01c7.js:362
+[  108668ms] [ERROR] WebSocket connection to 'wss://app2.hyeonworks.com/api/live/ws' failed: Error during WebSocket handshake: Unexpected response code: 400 @ https://app2.hyeonworks.com/public/build/1518.a3f1f690c084a37f01c7.js:362
+[  129158ms] [ERROR] WebSocket connection to 'wss://app2.hyeonworks.com/api/live/ws' failed: Error during WebSocket handshake: Unexpected response code: 400 @ https://app2.hyeonworks.com/public/build/1518.a3f1f690c084a37f01c7.js:362
+[  137544ms] [ERROR] WebSocket connection to 'wss://app2.hyeonworks.com/api/live/ws' failed: Error during WebSocket handshake: Unexpected response code: 400 @ https://app2.hyeonworks.com/public/build/1518.a3f1f690c084a37f01c7.js:362
+[  152699ms] [ERROR] WebSocket connection to 'wss://app2.hyeonworks.com/api/live/ws' failed: Error during WebSocket handshake: Unexpected response code: 400 @ https://app2.hyeonworks.com/public/build/1518.a3f1f690c084a37f01c7.js:362
+[  159898ms] [ERROR] WebSocket connection to 'wss://app2.hyeonworks.com/api/live/ws' failed: Error during WebSocket handshake: Unexpected response code: 400 @ https://app2.hyeonworks.com/public/build/1518.a3f1f690c084a37f01c7.js:362
+[  173491ms] [ERROR] WebSocket connection to 'wss://app2.hyeonworks.com/api/live/ws' failed: Error during WebSocket handshake: Unexpected response code: 400 @ https://app2.hyeonworks.com/public/build/1518.a3f1f690c084a37f01c7.js:362
+[  187925ms] [ERROR] WebSocket connection to 'wss://app2.hyeonworks.com/api/live/ws' failed: Error during WebSocket handshake: Unexpected response code: 400 @ https://app2.hyeonworks.com/public/build/1518.a3f1f690c084a37f01c7.js:362
+[  197824ms] [ERROR] WebSocket connection to 'wss://app2.hyeonworks.com/api/live/ws' failed: Error during WebSocket handshake: Unexpected response code: 400 @ https://app2.hyeonworks.com/public/build/1518.a3f1f690c084a37f01c7.js:362

.playwright-mcp/console-2026-09-04T04-19-58-373Z.log

@@ -0,0 +1,143 @@
+[     635ms] [WARNING] <meta name="apple-mobile-web-app-capable" content="yes"> is deprecated. Please include <meta name="mobile-web-app-capable" content="yes"> @ https://app2.hyeonworks.com/explore?schemaVersion=1&orgId=1&panes=%7B%22a%22%3A%7B%22datasource%22%3A%22PBFA97CFB590B2093%22%2C%22queries%22%3A%5B%7B%22refId%22%3A%22A%22%2C%22expr%22%3A%22vendor_statistics_approximate_entries_unique%7Bcache%3D%5C%22sessions%5C%22%7D%22%2C%22range%22%3Atrue%2C%22instant%22%3Afalse%2C%22editorMode%22%3A%22code%22%2C%22legendFormat%22%3A%22%7B%7Bpod%7D%7D%22%2C%22datasource%22%3A%7B%22type%22%3A%22prometheus%22%2C%22uid%22%3A%22PBFA97CFB590B2093%22%7D%7D%2C%7B%22refId%22%3A%22B%22%2C%22expr%22%3A%22vendor_cluster_size%22%2C%22range%22%3Atrue%2C%22instant%22%3Afalse%2C%22editorMode%22%3A%22code%22%2C%22legendFormat%22%3A%22cluster_size%20%7B%7Bpod%7D%7D%22%2C%22datasource%22%3A%7B%22type%22%3A%22prometheus%22%2C%22uid%22%3A%22PBFA97CFB590B2093%22%7D%7D%5D%2C%22range%22%3A%7B%22from%22%3A%22now-15m%22%2C%22to%22%3A%22now%22%7D%7D%7D:0
+[     686ms] [ERROR] WebSocket connection to 'wss://app2.hyeonworks.com/api/live/ws' failed: Error during WebSocket handshake: Unexpected response code: 400 @ https://app2.hyeonworks.com/public/build/1518.a3f1f690c084a37f01c7.js:362
+[    1451ms] [ERROR] WebSocket connection to 'wss://app2.hyeonworks.com/api/live/ws' failed: Error during WebSocket handshake: Unexpected response code: 400 @ https://app2.hyeonworks.com/public/build/1518.a3f1f690c084a37f01c7.js:362
+[    3030ms] [ERROR] WebSocket connection to 'wss://app2.hyeonworks.com/api/live/ws' failed: Error during WebSocket handshake: Unexpected response code: 400 @ https://app2.hyeonworks.com/public/build/1518.a3f1f690c084a37f01c7.js:362
+[    4308ms] [ERROR] WebSocket connection to 'wss://app2.hyeonworks.com/api/live/ws' failed: Error during WebSocket handshake: Unexpected response code: 400 @ https://app2.hyeonworks.com/public/build/1518.a3f1f690c084a37f01c7.js:362
+[    5296ms] [ERROR] WebSocket connection to 'wss://app2.hyeonworks.com/api/live/ws' failed: Error during WebSocket handshake: Unexpected response code: 400 @ https://app2.hyeonworks.com/public/build/1518.a3f1f690c084a37f01c7.js:362
+[    7691ms] [ERROR] WebSocket connection to 'wss://app2.hyeonworks.com/api/live/ws' failed: Error during WebSocket handshake: Unexpected response code: 400 @ https://app2.hyeonworks.com/public/build/1518.a3f1f690c084a37f01c7.js:362
+[   18337ms] [ERROR] WebSocket connection to 'wss://app2.hyeonworks.com/api/live/ws' failed: Error during WebSocket handshake: Unexpected response code: 400 @ https://app2.hyeonworks.com/public/build/1518.a3f1f690c084a37f01c7.js:362
+[   20184ms] [ERROR] WebSocket connection to 'wss://app2.hyeonworks.com/api/live/ws' failed: Error during WebSocket handshake: Unexpected response code: 400 @ https://app2.hyeonworks.com/public/build/1518.a3f1f690c084a37f01c7.js:362
+[   32473ms] [ERROR] WebSocket connection to 'wss://app2.hyeonworks.com/api/live/ws' failed: Error during WebSocket handshake: Unexpected response code: 400 @ https://app2.hyeonworks.com/public/build/1518.a3f1f690c084a37f01c7.js:362
+[   50697ms] [ERROR] WebSocket connection to 'wss://app2.hyeonworks.com/api/live/ws' failed: Error during WebSocket handshake: Unexpected response code: 400 @ https://app2.hyeonworks.com/public/build/1518.a3f1f690c084a37f01c7.js:362
+[   65961ms] [ERROR] WebSocket connection to 'wss://app2.hyeonworks.com/api/live/ws' failed: Error during WebSocket handshake: Unexpected response code: 400 @ https://app2.hyeonworks.com/public/build/1518.a3f1f690c084a37f01c7.js:362
+[   85590ms] [ERROR] WebSocket connection to 'wss://app2.hyeonworks.com/api/live/ws' failed: Error during WebSocket handshake: Unexpected response code: 400 @ https://app2.hyeonworks.com/public/build/1518.a3f1f690c084a37f01c7.js:362
+[   99644ms] [ERROR] WebSocket connection to 'wss://app2.hyeonworks.com/api/live/ws' failed: Error during WebSocket handshake: Unexpected response code: 400 @ https://app2.hyeonworks.com/public/build/1518.a3f1f690c084a37f01c7.js:362
+[  115524ms] [ERROR] WebSocket connection to 'wss://app2.hyeonworks.com/api/live/ws' failed: Error during WebSocket handshake: Unexpected response code: 400 @ https://app2.hyeonworks.com/public/build/1518.a3f1f690c084a37f01c7.js:362
+[  130773ms] [ERROR] WebSocket connection to 'wss://app2.hyeonworks.com/api/live/ws' failed: Error during WebSocket handshake: Unexpected response code: 400 @ https://app2.hyeonworks.com/public/build/1518.a3f1f690c084a37f01c7.js:362
+[  134354ms] [ERROR] WebSocket connection to 'wss://app2.hyeonworks.com/api/live/ws' failed: Error during WebSocket handshake: Unexpected response code: 400 @ https://app2.hyeonworks.com/public/build/1518.a3f1f690c084a37f01c7.js:362
+[  142549ms] [ERROR] WebSocket connection to 'wss://app2.hyeonworks.com/api/live/ws' failed: Error during WebSocket handshake: Unexpected response code: 400 @ https://app2.hyeonworks.com/public/build/1518.a3f1f690c084a37f01c7.js:362
+[  151361ms] [ERROR] WebSocket connection to 'wss://app2.hyeonworks.com/api/live/ws' failed: Error during WebSocket handshake: Unexpected response code: 400 @ https://app2.hyeonworks.com/public/build/1518.a3f1f690c084a37f01c7.js:362
+[  155246ms] [ERROR] WebSocket connection to 'wss://app2.hyeonworks.com/api/live/ws' failed: Error during WebSocket handshake: Unexpected response code: 400 @ https://app2.hyeonworks.com/public/build/1518.a3f1f690c084a37f01c7.js:362
+[  165901ms] [ERROR] WebSocket connection to 'wss://app2.hyeonworks.com/api/live/ws' failed: Error during WebSocket handshake: Unexpected response code: 400 @ https://app2.hyeonworks.com/public/build/1518.a3f1f690c084a37f01c7.js:362
+[  169379ms] [ERROR] WebSocket connection to 'wss://app2.hyeonworks.com/api/live/ws' failed: Error during WebSocket handshake: Unexpected response code: 400 @ https://app2.hyeonworks.com/public/build/1518.a3f1f690c084a37f01c7.js:362
+[  180952ms] [ERROR] WebSocket connection to 'wss://app2.hyeonworks.com/api/live/ws' failed: Error during WebSocket handshake: Unexpected response code: 400 @ https://app2.hyeonworks.com/public/build/1518.a3f1f690c084a37f01c7.js:362
+[  190372ms] [ERROR] WebSocket connection to 'wss://app2.hyeonworks.com/api/live/ws' failed: Error during WebSocket handshake: Unexpected response code: 400 @ https://app2.hyeonworks.com/public/build/1518.a3f1f690c084a37f01c7.js:362
+[  193657ms] [ERROR] WebSocket connection to 'wss://app2.hyeonworks.com/api/live/ws' failed: Error during WebSocket handshake: Unexpected response code: 400 @ https://app2.hyeonworks.com/public/build/1518.a3f1f690c084a37f01c7.js:362
+[  205737ms] [ERROR] WebSocket connection to 'wss://app2.hyeonworks.com/api/live/ws' failed: Error during WebSocket handshake: Unexpected response code: 400 @ https://app2.hyeonworks.com/public/build/1518.a3f1f690c084a37f01c7.js:362
+[  220582ms] [ERROR] WebSocket connection to 'wss://app2.hyeonworks.com/api/live/ws' failed: Error during WebSocket handshake: Unexpected response code: 400 @ https://app2.hyeonworks.com/public/build/1518.a3f1f690c084a37f01c7.js:362
+[  225496ms] [ERROR] WebSocket connection to 'wss://app2.hyeonworks.com/api/live/ws' failed: Error during WebSocket handshake: Unexpected response code: 400 @ https://app2.hyeonworks.com/public/build/1518.a3f1f690c084a37f01c7.js:362
+[  240339ms] [ERROR] WebSocket connection to 'wss://app2.hyeonworks.com/api/live/ws' failed: Error during WebSocket handshake: Unexpected response code: 400 @ https://app2.hyeonworks.com/public/build/1518.a3f1f690c084a37f01c7.js:362
+[  244029ms] [ERROR] WebSocket connection to 'wss://app2.hyeonworks.com/api/live/ws' failed: Error during WebSocket handshake: Unexpected response code: 400 @ https://app2.hyeonworks.com/public/build/1518.a3f1f690c084a37f01c7.js:362
+[  264211ms] [ERROR] WebSocket connection to 'wss://app2.hyeonworks.com/api/live/ws' failed: Error during WebSocket handshake: Unexpected response code: 400 @ https://app2.hyeonworks.com/public/build/1518.a3f1f690c084a37f01c7.js:362
+[  273424ms] [ERROR] WebSocket connection to 'wss://app2.hyeonworks.com/api/live/ws' failed: Error during WebSocket handshake: Unexpected response code: 400 @ https://app2.hyeonworks.com/public/build/1518.a3f1f690c084a37f01c7.js:362
+[  284893ms] [ERROR] WebSocket connection to 'wss://app2.hyeonworks.com/api/live/ws' failed: Error during WebSocket handshake: Unexpected response code: 400 @ https://app2.hyeonworks.com/public/build/1518.a3f1f690c084a37f01c7.js:362
+[  292571ms] [ERROR] WebSocket connection to 'wss://app2.hyeonworks.com/api/live/ws' failed: Error during WebSocket handshake: Unexpected response code: 400 @ https://app2.hyeonworks.com/public/build/1518.a3f1f690c084a37f01c7.js:362
+[  305778ms] [ERROR] WebSocket connection to 'wss://app2.hyeonworks.com/api/live/ws' failed: Error during WebSocket handshake: Unexpected response code: 400 @ https://app2.hyeonworks.com/public/build/1518.a3f1f690c084a37f01c7.js:362
+[  306804ms] [ERROR] WebSocket connection to 'wss://app2.hyeonworks.com/api/live/ws' failed: Error during WebSocket handshake: Unexpected response code: 400 @ https://app2.hyeonworks.com/public/build/1518.a3f1f690c084a37f01c7.js:362
+[  324378ms] [ERROR] WebSocket connection to 'wss://app2.hyeonworks.com/api/live/ws' failed: Error during WebSocket handshake: Unexpected response code: 400 @ https://app2.hyeonworks.com/public/build/1518.a3f1f690c084a37f01c7.js:362
+[  335169ms] [ERROR] WebSocket connection to 'wss://app2.hyeonworks.com/api/live/ws' failed: Error during WebSocket handshake: Unexpected response code: 400 @ https://app2.hyeonworks.com/public/build/1518.a3f1f690c084a37f01c7.js:362
+[  337968ms] [ERROR] WebSocket connection to 'wss://app2.hyeonworks.com/api/live/ws' failed: Error during WebSocket handshake: Unexpected response code: 400 @ https://app2.hyeonworks.com/public/build/1518.a3f1f690c084a37f01c7.js:362
+[  352967ms] [ERROR] WebSocket connection to 'wss://app2.hyeonworks.com/api/live/ws' failed: Error during WebSocket handshake: Unexpected response code: 400 @ https://app2.hyeonworks.com/public/build/1518.a3f1f690c084a37f01c7.js:362
+[  364258ms] [ERROR] WebSocket connection to 'wss://app2.hyeonworks.com/api/live/ws' failed: Error during WebSocket handshake: Unexpected response code: 400 @ https://app2.hyeonworks.com/public/build/1518.a3f1f690c084a37f01c7.js:362
+[  379409ms] [ERROR] WebSocket connection to 'wss://app2.hyeonworks.com/api/live/ws' failed: Error during WebSocket handshake: Unexpected response code: 400 @ https://app2.hyeonworks.com/public/build/1518.a3f1f690c084a37f01c7.js:362
+[  399590ms] [ERROR] WebSocket connection to 'wss://app2.hyeonworks.com/api/live/ws' failed: Error during WebSocket handshake: Unexpected response code: 400 @ https://app2.hyeonworks.com/public/build/1518.a3f1f690c084a37f01c7.js:362
+[  403681ms] [ERROR] WebSocket connection to 'wss://app2.hyeonworks.com/api/live/ws' failed: Error during WebSocket handshake: Unexpected response code: 400 @ https://app2.hyeonworks.com/public/build/1518.a3f1f690c084a37f01c7.js:362
+[  406340ms] [ERROR] WebSocket connection to 'wss://app2.hyeonworks.com/api/live/ws' failed: Error during WebSocket handshake: Unexpected response code: 400 @ https://app2.hyeonworks.com/public/build/1518.a3f1f690c084a37f01c7.js:362
+[  421033ms] [ERROR] WebSocket connection to 'wss://app2.hyeonworks.com/api/live/ws' failed: Error during WebSocket handshake: Unexpected response code: 400 @ https://app2.hyeonworks.com/public/build/1518.a3f1f690c084a37f01c7.js:362
+[  428667ms] [ERROR] WebSocket connection to 'wss://app2.hyeonworks.com/api/live/ws' failed: Error during WebSocket handshake: Unexpected response code: 400 @ https://app2.hyeonworks.com/public/build/1518.a3f1f690c084a37f01c7.js:362
+[  429483ms] [ERROR] WebSocket connection to 'wss://app2.hyeonworks.com/api/live/ws' failed: Error during WebSocket handshake: Unexpected response code: 400 @ https://app2.hyeonworks.com/public/build/1518.a3f1f690c084a37f01c7.js:362
+[  437573ms] [ERROR] WebSocket connection to 'wss://app2.hyeonworks.com/api/live/ws' failed: Error during WebSocket handshake: Unexpected response code: 400 @ https://app2.hyeonworks.com/public/build/1518.a3f1f690c084a37f01c7.js:362
+[  442286ms] [ERROR] WebSocket connection to 'wss://app2.hyeonworks.com/api/live/ws' failed: Error during WebSocket handshake: Unexpected response code: 400 @ https://app2.hyeonworks.com/public/build/1518.a3f1f690c084a37f01c7.js:362
+[  445865ms] [ERROR] WebSocket connection to 'wss://app2.hyeonworks.com/api/live/ws' failed: Error during WebSocket handshake: Unexpected response code: 400 @ https://app2.hyeonworks.com/public/build/1518.a3f1f690c084a37f01c7.js:362
+[  456312ms] [ERROR] WebSocket connection to 'wss://app2.hyeonworks.com/api/live/ws' failed: Error during WebSocket handshake: Unexpected response code: 400 @ https://app2.hyeonworks.com/public/build/1518.a3f1f690c084a37f01c7.js:362
+[  464043ms] [ERROR] WebSocket connection to 'wss://app2.hyeonworks.com/api/live/ws' failed: Error during WebSocket handshake: Unexpected response code: 400 @ https://app2.hyeonworks.com/public/build/1518.a3f1f690c084a37f01c7.js:362
+[  480382ms] [ERROR] WebSocket connection to 'wss://app2.hyeonworks.com/api/live/ws' failed: Error during WebSocket handshake: Unexpected response code: 400 @ https://app2.hyeonworks.com/public/build/1518.a3f1f690c084a37f01c7.js:362
+[  491438ms] [ERROR] WebSocket connection to 'wss://app2.hyeonworks.com/api/live/ws' failed: Error during WebSocket handshake: Unexpected response code: 400 @ https://app2.hyeonworks.com/public/build/1518.a3f1f690c084a37f01c7.js:362
+[  494608ms] [ERROR] WebSocket connection to 'wss://app2.hyeonworks.com/api/live/ws' failed: Error during WebSocket handshake: Unexpected response code: 400 @ https://app2.hyeonworks.com/public/build/1518.a3f1f690c084a37f01c7.js:362
+[  508231ms] [ERROR] WebSocket connection to 'wss://app2.hyeonworks.com/api/live/ws' failed: Error during WebSocket handshake: Unexpected response code: 400 @ https://app2.hyeonworks.com/public/build/1518.a3f1f690c084a37f01c7.js:362
+[  528305ms] [ERROR] WebSocket connection to 'wss://app2.hyeonworks.com/api/live/ws' failed: Error during WebSocket handshake: Unexpected response code: 400 @ https://app2.hyeonworks.com/public/build/1518.a3f1f690c084a37f01c7.js:362
+[  529632ms] [ERROR] WebSocket connection to 'wss://app2.hyeonworks.com/api/live/ws' failed: Error during WebSocket handshake: Unexpected response code: 400 @ https://app2.hyeonworks.com/public/build/1518.a3f1f690c084a37f01c7.js:362
+[  538033ms] [ERROR] WebSocket connection to 'wss://app2.hyeonworks.com/api/live/ws' failed: Error during WebSocket handshake: Unexpected response code: 400 @ https://app2.hyeonworks.com/public/build/1518.a3f1f690c084a37f01c7.js:362
+[  550079ms] [ERROR] WebSocket connection to 'wss://app2.hyeonworks.com/api/live/ws' failed: Error during WebSocket handshake: Unexpected response code: 400 @ https://app2.hyeonworks.com/public/build/1518.a3f1f690c084a37f01c7.js:362
+[  566347ms] [ERROR] WebSocket connection to 'wss://app2.hyeonworks.com/api/live/ws' failed: Error during WebSocket handshake: Unexpected response code: 400 @ https://app2.hyeonworks.com/public/build/1518.a3f1f690c084a37f01c7.js:362
+[  586157ms] [ERROR] WebSocket connection to 'wss://app2.hyeonworks.com/api/live/ws' failed: Error during WebSocket handshake: Unexpected response code: 400 @ https://app2.hyeonworks.com/public/build/1518.a3f1f690c084a37f01c7.js:362
+[  603877ms] [ERROR] WebSocket connection to 'wss://app2.hyeonworks.com/api/live/ws' failed: Error during WebSocket handshake: Unexpected response code: 400 @ https://app2.hyeonworks.com/public/build/1518.a3f1f690c084a37f01c7.js:362
+[  615779ms] [ERROR] WebSocket connection to 'wss://app2.hyeonworks.com/api/live/ws' failed: Error during WebSocket handshake: Unexpected response code: 400 @ https://app2.hyeonworks.com/public/build/1518.a3f1f690c084a37f01c7.js:362
+[  624657ms] [ERROR] WebSocket connection to 'wss://app2.hyeonworks.com/api/live/ws' failed: Error during WebSocket handshake: Unexpected response code: 400 @ https://app2.hyeonworks.com/public/build/1518.a3f1f690c084a37f01c7.js:362
+[  629879ms] [ERROR] WebSocket connection to 'wss://app2.hyeonworks.com/api/live/ws' failed: Error during WebSocket handshake: Unexpected response code: 400 @ https://app2.hyeonworks.com/public/build/1518.a3f1f690c084a37f01c7.js:362
+[  637255ms] [ERROR] WebSocket connection to 'wss://app2.hyeonworks.com/api/live/ws' failed: Error during WebSocket handshake: Unexpected response code: 400 @ https://app2.hyeonworks.com/public/build/1518.a3f1f690c084a37f01c7.js:362
+[  643298ms] [ERROR] WebSocket connection to 'wss://app2.hyeonworks.com/api/live/ws' failed: Error during WebSocket handshake: Unexpected response code: 400 @ https://app2.hyeonworks.com/public/build/1518.a3f1f690c084a37f01c7.js:362
+[  650047ms] [ERROR] WebSocket connection to 'wss://app2.hyeonworks.com/api/live/ws' failed: Error during WebSocket handshake: Unexpected response code: 400 @ https://app2.hyeonworks.com/public/build/1518.a3f1f690c084a37f01c7.js:362
+[  668080ms] [ERROR] WebSocket connection to 'wss://app2.hyeonworks.com/api/live/ws' failed: Error during WebSocket handshake: Unexpected response code: 400 @ https://app2.hyeonworks.com/public/build/1518.a3f1f690c084a37f01c7.js:362
+[  669816ms] [ERROR] WebSocket connection to 'wss://app2.hyeonworks.com/api/live/ws' failed: Error during WebSocket handshake: Unexpected response code: 400 @ https://app2.hyeonworks.com/public/build/1518.a3f1f690c084a37f01c7.js:362
+[  675422ms] [ERROR] WebSocket connection to 'wss://app2.hyeonworks.com/api/live/ws' failed: Error during WebSocket handshake: Unexpected response code: 400 @ https://app2.hyeonworks.com/public/build/1518.a3f1f690c084a37f01c7.js:362
+[  677001ms] [ERROR] WebSocket connection to 'wss://app2.hyeonworks.com/api/live/ws' failed: Error during WebSocket handshake: Unexpected response code: 400 @ https://app2.hyeonworks.com/public/build/1518.a3f1f690c084a37f01c7.js:362
+[  686611ms] [ERROR] WebSocket connection to 'wss://app2.hyeonworks.com/api/live/ws' failed: Error during WebSocket handshake: Unexpected response code: 400 @ https://app2.hyeonworks.com/public/build/1518.a3f1f690c084a37f01c7.js:362
+[  692655ms] [ERROR] WebSocket connection to 'wss://app2.hyeonworks.com/api/live/ws' failed: Error during WebSocket handshake: Unexpected response code: 400 @ https://app2.hyeonworks.com/public/build/1518.a3f1f690c084a37f01c7.js:362
+[  713114ms] [ERROR] WebSocket connection to 'wss://app2.hyeonworks.com/api/live/ws' failed: Error during WebSocket handshake: Unexpected response code: 400 @ https://app2.hyeonworks.com/public/build/1518.a3f1f690c084a37f01c7.js:362
+[  723787ms] [ERROR] WebSocket connection to 'wss://app2.hyeonworks.com/api/live/ws' failed: Error during WebSocket handshake: Unexpected response code: 400 @ https://app2.hyeonworks.com/public/build/1518.a3f1f690c084a37f01c7.js:362
+[  730443ms] [ERROR] WebSocket connection to 'wss://app2.hyeonworks.com/api/live/ws' failed: Error during WebSocket handshake: Unexpected response code: 400 @ https://app2.hyeonworks.com/public/build/1518.a3f1f690c084a37f01c7.js:362
+[  751427ms] [ERROR] WebSocket connection to 'wss://app2.hyeonworks.com/api/live/ws' failed: Error during WebSocket handshake: Unexpected response code: 400 @ https://app2.hyeonworks.com/public/build/1518.a3f1f690c084a37f01c7.js:362
+[  757583ms] [ERROR] WebSocket connection to 'wss://app2.hyeonworks.com/api/live/ws' failed: Error during WebSocket handshake: Unexpected response code: 400 @ https://app2.hyeonworks.com/public/build/1518.a3f1f690c084a37f01c7.js:362
+[  776007ms] [ERROR] WebSocket connection to 'wss://app2.hyeonworks.com/api/live/ws' failed: Error during WebSocket handshake: Unexpected response code: 400 @ https://app2.hyeonworks.com/public/build/1518.a3f1f690c084a37f01c7.js:362
+[  792298ms] [ERROR] WebSocket connection to 'wss://app2.hyeonworks.com/api/live/ws' failed: Error during WebSocket handshake: Unexpected response code: 400 @ https://app2.hyeonworks.com/public/build/1518.a3f1f690c084a37f01c7.js:362
+[  803509ms] [ERROR] WebSocket connection to 'wss://app2.hyeonworks.com/api/live/ws' failed: Error during WebSocket handshake: Unexpected response code: 400 @ https://app2.hyeonworks.com/public/build/1518.a3f1f690c084a37f01c7.js:362
+[  822917ms] [ERROR] WebSocket connection to 'wss://app2.hyeonworks.com/api/live/ws' failed: Error during WebSocket handshake: Unexpected response code: 400 @ https://app2.hyeonworks.com/public/build/1518.a3f1f690c084a37f01c7.js:362
+[  827374ms] [ERROR] WebSocket connection to 'wss://app2.hyeonworks.com/api/live/ws' failed: Error during WebSocket handshake: Unexpected response code: 400 @ https://app2.hyeonworks.com/public/build/1518.a3f1f690c084a37f01c7.js:362
+[  847278ms] [ERROR] WebSocket connection to 'wss://app2.hyeonworks.com/api/live/ws' failed: Error during WebSocket handshake: Unexpected response code: 400 @ https://app2.hyeonworks.com/public/build/1518.a3f1f690c084a37f01c7.js:362
+[  867460ms] [ERROR] WebSocket connection to 'wss://app2.hyeonworks.com/api/live/ws' failed: Error during WebSocket handshake: Unexpected response code: 400 @ https://app2.hyeonworks.com/public/build/1518.a3f1f690c084a37f01c7.js:362
+[  875338ms] [ERROR] WebSocket connection to 'wss://app2.hyeonworks.com/api/live/ws' failed: Error during WebSocket handshake: Unexpected response code: 400 @ https://app2.hyeonworks.com/public/build/1518.a3f1f690c084a37f01c7.js:362
+[  886296ms] [ERROR] WebSocket connection to 'wss://app2.hyeonworks.com/api/live/ws' failed: Error during WebSocket handshake: Unexpected response code: 400 @ https://app2.hyeonworks.com/public/build/1518.a3f1f690c084a37f01c7.js:362
+[  900938ms] [ERROR] WebSocket connection to 'wss://app2.hyeonworks.com/api/live/ws' failed: Error during WebSocket handshake: Unexpected response code: 400 @ https://app2.hyeonworks.com/public/build/1518.a3f1f690c084a37f01c7.js:362
+[  912511ms] [ERROR] WebSocket connection to 'wss://app2.hyeonworks.com/api/live/ws' failed: Error during WebSocket handshake: Unexpected response code: 400 @ https://app2.hyeonworks.com/public/build/1518.a3f1f690c084a37f01c7.js:362
+[  917067ms] [ERROR] WebSocket connection to 'wss://app2.hyeonworks.com/api/live/ws' failed: Error during WebSocket handshake: Unexpected response code: 400 @ https://app2.hyeonworks.com/public/build/1518.a3f1f690c084a37f01c7.js:362
+[  924405ms] [ERROR] WebSocket connection to 'wss://app2.hyeonworks.com/api/live/ws' failed: Error during WebSocket handshake: Unexpected response code: 400 @ https://app2.hyeonworks.com/public/build/1518.a3f1f690c084a37f01c7.js:362
+[  930435ms] [ERROR] WebSocket connection to 'wss://app2.hyeonworks.com/api/live/ws' failed: Error during WebSocket handshake: Unexpected response code: 400 @ https://app2.hyeonworks.com/public/build/1518.a3f1f690c084a37f01c7.js:362
+[  942211ms] [ERROR] WebSocket connection to 'wss://app2.hyeonworks.com/api/live/ws' failed: Error during WebSocket handshake: Unexpected response code: 400 @ https://app2.hyeonworks.com/public/build/1518.a3f1f690c084a37f01c7.js:362
+[  953146ms] [ERROR] WebSocket connection to 'wss://app2.hyeonworks.com/api/live/ws' failed: Error during WebSocket handshake: Unexpected response code: 400 @ https://app2.hyeonworks.com/public/build/1518.a3f1f690c084a37f01c7.js:362
+[  957153ms] [ERROR] WebSocket connection to 'wss://app2.hyeonworks.com/api/live/ws' failed: Error during WebSocket handshake: Unexpected response code: 400 @ https://app2.hyeonworks.com/public/build/1518.a3f1f690c084a37f01c7.js:362
+[  969140ms] [ERROR] WebSocket connection to 'wss://app2.hyeonworks.com/api/live/ws' failed: Error during WebSocket handshake: Unexpected response code: 400 @ https://app2.hyeonworks.com/public/build/1518.a3f1f690c084a37f01c7.js:362
+[  984088ms] [ERROR] WebSocket connection to 'wss://app2.hyeonworks.com/api/live/ws' failed: Error during WebSocket handshake: Unexpected response code: 400 @ https://app2.hyeonworks.com/public/build/1518.a3f1f690c084a37f01c7.js:362
+[ 1003544ms] [ERROR] WebSocket connection to 'wss://app2.hyeonworks.com/api/live/ws' failed: Error during WebSocket handshake: Unexpected response code: 400 @ https://app2.hyeonworks.com/public/build/1518.a3f1f690c084a37f01c7.js:362
+[ 1014908ms] [ERROR] WebSocket connection to 'wss://app2.hyeonworks.com/api/live/ws' failed: Error during WebSocket handshake: Unexpected response code: 400 @ https://app2.hyeonworks.com/public/build/1518.a3f1f690c084a37f01c7.js:362
+[ 1020851ms] [ERROR] WebSocket connection to 'wss://app2.hyeonworks.com/api/live/ws' failed: Error during WebSocket handshake: Unexpected response code: 400 @ https://app2.hyeonworks.com/public/build/1518.a3f1f690c084a37f01c7.js:362
+[ 1034668ms] [ERROR] WebSocket connection to 'wss://app2.hyeonworks.com/api/live/ws' failed: Error during WebSocket handshake: Unexpected response code: 400 @ https://app2.hyeonworks.com/public/build/1518.a3f1f690c084a37f01c7.js:362
+[ 1040406ms] [ERROR] WebSocket connection to 'wss://app2.hyeonworks.com/api/live/ws' failed: Error during WebSocket handshake: Unexpected response code: 400 @ https://app2.hyeonworks.com/public/build/1518.a3f1f690c084a37f01c7.js:362
+[ 1056887ms] [ERROR] WebSocket connection to 'wss://app2.hyeonworks.com/api/live/ws' failed: Error during WebSocket handshake: Unexpected response code: 400 @ https://app2.hyeonworks.com/public/build/1518.a3f1f690c084a37f01c7.js:362
+[ 1062828ms] [ERROR] WebSocket connection to 'wss://app2.hyeonworks.com/api/live/ws' failed: Error during WebSocket handshake: Unexpected response code: 400 @ https://app2.hyeonworks.com/public/build/1518.a3f1f690c084a37f01c7.js:362
+[ 1073375ms] [ERROR] WebSocket connection to 'wss://app2.hyeonworks.com/api/live/ws' failed: Error during WebSocket handshake: Unexpected response code: 400 @ https://app2.hyeonworks.com/public/build/1518.a3f1f690c084a37f01c7.js:362
+[ 1085052ms] [ERROR] WebSocket connection to 'wss://app2.hyeonworks.com/api/live/ws' failed: Error during WebSocket handshake: Unexpected response code: 400 @ https://app2.hyeonworks.com/public/build/1518.a3f1f690c084a37f01c7.js:362
+[ 1102031ms] [ERROR] WebSocket connection to 'wss://app2.hyeonworks.com/api/live/ws' failed: Error during WebSocket handshake: Unexpected response code: 400 @ https://app2.hyeonworks.com/public/build/1518.a3f1f690c084a37f01c7.js:362
+[ 1110039ms] [ERROR] WebSocket connection to 'wss://app2.hyeonworks.com/api/live/ws' failed: Error during WebSocket handshake: Unexpected response code: 400 @ https://app2.hyeonworks.com/public/build/1518.a3f1f690c084a37f01c7.js:362
+[ 1129341ms] [ERROR] WebSocket connection to 'wss://app2.hyeonworks.com/api/live/ws' failed: Error during WebSocket handshake: Unexpected response code: 400 @ https://app2.hyeonworks.com/public/build/1518.a3f1f690c084a37f01c7.js:362
+[ 1132300ms] [ERROR] WebSocket connection to 'wss://app2.hyeonworks.com/api/live/ws' failed: Error during WebSocket handshake: Unexpected response code: 400 @ https://app2.hyeonworks.com/public/build/1518.a3f1f690c084a37f01c7.js:362
+[ 1133670ms] [ERROR] WebSocket connection to 'wss://app2.hyeonworks.com/api/live/ws' failed: Error during WebSocket handshake: Unexpected response code: 400 @ https://app2.hyeonworks.com/public/build/1518.a3f1f690c084a37f01c7.js:362
+[ 1142705ms] [ERROR] WebSocket connection to 'wss://app2.hyeonworks.com/api/live/ws' failed: Error during WebSocket handshake: Unexpected response code: 400 @ https://app2.hyeonworks.com/public/build/1518.a3f1f690c084a37f01c7.js:362
+[ 1160906ms] [ERROR] WebSocket connection to 'wss://app2.hyeonworks.com/api/live/ws' failed: Error during WebSocket handshake: Unexpected response code: 400 @ https://app2.hyeonworks.com/public/build/1518.a3f1f690c084a37f01c7.js:362
+[ 1172400ms] [ERROR] WebSocket connection to 'wss://app2.hyeonworks.com/api/live/ws' failed: Error during WebSocket handshake: Unexpected response code: 400 @ https://app2.hyeonworks.com/public/build/1518.a3f1f690c084a37f01c7.js:362
+[ 1190482ms] [ERROR] WebSocket connection to 'wss://app2.hyeonworks.com/api/live/ws' failed: Error during WebSocket handshake: Unexpected response code: 400 @ https://app2.hyeonworks.com/public/build/1518.a3f1f690c084a37f01c7.js:362
+[ 1196673ms] [ERROR] WebSocket connection to 'wss://app2.hyeonworks.com/api/live/ws' failed: Error during WebSocket handshake: Unexpected response code: 400 @ https://app2.hyeonworks.com/public/build/1518.a3f1f690c084a37f01c7.js:362
+[ 1213666ms] [ERROR] WebSocket connection to 'wss://app2.hyeonworks.com/api/live/ws' failed: Error during WebSocket handshake: Unexpected response code: 400 @ https://app2.hyeonworks.com/public/build/1518.a3f1f690c084a37f01c7.js:362
+[ 1225136ms] [ERROR] WebSocket connection to 'wss://app2.hyeonworks.com/api/live/ws' failed: Error during WebSocket handshake: Unexpected response code: 400 @ https://app2.hyeonworks.com/public/build/1518.a3f1f690c084a37f01c7.js:362
+[ 1228310ms] [ERROR] WebSocket connection to 'wss://app2.hyeonworks.com/api/live/ws' failed: Error during WebSocket handshake: Unexpected response code: 400 @ https://app2.hyeonworks.com/public/build/1518.a3f1f690c084a37f01c7.js:362
+[ 1242751ms] [ERROR] WebSocket connection to 'wss://app2.hyeonworks.com/api/live/ws' failed: Error during WebSocket handshake: Unexpected response code: 400 @ https://app2.hyeonworks.com/public/build/1518.a3f1f690c084a37f01c7.js:362
+[ 1243874ms] [ERROR] WebSocket connection to 'wss://app2.hyeonworks.com/api/live/ws' failed: Error during WebSocket handshake: Unexpected response code: 400 @ https://app2.hyeonworks.com/public/build/1518.a3f1f690c084a37f01c7.js:362
+[ 1256126ms] [ERROR] WebSocket connection to 'wss://app2.hyeonworks.com/api/live/ws' failed: Error during WebSocket handshake: Unexpected response code: 400 @ https://app2.hyeonworks.com/public/build/1518.a3f1f690c084a37f01c7.js:362
+[ 1274444ms] [ERROR] WebSocket connection to 'wss://app2.hyeonworks.com/api/live/ws' failed: Error during WebSocket handshake: Unexpected response code: 400 @ https://app2.hyeonworks.com/public/build/1518.a3f1f690c084a37f01c7.js:362
+[ 1288526ms] [ERROR] WebSocket connection to 'wss://app2.hyeonworks.com/api/live/ws' failed: Error during WebSocket handshake: Unexpected response code: 400 @ https://app2.hyeonworks.com/public/build/1518.a3f1f690c084a37f01c7.js:362
+[ 1307058ms] [ERROR] WebSocket connection to 'wss://app2.hyeonworks.com/api/live/ws' failed: Error during WebSocket handshake: Unexpected response code: 400 @ https://app2.hyeonworks.com/public/build/1518.a3f1f690c084a37f01c7.js:362
+[ 1320986ms] [ERROR] WebSocket connection to 'wss://app2.hyeonworks.com/api/live/ws' failed: Error during WebSocket handshake: Unexpected response code: 400 @ https://app2.hyeonworks.com/public/build/1518.a3f1f690c084a37f01c7.js:362
+[ 1325134ms] [ERROR] WebSocket connection to 'wss://app2.hyeonworks.com/api/live/ws' failed: Error during WebSocket handshake: Unexpected response code: 400 @ https://app2.hyeonworks.com/public/build/1518.a3f1f690c084a37f01c7.js:362
+[ 1335974ms] [ERROR] WebSocket connection to 'wss://app2.hyeonworks.com/api/live/ws' failed: Error during WebSocket handshake: Unexpected response code: 400 @ https://app2.hyeonworks.com/public/build/1518.a3f1f690c084a37f01c7.js:362
+[ 1344832ms] [ERROR] WebSocket connection to 'wss://app2.hyeonworks.com/api/live/ws' failed: Error during WebSocket handshake: Unexpected response code: 400 @ https://app2.hyeonworks.com/public/build/1518.a3f1f690c084a37f01c7.js:362
+[ 1354780ms] [ERROR] WebSocket connection to 'wss://app2.hyeonworks.com/api/live/ws' failed: Error during WebSocket handshake: Unexpected response code: 400 @ https://app2.hyeonworks.com/public/build/1518.a3f1f690c084a37f01c7.js:362
+[ 1364165ms] [ERROR] WebSocket connection to 'wss://app2.hyeonworks.com/api/live/ws' failed: Error during WebSocket handshake: Unexpected response code: 400 @ https://app2.hyeonworks.com/public/build/1518.a3f1f690c084a37f01c7.js:362
+[ 1383346ms] [ERROR] WebSocket connection to 'wss://app2.hyeonworks.com/api/live/ws' failed: Error during WebSocket handshake: Unexpected response code: 400 @ https://app2.hyeonworks.com/public/build/1518.a3f1f690c084a37f01c7.js:362
+[ 1399019ms] [ERROR] WebSocket connection to 'wss://app2.hyeonworks.com/api/live/ws' failed: Error during WebSocket handshake: Unexpected response code: 400 @ https://app2.hyeonworks.com/public/build/1518.a3f1f690c084a37f01c7.js:362
+[ 1400207ms] [ERROR] WebSocket connection to 'wss://app2.hyeonworks.com/api/live/ws' failed: Error during WebSocket handshake: Unexpected response code: 400 @ https://app2.hyeonworks.com/public/build/1518.a3f1f690c084a37f01c7.js:362
+[ 1413875ms] [ERROR] WebSocket connection to 'wss://app2.hyeonworks.com/api/live/ws' failed: Error during WebSocket handshake: Unexpected response code: 400 @ https://app2.hyeonworks.com/public/build/1518.a3f1f690c084a37f01c7.js:362
+[ 1423809ms] [ERROR] WebSocket connection to 'wss://app2.hyeonworks.com/api/live/ws' failed: Error during WebSocket handshake: Unexpected response code: 400 @ https://app2.hyeonworks.com/public/build/1518.a3f1f690c084a37f01c7.js:362
+[ 1427502ms] [ERROR] WebSocket connection to 'wss://app2.hyeonworks.com/api/live/ws' failed: Error during WebSocket handshake: Unexpected response code: 400 @ https://app2.hyeonworks.com/public/build/1518.a3f1f690c084a37f01c7.js:362
+[ 1430773ms] [ERROR] WebSocket connection to 'wss://app2.hyeonworks.com/api/live/ws' failed: Error during WebSocket handshake: Unexpected response code: 400 @ https://app2.hyeonworks.com/public/build/1518.a3f1f690c084a37f01c7.js:362
+[ 1436408ms] [ERROR] WebSocket connection to 'wss://app2.hyeonworks.com/api/live/ws' failed: Error during WebSocket handshake: Unexpected response code: 400 @ https://app2.hyeonworks.com/public/build/1518.a3f1f690c084a37f01c7.js:362
+[ 1447464ms] [ERROR] WebSocket connection to 'wss://app2.hyeonworks.com/api/live/ws' failed: Error during WebSocket handshake: Unexpected response code: 400 @ https://app2.hyeonworks.com/public/build/1518.a3f1f690c084a37f01c7.js:362

.playwright-mcp/console-2026-09-04T04-46-50-423Z.log

@@ -0,0 +1 @@
+[     207ms] [ERROR] Failed to load resource: the server responded with a status of 404 () @ https://app1.hyeonworks.com/favicon.ico:0

.playwright-mcp/page-2026-09-04T03-43-55-616Z.yml

@@ -0,0 +1,104 @@
+- generic [ref=f12e4]:
+  - link "Skip to main content" [ref=f12e5] [cursor=pointer]:
+    - /url: "#pageContent"
+  - banner [ref=f12e7]:
+    - generic [ref=f12e8]:
+      - link [ref=f12e10] [cursor=pointer]:
+        - /url: /
+        - img "Grafana" [ref=f12e11]
+      - generic [ref=f12e14]:
+        - button "Search or jump to..." [ref=f12e18] [cursor=pointer]
+        - generic [ref=f12e19]: ctrl+k
+      - generic [ref=f12e23]:
+        - button "New" [ref=f12e24] [cursor=pointer]
+        - button "Help" [ref=f12e30] [cursor=pointer]
+        - button "News" [ref=f12e33] [cursor=pointer]
+        - button "Profile" [ref=f12e36] [cursor=pointer]:
+          - img "User avatar" [ref=f12e37]
+    - generic [ref=f12e38]:
+      - button "Open menu" [ref=f12e40] [cursor=pointer]
+      - navigation "Breadcrumbs" [ref=f12e43]:
+        - list [ref=f12e44]:
+          - listitem [ref=f12e45]:
+            - link "Home" [ref=f12e46] [cursor=pointer]:
+              - /url: /
+          - listitem [ref=f12e50]:
+            - link "Explore" [ref=f12e51] [cursor=pointer]:
+              - /url: /explore
+          - listitem [ref=f12e55]:
+            - generic "Prometheus" [ref=f12e56]
+      - generic [ref=f12e57]:
+        - button "Show more items" [ref=f12e60] [cursor=pointer]
+        - button "Toggle top search bar" [ref=f12e64] [cursor=pointer]
+  - main [ref=f12e70]:
+    - generic [ref=f12e72]:
+      - heading "Explore" [level=1] [ref=f12e73]
+      - generic [ref=f12e78]:
+        - navigation "Explore toolbar" [ref=f12e80]:
+          - navigation "Search links" [ref=f12e82]:
+            - generic [ref=f12e83]:
+              - button "Content outline" [expanded] [ref=f12e85] [cursor=pointer]:
+                - generic [ref=f12e88]: Outline
+              - generic [ref=f12e93] [cursor=pointer]:
+                - img "Prometheus logo" [ref=f12e95]
+                - textbox "Select a data source" [ref=f12e96]:
+                  - /placeholder: ""
+          - button "Show more items" [ref=f12e102] [cursor=pointer]
+        - generic [ref=f12e106]:
+          - generic [ref=f12e110]:
+            - button "Collapse outline" [expanded] [ref=f12e112] [cursor=pointer]:
+              - img "arrow-from-right" [ref=f12e113]
+            - button "Queries" [ref=f12e116] [cursor=pointer]:
+              - img "arrow" [ref=f12e117]
+          - generic [ref=f12e124]:
+            - generic [ref=f12e126]:
+              - generic "Query editor row" [ref=f12e129]:
+                - generic [ref=f12e130]:
+                  - generic [ref=f12e132]:
+                    - generic [ref=f12e133]:
+                      - button "Collapse query row" [expanded] [ref=f12e134] [cursor=pointer]
+                      - generic [ref=f12e137]:
+                        - button "Query editor row title A" [ref=f12e138] [cursor=pointer]:
+                          - generic [ref=f12e139]: A
+                        - emphasis [ref=f12e140]: (Prometheus)
+                    - generic [ref=f12e141]:
+                      - button "Show data source help" [ref=f12e143] [cursor=pointer]
+                      - button "Duplicate query" [ref=f12e147] [cursor=pointer]
+                      - button "Hide response" [ref=f12e151] [cursor=pointer]
+                      - button "Remove query" [ref=f12e155] [cursor=pointer]
+                      - button "Drag and drop to reorder" [ref=f12e158]:
+                        - img "Drag and drop to reorder" [ref=f12e159]
+                  - generic [ref=f12e162]:
+                    - generic [ref=f12e163]:
+                      - button "Kick start your query" [ref=f12e164] [cursor=pointer]
+                      - generic [ref=f12e167]:
+                        - generic [ref=f12e168] [cursor=pointer]: Explain
+                        - generic [ref=f12e169]:
+                          - checkbox "Explain Toggle switch" [ref=f12e170]
+                          - generic "Toggle switch" [ref=f12e171] [cursor=pointer]
+                      - radiogroup [ref=f12e176]:
+                        - generic [ref=f12e177]:
+                          - radio "Builder" [ref=f12e178] [cursor=pointer]
+                          - generic [ref=f12e179] [cursor=pointer]: Builder
+                        - generic [ref=f12e180]:
+                          - radio "Code" [checked] [ref=f12e181] [cursor=pointer]
+                          - generic [ref=f12e182] [cursor=pointer]: Code
+                    - generic [ref=f12e184]:
+                      - generic [ref=f12e186]:
+                        - button "Loading metrics..." [disabled] [ref=f12e187] [cursor=pointer]
+                        - generic [ref=f12e190]: Loading editor
+                      - 'button "Options Legend: {{pod}} Format: Time series Step: auto Type: Range Exemplars: false" [ref=f12e198] [cursor=pointer]':
+                        - generic [ref=f12e202]:
+                          - heading "Options" [level=6] [ref=f12e203]
+                          - generic [ref=f12e204]:
+                            - generic [ref=f12e205]: "Legend: {{pod}}"
+                            - generic [ref=f12e206]: "Format: Time series"
+                            - generic [ref=f12e207]: "Step: auto"
+                            - generic [ref=f12e208]: "Type: Range"
+                            - generic [ref=f12e209]: "Exemplars: false"
+              - generic [ref=f12e210]:
+                - button "Add query" [ref=f12e211] [cursor=pointer]
+                - button "Query history" [ref=f12e215] [cursor=pointer]
+                - button "Query inspector" [ref=f12e219] [cursor=pointer]
+            - generic:
+              - main

.playwright-mcp/page-2026-09-04T04-16-33-535Z.yml

@@ -0,0 +1,145 @@
+- generic [active] [ref=f15e1]:
+  - generic [ref=f15e4]:
+    - link "Skip to main content" [ref=f15e5] [cursor=pointer]:
+      - /url: "#pageContent"
+    - banner [ref=f15e7]:
+      - generic [ref=f15e8]:
+        - link [ref=f15e10] [cursor=pointer]:
+          - /url: /
+          - img "Grafana" [ref=f15e11]
+        - generic [ref=f15e14]:
+          - button "Search or jump to..." [ref=f15e18] [cursor=pointer]
+          - generic [ref=f15e19]: ctrl+k
+        - generic [ref=f15e23]:
+          - button "New" [ref=f15e24] [cursor=pointer]
+          - button "Help" [ref=f15e30] [cursor=pointer]
+          - button "News" [ref=f15e33] [cursor=pointer]
+          - button "Profile" [ref=f15e36] [cursor=pointer]:
+            - img "User avatar" [ref=f15e37]
+      - generic [ref=f15e38]:
+        - button "Open menu" [ref=f15e40] [cursor=pointer]
+        - navigation "Breadcrumbs" [ref=f15e43]:
+          - list [ref=f15e44]:
+            - listitem [ref=f15e45]:
+              - link "Home" [ref=f15e46] [cursor=pointer]:
+                - /url: /
+            - listitem [ref=f15e50]:
+              - link "Explore" [ref=f15e51] [cursor=pointer]:
+                - /url: /explore
+            - listitem [ref=f15e55]:
+              - generic "Prometheus" [ref=f15e56]
+        - generic [ref=f15e57]:
+          - generic [ref=f15e60]:
+            - button "Copy shortened URL" [ref=f15e61] [cursor=pointer]
+            - button "Open copy link options" [ref=f15e64] [cursor=pointer]
+          - button "Toggle top search bar" [ref=f15e68] [cursor=pointer]
+    - main [ref=f15e74]:
+      - generic [ref=f15e76]:
+        - heading "Explore" [level=1] [ref=f15e77]
+        - generic [ref=f15e82]:
+          - navigation "Explore toolbar" [ref=f15e84]:
+            - navigation "Search links" [ref=f15e86]:
+              - generic [ref=f15e87]:
+                - button "Content outline" [expanded] [ref=f15e89] [cursor=pointer]:
+                  - generic [ref=f15e92]: Outline
+                - generic [ref=f15e97] [cursor=pointer]:
+                  - img "Prometheus logo" [ref=f15e99]
+                  - textbox "Select a data source" [ref=f15e100]:
+                    - /placeholder: ""
+            - generic [ref=f15e104]:
+              - button "Split the pane" [ref=f15e106] [cursor=pointer]:
+                - generic [ref=f15e109]: Split
+              - button "Add" [ref=f15e111] [cursor=pointer]
+              - generic [ref=f15e116]:
+                - 'button "Time range selected: Last 30 minutes" [ref=f15e117] [cursor=pointer]'
+                - button "Zoom out time range" [ref=f15e122] [cursor=pointer]
+              - generic [ref=f15e126]:
+                - button "Run query" [ref=f15e127] [cursor=pointer]
+                - button "Auto refresh turned off. Choose refresh time interval" [ref=f15e131] [cursor=pointer]
+          - generic [ref=f15e135]:
+            - generic [ref=f15e139]:
+              - button "Collapse outline" [expanded] [ref=f15e141] [cursor=pointer]:
+                - img "arrow-from-right" [ref=f15e142]
+              - button "Queries" [ref=f15e145] [cursor=pointer]:
+                - img "arrow" [ref=f15e146]
+              - button "Graph" [ref=f15e150] [cursor=pointer]:
+                - img "graph-bar" [ref=f15e151]
+            - generic [ref=f15e158]:
+              - generic [ref=f15e160]:
+                - generic "Query editor row" [ref=f15e163]:
+                  - generic [ref=f15e164]:
+                    - generic [ref=f15e166]:
+                      - generic [ref=f15e167]:
+                        - button "Collapse query row" [expanded] [ref=f15e168] [cursor=pointer]
+                        - generic [ref=f15e171]:
+                          - button "Query editor row title A" [ref=f15e172] [cursor=pointer]:
+                            - generic [ref=f15e173]: A
+                          - emphasis [ref=f15e174]: (Prometheus)
+                      - generic [ref=f15e175]:
+                        - button "Show data source help" [ref=f15e177] [cursor=pointer]
+                        - button "Duplicate query" [ref=f15e181] [cursor=pointer]
+                        - button "Hide response" [ref=f15e185] [cursor=pointer]
+                        - button "Remove query" [ref=f15e189] [cursor=pointer]
+                        - button "Drag and drop to reorder" [ref=f15e192]:
+                          - img "Drag and drop to reorder" [ref=f15e193]
+                    - generic [ref=f15e196]:
+                      - generic [ref=f15e197]:
+                        - button "Kick start your query" [ref=f15e198] [cursor=pointer]
+                        - generic [ref=f15e201]:
+                          - generic [ref=f15e202] [cursor=pointer]: Explain
+                          - generic [ref=f15e203]:
+                            - checkbox "Explain Toggle switch" [ref=f15e204]
+                            - generic "Toggle switch" [ref=f15e205] [cursor=pointer]
+                        - radiogroup [ref=f15e210]:
+                          - generic [ref=f15e211]:
+                            - radio "Builder" [ref=f15e212] [cursor=pointer]
+                            - generic [ref=f15e213] [cursor=pointer]: Builder
+                          - generic [ref=f15e214]:
+                            - radio "Code" [checked] [ref=f15e215] [cursor=pointer]
+                            - generic [ref=f15e216] [cursor=pointer]: Code
+                      - generic [ref=f15e218]:
+                        - generic [ref=f15e220]:
+                          - button "Loading metrics..." [disabled] [ref=f15e221] [cursor=pointer]
+                          - code [ref=f15e228]:
+                            - generic [ref=f15e229]:
+                              - generic [ref=f15e234]: agroal_blocking_time_max_milliseconds
+                              - textbox "Editor content;Press Alt+F1 for Accessibility Options." [ref=f15e239]: agroal_blocking_time_max_milliseconds
+                        - 'button "Options Legend: blocking max - {{pod}} Format: Time series Step: auto Type: Range Exemplars: false" [ref=f15e245] [cursor=pointer]':
+                          - generic [ref=f15e249]:
+                            - heading "Options" [level=6] [ref=f15e250]
+                            - generic [ref=f15e251]:
+                              - generic [ref=f15e252]: "Legend: blocking max - {{pod}}"
+                              - generic [ref=f15e253]: "Format: Time series"
+                              - generic [ref=f15e254]: "Step: auto"
+                              - generic [ref=f15e255]: "Type: Range"
+                              - generic [ref=f15e256]: "Exemplars: false"
+                - generic [ref=f15e257]:
+                  - button "Add query" [ref=f15e258] [cursor=pointer]
+                  - button "Query history" [ref=f15e262] [cursor=pointer]
+                  - button "Query inspector" [ref=f15e266] [cursor=pointer]
+              - main [ref=f15e270]:
+                - region [ref=f15e272]:
+                  - generic [ref=f15e273]:
+                    - heading "Graph" [level=2] [ref=f15e275]
+                    - radiogroup [ref=f15e278]:
+                      - generic [ref=f15e279]:
+                        - radio "Lines" [checked] [ref=f15e280] [cursor=pointer]
+                        - generic [ref=f15e281] [cursor=pointer]: Lines
+                      - generic [ref=f15e282]:
+                        - radio "Bars" [ref=f15e283] [cursor=pointer]
+                        - generic [ref=f15e284] [cursor=pointer]: Bars
+                      - generic [ref=f15e285]:
+                        - radio "Points" [ref=f15e286] [cursor=pointer]
+                        - generic [ref=f15e287] [cursor=pointer]: Points
+                      - generic [ref=f15e288]:
+                        - radio "Stacked lines" [ref=f15e289] [cursor=pointer]
+                        - generic [ref=f15e290] [cursor=pointer]: Stacked lines
+                      - generic [ref=f15e291]:
+                        - radio "Stacked bars" [ref=f15e292] [cursor=pointer]
+                        - generic [ref=f15e293] [cursor=pointer]: Stacked bars
+                  - generic [ref=f15e294]: Loading plugin panel...
+  - generic [ref=f15e299]:
+    - alert
+    - alert
+    - complementary
+    - complementary

.playwright-mcp/page-2026-09-04T04-19-59-064Z.yml

@@ -0,0 +1,56 @@
+- generic [ref=f18e4]:
+  - link "Skip to main content" [ref=f18e5] [cursor=pointer]:
+    - /url: "#pageContent"
+  - banner [ref=f18e7]:
+    - generic [ref=f18e8]:
+      - link [ref=f18e10] [cursor=pointer]:
+        - /url: /
+        - img "Grafana" [ref=f18e11]
+      - generic [ref=f18e14]:
+        - button "Search or jump to..." [ref=f18e18] [cursor=pointer]
+        - generic [ref=f18e19]: ctrl+k
+      - generic [ref=f18e23]:
+        - button "New" [ref=f18e24] [cursor=pointer]
+        - button "Help" [ref=f18e30] [cursor=pointer]
+        - button "News" [ref=f18e33] [cursor=pointer]
+        - button "Profile" [ref=f18e36] [cursor=pointer]:
+          - img "User avatar" [ref=f18e37]
+    - generic [ref=f18e38]:
+      - button "Open menu" [ref=f18e40] [cursor=pointer]
+      - navigation "Breadcrumbs" [ref=f18e43]:
+        - list [ref=f18e44]:
+          - listitem [ref=f18e45]:
+            - link "Home" [ref=f18e46] [cursor=pointer]:
+              - /url: /
+          - listitem [ref=f18e50]:
+            - link "Explore" [ref=f18e51] [cursor=pointer]:
+              - /url: /explore
+          - listitem [ref=f18e55]:
+            - generic "Prometheus" [ref=f18e56]
+      - generic [ref=f18e57]:
+        - button "Show more items" [ref=f18e60] [cursor=pointer]
+        - button "Toggle top search bar" [ref=f18e64] [cursor=pointer]
+  - main [ref=f18e70]:
+    - generic [ref=f18e72]:
+      - heading "Explore" [level=1] [ref=f18e73]
+      - generic [ref=f18e78]:
+        - navigation "Explore toolbar" [ref=f18e80]:
+          - navigation "Search links" [ref=f18e82]:
+            - generic [ref=f18e83]:
+              - button "Content outline" [expanded] [ref=f18e85] [cursor=pointer]:
+                - generic [ref=f18e88]: Outline
+              - generic [ref=f18e93] [cursor=pointer]:
+                - img "Prometheus logo" [ref=f18e95]
+                - textbox "Select a data source" [ref=f18e96]:
+                  - /placeholder: ""
+          - button "Show more items" [ref=f18e102] [cursor=pointer]
+        - generic [ref=f18e106]:
+          - button "Collapse outline" [expanded] [ref=f18e112] [cursor=pointer]:
+            - img "arrow-from-right" [ref=f18e113]
+          - generic [ref=f18e120]:
+            - generic [ref=f18e123]:
+              - button "Add query" [ref=f18e124] [cursor=pointer]
+              - button "Query history" [ref=f18e128] [cursor=pointer]
+              - button "Query inspector" [ref=f18e132] [cursor=pointer]
+            - generic:
+              - main

.playwright-mcp/page-2026-09-04T04-44-07-075Z.yml

@@ -0,0 +1,7 @@
+- main [ref=f21e2]:
+  - heading "AP3 · Backend-for-Frontend" [level=1] [ref=f21e3]
+  - paragraph [ref=f21e4]: 브라우저에는 OAuth token이 전혀 전달되지 않습니다. HttpOnly session cookie로 BFF만 호출하고, BFF가 서버 보관 access token을 Resource Server 요청에 붙입니다.
+  - button "Keycloak 로그인" [ref=f21e5] [cursor=pointer]
+  - button "token 경계 확인" [ref=f21e6] [cursor=pointer]
+  - button "BFF 경유 API 호출" [ref=f21e7] [cursor=pointer]
+  - button "CSRF token으로 상태 변경" [ref=f21e8] [cursor=pointer]

.playwright-mcp/page-2026-09-04T04-44-20-764Z.yml

@@ -0,0 +1,16 @@
+- generic [ref=f22e3]:
+  - banner [ref=f22e4]:
+    - generic [ref=f22e5]: keycloak-patterns
+  - main [ref=f22e6]:
+    - heading "Sign in to your account" [level=1] [ref=f22e8]
+    - generic [ref=f22e12]:
+      - generic [ref=f22e13]:
+        - generic [ref=f22e14]: Username or email
+        - textbox "Username or email" [active] [ref=f22e17]
+      - generic [ref=f22e18]:
+        - generic [ref=f22e19]: Password
+        - generic [ref=f22e21]:
+          - textbox "Password" [ref=f22e24]
+          - button "Show password" [ref=f22e26] [cursor=pointer]:
+            - generic [aria-hidden] [ref=f22e27]: 
+      - button "Sign In" [ref=f22e30] [cursor=pointer]

.playwright-mcp/page-2026-09-04T04-44-32-327Z.yml

@@ -0,0 +1,20 @@
+- generic [ref=f23e3]:
+  - banner [ref=f23e4]:
+    - generic [ref=f23e5]: keycloak-patterns
+  - main [ref=f23e6]:
+    - heading "Update Account Information" [level=1] [ref=f23e8]
+    - generic [ref=f23e9]:
+      - generic [ref=f23e10]: "* Required fields"
+      - generic [ref=f23e13]:
+        - generic [ref=f23e14]:
+          - generic [ref=f23e15]: Email *
+          - textbox "Email" [ref=f23e19]: labuser@example.com
+        - generic [ref=f23e20]:
+          - generic [ref=f23e21]: First name *
+          - textbox "First name" [invalid] [ref=f23e25]
+          - generic [ref=f23e26]: Please specify this field.
+        - generic [ref=f23e31]:
+          - generic [ref=f23e32]: Last name *
+          - textbox "Last name" [invalid] [ref=f23e36]
+          - generic [ref=f23e37]: Please specify this field.
+        - button "Submit" [ref=f23e44]

.playwright-mcp/page-2026-09-04T04-44-52-039Z.yml

@@ -0,0 +1,20 @@
+- generic [ref=f23e3]:
+  - banner [ref=f23e4]:
+    - generic [ref=f23e5]: keycloak-patterns
+  - main [ref=f23e6]:
+    - heading "Update Account Information" [level=1] [ref=f23e8]
+    - generic [ref=f23e9]:
+      - generic [ref=f23e10]: "* Required fields"
+      - generic [ref=f23e13]:
+        - generic [ref=f23e14]:
+          - generic [ref=f23e15]: Email *
+          - textbox "Email" [ref=f23e19]: labuser@example.com
+        - generic [ref=f23e20]:
+          - generic [ref=f23e21]: First name *
+          - textbox "First name" [invalid] [ref=f23e25]: Lab
+          - generic [ref=f23e26]: Please specify this field.
+        - generic [ref=f23e31]:
+          - generic [ref=f23e32]: Last name *
+          - textbox "Last name" [active] [invalid] [ref=f23e36]: User
+          - generic [ref=f23e37]: Please specify this field.
+        - button "Submit" [ref=f23e44]

.playwright-mcp/page-2026-09-04T04-45-23-537Z.yml

@@ -0,0 +1,7 @@
+- main [ref=f24e2]:
+  - heading "AP3 · Backend-for-Frontend" [level=1] [ref=f24e3]
+  - paragraph [ref=f24e4]: 브라우저에는 OAuth token이 전혀 전달되지 않습니다. HttpOnly session cookie로 BFF만 호출하고, BFF가 서버 보관 access token을 Resource Server 요청에 붙입니다.
+  - button "Keycloak 로그인" [ref=f24e5] [cursor=pointer]
+  - button "token 경계 확인" [ref=f24e6] [cursor=pointer]
+  - button "BFF 경유 API 호출" [ref=f24e7] [cursor=pointer]
+  - button "CSRF token으로 상태 변경" [ref=f24e8] [cursor=pointer]

.playwright-mcp/page-2026-09-04T04-45-28-992Z.yml

@@ -0,0 +1,16 @@
+- generic [ref=f25e3]:
+  - banner [ref=f25e4]:
+    - generic [ref=f25e5]: keycloak-patterns
+  - main [ref=f25e6]:
+    - heading "Sign in to your account" [level=1] [ref=f25e8]
+    - generic [ref=f25e12]:
+      - generic [ref=f25e13]:
+        - generic [ref=f25e14]: Username or email
+        - textbox "Username or email" [active] [ref=f25e17]
+      - generic [ref=f25e18]:
+        - generic [ref=f25e19]: Password
+        - generic [ref=f25e21]:
+          - textbox "Password" [ref=f25e24]
+          - button "Show password" [ref=f25e26] [cursor=pointer]:
+            - generic [aria-hidden] [ref=f25e27]: 
+      - button "Sign In" [ref=f25e30] [cursor=pointer]

.playwright-mcp/page-2026-09-04T04-45-37-881Z.yml

@@ -0,0 +1,9 @@
+- generic [ref=f26e2]:
+  - heading "Login with OAuth 2.0" [level=2] [ref=f26e3]
+  - alert [ref=f26e4]: Invalid credentials
+  - table [ref=f26e5]:
+    - rowgroup [ref=f26e6]:
+      - row [ref=f26e7]:
+        - cell [ref=f26e8]:
+          - link "keycloak" [ref=f26e9] [cursor=pointer]:
+            - /url: /oauth2/authorization/keycloak

.playwright-mcp/page-2026-09-04T04-46-14-914Z.yml

@@ -0,0 +1,7 @@
+- main [ref=f27e2]:
+  - heading "AP3 · Backend-for-Frontend" [level=1] [ref=f27e3]
+  - paragraph [ref=f27e4]: 브라우저에는 OAuth token이 전혀 전달되지 않습니다. HttpOnly session cookie로 BFF만 호출하고, BFF가 서버 보관 access token을 Resource Server 요청에 붙입니다.
+  - button "Keycloak 로그인" [ref=f27e5] [cursor=pointer]
+  - button "token 경계 확인" [ref=f27e6] [cursor=pointer]
+  - button "BFF 경유 API 호출" [ref=f27e7] [cursor=pointer]
+  - button "CSRF token으로 상태 변경" [ref=f27e8] [cursor=pointer]

.playwright-mcp/page-2026-09-04T04-46-19-545Z.yml

@@ -0,0 +1,7 @@
+- main [ref=f27e2]:
+  - heading "AP3 · Backend-for-Frontend" [level=1] [ref=f27e3]
+  - paragraph [ref=f27e4]: 브라우저에는 OAuth token이 전혀 전달되지 않습니다. HttpOnly session cookie로 BFF만 호출하고, BFF가 서버 보관 access token을 Resource Server 요청에 붙입니다.
+  - button "Keycloak 로그인" [ref=f27e5] [cursor=pointer]
+  - button "token 경계 확인" [ref=f27e6] [cursor=pointer]
+  - button "BFF 경유 API 호출" [ref=f27e7] [cursor=pointer]
+  - button "CSRF token으로 상태 변경" [ref=f27e8] [cursor=pointer]

.playwright-mcp/page-2026-09-04T04-46-29-422Z.yml

@@ -0,0 +1,7 @@
+- main [ref=f27e2]:
+  - heading "AP3 · Backend-for-Frontend" [level=1] [ref=f27e3]
+  - paragraph [ref=f27e4]: 브라우저에는 OAuth token이 전혀 전달되지 않습니다. HttpOnly session cookie로 BFF만 호출하고, BFF가 서버 보관 access token을 Resource Server 요청에 붙입니다.
+  - button "Keycloak 로그인" [ref=f27e5] [cursor=pointer]
+  - button "token 경계 확인" [ref=f27e6] [cursor=pointer]
+  - button "BFF 경유 API 호출" [ref=f27e7] [cursor=pointer]
+  - button "CSRF token으로 상태 변경" [ref=f27e8] [cursor=pointer]

.playwright-mcp/page-2026-09-04T04-46-50-621Z.yml

@@ -0,0 +1 @@
+- generic [active] [ref=f28e1]: "{\"pattern\":\"AP3-backend-for-frontend\",\"principal\":\"labuser\",\"accessTokenStoredOnServer\":true,\"refreshTokenStoredOnServer\":true,\"browserTokenCount\":0,\"csrfProtectionEnabled\":true}"

bff/.dockerignore

@@ -0,0 +1 @@
+target/

bff/Dockerfile

@@ -0,0 +1,14 @@
+FROM maven:3.9.11-eclipse-temurin-21-alpine AS build
+WORKDIR /workspace
+COPY pom.xml .
+RUN mvn --batch-mode dependency:go-offline
+COPY src src
+RUN mvn --batch-mode verify
+
+FROM eclipse-temurin:21-jre-alpine
+RUN addgroup -S spring && adduser -S spring -G spring
+WORKDIR /app
+COPY --from=build /workspace/target/keycloak-bff.jar app.jar
+USER spring:spring
+EXPOSE 8083
+ENTRYPOINT ["java", "-jar", "/app/app.jar"]

bff/pom.xml

@@ -0,0 +1,58 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<project xmlns="http://maven.apache.org/POM/4.0.0"
+         xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
+         xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 https://maven.apache.org/xsd/maven-4.0.0.xsd">
+    <modelVersion>4.0.0</modelVersion>
+
+    <parent>
+        <groupId>org.springframework.boot</groupId>
+        <artifactId>spring-boot-starter-parent</artifactId>
+        <version>3.5.16</version>
+        <relativePath/>
+    </parent>
+
+    <groupId>com.example</groupId>
+    <artifactId>keycloak-bff</artifactId>
+    <version>0.0.1-SNAPSHOT</version>
+    <name>keycloak-bff</name>
+
+    <properties>
+        <java.version>21</java.version>
+    </properties>
+
+    <dependencies>
+        <dependency>
+            <groupId>org.springframework.boot</groupId>
+            <artifactId>spring-boot-starter-actuator</artifactId>
+        </dependency>
+        <dependency>
+            <groupId>org.springframework.boot</groupId>
+            <artifactId>spring-boot-starter-oauth2-client</artifactId>
+        </dependency>
+        <dependency>
+            <groupId>org.springframework.boot</groupId>
+            <artifactId>spring-boot-starter-web</artifactId>
+        </dependency>
+
+        <dependency>
+            <groupId>org.springframework.boot</groupId>
+            <artifactId>spring-boot-starter-test</artifactId>
+            <scope>test</scope>
+        </dependency>
+        <dependency>
+            <groupId>org.springframework.security</groupId>
+            <artifactId>spring-security-test</artifactId>
+            <scope>test</scope>
+        </dependency>
+    </dependencies>
+
+    <build>
+        <finalName>keycloak-bff</finalName>
+        <plugins>
+            <plugin>
+                <groupId>org.springframework.boot</groupId>
+                <artifactId>spring-boot-maven-plugin</artifactId>
+            </plugin>
+        </plugins>
+    </build>
+</project>

bff/src/main/java/com/example/keycloakpattern/bff/BffApplication.java

@@ -0,0 +1,12 @@
+package com.example.keycloakpattern.bff;
+
+import org.springframework.boot.SpringApplication;
+import org.springframework.boot.autoconfigure.SpringBootApplication;
+
+@SpringBootApplication
+public class BffApplication {
+
+    public static void main(String[] args) {
+        SpringApplication.run(BffApplication.class, args);
+    }
+}

bff/src/main/java/com/example/keycloakpattern/bff/BffController.java

@@ -0,0 +1,112 @@
+package com.example.keycloakpattern.bff;
+
+import java.util.LinkedHashMap;
+import java.util.Map;
+import java.util.concurrent.atomic.AtomicReference;
+
+import org.springframework.beans.factory.annotation.Value;
+import org.springframework.http.CacheControl;
+import org.springframework.http.HttpHeaders;
+import org.springframework.http.ResponseEntity;
+import org.springframework.security.core.Authentication;
+import org.springframework.security.oauth2.client.OAuth2AuthorizeRequest;
+import org.springframework.security.oauth2.client.OAuth2AuthorizedClient;
+import org.springframework.security.oauth2.client.OAuth2AuthorizedClientManager;
+import org.springframework.security.oauth2.client.OAuth2AuthorizedClientService;
+import org.springframework.web.bind.annotation.GetMapping;
+import org.springframework.web.bind.annotation.PostMapping;
+import org.springframework.web.bind.annotation.RequestParam;
+import org.springframework.web.bind.annotation.RestController;
+import org.springframework.web.client.RestClient;
+import org.springframework.web.server.ResponseStatusException;
+
+import static org.springframework.http.HttpStatus.UNAUTHORIZED;
+
+@RestController
+public class BffController {
+
+    private final OAuth2AuthorizedClientService authorizedClientService;
+    private final OAuth2AuthorizedClientManager authorizedClientManager;
+    private final RestClient resourceApi;
+    private final AtomicReference<String> theme = new AtomicReference<>("system");
+
+    public BffController(
+        OAuth2AuthorizedClientService authorizedClientService,
+        OAuth2AuthorizedClientManager authorizedClientManager,
+        RestClient.Builder restClientBuilder,
+        @Value("${resource-api.base-url}") String resourceApiBaseUrl
+    ) {
+        this.authorizedClientService = authorizedClientService;
+        this.authorizedClientManager = authorizedClientManager;
+        this.resourceApi = restClientBuilder.baseUrl(resourceApiBaseUrl).build();
+    }
+
+    @GetMapping("/bff/token-boundary")
+    ResponseEntity<Map<String, Object>> tokenBoundary(Authentication authentication) {
+        OAuth2AuthorizedClient client = authorizedClientService.loadAuthorizedClient(
+            "keycloak",
+            authentication.getName()
+        );
+
+        Map<String, Object> response = new LinkedHashMap<>();
+        response.put("pattern", "AP3-backend-for-frontend");
+        response.put("principal", authentication.getName());
+        response.put("accessTokenStoredOnServer", client != null
+            && client.getAccessToken() != null);
+        response.put("refreshTokenStoredOnServer", client != null
+            && client.getRefreshToken() != null);
+        response.put("browserTokenCount", 0);
+        response.put("csrfProtectionEnabled", true);
+
+        return ResponseEntity.ok()
+            .cacheControl(CacheControl.noStore())
+            .header("Pragma", "no-cache")
+            .body(response);
+    }
+
+    @GetMapping("/bff/api/me")
+    ResponseEntity<?> currentUser(Authentication authentication) {
+        OAuth2AuthorizedClient client = authorizedClient(authentication);
+        return resourceApi.get()
+            .uri("/api/me")
+            .header(
+                HttpHeaders.AUTHORIZATION,
+                "Bearer " + client.getAccessToken().getTokenValue()
+            )
+            .retrieve()
+            .toEntity(Map.class);
+    }
+
+    @PostMapping("/bff/api/preferences")
+    Map<String, Object> updatePreference(
+        Authentication authentication,
+        @RequestParam(defaultValue = "system") String theme
+    ) {
+        this.theme.set(theme);
+        return Map.of(
+            "updated", true,
+            "theme", this.theme.get(),
+            "principal", authentication.getName()
+        );
+    }
+
+    @GetMapping("/bff/api/preferences")
+    Map<String, String> preference() {
+        return Map.of("theme", theme.get());
+    }
+
+    private OAuth2AuthorizedClient authorizedClient(Authentication authentication) {
+        OAuth2AuthorizeRequest request = OAuth2AuthorizeRequest
+            .withClientRegistrationId("keycloak")
+            .principal(authentication)
+            .build();
+        OAuth2AuthorizedClient client = authorizedClientManager.authorize(request);
+        if (client == null || client.getAccessToken() == null) {
+            throw new ResponseStatusException(
+                UNAUTHORIZED,
+                "No authorized Keycloak client is available"
+            );
+        }
+        return client;
+    }
+}

bff/src/main/java/com/example/keycloakpattern/bff/CsrfController.java

@@ -0,0 +1,25 @@
+package com.example.keycloakpattern.bff;
+
+import java.util.Map;
+
+import org.springframework.http.CacheControl;
+import org.springframework.http.ResponseEntity;
+import org.springframework.security.web.csrf.CsrfToken;
+import org.springframework.web.bind.annotation.GetMapping;
+import org.springframework.web.bind.annotation.RestController;
+
+@RestController
+public class CsrfController {
+
+    @GetMapping("/bff/csrf")
+    ResponseEntity<Map<String, String>> csrf(CsrfToken csrfToken) {
+        return ResponseEntity.ok()
+            .cacheControl(CacheControl.noStore())
+            .header("Pragma", "no-cache")
+            .body(Map.of(
+                "headerName", csrfToken.getHeaderName(),
+                "parameterName", csrfToken.getParameterName(),
+                "token", csrfToken.getToken()
+            ));
+    }
+}

bff/src/main/java/com/example/keycloakpattern/bff/SecurityConfig.java

@@ -0,0 +1,85 @@
+package com.example.keycloakpattern.bff;
+
+import org.springframework.context.annotation.Bean;
+import org.springframework.context.annotation.Configuration;
+import org.springframework.security.config.annotation.web.builders.HttpSecurity;
+import org.springframework.security.oauth2.client.AuthorizedClientServiceOAuth2AuthorizedClientManager;
+import org.springframework.security.oauth2.client.OAuth2AuthorizedClientManager;
+import org.springframework.security.oauth2.client.OAuth2AuthorizedClientProvider;
+import org.springframework.security.oauth2.client.OAuth2AuthorizedClientProviderBuilder;
+import org.springframework.security.oauth2.client.OAuth2AuthorizedClientService;
+import org.springframework.security.oauth2.client.registration.ClientRegistrationRepository;
+import org.springframework.security.oauth2.client.web.DefaultOAuth2AuthorizationRequestResolver;
+import org.springframework.security.oauth2.client.web.OAuth2AuthorizationRequestCustomizers;
+import org.springframework.security.web.SecurityFilterChain;
+import org.springframework.security.web.csrf.CookieCsrfTokenRepository;
+
+@Configuration
+public class SecurityConfig {
+
+    @Bean
+    SecurityFilterChain bffSecurity(
+        HttpSecurity http,
+        ClientRegistrationRepository clientRegistrationRepository
+    ) throws Exception {
+        DefaultOAuth2AuthorizationRequestResolver authorizationRequestResolver =
+            new DefaultOAuth2AuthorizationRequestResolver(
+                clientRegistrationRepository,
+                "/oauth2/authorization"
+            );
+        authorizationRequestResolver.setAuthorizationRequestCustomizer(
+            OAuth2AuthorizationRequestCustomizers.withPkce()
+        );
+
+        CookieCsrfTokenRepository csrfTokenRepository =
+            CookieCsrfTokenRepository.withHttpOnlyFalse();
+        csrfTokenRepository.setCookiePath("/");
+
+        return http
+            .csrf(csrf -> csrf
+                .csrfTokenRepository(csrfTokenRepository)
+                .csrfTokenRequestHandler(new SpaCsrfTokenRequestHandler()))
+            .authorizeHttpRequests(authorize -> authorize
+                .requestMatchers(
+                    "/",
+                    "/index.html",
+                    "/app.js",
+                    "/favicon.ico",
+                    "/actuator/health",
+                    "/actuator/health/**",
+                    // 실험대 전용 — B-0 은 "자동구성이 실제로 무엇을 골랐는가"를
+                    // 밖에서 읽어야 답할 수 있다. 운영에서는 절대 열지 않는다:
+                    // /actuator/beans 와 /actuator/env 는 내부 구조와 설정값을
+                    // 그대로 드러낸다.
+                    "/actuator/**"
+                )
+                .permitAll()
+                .anyRequest()
+                .authenticated())
+            .oauth2Login(oauth2 -> oauth2
+                .authorizationEndpoint(endpoint -> endpoint
+                    .authorizationRequestResolver(authorizationRequestResolver))
+                .defaultSuccessUrl("/", true))
+            .build();
+    }
+
+    @Bean
+    OAuth2AuthorizedClientManager authorizedClientManager(
+        ClientRegistrationRepository clientRegistrationRepository,
+        OAuth2AuthorizedClientService authorizedClientService
+    ) {
+        OAuth2AuthorizedClientProvider authorizedClientProvider =
+            OAuth2AuthorizedClientProviderBuilder.builder()
+                .authorizationCode()
+                .refreshToken()
+                .build();
+
+        AuthorizedClientServiceOAuth2AuthorizedClientManager manager =
+            new AuthorizedClientServiceOAuth2AuthorizedClientManager(
+                clientRegistrationRepository,
+                authorizedClientService
+            );
+        manager.setAuthorizedClientProvider(authorizedClientProvider);
+        return manager;
+    }
+}

bff/src/main/java/com/example/keycloakpattern/bff/SpaCsrfTokenRequestHandler.java

@@ -0,0 +1,40 @@
+package com.example.keycloakpattern.bff;
+
+import java.util.function.Supplier;
+
+import jakarta.servlet.http.HttpServletRequest;
+import jakarta.servlet.http.HttpServletResponse;
+
+import org.springframework.security.web.csrf.CsrfToken;
+import org.springframework.security.web.csrf.CsrfTokenRequestAttributeHandler;
+import org.springframework.security.web.csrf.CsrfTokenRequestHandler;
+import org.springframework.security.web.csrf.XorCsrfTokenRequestAttributeHandler;
+import org.springframework.util.StringUtils;
+
+final class SpaCsrfTokenRequestHandler implements CsrfTokenRequestHandler {
+
+    private final CsrfTokenRequestHandler plain =
+        new CsrfTokenRequestAttributeHandler();
+    private final CsrfTokenRequestHandler xor =
+        new XorCsrfTokenRequestAttributeHandler();
+
+    @Override
+    public void handle(
+        HttpServletRequest request,
+        HttpServletResponse response,
+        Supplier<CsrfToken> deferredCsrfToken
+    ) {
+        xor.handle(request, response, deferredCsrfToken);
+    }
+
+    @Override
+    public String resolveCsrfTokenValue(
+        HttpServletRequest request,
+        CsrfToken csrfToken
+    ) {
+        if (StringUtils.hasText(request.getHeader(csrfToken.getHeaderName()))) {
+            return plain.resolveCsrfTokenValue(request, csrfToken);
+        }
+        return xor.resolveCsrfTokenValue(request, csrfToken);
+    }
+}

bff/src/main/resources/application.yml

@@ -0,0 +1,52 @@
+server:
+  port: ${SERVER_PORT:8083}
+  servlet:
+    session:
+      cookie:
+        name: AP3_SESSION
+        http-only: true
+        same-site: lax
+
+spring:
+  application:
+    name: keycloak-bff
+  security:
+    oauth2:
+      client:
+        registration:
+          keycloak:
+            provider: keycloak
+            client-id: bff-confidential
+            client-secret: ${KEYCLOAK_CLIENT_SECRET}
+            client-authentication-method: client_secret_basic
+            authorization-grant-type: authorization_code
+            redirect-uri: "{baseUrl}/login/oauth2/code/{registrationId}"
+            scope:
+              - openid
+              - profile
+              - email
+        provider:
+          keycloak:
+            # 브라우저가 리다이렉트되는 주소와 BFF 가 서버끼리 부르는 주소는 다르다.
+            # 앞의 것은 외부에서 닿는 이름이어야 하고, 뒤의 것은 클러스터 안 주소여도 된다.
+            authorization-uri: ${KC_ISSUER_EXTERNAL:http://localhost:8080/realms/keycloak-patterns}/protocol/openid-connect/auth
+            token-uri:         ${KC_ISSUER_INTERNAL:http://keycloak:8080/realms/keycloak-patterns}/protocol/openid-connect/token
+            jwk-set-uri:       ${KC_ISSUER_INTERNAL:http://keycloak:8080/realms/keycloak-patterns}/protocol/openid-connect/certs
+            user-info-uri:     ${KC_ISSUER_INTERNAL:http://keycloak:8080/realms/keycloak-patterns}/protocol/openid-connect/userinfo
+            user-name-attribute: preferred_username
+
+resource-api:
+  base-url: ${RESOURCE_API_BASE_URL:http://localhost:8081}
+
+management:
+  endpoint:
+    health:
+      probes:
+        enabled: true
+      show-details: always
+  endpoints:
+    web:
+      exposure:
+        # beans / conditions 는 B-0 에서 "자동구성이 실제로 무엇을 골랐는가"를
+        # 보기 위해 연다. 운영에 그대로 두면 내부 구조가 노출된다.
+        include: health,info,beans,conditions,env

bff/src/main/resources/static/app.js

@@ -0,0 +1,59 @@
+const result = document.querySelector("#result");
+
+function render(value) {
+  result.textContent = JSON.stringify(value, null, 2);
+}
+
+function readCookie(name) {
+  const prefix = `${encodeURIComponent(name)}=`;
+  const value = document.cookie
+    .split("; ")
+    .find((cookie) => cookie.startsWith(prefix));
+  return value ? decodeURIComponent(value.slice(prefix.length)) : null;
+}
+
+async function request(path, options = {}) {
+  const response = await fetch(path, {
+    ...options,
+    headers: { Accept: "application/json", ...options.headers },
+  });
+  if (response.redirected || response.status === 401) {
+    window.location.assign("/oauth2/authorization/keycloak");
+    return null;
+  }
+  const body = await response.json();
+  render({ status: response.status, ...body });
+  return { response, body };
+}
+
+document.querySelector("#login").addEventListener("click", () => {
+  window.location.assign("/oauth2/authorization/keycloak");
+});
+
+document.querySelector("#inspect").addEventListener("click", () => {
+  void request("/bff/token-boundary");
+});
+
+document.querySelector("#call-bff").addEventListener("click", () => {
+  void request("/bff/api/me");
+});
+
+document.querySelector("#change-with-csrf").addEventListener("click", async () => {
+  const csrfResponse = await fetch("/bff/csrf", {
+    headers: { Accept: "application/json" },
+  });
+  const csrf = await csrfResponse.json();
+  const csrfToken = readCookie("XSRF-TOKEN");
+  if (!csrfToken) {
+    render({ status: 500, error: "XSRF-TOKEN cookie was not created" });
+    return;
+  }
+  await request("/bff/api/preferences", {
+    method: "POST",
+    body: new URLSearchParams({ theme: "dark" }),
+    headers: {
+      "Content-Type": "application/x-www-form-urlencoded",
+      [csrf.headerName]: csrfToken,
+    },
+  });
+});

bff/src/main/resources/static/index.html

@@ -0,0 +1,31 @@
+<!doctype html>
+<html lang="ko">
+<head>
+  <meta charset="utf-8">
+  <meta name="viewport" content="width=device-width, initial-scale=1">
+  <title>AP3 · Backend-for-Frontend</title>
+  <style>
+    :root { color-scheme: light dark; font-family: system-ui, sans-serif; }
+    body { max-width: 58rem; margin: 6vh auto; padding: 0 1.5rem; line-height: 1.6; }
+    button { margin: 0 0.5rem 0.5rem 0; padding: 0.6rem 0.9rem; cursor: pointer; }
+    pre { min-height: 9rem; padding: 1rem; border-radius: 0.4rem;
+      background: color-mix(in srgb, CanvasText 9%, Canvas); white-space: pre-wrap; }
+  </style>
+</head>
+<body>
+  <main>
+    <h1>AP3 · Backend-for-Frontend</h1>
+    <p>
+      브라우저에는 OAuth token이 전혀 전달되지 않습니다. HttpOnly session
+      cookie로 BFF만 호출하고, BFF가 서버 보관 access token을 Resource
+      Server 요청에 붙입니다.
+    </p>
+    <button id="login" type="button">Keycloak 로그인</button>
+    <button id="inspect" type="button">token 경계 확인</button>
+    <button id="call-bff" type="button">BFF 경유 API 호출</button>
+    <button id="change-with-csrf" type="button">CSRF token으로 상태 변경</button>
+    <pre id="result" aria-live="polite"></pre>
+  </main>
+  <script type="module" src="/app.js"></script>
+</body>
+</html>

bff/src/test/java/com/example/keycloakpattern/bff/BffControllerTest.java

@@ -0,0 +1,90 @@
+package com.example.keycloakpattern.bff;
+
+import static org.mockito.Mockito.mock;
+import static org.mockito.Mockito.when;
+import static org.springframework.security.test.web.servlet.request.SecurityMockMvcRequestPostProcessors.oidcLogin;
+import static org.springframework.security.test.web.servlet.request.SecurityMockMvcRequestPostProcessors.csrf;
+import static org.springframework.test.web.servlet.request.MockMvcRequestBuilders.get;
+import static org.springframework.test.web.servlet.request.MockMvcRequestBuilders.post;
+import static org.springframework.test.web.servlet.result.MockMvcResultMatchers.header;
+import static org.springframework.test.web.servlet.result.MockMvcResultMatchers.jsonPath;
+import static org.springframework.test.web.servlet.result.MockMvcResultMatchers.status;
+
+import org.junit.jupiter.api.Test;
+import org.springframework.beans.factory.annotation.Autowired;
+import org.springframework.boot.test.autoconfigure.web.servlet.AutoConfigureMockMvc;
+import org.springframework.boot.test.context.SpringBootTest;
+import org.springframework.security.oauth2.client.OAuth2AuthorizedClient;
+import org.springframework.security.oauth2.client.OAuth2AuthorizedClientManager;
+import org.springframework.security.oauth2.client.OAuth2AuthorizedClientService;
+import org.springframework.security.oauth2.core.OAuth2AccessToken;
+import org.springframework.security.oauth2.core.OAuth2RefreshToken;
+import org.springframework.test.context.bean.override.mockito.MockitoBean;
+import org.springframework.test.web.servlet.MockMvc;
+
+@SpringBootTest(properties = {
+    "KEYCLOAK_CLIENT_SECRET=test-only-secret",
+    "resource-api.base-url=http://127.0.0.1:9"
+})
+@AutoConfigureMockMvc
+class BffControllerTest {
+
+    @Autowired
+    private MockMvc mockMvc;
+
+    @MockitoBean
+    private OAuth2AuthorizedClientService authorizedClientService;
+
+    @MockitoBean
+    private OAuth2AuthorizedClientManager authorizedClientManager;
+
+    @Test
+    void reportsServerTokenCustodyWithoutReturningTokens() throws Exception {
+        OAuth2AuthorizedClient client = mock(OAuth2AuthorizedClient.class);
+        when(client.getAccessToken()).thenReturn(mock(OAuth2AccessToken.class));
+        when(client.getRefreshToken()).thenReturn(mock(OAuth2RefreshToken.class));
+        when(authorizedClientService.loadAuthorizedClient("keycloak", "test-subject"))
+            .thenReturn(client);
+
+        mockMvc.perform(get("/bff/token-boundary").with(oidcLogin()
+                .idToken(token -> token.subject("test-subject"))))
+            .andExpect(status().isOk())
+            .andExpect(header().string("Cache-Control", "no-store"))
+            .andExpect(jsonPath("$.accessTokenStoredOnServer").value(true))
+            .andExpect(jsonPath("$.refreshTokenStoredOnServer").value(true))
+            .andExpect(jsonPath("$.browserTokenCount").value(0))
+            .andExpect(jsonPath("$.csrfProtectionEnabled").value(true))
+            .andExpect(jsonPath("$.access_token").doesNotExist())
+            .andExpect(jsonPath("$.refresh_token").doesNotExist());
+    }
+
+    @Test
+    void rejectsStateChangeWithoutCsrfToken() throws Exception {
+        mockMvc.perform(post("/bff/api/preferences")
+                .param("theme", "attacker")
+                .with(oidcLogin().idToken(token -> token.subject("test-subject"))))
+            .andExpect(status().isForbidden());
+    }
+
+    @Test
+    void acceptsStateChangeWithCsrfToken() throws Exception {
+        mockMvc.perform(post("/bff/api/preferences")
+                .param("theme", "dark")
+                .with(oidcLogin().idToken(token -> token.subject("test-subject")))
+                .with(csrf()))
+            .andExpect(status().isOk())
+            .andExpect(jsonPath("$.updated").value(true))
+            .andExpect(jsonPath("$.theme").value("dark"));
+    }
+
+    @Test
+    void exposesSpaCsrfTokenWithoutCaching() throws Exception {
+        mockMvc.perform(get("/bff/csrf").with(oidcLogin()
+                .idToken(token -> token.subject("test-subject"))))
+            .andExpect(status().isOk())
+            .andExpect(header().string("Cache-Control", "no-store"))
+            .andExpect(header().exists("Set-Cookie"))
+            .andExpect(jsonPath("$.headerName").value("X-XSRF-TOKEN"))
+            .andExpect(jsonPath("$.token").isNotEmpty());
+    }
+}

deploy/lab/k8s/bff-redis.yaml

@@ -0,0 +1,161 @@
+# BFF (2 replicas) + Redis, for the B-layer experiments.
+#
+# The BFF is deployed FIRST WITHOUT any session store wiring. That is deliberate:
+# B-0 asks what Spring Boot's autoconfiguration actually picks when nothing is
+# configured, and the only honest way to answer is to look at a running instance
+# that has been given nothing. Redis is deployed alongside but left unused until
+# B-1 turns it on.
+#
+#   kubectl apply -f deploy/lab/k8s/bff-redis.yaml
+#
+# Image comes from the workstation, not a registry:
+#   docker build -t keycloak-pattern-bff:lab bff/
+#   docker save keycloak-pattern-bff:lab | ssh test-server "ssh kc-lab-1 'sudo k3s ctr images import -'"
+#   (repeat for kc-lab-2)
+# so imagePullPolicy must stay Never on both replicas.
+apiVersion: v1
+kind: Secret
+metadata:
+  name: bff-secrets
+  namespace: keycloak-lab
+type: Opaque
+stringData:
+  # Matches the client created with kcadm in the keycloak-patterns realm.
+  # Base64 in etcd is not encryption — see D-3.
+  KEYCLOAK_CLIENT_SECRET: bff-lab-secret
+---
+# Redis. No persistence yet: `--save ""` and no appendonly, so a restart loses
+# everything. B-5 and B-6 compare that against RDB and AOF, which is easier to
+# reason about when the starting point is "nothing survives".
+apiVersion: apps/v1
+kind: Deployment
+metadata:
+  name: redis
+  namespace: keycloak-lab
+spec:
+  replicas: 1
+  selector:
+    matchLabels: { app: redis }
+  template:
+    metadata:
+      labels: { app: redis }
+    spec:
+      # Same node as postgres so a node-loss experiment takes both stores at
+      # once, matching how A-4 was set up.
+      nodeSelector:
+        kubernetes.io/hostname: kc-lab-2
+      containers:
+        - name: redis
+          image: redis:7.4-alpine
+          args: ["redis-server", "--save", "", "--appendonly", "no"]
+          ports:
+            - containerPort: 6379
+              name: redis
+          readinessProbe:
+            exec: { command: ["redis-cli", "ping"] }
+            initialDelaySeconds: 3
+          resources:
+            requests: { memory: 32Mi, cpu: 20m }
+            limits:   { memory: 128Mi }
+---
+apiVersion: v1
+kind: Service
+metadata:
+  name: redis
+  namespace: keycloak-lab
+spec:
+  selector: { app: redis }
+  ports:
+    - port: 6379
+      targetPort: redis
+---
+apiVersion: apps/v1
+kind: Deployment
+metadata:
+  name: bff
+  namespace: keycloak-lab
+spec:
+  # Two replicas is the whole point: Q1 and Q2 only exist because a request can
+  # land on an instance that did not handle the login.
+  replicas: 2
+  selector:
+    matchLabels: { app: bff }
+  template:
+    metadata:
+      labels: { app: bff }
+    spec:
+      # Spread across both nodes so "the other instance" is genuinely another
+      # machine, not another process on the same kernel.
+      topologySpreadConstraints:
+        - maxSkew: 1
+          topologyKey: kubernetes.io/hostname
+          whenUnsatisfiable: ScheduleAnyway
+          labelSelector:
+            matchLabels: { app: bff }
+      containers:
+        - name: bff
+          image: keycloak-pattern-bff:lab
+          imagePullPolicy: Never
+          ports:
+            - containerPort: 8083
+              name: http
+          env:
+            # The browser is redirected to the public name; the BFF calls the
+            # token endpoint over the cluster network. Getting these two the same
+            # way round is what the 2-hop header experiment was about.
+            - name: KC_ISSUER_EXTERNAL
+              value: https://auth.hyeonworks.com/realms/keycloak-patterns
+            - name: KC_ISSUER_INTERNAL
+              value: http://keycloak.keycloak-lab.svc:8080/realms/keycloak-patterns
+            - name: RESOURCE_API_BASE_URL
+              value: http://echo.keycloak-lab.svc:8080
+            - name: KEYCLOAK_CLIENT_SECRET
+              valueFrom:
+                secretKeyRef: { name: bff-secrets, key: KEYCLOAK_CLIENT_SECRET }
+            # Spring needs to know it is behind TLS termination, for the same
+            # reason Keycloak needs KC_PROXY_HEADERS. Without it the redirect_uri
+            # it builds comes back as http:// and Keycloak rejects it.
+            - name: SERVER_FORWARD_HEADERS_STRATEGY
+              value: native
+            - name: JAVA_TOOL_OPTIONS
+              value: "-Xms128m -Xmx320m"
+          readinessProbe:
+            httpGet: { path: /actuator/health/readiness, port: http }
+            initialDelaySeconds: 20
+            failureThreshold: 30
+          livenessProbe:
+            httpGet: { path: /actuator/health/liveness, port: http }
+            initialDelaySeconds: 60
+          resources:
+            requests: { memory: 320Mi, cpu: 100m }
+            limits:   { memory: 512Mi }
+---
+apiVersion: v1
+kind: Service
+metadata:
+  name: bff
+  namespace: keycloak-lab
+spec:
+  selector: { app: bff }
+  ports:
+    - port: 8083
+      targetPort: http
+---
+apiVersion: networking.k8s.io/v1
+kind: Ingress
+metadata:
+  name: bff
+  namespace: keycloak-lab
+spec:
+  ingressClassName: traefik
+  rules:
+    - host: app1.hyeonworks.com
+      http:
+        paths:
+          - path: /
+            pathType: Prefix
+            backend:
+              service:
+                name: bff
+                port:
+                  number: 8083

docs/evidence/a5-asymmetric-partition/01-injection.txt

@@ -0,0 +1,42 @@
+=== A-5 기준선 ===
+  keycloak-0=10.42.1.77 (kc-lab-2)   keycloak-1=10.42.0.42 (kc-lab-1)
+keycloak-0                  1/1   Running   0               11m
+keycloak-1                  1/1   Running   1 (2m48s ago)   155m
+postgres-7b474b88c8-9cmsv   1/1   Running   0               14m
+Traceback (most recent call last):
+  File "<string>", line 3, in <module>
+    for r in json.load(sys.stdin)["data"]["result"]: print(f"  cluster_size {r["metric"].get("pod"):12} = {r["value"][1]}")
+             ~~~~~~~~~^^^^^^^^^^^
+  File "/usr/lib/python3.14/json/__init__.py", line 298, in load
+    return loads(fp.read(),
+        cls=cls, object_hook=object_hook,
+        parse_float=parse_float, parse_int=parse_int,
+        parse_constant=parse_constant, object_pairs_hook=object_pairs_hook, **kw)
+  File "/usr/lib/python3.14/json/__init__.py", line 352, in loads
+    return _default_decoder.decode(s)
+           ~~~~~~~~~~~~~~~~~~~~~~~^^^
+  File "/usr/lib/python3.14/json/decoder.py", line 345, in decode
+    obj, end = self.raw_decode(s, idx=_w(s, 0).end())
+               ~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^
+  File "/usr/lib/python3.14/json/decoder.py", line 363, in raw_decode
+    raise JSONDecodeError("Expecting value", s, err.value) from None
+json.decoder.JSONDecodeError: Expecting value: line 1 column 1 (char 0)
+
+=== 주입: keycloak-0 으로 들어가는 7800/57800 만 DROP (한 방향) ===
+  A-1 의 NetworkPolicy 는 conntrack ESTABLISHED 에 막혀 기존 연결을 못 끊었다.
+  FORWARD 최상단에 넣으면 conntrack 승인보다 먼저 평가된다.
+Chain FORWARD (policy ACCEPT)
+num  target     prot opt source               destination         
+1    DROP       6    --  0.0.0.0/0            10.42.1.77           tcp dpt:57800
+2    DROP       6    --  0.0.0.0/0            10.42.1.77           tcp dpt:7800
+  주입 시각: 12:28:23
+
+=== 관찰 — 어느 쪽이 먼저 상대를 의심하는가 ===
+  +25초   | keycloak-0:1/1 keycloak-1:1/1 | 외부 200
+  +50초   | keycloak-0:1/1 keycloak-1:1/1 | 외부 200
+  +75초   | keycloak-0:1/1 keycloak-1:1/1 | 외부 200
+  +100초   | keycloak-0:1/1 keycloak-1:1/1 | 외부 200
+  +125초   | keycloak-0:1/1 keycloak-1:1/1 | 외부 200
+  +150초   | keycloak-0:1/1 keycloak-1:1/1 | 외부 200
+  +175초   | keycloak-0:1/1 keycloak-1:1/1 | 외부 200
+  +200초   | keycloak-0:1/1 keycloak-1:1/1 | 외부 200

docs/evidence/a5-asymmetric-partition/03-raw-table-injection.txt

@@ -0,0 +1,16 @@
+=== 실패한 규칙 제거 ===
+제거완료
+
+=== raw 테이블 PREROUTING 에 넣는다 — conntrack 보다 먼저 실행된다 ===
+  netfilter 순서: raw PREROUTING → conntrack → mangle → nat → filter
+Chain PREROUTING (policy ACCEPT 0 packets, 0 bytes)
+num   pkts bytes target     prot opt in     out     source               destination         
+1        0     0 DROP       6    --  *      *       0.0.0.0/0            10.42.1.77           tcp dpt:57800
+2        0     0 DROP       6    --  *      *       0.0.0.0/0            10.42.1.77           tcp dpt:7800
+  주입: 12:32:35
+
+=== [검증] 이번엔 패킷이 걸렸는가 ===
+  Chain PREROUTING (policy ACCEPT 0 packets, 0 bytes)
+   pkts bytes target     prot opt in     out     source               destination         
+      0     0 DROP       6    --  *      *       0.0.0.0/0            10.42.1.77           tcp dpt:57800
+      0     0 DROP       6    --  *      *       0.0.0.0/0            10.42.1.77           tcp dpt:7800

docs/evidence/a5-asymmetric-partition/04-correct-direction.txt

@@ -0,0 +1,18 @@
+=== keycloak-1(수신측)으로 들어가는 7800/57800 만 DROP — kc-lab-1 에 넣는다 ===
+  주입: 12:33:58
+
+=== [검증] 패킷이 걸리는가 ===
+  Chain PREROUTING (policy ACCEPT 0 packets, 0 bytes)
+   pkts bytes target     prot opt in     out     source               destination         
+      0     0 DROP       6    --  *      *       0.0.0.0/0            10.42.0.42           tcp dpt:57800
+     19  2938 DROP       6    --  *      *       0.0.0.0/0            10.42.0.42           tcp dpt:7800
+
+=== 관찰 ===
+  +25초  - | keycloak-0:1/1 keycloak-1:1/1 | 외부 200
+  +50초  - | keycloak-0:1/1 keycloak-1:1/1 | 외부 200
+  +75초  - | keycloak-0:1/1 keycloak-1:0/1 | 외부 200
+  +100초  - | keycloak-0:1/1 keycloak-1:1/1 | 외부 200
+  +125초  - | keycloak-0:1/1 keycloak-1:1/1 | 외부 200
+  +150초  - | keycloak-0:1/1 keycloak-1:1/1 | 외부 200
+  +175초  - | keycloak-0:1/1 keycloak-1:1/1 | 외부 200
+  +200초  - | keycloak-0:1/1 keycloak-1:1/1 | 외부 200

docs/evidence/a5-asymmetric-partition/05-reconnect-observed.txt

@@ -0,0 +1,19 @@
+=== 지금 연결 방향은? (차단은 → 10.42.0.42:7800 만) ===
+  tcp      6 299 ESTABLISHED src=10.42.0.42 dst=10.42.1.77 sport=48473 dport=7800 src=10.42.1.77 dst=10.42.0.42 sport=7800 dport=48473
+  tcp      6 86232 ESTABLISHED src=10.42.0.42 dst=10.42.1.77 sport=44205 dport=57800 src=10.42.1.77 dst=10.42.0.42 sport=57800 dport=44205
+
+=== 차단 규칙 누적 카운터 ===
+  Chain PREROUTING (policy ACCEPT 0 packets, 0 bytes)
+   pkts bytes target     prot opt in     out     source               destination         
+     19  1096 DROP       6    --  *      *       0.0.0.0/0            10.42.0.42           tcp dpt:57800
+     21  3058 DROP       6    --  *      *       0.0.0.0/0            10.42.0.42           tcp dpt:7800
+
+=== 클러스터 멤버 (파드에서 직접) ===
+  keycloak-0  cluster_size=2.0
+  keycloak-1  cluster_size=2.0
+
+=== 최근 뷰 로그 ===
+  keycloak-0: [keycloak-0-24309(v=16.0.12)|12] (1) [keycloak-0-24309(v=16.0.12)]
+
+  keycloak-1: [keycloak-1-45480(v=16.0.12)|12] (1) [keycloak-1-45480(v=16.0.12)]
+

docs/evidence/a5-asymmetric-partition/06-view-history-and-cleanup.txt

@@ -0,0 +1,28 @@
+=== 뷰 변화 전체 이력 (차단 12:33:58 전후) ===
+--- keycloak-0 ---
+  2026-09-04 03:33:49 | during merge: CacheTopology{id=37, phase=NO_REBALANCE, rebalanceId=11, currentCH=DefaultConsistentHash{ns=25
+  2026-09-04 03:33:49,398 INFO  [org.infinispan.CLUSTER] (non-blocking-thread--p2-t1) [Context=offlineSessions] ISPN100007: After me
+  2026-09-04 03:33:49 | during merge: CacheTopology{id=37, phase=NO_REBALANCE, rebalanceId=11, currentCH=DefaultConsistentHash{ns=25
+  2026-09-04 03:33:49,399 INFO  [org.infinispan.CLUSTER] (non-blocking-thread--p2-t1) [Context=loginFailures] ISPN100007: After merg
+  2026-09-04 03:33:49 | during merge: CacheTopology{id=37, phase=NO_REBALANCE, rebalanceId=11, currentCH=DefaultConsistentHash{ns=25
+  2026-09-04 03:33:49,402 INFO  [org.infinispan.CLUSTER] (non-blocking-thread--p2-t1) [Context=actionTokens] ISPN100007: After merge
+--- keycloak-1 ---
+  2026-09-04 03:32:59,874 INFO  [org.infinispan.CLUSTER] (non-blocking-thread--p2-t2) [Context=work] ISPN100007: After merge (or coo
+  2026-09-04 03:32:59,879 INFO  [org.infinispan.CLUSTER] (non-blocking-thread--p2-t2) [Context=clientSessions] ISPN100007: After mer
+  2026-09-04 03:32:59,879 INFO  [org.infinispan.CLUSTER] (non-blocking-thread--p2-t1) [Context=offlineSessions] ISPN100007: After me
+  2026-09-04 03:32:59,883 INFO  [org.infinispan.CLUSTER] (non-blocking-thread--p2-t1) [Context=loginFailures] ISPN100007: After merg
+  2026-09-04 03:32:59,884 INFO  [org.infinispan.CLUSTER] (non-blocking-thread--p2-t2) [Context=actionTokens] ISPN100007: After merge
+  2026-09-04 03:33:49 | MergeView::[keycloak-0-24309(v=16.0.12)|13] (2) [keycloak-0-24309(v=16.0.12), keycloak-1-45480(v=16.0.12)], 
+
+=== MERGE3 병합 이벤트 ===
+  keycloak-0  merge_events=1.0  suspected=0.0
+  keycloak-1  merge_events=1.0  suspected=0.0
+
+=== 차단 해제 ===
+해제완료
+  keycloak-0  cluster_size=2.0
+warning: couldn't attach to pod/a5-f, falling back to streaming logs: unable to upgrade connection: container a5-f not found in pod a5-f_keycloak-lab
+  keycloak-0  cluster_size=2.0
+  keycloak-1  cluster_size=2.0
+keycloak-0                  1/1   Running   0             22m
+keycloak-1                  1/1   Running   1 (13m ago)   166m

docs/evidence/a5-asymmetric-partition/07-bidirectional-block.txt

@@ -0,0 +1,17 @@
+=== 양방향 차단 — 두 노드 모두에 raw DROP ===
+  주입: 12:40:25
+  +25초  keycloak-0:1/1 keycloak-1:1/1 | ready=[10.42.0.42 10.42.1.77] 외부 200
+  +50초  keycloak-0:1/1 keycloak-1:1/1 | ready=[10.42.0.42 10.42.1.77] 외부 200
+  +75초  keycloak-0:1/1 keycloak-1:1/1 | ready=[10.42.0.42 10.42.1.77] 외부 200
+  +100초  keycloak-0:1/1 keycloak-1:0/1 | ready=[10.42.1.77] 외부 200
+  +125초  keycloak-0:1/1 keycloak-1:0/1 | ready=[10.42.1.77] 외부 200
+  +150초  keycloak-0:1/1 keycloak-1:0/1 | ready=[10.42.1.77] 외부 200
+  +175초  keycloak-0:1/1 keycloak-1:0/1 | ready=[10.42.1.77] 외부 200
+  +200초  keycloak-0:1/1 keycloak-1:0/1 | ready=[10.42.1.77] 외부 200
+  +225초  keycloak-0:1/1 keycloak-1:0/1 | ready=[10.42.1.77] 외부 200
+
+=== 뷰 상태 ===
+  keycloak-0  [keycloak-0-24309(v=16.0.12)|14] (1) [keycloak-0-24309(v=16.0.12)]
+
+  keycloak-1  [keycloak-1-45480(v=16.0.12)|14] (1) [keycloak-1-45480(v=16.0.12)]
+

docs/evidence/a5-asymmetric-partition/08-coordinator-and-recovery.txt

@@ -0,0 +1,39 @@
+=== 왜 한쪽만 DOWN 인가 — 코디네이터 여부 확인 ===
+       name       |       ip        | coord 
+------------------+-----------------+-------
+ keycloak-0-24309 | 10.42.1.77:7800 | t
+ keycloak-1-45480 | 10.42.0.42:7800 | t
+(2 rows)
+
+=== 양쪽 헬스체크 상세 ===
+--- keycloak-0 ---
+{"status":"UP","checks":[{"name":"GracefulShutdown","status":"UP"}
+{"name":"KeycloakInitialized","status":"UP"}
+{"name":"Keycloakclusterhealthcheck","status":"UP"}
+
+--- keycloak-1 ---
+{"status":"DOWN","checks":[{"name":"GracefulShutdown","status":"UP"}
+{"name":"Keycloakdatabaseconnectionsasynchealthcheck","status":"UP"}
+{"name":"KeycloakInitialized","status":"UP"}
+
+warning: couldn't attach to pod/a5-h, falling back to streaming logs: Internal error occurred: Internal error occurred: error attaching to container: container is in CONTAINER_EXITED state
+--- keycloak-0 ---
+{"status":"UP","checks":[{"name":"GracefulShutdown","status":"UP"}
+{"name":"KeycloakInitialized","status":"UP"}
+{"name":"Keycloakclusterhealthcheck","status":"UP"}
+
+--- keycloak-1 ---
+{"status":"DOWN","checks":[{"name":"GracefulShutdown","status":"UP"}
+{"name":"Keycloakdatabaseconnectionsasynchealthcheck","status":"UP"}
+{"name":"KeycloakInitialized","status":"UP"}
+
+
+=== 차단 해제 ===
+  해제: 12:44:37
+  +25초  keycloak-0:1/1 keycloak-1:0/1 
+  +50초  keycloak-0:1/1 keycloak-1:1/1 
+  → 복구 완료
+  keycloak-0  MergeView::[keycloak-0-24309(v=16.0.12)|15] (2) [keycloak-0-24309(v=16.0.12), keycloak-1-45480(
+
+  keycloak-1  MergeView::[keycloak-0-24309(v=16.0.12)|15] (2) [keycloak-0-24309(v=16.0.12), keycloak-1-45480(
+

docs/evidence/a5-asymmetric-partition/README.md

@@ -0,0 +1,23 @@
+# A-5 — 비대칭 파티션 증거
+
+2026-09-04 12:28–12:46 KST
+해설: [`docs/experiment-a5-asymmetric-partition.md`](../../experiment-a5-asymmetric-partition.md)
+
+| 파일 | 무엇을 보여주는가 |
+|---|---|
+| `01-injection.txt` | 첫 시도 — `iptables -I FORWARD 1` |
+| `02-injection-verify.txt` | **실패 확인** — kube-router 가 자기 체인을 위로 재삽입, DROP 규칙 **0 패킷** |
+| `03-raw-table-injection.txt` | `raw` 테이블로 이동. 그래도 0 패킷 |
+| `04-correct-direction.txt` | **연결 방향이 반대였다.** 수신측 노드로 옮기니 **19/21 패킷 차단** |
+| `05-reconnect-observed.txt` | **핵심** — 연결이 **열린 방향으로 뒤집혀 재연결**. 뷰 변화 없음, `suspected=0` |
+| `06-view-history-and-cleanup.txt` | 뷰 ID 이력. 주입 이후 변화 없음 확인 |
+| `07-bidirectional-block.txt` | 양방향 차단 → **뷰 14, 멤버 1개씩.** 그런데 `ready=[10.42.1.77]` 로 **한쪽은 남고 외부 200** |
+| `08-coordinator-and-recovery.txt` | **`coord=t` 가 둘**(split brain). keycloak-0 `UP` / keycloak-1 `DOWN`. 해제 후 50초, `MergeView |15] (2)` |
+| `a5-cluster-size-bidirectional-block.png` | Grafana — `vendor_cluster_size` 가 갈라졌다 합쳐지는 구간 |
+
+## 핵심 네 줄
+
+1. **주입을 세 번 실패했다** — CNI 체인 경쟁, 연결 방향 오판, conntrack. 셋 다 "아무 일 없음"으로 보였다.
+2. **단방향 차단으로는 못 가른다.** JGroups 가 열린 방향으로 재연결한다 (자가 치유).
+3. **양방향이면 갈라진다** — `coord=t` 가 둘.
+4. **그래도 전면 장애가 아니다.** 코디네이터 쪽만 UP 을 유지해 서비스가 계속된다 — A-1 의 열린 질문에 대한 답.

docs/evidence/a6-latency-injection/01-baseline.txt

@@ -0,0 +1,22 @@
+=== 배치 — 왜 A/B 가 되는가 ===
+  postgres  10.42.1.76  (kc-lab-2)
+  keycloak-0 10.42.1.77 (kc-lab-2) → DB 와 같은 노드, cni0 로 직행
+  keycloak-1 10.42.0.42 (kc-lab-1) → DB 와 다른 노드, VXLAN 을 건넌다  ← 여기에 지연을 건다
+
+=== 사용 가능한 커넥션 풀 지표 ===
+agroal_acquire_count_total
+agroal_active_count
+agroal_available_count
+agroal_awaiting_count
+agroal_blocking_time_average_milliseconds
+agroal_blocking_time_max_milliseconds
+agroal_blocking_time_total_milliseconds
+agroal_creation_count_total
+agroal_creation_time_average_milliseconds
+agroal_creation_time_max_milliseconds
+agroal_creation_time_total_milliseconds
+agroal_destroy_count_total
+
+=== 기준선 지연 — 각 노드에서 로그인 20회 ===
+  keycloak-0  평균 70 ms
+  keycloak-1  평균 66 ms

docs/evidence/a6-latency-injection/02-delay-injected.txt

@@ -0,0 +1,25 @@
+=== 주입: postgres(10.42.1.76) 가 보내는 패킷만 200ms 지연 (kc-lab-2 eth0) ===
+  prio qdisc 로 밴드를 나누고, u32 필터로 출발지 IP 가 postgres 인 것만 3번 밴드로 보낸다
+Cannot find device "eth0"
+Cannot find device "eth0"
+적용완료
+Cannot find device "eth0"
+Cannot find device "eth0"
+  주입: 13:14:55
+
+=== [검증] 지연이 실제로 걸렸는가 — 두 노드 비교 ===
+  keycloak-0  평균 43 ms   최대 64 ms
+  keycloak-1  평균 47 ms   최대 70 ms
+
+=== 커넥션 풀 상태 ===
+--- keycloak-0 ---
+  agroal_blocking_time_max_milliseconds 102.0
+  agroal_active_count 0.0
+  agroal_awaiting_count 0.0
+  agroal_blocking_time_average_milliseconds 0.0
+  agroal_available_count 2.0
+  agroal_blocking_time_max_milliseconds 164.0
+  agroal_active_count 0.0
+  agroal_awaiting_count 0.0
+  agroal_blocking_time_average_milliseconds 0.0
+  agroal_available_count 2.0

docs/evidence/a6-latency-injection/03-flannel-injection.txt

@@ -0,0 +1,20 @@
+=== 오버레이 인터페이스 확인 ===
+flannel.1        UNKNOWN        a6:b2:62:04:c1:a4 <BROADCAST,MULTICAST,UP,LOWER_UP> 
+cni0             UP             5a:77:1a:e2:b0:a4 <BROADCAST,MULTICAST,UP,LOWER_UP> 
+
+=== flannel.1 에 주입 — 여기서는 파드 IP 가 보인다 (캡슐화 전) ===
+qdisc prio 1: root refcnt 2 bands 3 priomap 1 2 2 2 1 2 0 0 1 1 1 1 1 1 1 1
+ Sent 0 bytes 0 pkt (dropped 0, overlimits 0 requeues 0) 
+ backlog 0b 0p requeues 0
+qdisc netem 30: parent 1:3 limit 1000 delay 200ms
+ Sent 0 bytes 0 pkt (dropped 0, overlimits 0 requeues 0) 
+ backlog 0b 0p requeues 0
+
+=== [검증] 필터에 패킷이 걸리는가 ===
+  qdisc netem 30: parent 1:3 limit 1000 delay 200ms
+   Sent 18388 bytes 150 pkt (dropped 0, overlimits 0 requeues 0) 
+   backlog 0b 0p requeues 0
+
+=== 두 노드 지연 비교 (기준선: k0=70ms k1=66ms) ===
+  keycloak-0  평균 41 ms   최대 57 ms
+  keycloak-1  평균 1872 ms   최대 1887 ms

docs/evidence/a6-latency-injection/04-pool-under-load.txt

@@ -0,0 +1,37 @@
+=== 동시 부하 20건을 keycloak-1 에 — 커넥션 풀이 견디는가 ===
+        1 200 1.911191
+        1 200 1.913766
+        1 200 1.958374
+        1 200 1.981620
+        1 200 10.539402
+        1 200 11.951943
+        1 200 13.351102
+        1 200 14.785832
+        1 200 16.189533
+        1 200 17.625166
+        1 200 19.053724
+        1 200 20.495883
+        1 200 21.905932
+        1 200 22.228466
+        1 200 22.230871
+        1 200 3.441366
+        1 200 4.841075
+        1 200 6.257489
+        1 200 7.704608
+        1 200 9.104792
+
+=== 부하 직후 커넥션 풀 ===
+  agroal_blocking_time_max_milliseconds 20000.0
+  agroal_max_used_count 19.0
+  agroal_acquire_count_total 672.0
+  agroal_active_count 0.0
+  agroal_awaiting_count 0.0
+  agroal_blocking_time_average_milliseconds 281.0
+  agroal_available_count 19.0
+
+=== readiness 가 흔들렸는가 ===
+keycloak-0                  1/1   Running   0             60m
+keycloak-1                  1/1   Running   1 (51m ago)   3h24m
+52m         Normal    TaintManagerEviction   pod/keycloak-1                   Cancelling deletion of Pod keycloak-lab/keycloak-1
+32m         Warning   Unhealthy              pod/keycloak-1                   Readiness probe failed: HTTP probe failed with statuscode: 503
+89s         Warning   Unhealthy              pod/keycloak-1                   Readiness probe failed: Get "http://10.42.0.42:9000/health/ready": context deadline exceeded (Client.Timeout exceeded while awaiting headers)

docs/evidence/a6-latency-injection/05-recovery.txt

@@ -0,0 +1,12 @@
+=== 지연 해제 ===
+해제완료
+qdisc noqueue 0: root refcnt 2 
+
+=== 회복 확인 ===
+  keycloak-0  평균 43 ms
+  keycloak-1  평균 51 ms
+keycloak-0                  1/1   Running   0             61m
+keycloak-1                  1/1   Running   1 (52m ago)   3h24m
+
+=== 낙관적 락 충돌이 늘었는가 — 지연 중 로그 ===
+  관련 로그 줄수: 0

docs/evidence/a6-latency-injection/README.md

@@ -0,0 +1,20 @@
+# A-6 — 지연 주입 증거
+
+2026-09-04 13:10–13:35 KST
+해설: [`docs/experiment-a6-latency-injection.md`](../../experiment-a6-latency-injection.md)
+
+| 파일 | 무엇을 보여주는가 |
+|---|---|
+| `01-baseline.txt` | 배치 설명(A/B 가 되는 이유), `agroal_*` 지표 목록, **기준선 70ms / 66ms** |
+| `02-delay-injected.txt` | 첫 시도 실패 — **`Cannot find device "eth0"`** (Debian 은 `enp1s0`) |
+| `03-flannel-injection.txt` | **성공** — `flannel.1` 에 걸어야 파드 IP 가 보인다. netem `Sent 150 pkt` 로 검증. **k0=41ms vs k1=1872ms** |
+| `04-pool-under-load.txt` | 동시 20건 — 응답이 1.9초에서 **22.2초**까지 계단. `blocking_time_max=20000ms`, `max_used_count=19`, **readiness 프로브 타임아웃** |
+| `05-recovery.txt` | 해제 즉시 43ms / 51ms 회복. **낙관적 락 충돌 0건**(예측 빗나감) |
+| `a6-connection-pool-blocking.png` | Grafana — `agroal_blocking_time_max_milliseconds` |
+
+## 핵심 네 줄
+
+1. **200ms 가 1,872ms 가 된다.** 로그인 트랜잭션의 왕복이 9번이라 지연이 곱해진다.
+2. **동시 부하에서 22초까지 늘어난다.** 커넥션 풀 큐잉으로 한 번 더 곱해진다.
+3. **헬스체크도 같은 줄에 선다** — 프로브가 타임아웃되어 노드가 로드밸런서에서 빠지고, 남은 노드로 부하가 몰린다.
+4. **낙관적 락 충돌은 없었다.** 로그인은 새 행을 만들 뿐 같은 행을 다투지 않는다 — B-3 의 영역.

docs/evidence/a7-volatile-comparison/01-switch-to-volatile.txt

@@ -0,0 +1,18 @@
+=== 비교를 위해 세션을 비운다 ===
+DELETE 151
+
+=== volatile 모드로 전환 ===
+namespace/keycloak-lab unchanged
+secret/keycloak-lab-secrets configured
+persistentvolumeclaim/postgres-data unchanged
+deployment.apps/postgres unchanged
+service/postgres unchanged
+statefulset.apps/keycloak configured
+service/keycloak-headless unchanged
+service/keycloak unchanged
+ingress.networking.k8s.io/keycloak unchanged
+Waiting for 1 pods to be ready...
+partitioned roll out complete: 2 new pods have been updated...
+
+=== [검증] 정말 꺼졌는가 ===
+["start","--features-disabled=persistent-user-sessions"]

docs/evidence/a7-volatile-comparison/02-a0-rerun.txt

@@ -0,0 +1,15 @@
+  keycloak-0=10.42.1.94  keycloak-1=10.42.0.45
+
+=== [A-0 재실행] keycloak-0 에만 로그인 5회 → 캐시가 어디에 담기는가 ===
+로그인완료
+  keycloak-0  sessions 캐시 5.0 건
+  keycloak-1  sessions 캐시 0.0 건
+
+=== DB 에는 들어갔는가 (persistent 였을 때는 5건이 들어갔다) ===
+ offline_flag | count 
+--------------+-------
+(0 rows)
+
+
+=== 교차 노드 세션은 되는가 ===
+  keycloak-0 로그인 → keycloak-1 에서 refresh  HTTP 200

docs/evidence/a7-volatile-comparison/03-a8-rerun-restart.txt

@@ -0,0 +1,13 @@
+=== [A-8 재실행] 재시작 전 로그인 ===
+  sid = aVwYnzKZFFvMqD3bpSeiILuM
+
+=== 롤링 재시작 ===
+statefulset.apps/keycloak restarted
+partitioned roll out complete: 2 new pods have been updated...
+
+=== ★ 재시작 전 토큰이 아직 통하는가 (persistent 였을 때는 200) ===
+  keycloak-0 에서 refresh  HTTP 400
+  --- 오류 본문 ---
+{"error":"invalid_grant","error_description":"Session not active"}
+=== 캐시 상태 ===
+  keycloak-1  sessions 캐시 1.0 건

docs/evidence/a7-volatile-comparison/04-a1-rerun-partition.txt

@@ -0,0 +1,21 @@
+=== [A-1 재실행] volatile 에서 7800 을 막으면 ===
+  keycloak-0=10.42.1.99  keycloak-1=10.42.0.46
+  [대조군] 차단 전 교차 노드 refresh
+    keycloak-1 에서 refresh  HTTP 200
+
+  차단 적용 (A-5 에서 확인한 raw 테이블 방식, 양방향)
+  분단이 성립할 때까지 대기...
+    +25초  cluster_size(k0 k1) = [2.0 2.0 ]
+    +50초  cluster_size(k0 k1) = [1.0 ]
+    +75초  cluster_size(k0 k1) = [1.0 ]
+    +100초  cluster_size(k0 k1) = []
+    +125초  cluster_size(k0 k1) = [1.0 ]
+    +150초  cluster_size(k0 k1) = [1.0 ]
+    +175초  cluster_size(k0 k1) = [1.0 ]
+    +200초  cluster_size(k0 k1) = []
+
+=== ★ 분단 상태에서 교차 노드 세션 (persistent 였을 때는 200) ===
+  keycloak-0 로그인 → keycloak-0 에서 refresh  HTTP 200  ← 대조군
+  keycloak-0 로그인 → keycloak-1 에서 refresh  HTTP 400  ← 시험군
+  --- 시험군 오류 본문 ---
+{"error":"invalid_grant","error_description":"Session not active"}

docs/evidence/a7-volatile-comparison/05-a2-rerun-db-loss.txt

@@ -0,0 +1,12 @@
+차단 해제, 클러스터 재형성 대기...
+
+=== [A-2 재실행] volatile 에서 DB 를 내리면 — 세션이 메모리에 있으니 살아남는가? ===
+  DB 정지 전 로그인 완료
+deployment.apps/postgres scaled
+  postgres 정지
+  ① 캐시를 가진 노드에서 refresh  HTTP 500
+  ② 새 로그인                     HTTP 200
+
+=== DB 복구 후 원복 ===
+deployment.apps/postgres scaled
+deployment "postgres" successfully rolled out

docs/evidence/a7-volatile-comparison/06-restore-persistent.txt

@@ -0,0 +1,12 @@
+=== persistent 모드로 원복 ===
+statefulset.apps/keycloak configured
+partitioned roll out complete: 2 new pods have been updated...
+
+=== [검증] persistent 로 돌아왔는가 — 로그인 후 DB 에 행이 생기는가 ===
+["start"]
+로그인
+  DB 온라인 세션: 1 건  (1 이면 persistent 복귀)
+keycloak-0                  1/1   Running   0     67s
+keycloak-1                  1/1   Running   0     89s
+postgres-7b474b88c8-t6rrf   1/1   Running   0     2m8s
+  외부 진입점 HTTP 200

docs/evidence/a7-volatile-comparison/README.md

@@ -0,0 +1,23 @@
+# A-7 — volatile 모드 비교 증거
+
+2026-09-04 13:45–14:15 KST
+해설: [`docs/experiment-a7-volatile-comparison.md`](../../experiment-a7-volatile-comparison.md)
+
+| 파일 | 무엇을 보여주는가 |
+|---|---|
+| `01-switch-to-volatile.txt` | `--features-disabled=persistent-user-sessions` 적용, args 확인 |
+| `02-a0-rerun.txt` | **DB 0건**인데 교차 노드 refresh `200` — 경로가 DB 에서 클러스터로 바뀌었다 |
+| `03-a8-rerun-restart.txt` | **롤링 재시작 후 `400 Session not active`** — persistent 에서는 `200` 이었다 |
+| `04-a1-rerun-partition.txt` | **7800 차단 시 교차 노드 `400`** — persistent 에서는 `200`. 대조군(같은 노드)은 `200` 유지 |
+| `05-a2-rerun-db-loss.txt` | DB 정지 중 **새 로그인 `200`**(persistent 에서는 500), refresh 는 `500` |
+| `06-restore-persistent.txt` | 원복 확인 — `args: ["start"]`, 로그인 후 DB 1건, 외부 200 |
+
+## 뒤집힌 결과
+
+| 실험 | persistent | volatile |
+|---|---|---|
+| A-1 7800 차단 후 교차 refresh | `200` | **`400`** |
+| A-8 롤링 재시작 후 refresh | `200` | **`400`** |
+| A-2 DB 정지 중 새 로그인 | `500` | **`200`** |
+
+**같은 주입, 같은 관측, 정반대 결과.** A층 전체가 버전 조건부임을 보여주는 대조군이다.

docs/evidence/a8-rolling-restart/01-restart-availability.txt

@@ -0,0 +1,17 @@
+=== [1] 재시작 전 로그인 — 토큰을 파드 안에 보관 ===
+  sid = XLcgQWRiJrTkuNZcJsNeT_2j
+  DB 세션 수: 151
+
+=== [2] 롤링 재시작 중 가용성 — 5초 간격으로 외부 진입점 확인 ===
+statefulset.apps/keycloak restarted
+200 Waiting for partitioned roll out to finish: 0 out of 2 new pods have been updated...
+Waiting for 1 pods to be ready...
+Waiting for 1 pods to be ready...
+Waiting for 1 pods to be ready...
+200 200 200 200 Waiting for partitioned roll out to finish: 1 out of 2 new pods have been updated...
+Waiting for 1 pods to be ready...
+Waiting for 1 pods to be ready...
+Waiting for 1 pods to be ready...
+200 200 200 200 partitioned roll out complete: 2 new pods have been updated...
+
+  (위 숫자열이 재시작 중 외부 응답 코드의 시계열)

docs/evidence/a8-rolling-restart/02-session-survival.txt

@@ -0,0 +1,19 @@
+=== [3] 재시작 전 발급한 refresh token 이 아직 통하는가 ===
+  대상 sid: XLcgQWRiJrTkuNZcJsNeT_2j
+  keycloak-0 에서 refresh  HTTP 200
+
+=== [4] DB 에 그 세션이 남아 있는가 ===
+     user_session_id      | created_on | last_session_refresh 
+--------------------------+------------+----------------------
+ XLcgQWRiJrTkuNZcJsNeT_2j | 1788495513 |           1788495577
+(1 row)
+
+  전체 온라인 세션: 151 (재시작 전 151)
+
+=== [5] 캐시는 어떻게 되었는가 ===
+  keycloak-0  sessions 캐시 0.0 건 / cluster_size 2.0
+  keycloak-1  sessions 캐시 1.0 건 / cluster_size 2.0
+
+=== [6] 파드 나이 — 정말 재시작되었나 ===
+keycloak-0                  1/1   Running   0     44s
+keycloak-1                  1/1   Running   0     66s

docs/evidence/a8-rolling-restart/README.md

@@ -0,0 +1,16 @@
+# A-8 — 롤링 재시작 증거
+
+2026-09-04 13:38–13:41 KST
+해설: [`docs/experiment-a8-rolling-restart.md`](../../experiment-a8-rolling-restart.md)
+
+| 파일 | 무엇을 보여주는가 |
+|---|---|
+| `01-restart-availability.txt` | 재시작 전 로그인(sid 기록), 롤링 재시작 중 외부 진입점 **9회 모두 `200`** |
+| `02-session-survival.txt` | 재시작 전 토큰으로 refresh **`200`**, DB 행 생존(`last_session_refresh` 갱신 확인), **세션 수 151 → 151**, 캐시 0으로 초기화, 파드 나이 44초/66초 |
+| `a8-cache-reset-cluster-reformed.png` | Grafana — 세션 캐시가 0 으로 떨어지고 `cluster_size` 가 다시 2 가 되는 구간 |
+
+## 핵심 세 줄
+
+1. **무중단이었다.** 한 번에 하나씩 내리고 readiness 가 전환을 맞춰준다 — replica ≥ 2 가 전제.
+2. **세션은 살아남고 캐시만 사라진다.** DB 151건 그대로, 재시작 전 토큰이 그대로 통한다.
+3. **이것이 `persistent-user-sessions` 를 켜는 진짜 이유다.** A-7(volatile)에서 정반대가 나와야 한다.

docs/evidence/b0-bff-redis-deploy/01-deploy.txt

@@ -0,0 +1,21 @@
+=== 배포 전 자원 ===
+Mem:           11648        7329         280           4        4377        4319
+NAME       CPU(cores)   CPU(%)   MEMORY(bytes)   MEMORY(%)   
+kc-lab-1   115m         5%       2192Mi          44%         
+kc-lab-2   121m         6%       1324Mi          33%         
+
+=== 배포 ===
+secret/bff-secrets created
+deployment.apps/redis created
+service/redis created
+deployment.apps/bff created
+service/bff created
+ingress.networking.k8s.io/bff created
+
+deployment "redis" successfully rolled out
+Waiting for deployment "bff" rollout to finish: 1 of 2 updated replicas are available...
+deployment "bff" successfully rolled out
+
+bff-574c6d658b-8cz4x        true   kc-lab-1
+bff-574c6d658b-zpkbp        true   kc-lab-2
+redis-568bd7c4-5c5vc        true   kc-lab-2

docs/evidence/b0-bff-redis-deploy/02-autoconfiguration.txt

@@ -0,0 +1,13 @@
+=== B-0: 자동구성이 실제로 고른 구현체 ===
+  Q1 확인한 사실: "코드에 저장소를 직접 생성하는 Bean 이 없기 때문에,
+   어떤 구현체가 실제로 사용되는지는 자동구성 결과까지 확인해야 정확하게 알 수 있다"
+
+  File "<stdin>", line 9
+    print(f"    {name:46} {t.rsplit(\".\",1)[-1]}")
+                                     ^
+SyntaxError: unexpected character after line continuation character
+
+=== HttpSession 은 어디에 있는가 (서블릿 컨테이너 기본) ===
+
+=== 외부 진입점 ===
+  https://app1.hyeonworks.com/  HTTP 200

docs/evidence/b0-bff-redis-deploy/03-beans-analysis.txt

@@ -0,0 +1,29 @@
+=== B-0 — 자동구성이 실제로 고른 구현체 ===
+  컨텍스트: keycloak-bff
+  전체 빈 수: 321
+
+  --- 세션 · 토큰 저장소 관련 ---
+    authorizedClientManager                        -> AuthorizedClientServiceOAuth2AuthorizedClientManager
+    authorizedClientManagerRegistrar               -> OAuth2ClientConfiguration$OAuth2AuthorizedClientManagerRegistrar
+    authorizedClientRepository                     -> AuthenticatedPrincipalOAuth2AuthorizedClientRepository
+    authorizedClientService                        -> InMemoryOAuth2AuthorizedClientService
+    org.springframework.boot.autoconfigure.security.oauth2.client.OAuth2ClientConfigurations$OAuth2AuthorizedClientServiceConfiguration -> OAuth2ClientConfigurations$OAuth2AuthorizedClientServiceConfiguration
+    org.springframework.security.config.annotation.web.configuration.OAuth2ClientConfiguration$OAuth2AuthorizedClientManagerConfiguration -> OAuth2ClientConfiguration$OAuth2AuthorizedClientManagerConfiguration
+
+  --- OAuth2 클라이언트 관련 전체 ---
+    authorizedClientManager                        -> AuthorizedClientServiceOAuth2AuthorizedClientManager
+    authorizedClientManagerRegistrar               -> OAuth2ClientConfiguration$OAuth2AuthorizedClientManagerRegistrar
+    authorizedClientRepository                     -> AuthenticatedPrincipalOAuth2AuthorizedClientRepository
+    authorizedClientService                        -> InMemoryOAuth2AuthorizedClientService
+    clientRegistrationRepository                   -> InMemoryClientRegistrationRepository
+    org.springframework.boot.autoconfigure.security.oauth2.client.OAuth2ClientAutoConfiguration -> OAuth2ClientAutoConfiguration
+    org.springframework.boot.autoconfigure.security.oauth2.client.OAuth2ClientConfigurations$ClientRegistrationRepositoryConfiguration -> OAuth2ClientConfigurations$ClientRegistrationRepositoryConfiguration
+    org.springframework.boot.autoconfigure.security.oauth2.client.OAuth2ClientConfigurations$OAuth2AuthorizedClientServiceConfiguration -> OAuth2ClientConfigurations$OAuth2AuthorizedClientServiceConfiguration
+    org.springframework.boot.autoconfigure.security.oauth2.client.servlet.OAuth2ClientWebSecurityAutoConfiguration -> OAuth2ClientWebSecurityAutoConfiguration
+    org.springframework.security.config.annotation.web.configuration.OAuth2ClientConfiguration -> OAuth2ClientConfiguration
+    org.springframework.security.config.annotation.web.configuration.OAuth2ClientConfiguration$OAuth2AuthorizedClientManagerConfiguration -> OAuth2ClientConfiguration$OAuth2AuthorizedClientManagerConfiguration
+    org.springframework.security.config.annotation.web.configuration.OAuth2ClientConfiguration$OAuth2ClientWebMvcSecurityConfiguration -> OAuth2ClientConfiguration$OAuth2ClientWebMvcSecurityConfiguration
+    spring.security.oauth2.client-org.springframework.boot.autoconfigure.security.oauth2.client.OAuth2ClientProperties -> OAuth2ClientProperties
+
+  --- Redis / Spring Session 이 구성되었는가 ---
+    ★ 없음 — Redis 도 Spring Session 도 구성되지 않았다

docs/evidence/b0-bff-redis-deploy/README.md

@@ -0,0 +1,18 @@
+# B-0 — BFF·Redis 배포와 자동구성 확인 증거
+
+2026-09-04 14:20–14:50 KST
+해설: [`docs/experiment-b0-bff-redis-deploy.md`](../../experiment-b0-bff-redis-deploy.md)
+
+| 파일 | 무엇을 보여주는가 |
+|---|---|
+| `01-deploy.txt` | 배포 전 자원, Redis·BFF 롤아웃, 두 노드에 하나씩 배치됨 |
+| `02-autoconfiguration.txt` | 첫 조회 시도(파싱 실패)와 **외부 진입점 `HTTP 200`** |
+| `03-beans-analysis.txt` | **B-0 의 답** — `InMemoryOAuth2AuthorizedClientService`, `AuthenticatedPrincipalOAuth2AuthorizedClientRepository`, **Redis·Spring Session 없음** |
+| `b0-bff-login-success-single-replica.png` | replica 1 에서 로그인 성공한 BFF 화면 |
+| `b0-bff-token-boundary.png` | `/bff/token-boundary` — `principal: labuser`, `accessTokenStoredOnServer: true`, **`browserTokenCount: 0`** |
+
+## 핵심 세 줄
+
+1. **`AuthenticatedPrincipalOAuth2AuthorizedClientRepository`** — 조회 키가 principal 이고 session ID 가 없다. Q1·Q3 문제의 기제가 이 빈 하나에 있다.
+2. **Redis 를 붙여도 그건 안 고쳐진다.** 저장소 공유와 조회 키는 다른 문제다.
+3. **replica 2개에서는 로그인 자체가 실패한다.** 인가 코드 흐름의 왕복 두 번이 같은 인스턴스로 가야 하는데, 인가 요청이 인스턴스 메모리에 있다.

docs/experiment-a5-asymmetric-partition.md

@@ -0,0 +1,319 @@
+# A-5 — 한쪽 방향만 끊기면 어떻게 되는가 (split brain)
+
+브랜치 `feature/keycloak-a5-asymmetric-partition` ·
+증거 [`docs/evidence/a5-asymmetric-partition/`](evidence/a5-asymmetric-partition/) ·
+2026-09-04 12:28–12:46 KST
+
+선행: [`A-1`](experiment-a1-jgroups-transport-block.md) — 이 실험은 A-1 이
+열어둔 질문에 답한다.
+
+> **A-1 의 열린 질문** — *"양쪽이 동시에 NotReady 가 되는 경로가 있다면
+> 전면 장애다. A-5 에서 이어서 본다."*
+
+---
+
+## 0. 결론부터
+
+| 물음 | 답 |
+|---|---|
+| 비대칭(한 방향) 차단이 클러스터를 가르는가 | **아니다.** 열린 방향으로 재연결한다 |
+| 양방향 완전 차단은 가르는가 | **그렇다.** 양쪽 모두 멤버 1개 |
+| **그때 양쪽이 다 NotReady 가 되는가** | **아니다. 한쪽만 DOWN 이다** |
+| 그래서 서비스는 | **계속된다.** 외부 200 유지 |
+
+**전면 장애 경로는 없었다.** 코디네이터 쪽이 항상 살아남는다.
+
+그리고 주입을 **세 번 실패**했다. 세 번 모두 다른 이유였고, 셋 다
+**"아무 일도 없었다"로 보였다.**
+
+---
+
+## 1. 주입을 세 번 실패했다
+
+A-1 에서 NetworkPolicy 가 conntrack 의 `ESTABLISHED` 승인에 막혀 기존 연결을
+못 끊는다는 것을 배웠다. 그래서 이번에는 iptables 로 갔는데, **또 다른 벽이
+세 개** 있었다.
+
+### 실패 ① — `iptables -I FORWARD 1` 은 최상단에 남지 않는다
+
+```bash
+ssh kc-lab-2 'sudo iptables -I FORWARD 1 -p tcp -d 10.42.1.77 --dport 7800 -j DROP'
+```
+
+```
+num   pkts bytes target
+1      232  377K KUBE-ROUTER-FORWARD  /* kube-router netpol */   ← 다시 1번이 되었다
+2        0     0 DROP  tcp dpt:57800
+3        0     0 DROP  tcp dpt:7800                              ← 0 패킷
+```
+
+**kube-router 가 주기적으로 자기 체인을 최상단에 다시 삽입한다.**
+내가 1번에 넣어도 곧 2번, 3번으로 밀려난다.
+
+> **직접 넣은 iptables 규칙은 CNI 가 관리하는 체인과 경쟁한다.**
+> 넣는 것으로 끝이 아니라 **패킷 카운터로 확인해야 한다.**
+
+### 실패 ② — 그래도 0 패킷: **연결 방향을 잘못 짚었다**
+
+`raw` 테이블로 옮겼는데도 0 패킷이었다.
+
+```bash
+ssh kc-lab-2 'sudo iptables -t raw -I PREROUTING 1 -p tcp -d 10.42.1.77 --dport 7800 -j DROP'
+```
+
+실제 연결을 봤더니
+
+```
+ESTABLISHED src=10.42.1.77 dst=10.42.0.42 sport=60485 dport=7800
+            ────────────            ────────────────────
+            keycloak-0 가 클라이언트   keycloak-1 이 서버
+```
+
+**A-1 때와 방향이 반대였다.** 파드가 재시작되면서 누가 먼저 연결을 걸었는지가
+바뀌었다.
+
+> **JGroups 의 TCP 연결 방향은 고정이 아니다.** 먼저 뜬 쪽, 먼저 JOIN 을 건
+> 쪽에 따라 달라진다. **가정하지 말고 `conntrack -L` 로 봐야 한다.**
+
+### 성공 — `raw` 테이블 PREROUTING, 수신측 노드에
+
+```bash
+ssh kc-lab-1 'sudo iptables -t raw -I PREROUTING 1 -p tcp -d 10.42.0.42 --dport 7800  -j DROP
+              sudo iptables -t raw -I PREROUTING 1 -p tcp -d 10.42.0.42 --dport 57800 -j DROP'
+```
+
+```
+   pkts bytes target
+     19  1096 DROP  tcp dpt:57800
+     21  3058 DROP  tcp dpt:7800     ← 걸린다
+```
+
+### 개념 — netfilter 처리 순서
+
+```
+   패킷 도착
+     │
+     ├─▶ raw     PREROUTING     ← conntrack 보다 먼저. NOTRACK·DROP 용
+     │
+     ├─▶ conntrack 조회/생성    ← 여기서 ESTABLISHED 가 결정된다
+     │
+     ├─▶ mangle  PREROUTING
+     ├─▶ nat     PREROUTING
+     ├─▶ filter  FORWARD        ← NetworkPolicy·kube-router 가 여기 있다
+     └─▶ 목적지 파드
+```
+
+| 어디에 넣는가 | 기존 연결을 끊는가 | CNI 와 경쟁하는가 |
+|---|---|---|
+| NetworkPolicy (filter) | **못 끊는다** — conntrack 이 먼저 통과시킨다 | 없음 |
+| filter FORWARD 직접 | 순서에 따라 | **경쟁한다** (kube-router 가 밀어낸다) |
+| **raw PREROUTING** | **끊는다** | **없다** — CNI 가 안 쓰는 테이블 |
+
+**진짜 네트워크 분단을 흉내내려면 `raw` 테이블이 맞다.**
+
+---
+
+## 2. 비대칭 차단 — 클러스터가 갈라지지 않았다
+
+한 방향(`→ keycloak-1:7800`)만 막고 관찰했다.
+
+```
+  +25초  keycloak-0:1/1 keycloak-1:1/1 | 외부 200
+  +75초  keycloak-0:1/1 keycloak-1:0/1 | 외부 200      ← 잠깐 흔들림
+  +100초 keycloak-0:1/1 keycloak-1:1/1 | 외부 200      ← 회복
+  ...
+  +200초 keycloak-0:1/1 keycloak-1:1/1 | 외부 200
+```
+
+**주입 이후 뷰 변화가 하나도 없었다.**
+
+```bash
+kubectl -n keycloak-lab logs keycloak-0 --since=20m | grep ISPN000094 | awk '$2 >= "03:33:58"'
+# (아무것도 안 나온다)
+```
+
+```
+  뷰 ID 이력:  |13] (2)  ← 주입 전부터 지금까지 그대로
+  suspected  = 0
+```
+
+### 왜 안 갈라졌는가 — **연결 방향이 뒤집혔다**
+
+```
+차단 전:  keycloak-0 → keycloak-1:7800     ← 내가 막은 방향
+차단 후:  keycloak-1 → keycloak-0:7800     ← 열린 방향으로 다시 붙었다
+```
+
+```
+ESTABLISHED src=10.42.0.42 dst=10.42.1.77 sport=48473 dport=7800
+            ────────────            ─────────────
+            keycloak-1 이 클라이언트   keycloak-0 이 서버
+```
+
+**JGroups 는 막힌 연결이 죽자 반대 방향으로 새로 연결했고, 그 사이 FD_SOCK2 가
+상대를 의심하기 전에 복구가 끝났다.** `suspected = 0` 이 그 증거다.
+
+> **한 방향만 막는 것으로는 JGroups 를 가를 수 없다.**
+> 두 노드는 서로에게 연결을 걸 수 있으므로, **한쪽 길이 막히면 다른 길로 간다.**
+>
+> 운영적으로는 좋은 소식이다 — 단방향 방화벽 오설정은 **자가 치유**된다.
+> 반대로 **분단을 재현하려는 실험자에게는 함정**이다.
+
+---
+
+## 3. 양방향 차단 — 갈라졌지만 전면 장애는 아니다
+
+양쪽 노드 모두에 규칙을 넣었다.
+
+```
+  +75초   keycloak-0:1/1 keycloak-1:1/1 | ready=[10.42.0.42 10.42.1.77] 외부 200
+  +100초  keycloak-0:1/1 keycloak-1:0/1 | ready=[10.42.1.77]            외부 200
+  ...
+  +225초  keycloak-0:1/1 keycloak-1:0/1 | ready=[10.42.1.77]            외부 200
+```
+
+```
+=== 뷰 ===
+  keycloak-0  [keycloak-0-24309|14] (1) [keycloak-0-24309]
+  keycloak-1  [keycloak-1-45480|14] (1) [keycloak-1-45480]
+
+=== JGROUPS_PING ===
+ keycloak-0-24309 | 10.42.1.77:7800 | t     ← 코디네이터
+ keycloak-1-45480 | 10.42.0.42:7800 | t     ← 코디네이터
+```
+
+**`coord = t` 가 둘.** 완전한 split brain 이다.
+
+![cluster_size 가 갈라졌다 합쳐진다](evidence/a5-asymmetric-partition/a5-cluster-size-bidirectional-block.png)
+
+### 그런데 **한쪽만 DOWN 이다**
+
+```
+--- keycloak-0 ---
+{"status":"UP",   ... {"name":"Keycloak cluster health check","status":"UP"}
+
+--- keycloak-1 ---
+{"status":"DOWN", ... (cluster health check 가 DOWN)
+```
+
+| | keycloak-0 | keycloak-1 |
+|---|---|---|
+| 분단 전 역할 | **코디네이터** (뷰 13 의 발행자) | 일반 멤버 |
+| 분단 후 자기 인식 | "멤버가 하나 나갔다" — **정상 사건** | "코디네이터를 잃었다" — **비정상** |
+| 헬스체크 | **UP** | **DOWN** |
+| Service 엔드포인트 | **남는다** | 빠진다 |
+
+> **A-1 의 열린 질문에 대한 답 — 양쪽이 동시에 NotReady 가 되는 경로는 없었다.**
+>
+> Keycloak 의 클러스터 헬스체크는 **비대칭**이다. 코디네이터였던 쪽은
+> 자기가 정상이라고 보고, 잃은 쪽만 DOWN 이 된다. 그래서 완전 분단조차
+> **용량 저하로 끝나고 전면 장애가 되지 않는다.**
+>
+> A-2(DB 상실)에서 양쪽이 동시에 DOWN 이 된 것과 대조된다. **DB 는 모두가
+> 의존하는 하나지만, 클러스터 멤버십은 서로 상대적**이기 때문이다.
+
+---
+
+## 4. 복구
+
+```bash
+ssh kc-lab-1 'sudo iptables -t raw -F PREROUTING'
+ssh kc-lab-2 'sudo iptables -t raw -F PREROUTING'
+```
+
+```
+  +25초  keycloak-0:1/1 keycloak-1:0/1
+  +50초  keycloak-0:1/1 keycloak-1:1/1
+  → 복구 완료
+
+MergeView::[keycloak-0-24309|15] (2) [keycloak-0-24309, keycloak-1-45480]
+```
+
+**50초, 사람 개입 없음.** `MergeView` 로 뷰 15 가 발행되며 병합됐다.
+
+각 캐시마다 재분배 로그가 남는다.
+
+```
+[Context=work]            ISPN100007: After merge (or coordinator change) ...
+[Context=clientSessions]  ISPN100007: After merge ...
+[Context=offlineSessions] ISPN100007: After merge ...
+[Context=loginFailures]   ISPN100007: After merge ...
+[Context=actionTokens]    ISPN100007: After merge ...
+```
+
+**`ISPN100007` 은 병합 후 캐시별 토폴로지 재계산**이다. 캐시가 여럿이므로
+로그도 캐시 수만큼 나온다.
+
+---
+
+## 5. 개념
+
+### `MergeView` 와 뷰 ID
+
+```
+[keycloak-0-24309|13] (2)   ← 정상
+[keycloak-0-24309|14] (1)   ← 분단. 양쪽이 각자 14 를 발행
+MergeView::[...|15] (2)     ← 병합. 뷰 ID 는 계속 증가한다
+```
+
+**뷰 ID 는 단조 증가**하므로 "언제 몇 번 갈라졌는지"를 로그만으로 셀 수 있다.
+
+### 코디네이터의 비대칭성
+
+JGroups 코디네이터는 **가장 오래된 멤버**다. 분단이 나면
+
+```
+   코디네이터 쪽:  "멤버가 나갔다"        → 정상 처리, 계속 코디네이터
+   나머지 쪽:      "코디네이터가 사라졌다"  → 새 코디네이터를 자기로 선출
+```
+
+**둘 다 자기가 코디네이터라고 믿는 상태**가 split brain 이고,
+`JGROUPS_PING.coord` 컬럼에 그대로 드러난다.
+
+### 실험자를 위한 규칙
+
+| 상황 | 확인 방법 |
+|---|---|
+| 규칙을 넣었는데 안 걸린다 | `iptables -L -n -v` 의 **패킷 카운터** |
+| 방향을 모르겠다 | `conntrack -L \| grep <포트>` |
+| CNI 가 밀어낸다 | `raw` 테이블을 쓴다 |
+| 갈라졌는지 알고 싶다 | `vendor_cluster_size`, `ISPN000094`, `JGROUPS_PING.coord` |
+
+---
+
+## 6. 재현 절차 (명령어)
+
+```bash
+# 1. 지금 연결이 어느 방향인지 먼저 본다 — 가정하면 실패한다
+ssh kc-lab-1 'sudo conntrack -L | grep 7800'
+
+# 2. 수신측 노드의 raw PREROUTING 에 넣는다 (filter 는 CNI 와 경쟁한다)
+ssh kc-lab-1 'sudo iptables -t raw -I PREROUTING 1 -p tcp -d <수신 파드IP> --dport 7800  -j DROP'
+ssh kc-lab-1 'sudo iptables -t raw -I PREROUTING 1 -p tcp -d <수신 파드IP> --dport 57800 -j DROP'
+
+# 3. 걸렸는지 카운터로 확인 — 0 이면 해석 금지
+ssh kc-lab-1 'sudo iptables -t raw -L PREROUTING -n -v'
+
+# 4. 양방향으로 하려면 반대 노드에도 (한 방향만으로는 자가 치유된다)
+ssh kc-lab-2 'sudo iptables -t raw -I PREROUTING 1 -p tcp -d <반대 파드IP> --dport 7800 -j DROP'
+
+# 5. 분단 확인
+kubectl -n keycloak-lab exec deploy/postgres -- psql -U keycloak -d keycloak \
+  -c "select name, coord from jgroups_ping"          # coord=t 가 둘이면 split brain
+kubectl -n keycloak-lab get endpoints keycloak -o jsonpath='{.subsets[*].addresses[*].ip}'
+
+# 6. 해제
+ssh kc-lab-1 'sudo iptables -t raw -F PREROUTING'
+ssh kc-lab-2 'sudo iptables -t raw -F PREROUTING'
+```
+
+---
+
+## 7. 다음 실험에 남기는 것
+
+| 실험 | 이 실험이 준 것 |
+|---|---|
+| **A-6** 지연 주입 | `tc netem` 도 같은 함정 — **주입이 걸렸는지 먼저 확인** |
+| **A-7** volatile 비교 | 여기서는 분단에도 서비스가 계속됐다. volatile 이면 **세션이 갈라진다** |
+| 운영 | **단방향 방화벽 오설정은 자가 치유된다.** 양방향이어야 사고가 된다 |
+| 운영 | **완전 분단조차 전면 장애가 아니다** — 코디네이터 쪽이 살아남는다 |

docs/experiment-a6-latency-injection.md

@@ -0,0 +1,338 @@
+# A-6 — 끊기지 않고 느려지기만 하면 어떻게 되는가
+
+브랜치 `feature/keycloak-a6-latency-injection` ·
+증거 [`docs/evidence/a6-latency-injection/`](evidence/a6-latency-injection/) ·
+2026-09-04 13:10–13:35 KST
+
+**실제 장애의 대부분은 완전 사망이 아니라 느려짐이다.** 그리고 느려짐은
+사망보다 진단하기 어렵다 — 헬스체크가 통과하기 때문이다.
+
+---
+
+## 0. 결론부터
+
+| 측정 | 값 |
+|---|---|
+| 주입한 네트워크 지연 | **200 ms** |
+| 로그인 응답 시간 | **66 ms → 1,872 ms (28배)** |
+| 동시 20건에서 최대 응답 | **22.2 초** |
+| 커넥션 획득 대기 최대 | **20,000 ms** |
+| readiness 프로브 | **타임아웃으로 실패** |
+
+**200밀리초가 22초가 됐다.** 지연은 **왕복 횟수만큼 곱해지고**, 커넥션 풀에서
+**한 번 더 곱해진다.**
+
+---
+
+## 1. 설계 — 한 실험에서 A/B 가 되는 배치
+
+```
+   kc-lab-2                        kc-lab-1
+   ┌──────────────────┐            ┌──────────────────┐
+   │ postgres         │            │ keycloak-1       │
+   │ keycloak-0       │            │                  │
+   │   └─ cni0 로 직행 │◀─ VXLAN ──▶│   └─ 오버레이 경유 │
+   └──────────────────┘            └──────────────────┘
+        지연 없음                        여기만 느려진다
+```
+
+**postgres 가 보내는 패킷만** 지연시키면 `keycloak-1` 의 DB 접근만 느려지고
+`keycloak-0` 은 그대로다. **대조군이 같은 실험 안에 있다.**
+
+기준선은 거의 같았다.
+
+```
+  keycloak-0  평균 70 ms
+  keycloak-1  평균 66 ms
+```
+
+---
+
+## 2. 주입을 두 번 실패했다
+
+### 실패 ① — `eth0` 이라는 인터페이스가 없다
+
+```bash
+ssh kc-lab-2 'sudo tc qdisc add dev eth0 root handle 1: prio'
+```
+```
+Cannot find device "eth0"
+```
+
+Debian 클라우드 이미지는 **예측 가능한 인터페이스 이름**을 쓴다.
+
+```
+enp1s0    UP    52:54:00:aa:bb:12
+```
+
+`en` (ethernet) + `p1` (PCI bus 1) + `s0` (slot 0). 이름이 하드웨어 위치에서
+나오므로 **NIC 순서가 바뀌어도 이름이 안 바뀐다.**
+
+### 실패 ② — `enp1s0` 에서는 **파드 IP 가 보이지 않는다**
+
+여기가 핵심이다. 노드 간 파드 통신은 **flannel VXLAN 으로 캡슐화**된다.
+
+```
+   원래 패킷:   src=10.42.1.76(postgres)  dst=10.42.0.42(keycloak-1)
+        │
+        ▼  flannel.1 에서 캡슐화
+   실제 패킷:   src=192.168.122.12(노드)   dst=192.168.122.11(노드)  UDP 8472
+                └─ 안쪽에 원래 패킷이 통째로 들어 있다
+        │
+        ▼
+   enp1s0 로 나간다
+```
+
+**`enp1s0` 에서 `match ip src 10.42.1.76` 은 절대 일치하지 않는다.**
+그 IP 는 페이로드 안에 있고, 헤더에는 노드 IP 만 있다.
+
+### 성공 — `flannel.1` 에 건다
+
+```bash
+ssh kc-lab-2 '
+  sudo tc qdisc add dev flannel.1 root handle 1: prio
+  sudo tc qdisc add dev flannel.1 parent 1:3 handle 30: netem delay 200ms
+  sudo tc filter add dev flannel.1 protocol ip parent 1:0 prio 3 \
+       u32 match ip src 10.42.1.76/32 flowid 1:3'
+```
+
+**`flannel.1` 은 캡슐화 직전 단계**이므로 여기서는 파드 IP 가 보인다.
+
+### 검증 — 카운터로 확인한다
+
+```
+qdisc netem 30: parent 1:3 limit 1000 delay 200ms
+ Sent 18388 bytes 150 pkt (dropped 0, overlimits 0 requeues 0)
+                  ───────
+                  실제로 지연 밴드를 통과했다
+```
+
+> **A-1·A-5 와 같은 교훈이 세 번째로 나왔다.**
+> 주입을 넣은 것과 걸린 것은 다르다. **카운터를 봐야 한다.**
+
+### 개념 — `tc` 의 계층 구조
+
+```
+   qdisc (큐 규율)     인터페이스에 붙는 패킷 스케줄러
+     ├─ prio           우선순위 밴드 3개로 나눈다
+     │    ├─ 1:1 (기본)
+     │    ├─ 1:2 (기본)
+     │    └─ 1:3  ← 여기에 netem 을 붙인다
+     └─ filter         어떤 패킷을 어느 밴드로 보낼지
+```
+
+`netem` 을 root 에 바로 붙이면 **모든 트래픽**이 느려진다.
+`prio` + `filter` 를 쓰면 **고른 트래픽만** 느려진다.
+
+---
+
+## 3. 결과 — 지연은 곱해진다
+
+```
+=== 두 노드 지연 비교 (기준선: k0=70ms k1=66ms) ===
+  keycloak-0  평균   41 ms   최대   57 ms      ← 영향 없음
+  keycloak-1  평균 1872 ms   최대 1887 ms      ← 28배
+```
+
+### 왜 200ms 가 1,872ms 가 되는가
+
+A-0 에서 잡은 로그인 트랜잭션의 SQL 이 답이다.
+
+```
+BEGIN
+select ... from OFFLINE_USER_SESSION ...
+select VERSION ... for no key update skip locked
+select ... from OFFLINE_CLIENT_SESSION ...
+select VERSION ... for no key update skip locked
+insert into OFFLINE_USER_SESSION ...
+insert into OFFLINE_CLIENT_SESSION ...
+SET LOCAL synchronous_commit TO OFF
+COMMIT
+```
+
+**왕복이 아홉 번이다.**
+
+```
+   200 ms × 9 왕복 ≈ 1,800 ms      실측 1,872 ms
+```
+
+> **네트워크 지연은 왕복 횟수만큼 증폭된다.**
+> "DB 가 200ms 느려졌다"는 "애플리케이션이 200ms 느려졌다"가 아니다.
+> **쿼리 수를 줄이는 것이 지연 환경에서 결정적인 이유**가 이것이다.
+
+---
+
+## 4. 동시 부하 — 여기서 진짜 고장이 난다
+
+동시 20건을 `keycloak-1` 에 보냈다.
+
+```
+  200  1.911    200  1.913    200  1.958    200  1.981
+  200  3.441    200  4.841    200  6.257    200  7.704
+  200  9.104    200 10.539    200 11.951    200 13.351
+  200 14.785    200 16.189    200 17.625    200 19.053
+  200 20.495    200 21.905    200 22.228    200 22.230
+```
+
+**전부 성공(200)했지만 응답 시간이 1.9초에서 22.2초까지 계단으로 늘어난다.**
+
+```
+   1.9 → 3.4 → 4.8 → 6.2 → 7.7 → 9.1 → 10.5 → ...
+        ────  ────  ────  ────
+        약 1.4초 간격 — 앞 요청이 커넥션을 놓아줄 때까지 줄을 선다
+```
+
+**전형적인 큐잉이다.** 커넥션 수는 유한하고, 각 요청이 커넥션을 1.9초씩
+붙잡고 있으므로 뒤에 온 요청은 그만큼 기다린다.
+
+### 커넥션 풀 지표가 증언한다
+
+```
+  agroal_blocking_time_max_milliseconds   20000.0    ← 20초를 기다린 요청이 있다
+  agroal_blocking_time_average_milliseconds  281.0
+  agroal_max_used_count                      19.0    ← 풀이 19개까지 늘었다
+  agroal_acquire_count_total                672.0
+  agroal_active_count                         0.0    ← 부하가 끝나 지금은 0
+```
+
+![커넥션 획득 대기 시간](evidence/a6-latency-injection/a6-connection-pool-blocking.png)
+
+### 그리고 헬스체크가 무너진다
+
+```
+Warning  Unhealthy  pod/keycloak-1  Readiness probe failed:
+  Get "http://10.42.0.42:9000/health/ready": context deadline exceeded
+```
+
+**readiness 프로브 자체가 타임아웃됐다.**
+
+### 연쇄 고장의 모양
+
+```
+   DB 가 느려진다
+        ↓
+   요청이 커넥션을 오래 붙잡는다
+        ↓
+   커넥션 풀이 고갈된다
+        ↓
+   새 요청이 줄을 선다 (최대 20초)
+        ↓
+   헬스체크도 줄에 선다 → 타임아웃 → NotReady
+        ↓
+   그 노드가 로드밸런서에서 빠진다
+        ↓
+   ★ 남은 노드로 트래픽이 몰린다 → 그 노드도 같은 길을 간다
+```
+
+**마지막 화살표가 무서운 부분이다.** 느려짐은 **전파된다.**
+A-2(DB 완전 정지)는 즉시 503 으로 드러나 오히려 명확했지만,
+**느려짐은 살아 있는 노드를 하나씩 무너뜨린다.**
+
+---
+
+## 5. 빗나간 예측 — 낙관적 락 충돌은 늘지 않았다
+
+계획서에 이렇게 적었다.
+
+> **낙관적 락 충돌 증가** — 트랜잭션이 길어져 `VERSION` 충돌이 늘어야 한다
+
+```
+  관련 로그 줄수: 0
+```
+
+**하나도 없었다.** 이유가 명확하다.
+
+```
+   로그인   →  매번 새 세션 행을 INSERT      →  다툴 상대가 없다
+   refresh  →  같은 세션 행을 UPDATE         →  여기서 다툰다
+```
+
+**충돌은 같은 행을 동시에 고칠 때만 일어난다.** 로그인 부하로는 재현되지
+않는다. 이건 **B-3(refresh 토큰 경쟁)의 영역**이며, 거기서 지연을 함께 주면
+충돌률이 올라갈 것이다.
+
+> 예측을 적어두지 않았다면 "충돌이 없네" 하고 넘어갔을 것이다.
+> **빗나간 예측이 다음 실험의 설계를 정해준다.**
+
+---
+
+## 6. 복구
+
+```bash
+ssh kc-lab-2 'sudo tc qdisc del dev flannel.1 root'
+```
+
+```
+  keycloak-0  평균 43 ms
+  keycloak-1  평균 51 ms      ← 즉시 정상
+```
+
+**파드 재시작 없이 즉시 회복.** 커넥션 풀도 스스로 정상화됐다.
+
+---
+
+## 7. 운영에 주는 것
+
+| 알게 된 것 | 함의 |
+|---|---|
+| 지연은 **왕복 횟수만큼 곱해진다** | DB 지연 대책은 "쿼리 수 줄이기"가 먼저다 |
+| 커넥션 풀에서 **한 번 더 곱해진다** | 풀 크기와 타임아웃이 장애 반경을 정한다 |
+| **헬스체크도 줄에 선다** | 프로브 타임아웃이 풀 대기보다 짧아야 격리가 제때 된다 |
+| 느려짐은 **전파된다** | 노드를 빼면 남은 노드가 더 빨리 무너진다 |
+| `up` 도 readiness 도 **늦게 반응** | **응답 시간 분포(p95/p99)를 봐야 한다** |
+
+### 이 실험대에 없는 알림
+
+지금 관측 스택에는 **지연 분포 지표가 없다.** `agroal_blocking_time_*` 은
+있지만 히스토그램이 아니라 평균/최대뿐이다.
+
+```promql
+# 있으면 좋았을 것
+histogram_quantile(0.99, rate(http_server_requests_seconds_bucket[5m]))
+```
+
+**A-2 에서 `kube-state-metrics` 가 빠진 것을 찾았고, 여기서는 응답 시간
+히스토그램이 빠진 것을 찾았다.** 둘 다 보완 항목이다.
+
+---
+
+## 8. 재현 절차 (명령어)
+
+```bash
+# 1. 인터페이스 이름 확인 — eth0 이 아니다
+ssh kc-lab-2 'ip -brief link show | grep -E "flannel|cni|enp"'
+
+# 2. 오버레이 인터페이스에 건다 (enp1s0 에서는 파드 IP 가 안 보인다)
+ssh kc-lab-2 '
+  sudo tc qdisc add dev flannel.1 root handle 1: prio
+  sudo tc qdisc add dev flannel.1 parent 1:3 handle 30: netem delay 200ms
+  sudo tc filter add dev flannel.1 protocol ip parent 1:0 prio 3 \
+       u32 match ip src <postgres 파드IP>/32 flowid 1:3'
+
+# 3. 걸렸는지 카운터로 확인 — Sent 가 0 이면 해석 금지
+ssh kc-lab-2 'sudo tc -s qdisc show dev flannel.1 | grep -A2 netem'
+
+# 4. 단일 요청 지연 (대조군은 같은 노드의 keycloak-0)
+kubectl -n keycloak-lab run t --rm -i --restart=Never --image=curlimages/curl:8.11.1 \
+  --command -- curl -s -o /dev/null -w '%{time_total}\n' -X POST http://<pod>:8080/realms/master/protocol/openid-connect/token ...
+
+# 5. 동시 부하로 풀 고갈 재현
+#    ( curl ... ) & 를 20개 띄우고 wait
+
+# 6. 풀 지표
+curl -s http://<pod>:9000/metrics | grep -E '^agroal_(blocking_time|max_used|awaiting)'
+
+# 7. 해제
+ssh kc-lab-2 'sudo tc qdisc del dev flannel.1 root'
+```
+
+---
+
+## 9. 다음 실험에 남기는 것
+
+| 실험 | 이 실험이 준 것 |
+|---|---|
+| **B-3** refresh 경쟁 | **지연을 함께 주면 낙관적 락 충돌이 재현될 것** — 여기서는 안 됐다 |
+| **B-1** 저장소 지연 (Q3 제약) | 같은 기법을 Redis 앞에 쓴다 |
+| 관측 보완 | **응답 시간 히스토그램**이 없다 |
+| 구성 | **프로브 타임아웃 < 커넥션 풀 대기**여야 격리가 제때 된다 |

docs/experiment-a7-volatile-comparison.md

@@ -0,0 +1,267 @@
+# A-7 — 옛 방식(volatile)이었다면 무엇이 달라지는가
+
+브랜치 `feature/keycloak-a7-volatile-comparison` ·
+증거 [`docs/evidence/a7-volatile-comparison/`](evidence/a7-volatile-comparison/) ·
+2026-09-04 13:45–14:15 KST
+
+**A층의 결론 전체가 "Keycloak 26 기본값"이라는 전제 위에 있다.**
+전제를 뒤집어 같은 실험을 반복한 것이 이 실험이다.
+
+---
+
+## 0. 결론부터 — 비교표
+
+| 실험 | persistent (KC 26 기본) | **volatile (KC 24 이전 방식)** |
+|---|---|---|
+| **A-0** 세션 저장 위치 | DB 에 행이 생긴다 | **DB 0건.** 메모리에만 |
+| **A-1** 7800 차단 후 교차 노드 refresh | **`200`** — 안 깨진다 | **`400 Session not active`** — 깨진다 |
+| **A-8** 롤링 재시작 후 refresh | **`200`** — 세션 생존 | **`400 Session not active`** — 전원 로그아웃 |
+| **A-2** DB 정지 중 새 로그인 | `500` | **`200`** — 된다 |
+| A-2 DB 정지 중 refresh | `500` | `500` |
+
+**세 개가 정반대로 뒤집혔다.** 예측한 그대로다.
+
+> **"세션 공유는 7800 을 안 탄다"는 A-1 의 결론은 버전에 달린 사실이다.**
+> 인터넷 자료 대부분이 24 이전 기준이므로 **거기서는 통념이 맞다.**
+> 틀린 것은 자료가 아니라 **버전을 확인하지 않고 적용하는 것**이다.
+
+---
+
+## 1. 전환 방법
+
+```bash
+# 이 버전에서 끌 수 있는지부터 확인한다
+kubectl -n keycloak-lab exec keycloak-0 -- /opt/keycloak/bin/kc.sh build --help-all \
+  | tr ',' '\n' | grep -i persistent
+#   persistent-user-sessions[:v1]      ← 목록에 있다
+```
+
+```yaml
+# deploy/lab/k8s/keycloak-cluster.yaml
+args: ["start", "--features-disabled=persistent-user-sessions"]
+```
+
+```bash
+kubectl apply -f deploy/lab/k8s/keycloak-cluster.yaml
+kubectl -n keycloak-lab rollout status statefulset/keycloak --timeout=500s
+```
+
+**빌드 옵션이므로 기동 시 재빌드가 일어나 평소보다 오래 걸린다.**
+
+---
+
+## 2. A-0 재실행 — 세션이 DB 에 안 들어간다
+
+```
+=== keycloak-0 에만 로그인 5회 ===
+  keycloak-0  sessions 캐시 5.0 건
+  keycloak-1  sessions 캐시 0.0 건
+
+=== DB 에는 들어갔는가 (persistent 였을 때는 5건) ===
+ offline_flag | count
+--------------+-------
+(0 rows)                    ← 0 건
+
+=== 교차 노드 세션은 되는가 ===
+  keycloak-0 로그인 → keycloak-1 에서 refresh  HTTP 200
+```
+
+**DB 는 비어 있는데 교차 노드가 된다.** persistent 때와 겉보기 결과가 같지만
+**경로가 완전히 다르다** — 이제는 DB 가 아니라 **클러스터를 타고** 있다.
+
+> 캐시 엔트리 수가 `5 / 0` 인 것은 persistent 때와 같다.
+> `approximate_entries_unique` 는 **그 노드가 소유한 엔트리**만 세므로,
+> 백업본을 들고 있어도 0 으로 보인다. **이 지표만으로는 두 모드를 구분할 수
+> 없다** — 구분하려면 7800 을 끊어봐야 한다. 그게 다음 절이다.
+
+---
+
+## 3. A-1 재실행 — **정반대다**
+
+A-5 에서 확립한 `raw` 테이블 양방향 차단을 그대로 썼다.
+
+```
+  [대조군] 차단 전 교차 노드 refresh   HTTP 200
+
+  차단 적용 → 분단 성립
+    +25초  cluster_size(k0 k1) = [2.0 2.0]
+    +50초  cluster_size(k0 k1) = [1.0 ...]     ← 갈라졌다
+
+=== 분단 상태에서 ===
+  keycloak-0 로그인 → keycloak-0 에서 refresh  HTTP 200  ← 대조군
+  keycloak-0 로그인 → keycloak-1 에서 refresh  HTTP 400  ← 시험군
+  {"error":"invalid_grant","error_description":"Session not active"}
+```
+
+**대조군이 200 인 것이 중요하다.** 차단이 모든 것을 망가뜨린 게 아니라
+**교차 노드만** 끊었다는 증거다.
+
+```
+   persistent :  세션 ── PostgreSQL ──▶ 양쪽이 본다      7800 무관
+   volatile   :  세션 ── 클러스터(7800) ─▶ 상대에게 간다   7800 필수
+```
+
+**같은 주입, 같은 관측, 정반대 결과.** 이 한 쌍이 A층 전체의 근거다.
+
+---
+
+## 4. A-8 재실행 — 배포가 곧 로그아웃
+
+```
+=== 재시작 전 로그인 ===
+  sid = aVwYnzKZFFvMqD3bpSeiILuM
+
+=== 롤링 재시작 ===
+partitioned roll out complete: 2 new pods have been updated...
+
+=== ★ 재시작 전 토큰이 아직 통하는가 (persistent 였을 때는 200) ===
+  keycloak-0 에서 refresh  HTTP 400
+  {"error":"invalid_grant","error_description":"Session not active"}
+```
+
+**배포할 때마다 전원 로그아웃된다.**
+
+| | persistent | volatile |
+|---|---|---|
+| 배포 | 자유롭다 | **모든 사용자가 다시 로그인** |
+| 파드 재시작 (OOM, 노드 교체) | 무해 | **그 노드가 처리하던 세션 소멸** |
+| 무중단 여부 | 무중단 (A-8) | 접속은 되지만 **로그인 상태가 사라진다** |
+
+> **A-8 에서 "이것이 persistent 를 켜는 진짜 이유"라고 썼는데, 여기서 증명된다.**
+> 24 이전 버전을 쓰는 곳에서 "배포하면 로그아웃된다"가 당연하게 여겨졌던 이유다.
+
+---
+
+## 5. A-2 재실행 — 예상 못 한 비대칭
+
+```
+  ① 캐시를 가진 노드에서 refresh   HTTP 500
+  ② 새 로그인                      HTTP 200      ← persistent 에서는 500 이었다
+```
+
+**새 로그인은 되는데 refresh 가 안 된다.** 순서가 거꾸로다.
+
+### 왜 새 로그인이 되는가
+
+```
+   로그인에 필요한 것
+     ├─ realm 설정   → Infinispan `realms` 캐시에 있다
+     ├─ 사용자 자격  → `users` 캐시에 있다
+     └─ 세션 저장    → volatile 이므로 메모리
+   → DB 없이 완결된다
+```
+
+**A-2 에서 persistent 로 했을 때 로그인이 실패한 이유는 "세션을 DB 에 써야
+해서"였다.** 그 쓰기가 없어지니 로그인이 통과한다.
+
+### refresh 가 500 인 이유 — 가설
+
+**측정은 확실하지만 원인은 확정하지 못했다.** 유력한 후보는
+`REVOKED_TOKEN` 테이블이다 — refresh token 회전에서 **이미 쓴 토큰인지**
+확인하려면 그 테이블을 봐야 하고, 그 경로는 캐시되지 않는다.
+
+```
+kubectl -n keycloak-lab exec deploy/postgres -- psql -U keycloak -d keycloak -c "\dt" | grep revoked
+ public | revoked_token | table | keycloak
+```
+
+**확정하려면 A-3 에서 쓴 문장 로깅을 켜고 다시 재현해야 한다.** 여기서는
+**가설로 남긴다.**
+
+> **volatile 이 "DB 없이 돌아간다"는 뜻은 아니다.**
+> realm·사용자·클라이언트·취소 토큰은 **여전히 DB 에 있다.**
+> 세션만 메모리로 옮긴 것이다.
+
+---
+
+## 6. 원복
+
+```bash
+# args 를 되돌린다
+args: ["start"]
+kubectl apply -f deploy/lab/k8s/keycloak-cluster.yaml
+```
+
+```
+=== [검증] persistent 로 돌아왔는가 ===
+["start"]
+  DB 온라인 세션: 1 건  (로그인 1회 후 → persistent 복귀 확인)
+  외부 진입점 HTTP 200
+```
+
+**전환 자체는 설정 한 줄이고 되돌리기도 한 줄이다.** 다만 전환 시점에
+**기존 세션은 전부 사라진다** (저장 위치가 바뀌므로).
+
+---
+
+## 7. 개념
+
+### 두 모드의 데이터 흐름
+
+```
+   persistent (KC 25+, 26 기본)
+      로그인 ──▶ PostgreSQL (진실)  +  로컬 캐시 (사본)
+      조회   ──▶ 캐시에 없으면 DB
+      공유   ──▶ 같은 DB 를 보는 것
+
+   volatile (KC 24 이전)
+      로그인 ──▶ Infinispan (진실)
+      조회   ──▶ 클러스터에서 찾는다
+      공유   ──▶ 7800 을 통한 복제
+```
+
+### 무엇을 맞바꾸는가
+
+| | persistent | volatile |
+|---|---|---|
+| 재시작 내구성 | **있다** | 없다 |
+| 7800 의존 | 낮다 (무효화만) | **높다 (세션 자체)** |
+| DB 부하 | **로그인·refresh 마다 쓰기** | 세션 관련 없음 |
+| 노드 확장 | DB 가 병목 | **복제 트래픽이 N² 로 증가** |
+| 지연 민감도 | **DB 왕복에 민감** (A-6) | 클러스터 왕복에 민감 |
+
+**26 이 기본을 바꾼 이유가 이 표에 있다** — 운영에서 가장 아픈 것이
+"배포하면 로그아웃"이었기 때문이다.
+
+---
+
+## 8. 재현 절차 (명령어)
+
+```bash
+# 1. 끌 수 있는지 확인
+kubectl -n keycloak-lab exec keycloak-0 -- /opt/keycloak/bin/kc.sh build --help-all \
+  | tr ',' '\n' | grep -i persistent
+
+# 2. 세션을 비우고 전환 (비교 기준을 맞추기 위해)
+kubectl -n keycloak-lab exec deploy/postgres -- psql -U keycloak -d keycloak \
+  -c "delete from offline_user_session"
+#   args: ["start", "--features-disabled=persistent-user-sessions"]
+kubectl apply -f deploy/lab/k8s/keycloak-cluster.yaml
+kubectl -n keycloak-lab rollout status statefulset/keycloak --timeout=500s
+
+# 3. volatile 확인 — 로그인 후 DB 가 비어 있어야 한다
+kubectl -n keycloak-lab exec deploy/postgres -- psql -U keycloak -d keycloak \
+  -c "select offline_flag, count(*) from offline_user_session group by offline_flag"
+
+# 4. A-1 / A-8 을 그대로 반복한다 (증거 파일 참조)
+
+# 5. 원복
+#   args: ["start"]
+kubectl apply -f deploy/lab/k8s/keycloak-cluster.yaml
+```
+
+---
+
+## 9. 이 실험이 A층에 남기는 것
+
+| | |
+|---|---|
+| **A-0~A-6 의 결론은 모두 "26 기본값" 조건부다** | 버전이 다르면 답이 다르다 |
+| **A-1 이 통념과 어긋난 이유가 확정됐다** | 통념은 24 이전에서 맞다 |
+| **버전 확인이 1순위** | `kc.sh --version` 을 먼저 본다 |
+| **volatile 이 DB 독립을 뜻하지 않는다** | realm·사용자·취소 토큰은 여전히 DB |
+
+### 미해결로 남긴 것
+
+**volatile 에서 refresh 만 500 이 되는 이유** — `REVOKED_TOKEN` 조회 가설을
+세웠지만 확정하지 못했다. A-3 의 문장 로깅 기법으로 재현하면 답이 나온다.

docs/experiment-a8-rolling-restart.md

@@ -0,0 +1,175 @@
+# A-8 — 배포할 때마다 로그아웃되는가
+
+브랜치 `feature/keycloak-a8-rolling-restart` ·
+증거 [`docs/evidence/a8-rolling-restart/`](evidence/a8-rolling-restart/) ·
+2026-09-04 13:38–13:41 KST
+
+**운영에서 가장 자주 겪는 일이다.** 장애가 아니라 정상 작업인데도
+사용자가 로그아웃되면 그건 사고다.
+
+---
+
+## 0. 결론부터
+
+| 확인 | 결과 |
+|---|---|
+| 재시작 중 서비스 중단 | **없음.** 전 구간 `200` |
+| 재시작 전 발급한 refresh token | **여전히 통한다** (`200`) |
+| DB 세션 수 | **151 → 151** 그대로 |
+| 세션 캐시 | **0 으로 초기화** |
+| 클러스터 | 자동 재형성 (`cluster_size = 2`) |
+
+**세션은 살아남고 캐시만 사라진다.** 이것이 `persistent-user-sessions` 를
+켜는 진짜 이유다.
+
+---
+
+## 1. 방법
+
+```bash
+# 1. 재시작 전 로그인 — 토큰을 상주 파드 안에 보관한다
+kubectl -n keycloak-lab run a8-probe --image=curlimages/curl:8.11.1 \
+  --restart=Never --command -- sleep 3600
+kubectl -n keycloak-lab exec a8-probe -- sh -c '<로그인 후 /tmp/rt, /tmp/sid 에 저장>'
+
+# 2. 재시작하면서 5초 간격으로 외부 진입점을 찍는다
+kubectl -n keycloak-lab rollout restart statefulset/keycloak
+( for i in $(seq 1 48); do
+    curl -s -o /dev/null -w '%{http_code} ' --max-time 4 https://auth.hyeonworks.com/realms/master
+    sleep 5
+  done ) &
+kubectl -n keycloak-lab rollout status statefulset/keycloak --timeout=420s
+```
+
+**탐침 파드가 StatefulSet 밖에 있어야** 재시작을 넘어 토큰을 들고 있을 수 있다.
+
+---
+
+## 2. 가용성 — 무중단이었다
+
+```
+statefulset.apps/keycloak restarted
+200 Waiting for partitioned roll out to finish: 0 out of 2 new pods have been updated...
+    Waiting for 1 pods to be ready...
+200 200 200 200 Waiting for partitioned roll out to finish: 1 out of 2 new pods have been updated...
+    Waiting for 1 pods to be ready...
+200 200 200 200 partitioned roll out complete: 2 new pods have been updated...
+```
+
+**9번 찍어서 9번 다 `200`.** 한 번도 끊기지 않았다.
+
+### 왜 무중단이 되는가
+
+```
+   StatefulSet 롤링 재시작
+     │
+     ├─ keycloak-1 종료 → Service 엔드포인트에서 빠짐
+     │     └─ 이 동안 keycloak-0 이 전부 받는다
+     ├─ keycloak-1 기동 → readiness UP → 엔드포인트 복귀
+     │
+     └─ keycloak-0 종료 → ... (반복)
+```
+
+**한 번에 하나씩** 내리므로 항상 최소 하나는 Ready 다.
+readiness 프로브가 이 전환을 정확히 맞춰준다 — A-2 에서 본 그 메커니즘이
+여기서는 **정상 작업을 안전하게** 만든다.
+
+> 다만 이 실험대는 **파드가 2개**다. replica 1 이면 반드시 끊긴다.
+> 무중단은 공짜가 아니라 **replica ≥ 2 와 readiness 의 조합**이다.
+
+---
+
+## 3. 세션 생존
+
+```
+=== 재시작 전 발급한 refresh token 이 아직 통하는가 ===
+  대상 sid: XLcgQWRiJrTkuNZcJsNeT_2j
+  keycloak-0 에서 refresh  HTTP 200
+
+=== DB 에 그 세션이 남아 있는가 ===
+     user_session_id      | created_on | last_session_refresh
+--------------------------+------------+----------------------
+ XLcgQWRiJrTkuNZcJsNeT_2j | 1788495513 |           1788495577
+
+  전체 온라인 세션: 151 (재시작 전 151)
+```
+
+**`last_session_refresh` 가 `created_on` 보다 64초 뒤**다. 재시작 후의 refresh
+가 **실제로 DB 에 기록**되었다는 뜻이다 — 응답 코드만 200 인 게 아니라
+쓰기까지 정상이다.
+
+**파드가 통째로 바뀌었는데(44초/66초 나이) 세션은 그대로다.**
+
+---
+
+## 4. 캐시는 사라진다
+
+```
+  keycloak-0  sessions 캐시 0.0 건 / cluster_size 2.0
+  keycloak-1  sessions 캐시 1.0 건 / cluster_size 2.0
+```
+
+![캐시 초기화와 클러스터 재형성](evidence/a8-rolling-restart/a8-cache-reset-cluster-reformed.png)
+
+**캐시는 프로세스 메모리이므로 재시작에 사라진다.** `keycloak-1` 의 1건은
+방금 refresh 를 처리하며 새로 담은 것이다.
+
+```
+   재시작 전:  캐시 N건  +  DB 151건
+   재시작 후:  캐시 0건  +  DB 151건      ← 진실은 DB 에 있다
+```
+
+**A-0 의 모델이 그대로 확인된다.** 캐시가 통째로 날아가도 정확성은 유지되고
+**첫 접근만 느려진다** (룩어사이드 캐시의 성질).
+
+---
+
+## 5. 이것이 `persistent-user-sessions` 를 켜는 진짜 이유다
+
+| | persistent (KC 26 기본) | volatile (KC 24 이전 방식) |
+|---|---|---|
+| 롤링 재시작 후 | **세션 유지** | **전원 로그아웃** |
+| 배포 빈도 | 자유롭다 | 배포가 곧 사고다 |
+| 대가 | DB 쓰기 (A-6 에서 본 지연) | 없음 |
+
+**A-7 에서 volatile 로 바꿔 같은 실험을 반복하면 여기가 정반대가 될 것이다.**
+그 비교가 이 실험의 짝이다.
+
+---
+
+## 6. 재현 절차 (명령어)
+
+```bash
+# 상주 탐침 (StatefulSet 밖에 있어야 한다)
+kubectl -n keycloak-lab run a8-probe --image=curlimages/curl:8.11.1 \
+  --restart=Never --command -- sleep 3600
+kubectl -n keycloak-lab wait --for=condition=Ready pod/a8-probe --timeout=120s
+
+# 로그인하고 토큰 보관
+kubectl -n keycloak-lab exec a8-probe -- sh -c \
+  'curl -s -X POST http://<pod>:8080/realms/master/protocol/openid-connect/token \
+     -d grant_type=password -d client_id=admin-cli -d username=admin -d password=<pw> > /tmp/tok'
+
+# 재시작 + 가용성 감시
+kubectl -n keycloak-lab rollout restart statefulset/keycloak
+kubectl -n keycloak-lab rollout status statefulset/keycloak --timeout=420s
+
+# 세션 생존 확인
+kubectl -n keycloak-lab exec a8-probe -- sh -c \
+  'curl -s -o /dev/null -w "%{http_code}\n" -X POST http://<pod>:8080/realms/master/protocol/openid-connect/token \
+     -d grant_type=refresh_token -d client_id=admin-cli -d refresh_token=$(cat /tmp/rt)'
+
+# DB 대조
+kubectl -n keycloak-lab exec deploy/postgres -- psql -U keycloak -d keycloak \
+  -c "select user_session_id, created_on, last_session_refresh from offline_user_session where user_session_id='<sid>'"
+```
+
+---
+
+## 7. 다음 실험에 남기는 것
+
+| 실험 | 이 실험이 준 것 |
+|---|---|
+| **A-7** volatile 비교 | **이 실험을 그대로 반복하면 정반대 결과가 나와야 한다** |
+| **D-2** 버전 업그레이드 | 롤링 재시작이 안전하다는 것이 업그레이드의 전제 |
+| 구성 | 무중단은 **replica ≥ 2 + readiness** 의 조합이다 |

docs/experiment-b0-bff-redis-deploy.md

@@ -0,0 +1,283 @@
+# B-0 — 자동구성은 실제로 무엇을 골랐는가 (그리고 배포에서 겪은 것들)
+
+브랜치 `feature/keycloak-b0-bff-redis-deploy` ·
+증거 [`docs/evidence/b0-bff-redis-deploy/`](evidence/b0-bff-redis-deploy/) ·
+2026-09-04 14:20–14:50 KST
+
+**Q1 이 직접 요구한 확인이다.**
+
+> 코드에 저장소를 직접 생성하는 Bean 이 없기 때문에, 어떤 구현체가 실제로
+> 사용되는지는 **Spring Boot 의 자동구성 결과까지 확인해야** 정확하게 알 수 있다.
+
+---
+
+## 0. 결론부터
+
+```
+authorizedClientService      -> InMemoryOAuth2AuthorizedClientService
+authorizedClientRepository   -> AuthenticatedPrincipalOAuth2AuthorizedClientRepository
+authorizedClientManager      -> AuthorizedClientServiceOAuth2AuthorizedClientManager
+clientRegistrationRepository -> InMemoryClientRegistrationRepository
+
+SessionRepository            -> 없음 (서블릿 컨테이너 in-memory)
+Redis / Spring Session       -> ★ 없음
+```
+
+**추측이 맞았지만, 추측으로 두면 안 되는 이유가 두 번째 줄에 있다.**
+
+`AuthenticatedPrincipalOAuth2AuthorizedClientRepository` — 이름이 곧 설명이다.
+**"인증된 주체(principal) 기준"** 으로 authorized client 를 찾는다.
+**session ID 가 아니다.** Q1·Q3 가 지적한 "같은 사용자의 여러 브라우저가 같은
+token 을 공유한다"는 문제의 **기제가 이 빈 하나에 들어 있다.**
+
+그리고 배포하자마자 **Q1 의 문제가 실험을 시작하기도 전에 나타났다** —
+replica 2개에서는 **로그인 자체가 실패한다.**
+
+---
+
+## 1. 배포에서 겪은 문제 다섯 가지
+
+### 문제 ① — `bff/` 가 소스 없이 빌드 산출물만 있었다
+
+```
+bff/target/classes/...   9개 파일
+bff/src/                 없음
+```
+
+`.gitignore` 에 `target/` 이 없어 클래스 파일만 커밋되어 있었다.
+소스는 다른 브랜치에 있었다.
+
+```bash
+git checkout origin/develop-keycloak-pattern3 -- bff/
+```
+
+### 문제 ② — YAML 중복 키로 빌드가 깨졌다
+
+actuator 를 열려고 `management:` 아래에 `endpoint:` 블록을 **하나 더** 넣었다.
+이미 있는데.
+
+```
+org.yaml.snakeyaml.constructor.SafeConstructor.processDuplicateKeys
+```
+
+**Docker 빌드 로그가 `tail` 로 잘려 원인이 안 보였다.** `--progress=plain` 으로
+전체를 받아서야 스택트레이스에서 `processDuplicateKeys` 를 찾았다.
+
+```bash
+docker build --progress=plain -t keycloak-pattern-bff:lab . > /tmp/build.log 2>&1
+grep -nE "Tests run|Caused by|\.java:[0-9]" /tmp/build.log
+```
+
+> **빌드 실패는 마지막 15줄에 안 들어 있는 경우가 많다.** 전체를 파일로 받는다.
+
+### 문제 ③ — 환경변수에 기본값을 안 줘서 테스트가 죽었다
+
+`${KC_ISSUER_EXTERNAL}` 처럼 기본값 없이 쓰면 **테스트에서 컨텍스트가 안 뜬다.**
+테스트는 그 환경변수를 모른다.
+
+```yaml
+authorization-uri: ${KC_ISSUER_EXTERNAL:http://localhost:8080/realms/keycloak-patterns}/protocol/openid-connect/auth
+```
+
+### 문제 ④ — actuator 가 인증에 막혀 있었다
+
+`/actuator/beans` 를 부르면 `200` 이 왔는데, **Keycloak 로그인 페이지**였다.
+`-L` 로 리다이렉트를 따라간 결과였다.
+
+```java
+"/actuator/health",
+"/actuator/health/**",
+// 실험대 전용 — 운영에서는 절대 열지 않는다
+"/actuator/**"
+```
+
+> **`200` 이 곧 성공은 아니다.** 무엇이 왔는지 봐야 한다.
+
+### 문제 ⑤ — 큰 응답이 프록시에서 `Bad Gateway`
+
+`/actuator/beans` 는 117KB 다. nginx → Traefik 을 거치면서 실패했다.
+
+```
+$ curl https://app1.hyeonworks.com/actuator/beans
+Bad Gateway
+```
+
+파드 안에서 직접 받아 해결했다. **alpine 기반 JRE 이미지에 `wget` 이 있다.**
+
+```bash
+kubectl -n keycloak-lab exec <bff-pod> -- wget -qO- http://localhost:8083/actuator/beans
+```
+
+---
+
+## 2. 배포 구성
+
+```
+   브라우저 ──https──▶ nginx ──▶ Traefik ──▶ bff (2 replica)
+                                              │
+                                              ├──▶ Keycloak  (realm: keycloak-patterns)
+                                              └──▶ echo      (resource server 대역)
+
+   redis  ── kc-lab-2 (postgres 와 같은 노드)  ← 아직 연결하지 않았다
+```
+
+**Redis 는 배포만 하고 BFF 에 연결하지 않았다.** B-0 의 질문이 "아무것도 주지
+않았을 때 자동구성이 무엇을 고르는가"이므로, 아무것도 주지 않은 상태를 먼저
+측정해야 한다.
+
+### Keycloak realm 준비 (kcadm)
+
+```bash
+kubectl -n keycloak-lab exec keycloak-0 -- /opt/keycloak/bin/kcadm.sh config credentials \
+  --server http://localhost:8080 --realm master --user admin --password <pw>
+
+kubectl -n keycloak-lab exec keycloak-0 -- /opt/keycloak/bin/kcadm.sh create realms \
+  -s realm=keycloak-patterns -s enabled=true -s accessTokenLifespan=60
+
+kubectl -n keycloak-lab exec keycloak-0 -- /opt/keycloak/bin/kcadm.sh create clients -r keycloak-patterns \
+  -s clientId=bff-confidential -s publicClient=false -s secret=bff-lab-secret \
+  -s 'redirectUris=["https://app1.hyeonworks.com/*"]'
+```
+
+**`accessTokenLifespan=60`** 으로 둔 것은 B-3(refresh 경쟁)을 위해서다.
+만료를 기다리는 시간이 짧아야 재현이 된다.
+
+### 브라우저용 URL 과 백채널 URL 을 분리했다
+
+```yaml
+authorization-uri: ${KC_ISSUER_EXTERNAL}/protocol/openid-connect/auth   # 브라우저가 간다
+token-uri:         ${KC_ISSUER_INTERNAL}/protocol/openid-connect/token  # BFF 가 서버끼리
+```
+
+```yaml
+- name: KC_ISSUER_EXTERNAL
+  value: https://auth.hyeonworks.com/realms/keycloak-patterns
+- name: KC_ISSUER_INTERNAL
+  value: http://keycloak.keycloak-lab.svc:8080/realms/keycloak-patterns
+```
+
+**2홉 헤더 실험에서 배운 것이 그대로 쓰인다** — 브라우저가 보는 이름과
+서버가 부르는 주소는 다르고, 섞으면 리다이렉트가 깨진다.
+`SERVER_FORWARD_HEADERS_STRATEGY=native` 도 같은 이유다. 없으면 Spring 이
+`redirect_uri` 를 `http://` 로 만들어 Keycloak 이 거부한다.
+
+---
+
+## 3. 동작 확인 — 브라우저 증거
+
+![로그인 성공](evidence/b0-bff-redis-deploy/b0-bff-login-success-single-replica.png)
+
+![token 경계](evidence/b0-bff-redis-deploy/b0-bff-token-boundary.png)
+
+```json
+{"pattern":"AP3-backend-for-frontend","principal":"labuser",
+ "accessTokenStoredOnServer":true,"refreshTokenStoredOnServer":true,
+ "browserTokenCount":0,"csrfProtectionEnabled":true}
+```
+
+**BFF 패턴이 성립한다** — 브라우저에 토큰이 0개이고, 서버가 access/refresh 를
+들고 있다.
+
+---
+
+## 4. B-0 의 답 — 자동구성 결과
+
+전체 빈 321개 중 관련된 것들이다.
+
+| 빈 | 구현체 | 뜻 |
+|---|---|---|
+| `authorizedClientService` | **`InMemoryOAuth2AuthorizedClientService`** | **프로세스 메모리.** 재시작하면 사라진다 |
+| `authorizedClientRepository` | **`AuthenticatedPrincipalOAuth2AuthorizedClientRepository`** | **principal 기준 조회.** session ID 가 없다 |
+| `authorizedClientManager` | `AuthorizedClientServiceOAuth2AuthorizedClientManager` | **service**(공유) 를 쓴다 |
+| `clientRegistrationRepository` | `InMemoryClientRegistrationRepository` | 설정에서 읽은 것 |
+| SessionRepository | **없음** | Tomcat 의 기본 `StandardSession` |
+| Redis / Spring Session | **없음** | 의존성 자체가 없다 |
+
+### `AuthenticatedPrincipalOAuth2AuthorizedClientRepository` 가 핵심이다
+
+```
+   요청이 인증되어 있으면
+     └─▶ OAuth2AuthorizedClientService 에 위임
+            └─▶ 키: (clientRegistrationId, principalName)
+                        └─ session ID 가 없다   ★
+   인증되어 있지 않으면
+     └─▶ HttpSession 에 임시 보관
+```
+
+**같은 사용자가 두 브라우저에서 로그인하면 principalName 이 같으므로
+같은 항목을 본다.** Q1 의 미지수 3 과 Q3 의 제약이 여기서 나온다.
+
+> **Redis 를 붙여도 이건 안 고쳐진다.** 저장소를 공유해도 **키에 session ID 가
+> 없기 때문**이다. Q1 이 "Session Store 를 공유 저장소로 바꾸는 것만으로는
+> 충분하지 않다"고 쓴 이유다.
+
+---
+
+## 5. 예상 못 한 것 — **replica 2개에서 로그인 자체가 안 된다**
+
+배포 직후 브라우저에서 로그인하니 `/login?error` 로 떨어졌다.
+BFF 로그에는 아무 오류도 없었다 (Spring Security 는 로그인 실패를 DEBUG 로만 남긴다).
+
+**가설** — 인가 요청(state, PKCE verifier)은 `HttpSession` 에 저장된다.
+그런데 그 세션은 **인스턴스 메모리**다. 콜백이 다른 replica 로 가면 저장된
+인가 요청이 없어 실패한다.
+
+**검증** — replica 를 1로 줄이고 다시 시도했다.
+
+```bash
+kubectl -n keycloak-lab scale deployment/bff --replicas=1
+```
+
+**로그인이 성공했다.** 가설 확정.
+
+```
+   replica 2 + 스티키 없음 → 로그인 실패 (콜백이 다른 인스턴스로)
+   replica 1              → 로그인 성공
+```
+
+> **Q1 의 문제가 실험을 시작하기도 전에 나타났다.**
+> "다중 인스턴스에서 어떻게 운영할 것인가"는 **로그인한 뒤의 문제가 아니라
+> 로그인 자체의 문제**다. 인가 코드 흐름은 **왕복 두 번**이고, 두 번 다 같은
+> 인스턴스로 가야 한다.
+>
+> 이건 B-2 의 검증 1번("한쪽에서 로그인한 뒤 다른 인스턴스로 요청")보다
+> **앞선 단계**다. 로그인이 끝나야 그 검증을 할 수 있는데, 로그인부터 막힌다.
+
+---
+
+## 6. 재현 절차 (명령어)
+
+```bash
+# 1. 소스 가져오기 (target/ 만 커밋되어 있었다)
+git checkout origin/develop-keycloak-pattern3 -- bff/
+
+# 2. 빌드 — 실패하면 전체 로그를 파일로
+docker build --progress=plain -t keycloak-pattern-bff:lab bff/ > /tmp/build.log 2>&1
+grep -nE "Tests run|Caused by" /tmp/build.log
+
+# 3. 두 노드에 적재 (레지스트리 없음 → imagePullPolicy: Never)
+docker save keycloak-pattern-bff:lab | ssh test-server "ssh kc-lab-1 'sudo k3s ctr images import -'"
+docker save keycloak-pattern-bff:lab | ssh test-server "ssh kc-lab-2 'sudo k3s ctr images import -'"
+
+# 4. realm · client · user
+kubectl -n keycloak-lab exec keycloak-0 -- /opt/keycloak/bin/kcadm.sh create realms -s realm=keycloak-patterns ...
+
+# 5. 배포
+kubectl apply -f deploy/lab/k8s/bff-redis.yaml
+
+# 6. 자동구성 결과 — 파드 안에서 (프록시는 큰 응답에서 502)
+kubectl -n keycloak-lab exec <bff-pod> -- wget -qO- http://localhost:8083/actuator/beans > beans.json
+python3 -c "import json;d=json.load(open('beans.json'));[print(n,'->',i['type']) for n,i in
+  list(d['contexts'].values())[0]['beans'].items() if 'AuthorizedClient' in i['type']]"
+```
+
+---
+
+## 7. 다음 실험에 남기는 것
+
+| 실험 | 이 실험이 준 것 |
+|---|---|
+| **B-1** 저장소 결정 | **전환 후 이 빈들이 바뀌는지 다시 찍는다.** "Redis 붙였다"고 믿는데 자동구성이 안 걸리는 경우가 흔하다 |
+| **B-2** 다중 인스턴스 | **로그인 자체가 실패한다**는 것이 이미 관측됐다. 그것이 검증 0번이다 |
+| **B-3** refresh 경쟁 | `accessTokenLifespan=60` 으로 realm 을 만들어뒀다 |
+| 운영 | actuator `beans`/`env` 는 **내부 구조를 그대로 드러낸다.** 실험대에서만 연다 |