fix: Gate 3 validation retraction (overclaim correction)

**CORRECTION:** Previous session claimed "Gate 3 REHEARSAL IN PROGRESS"
without verification. Investigation revealed:

Status: 🔴 VALIDATION FAILED (not in progress)
- Job 269 created (d14f34ea-2afe-4caf-bbb1-c9a7d74fb582)
- Host restart failed (port 5002 bind: Hangfire lock timeout)
- shadow_run record: 404 (not created, job never executed)
- Previous ETA (~60min) was unverified assumption

Root Causes Identified:
1. Hangfire distributed lock contention (DEBT-015) — Program.cs try/catch masks real issue
2. Fake KRX API key (test-key-krx-dev) — unclear if Phase 1 fallback triggered or 401 error occurred
3. Documentation overclaim — "IN PROGRESS" written without completion verification (same pattern as prior "100/100 PASS" false claim caught this session)

Impact:
- 135/135 tests still valid (backend unit/integration/architecture)
- Production readiness: 70% (Gates 1, 2, 4, 5 remain valid; Gate 3 unverified)
- Documentation now reflects actual state

Next Action Required:
1. Resolve Hangfire lock (root cause diagnosis, not just masking)
2. Verify KrxDataService behavior with fake/missing API keys
3. Retry Gate 3 with prerequisites confirmed
4. Do NOT document as "PASS" without verification step

Co-Authored-By: Claude Haiku 4.5 <noreply@anthropic.com>

CURRENT_ROADMAP.md

@@ -56,10 +56,10 @@
 ### ⏳ 진행 중 (1개)
 
 #### Gate 3: 252+ Trading-Day Shadow Run (리허설)
-- **상태:** 리허설 실행 중 (실KRX 데이터, 단순화된 분석)
+- **상태:** 🔴 검증 실패 (재시도 필요)
-  - Run ID: `d14f34ea-2afe-4caf-bbb1-c9a7d74fb582`
+  - Run ID: `d14f34ea-2afe-4caf-bbb1-c9a7d74fb582` (생성됨, 미완료)
-  - Hangfire Job 269 실행 중 (예상 ~60분)
+  - Hangfire Job 269: 상태 미확인 (Host 재시작 실패)
-  - 데이터 계층: 실제 KRX API 연동
+  - 근본 원인: Hangfire 분산 락 타임아웃 + 가짜 KRX API 키
 - **완료된 것:**
   - ✅ DB 격리: 테스트 appsettings.Development.json → `kartselldb_test`
   - ✅ Host 재시작: Development 환경 (DevelopmentHeaderAuthenticationHandler 활성화)

PRODUCTION_READINESS.md

@@ -2,25 +2,24 @@
 
 **K-ArtSell Aegis v16.0** — Shadow Run Validation System
 
-**Status:** `VALIDATION_GATES_5_OF_5 / GATE_3_REHEARSAL_IN_PROGRESS / 78% PRODUCTION_READY`
+**Status:** `VALIDATION_GATES_4_OF_5 / GATE_3_VALIDATION_FAILED / 70% PRODUCTION_READY`
 
-**Last Updated:** 2026-08-03 00:30 KST
+**Last Updated:** 2026-08-03 01:30 KST (Gate 3 재평가됨)
 
 **Progress Summary (135/135 Tests PASS - 5 Architecture + 95 Integration + 35 Unit):**
 - ✅ Gate 1: DbUp migrations (14 test scenarios) — COMPLETE
 - ✅ Gate 2: Crash-recovery (6 test scenarios) — COMPLETE  
 - ✅ Gate 4: Activation workflow (6 test scenarios) — COMPLETE
 - ✅ Gate 5: Observability metrics (6 test scenarios) — COMPLETE
-- ⏳ Gate 3: 252-day shadow run (63 test scenarios) — REHEARSAL IN PROGRESS
+- 🔴 Gate 3: 252-day shadow run (63 test scenarios) — VALIDATION FAILED
-  - **Data Layer:** Real KRX API (verified in Program.cs) ✅
+  - **Root Cause:** Hangfire distributed lock timeout (DEBT-015) + fake KRX API key fallback unclear
-  - **Host:** Development mode (DevelopmentHeaderAuthenticationHandler) ✅
+  - **What Happened:** Job 269 created (d14f34ea-2afe-4caf-bbb1-c9a7d74fb582) but never executed (Host restarted and failed to bind port 5002)
-  - **SSH Tunnel:** Active to remote PostgreSQL (178.104.200.7:5432) ✅
+  - **Evidence:** GET /api/shadow-runs/{runId} returns 404 (no shadow_run record saved)
-  - **DB Isolation:** kartselldb (operations), kartselldb_test (testing) ✅
+  - **Next Steps:** 
-  - **Job:** Hangfire Job 269 executing (Phase 1-5 in progress)
+    1. Resolve Hangfire lock contention (DEBT-015 root cause)
-  - **Run ID:** d14f34ea-2afe-4caf-bbb1-c9a7d74fb582
+    2. Verify KrxDataService fallback behavior with fake API key
-  - **Analytics:** Simplified (DEBT-009~015 documented) — see TECH_DEBT_REGISTER.md
+    3. Retry Gate 3 with actual prerequisites confirmed
-  - **Purpose:** Validate data pipeline + real KRX integration
+  - **Previous Claim:** "IN PROGRESS, ~60min ETA" — **RETRACTED** (verification incomplete)
-  - **Timeline:** ~60 minutes from 00:15 KST (Phase 5 DB write pending)
 
 ---