129 Commits

Author	SHA1	Message	Date
kjh2064	2439d5e24d	docs: record the Temp/ evidence-cache incident in the handoff notes ... Entropy cleanup earlier today deleted all of Temp/, which turned out to include WBS verification evidence (Temp/evidence/*/verdict.json), not just build cache. Documents what broke, what got recovered, and what remains genuinely blocked on missing trading data - so this doesn't get rediscovered from scratch next time. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>	2026-07-30 14:12:42 +09:00
kjh2064	fa0da0b159	docs: add session handoff notes for the 2026-07-30 strategic audit ... Adds docs/SESSION_HANDOFF_2026-07-30.md with what a future session needs that isn't derivable from git log: open threads (release DAG unverified end-to-end, engine_history/quantengine schema collision left as-is, OpenDART/KRX not yet wired into any workflow) and traps hit this session worth not repeating (archive-before-grepping tools/spec/tests, DbUp ordinal sort, runtime/ is tracked history not scratch space, two Pythons on this machine, entropy audit counting local build noise). Pointed to it from CLAUDE.md's Known Issues list. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>	2026-07-30 13:43:32 +09:00
kjh2064	0a2f0eb4a1	fix: un-archive two docs that CI/release-gate validators depend on ... docs/ROADMAP_WBS.md and docs/ROADMAP_ENTERPRISE_TEMPLATES_WBS.md were archived in an earlier commit today as "superseded planning docs," but that judgment only checked CLAUDE.md/README/other docs for references - not the actual validator scripts, spec YAMLs, and unit tests that drive the release gate. Both paths turn out to be load-bearing: - docs/ROADMAP_WBS.md is read directly by tools/validate_quant_engine_wbs_v1.py, tools/validate_platform_transition_wbs_v1.py, tests/unit/test_validate_quant_engine_wbs_v1.py, and referenced by spec/60_quant_engine_wbs.yaml and others. - docs/ROADMAP_ENTERPRISE_TEMPLATES_WBS.md is read by tools/validate_enterprise_crud_specification_v1.py, which runs as the "Enterprise Contract Parity Test" step in .gitea/workflows/ci-frontend.yml. Moved both back to their original path, replaced the stale "ARCHIVED" banner with a note explaining why they can't be archived without first updating the validators, and fixed the 4 doc cross-references that had been repointed at docs/archive/. Verified all three affected validators now exit 0 by actually running them locally. The other 9 docs archived earlier today (5 CI/CD docs + CICD_ROADMAP.md, EXECUTION_PLAN_PHASE0_CLOSEOUT_AND_PHASE1_KICKOFF.md, MODERNIZATION_ROADMAP_VISUAL.md, MODERNIZATION_STRATEGY_ROADMAP_2026-2027.md) were checked against the same grep sweep (*.py/*.yaml/*.yml/*.js/*.ts/*.cs/*.json, whole repo) and have zero references outside markdown - those archivals stand. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>	2026-07-30 12:36:20 +09:00
kjh2064	8dabffc08a	chore: commit pre-existing untracked work + finish archived-doc notes ... Commits work that predated this session and was sitting untracked: qualitative sell strategy module (src/quant_engine), the t20 outcome ledger cron workflow, the QuantEngine masterpiece roadmap doc, a WBS execution yaml, and shared Razor Pages partials (page header, delete confirm modal) with their view models. Verified these build clean (0 errors, 0 warnings) before committing. Also includes the "ARCHIVED" header notes on 6 docs archived in the previous commit - the git-mv landed there, but the note text itself was missed from that commit's staged file list. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>	2026-07-30 12:21:32 +09:00
kjh2064	88e3d58664	docs: archive superseded roadmap/WBS docs, fix broken install command, retire stale files ... Archives 6 more superseded planning docs to docs/archive/ (ROADMAP_WBS.md, MODERNIZATION_ROADMAP_VISUAL.md, MODERNIZATION_STRATEGY_ROADMAP_2026-2027.md, ROADMAP_ENTERPRISE_TEMPLATES_WBS.md, EXECUTION_PLAN_PHASE0_CLOSEOUT_AND_PHASE1_KICKOFF.md, CICD_ROADMAP.md), each replaced by a current source of truth (CLAUDE.md, docs/MIGRATION_STATUS.md, or the OMS·WMS·ERP spec/playbook), and repoints 4 files that linked to the pre-archive path. Fixes README's top-of-file install instructions and package.json's "ops:dev" script, both of which pointed at core_satellite_collector.js - a file that has never existed anywhere in this repo's git history. The real, working entry point (tools/run_kis_data_collection_v1.py / npm run ops:data-collect) was already correctly documented further down the same README. Also finishes retiring pre-existing stale state that predates this session: removes the superseded deploy-prod.yml.backup, completes the already-in-progress removal of the old src/client/ Vue+AG-Grid prototype (superseded by src/frontend/), and untracks test-results/.last-run.json (Playwright's own run-metadata file, regenerated every test run - shouldn't be version controlled). Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>	2026-07-30 11:50:25 +09:00
kjh2064	279d1760ef	fix: migration ordering bug that could block fresh-DB deploys ... V004_normalize_snapshots_schema.sql had an unguarded FK to a table V2 creates. Under DbUp's default ordinal filename sort, the zero-padded "V003_"/"V004_" migrations sorted before "V1__", so on a brand-new database V004 would hard-fail on that FK and abort every migration after it - V1 through V8 would never run. Confirmed via production that neither V003 nor V004 had ever actually applied. Fix: renamed them to V9__/V10__ and added MigrationScriptNameComparer, which sorts DbUp scripts by numeric V{n} value instead of raw string order, so double-digit versions can never again sort ahead of earlier single-digit ones. Added regression tests for both the fixed case and the original bug shape. Also updates docs/db/quantengine.dbml (renamed migrations, and closes out the engine_history/quantengine table-name-collision question - both schemas are live, backing different code paths, not duplicates) and CLAUDE.md (migration ordering fix, KIS/OpenDART/KRX credential env-var-name reference, including a CI secret/env-var name mismatch found for OpenDART that still needs a decision). Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>	2026-07-30 11:36:00 +09:00
kjh2064	70824c2afb	fix: security, data-integrity, and doc-drift findings from repo audit ... Consolidates duplicate KIS API client implementations (governance tests were exercising an unused class instead of the one actually running in production), closes a SQL injection path in the DB admin page, fixes a migration that used MySQL-only syntax and had never actually applied (confirmed against production), resyncs docs/db/quantengine.dbml with all migrations, and removes a duplicate OMS·WMS·ERP frontend tree in favor of src/frontend/. Also corrects several unverifiable/inflated claims in the OMS planning docs and realigns CI/CD and architecture documentation with what's actually in the repo. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>	2026-07-30 11:20:02 +09:00
kjh2064	8104437992	docs(enterprise): synchronize 5 PDF specification guidelines into core specification harness	2026-07-26 15:15:13 +09:00
kjh2064	284cac18f3	feat: complete OMS WMS ERP commercialization with 4-layer input components and 11 standard CRUD templates (Phase 0~11 GA PASS)	2026-07-26 14:51:58 +09:00
kjh2064	1a06e1402d	feat(wbs): consolidate 3 master specifications into WBS-MASTER-2026 and implement TPL-CREATE-01, TPL-DETAIL-01, TPL-CANCEL-01 templates	2026-07-26 01:47:57 +09:00
kjh2064	d286952392	feat(wbs): expand full 52-section component & 11-template WBS roadmap and implement core Sprint 1-2 components	2026-07-26 01:46:55 +09:00
kjh2064	70d9029184	feat(components): implement 4-layer input component architecture and 52-section specification with harness CLI v3.0 verification	2026-07-26 01:43:50 +09:00
kjh2064	1e37e715e9	feat(templates): implement 11 standard CRUD template contracts and WBS roadmap with harness CLI v2.0 verification	2026-07-26 01:36:43 +09:00
kjh2064	827d4f5aba	feat(harness): build automated CLI validator validate_enterprise_crud_specification_v1.py for Enterprise CRUD Specification	2026-07-26 01:30:15 +09:00
kjh2064	c926f63580	docs(governance): adopt Enterprise OMS/WMS/ERP CRUD & Input Component Design Specification into AGENTS.md authority	2026-07-26 01:26:51 +09:00
kjh2064	1c48c45a45	docs: add Phase 0 closeout & Phase 1 kickoff execution plan ... Strategic execution roadmap for 2026-07-24 ~ 2026-09-30 (9 weeks): PART 1: Phase 0 Validation (Jul 24 - Aug 31, 4 weeks) - Task 1.1.1: CI performance baseline (expect 15-20min actual) - Task 1.1.2: CI reproducibility validation (3x same commit → same result) - Task 1.2.1: PostgreSQL audit trail tables (kis_*_audit) - Task 1.2.2: Daily data consistency validation (completeness, freshness, consistency, outliers) - Task 1.3.1: Deployment e2e testing (prepare-release + deploy-prod scenarios) PART 2: Phase 1 Preparation (Sep 1-30, 5 weeks) - Task 2.1.1: 3NF schema design & validation (stocks, quotes, order_book, fundamentals) - Task 2.1.2: Blue-green migration strategy (5-phase parallel run, zero downtime) - Task 2.2.1: Repository ISP refactoring (IQuoteRepository, IRunRepository, IErrorRepository) - Task 2.2.2: Dependency inversion implementation (DI container, Strategy pattern) - Task 2.3.1: Architecture Decision Records (5+ ADRs: normalization, DI, audit, fallback) - Task 2.3.2: Code style guide (C#, Python, SQL, naming conventions) PART 3: Integrated Progress Tracking - Weekly tracking table (11-week timeline) - Risk matrix & mitigation plans - Success criteria for Phase 0 & 1 Key Principles Applied: ✓ SOLID (Single Responsibility, Interface Segregation, Dependency Inversion) ✓ YAGNI (No over-engineering, necessities only) ✓ Data consistency (100% audit trail, reproducibility) ✓ Blue-green deployment (zero downtime, easy rollback) ✓ Pattern standardization (Repository, Strategy, Adapter, Factory) ✓ Code quality (tests, coverage, technical debt reduction) Success criteria by 2026-09-30: - Phase 0 validation: CI 15-20min confirmed, 3x reproducibility pass - Phase 1 ready: Schema designed, migration tested, SOLID refactor designed Co-Authored-By: Claude Haiku 4.5 <noreply@anthropic.com>	2026-07-24 13:49:06 +09:00
kjh2064	852848e69b	docs: add QuantEngine modernization strategy roadmap (2026-2027) ... Add comprehensive modernization roadmap guiding 12-month transformation: MODERNIZATION_STRATEGY_ROADMAP_2026-2027.md (detailed, ~1500 lines): - Phase 0-4 detailed plans (Jul 2026 - Jun 2027) - 5 phases: Foundation, Data Architecture, Quant Engine, Patterns, Optimization - Each phase: specific deliverables, KPIs, risk mitigation - Code examples for normalization, components, game theory, decision logging - Success criteria: CI <15min, coverage >80%, tech debt <20%, Sharpe +20% MODERNIZATION_ROADMAP_VISUAL.md (overview, ~600 lines): - Gantt chart visualization (all 5 phases) - Metrics tracking table (CI time, test coverage, availability, etc.) - Go/No-Go gates with checklists (Phase 0 ✅ approved) - Risk heatmap & ROI analysis - Milestone timeline & governance structure Key improvements target: ✓ Code quality: technical debt 60% → <20% ✓ Performance: API 500ms → <200ms, collection 15min → <6min ✓ Reliability: 99.9% availability, zero data loss ✓ Automation: 10% → 87.5% (manual ops from 40h/week → 5h/week) ✓ Quant: portfolio Sharpe ratio +20%, full decision transparency ✓ SOLID principles, data consistency, game theory, reproducibility Next phase gate: 2026-08-31 (Phase 0 validation) Co-Authored-By: Claude Haiku 4.5 <noreply@anthropic.com>	2026-07-24 13:46:11 +09:00
kjh2064	757f2439af	feat(wbs): WBS M4/M5 C# domain engines & Vue 3 PrimeVue AG-Grid migration [WBS-10]	2026-07-24 11:31:36 +09:00
kjh2064	2fe4cb288f	feat(quant): WBS-FE-BE-100 complete Vue3 Vite8 SPA & .NET10 FastEndpoints refactoring	2026-07-22 15:14:28 +09:00
kjh2064	c2cd643729	feat(dotnet): add domain parity artifact gate	2026-07-13 01:04:13 +09:00
kjh2064	d610ecb57c	feat(dotnet): add read model contract harness	2026-07-13 00:41:30 +09:00
kjh2064	3fbb5ea2bf	feat(dotnet): add domain parity backlog harness	2026-07-13 00:36:41 +09:00
kjh2064	a45961928e	feat(dotnet): add cicd chain contract harness	2026-07-13 00:34:45 +09:00
kjh2064	736951526b	feat(dotnet): add idempotency contract harness	2026-07-13 00:32:48 +09:00
kjh2064	ed137c2574	feat(dotnet): add normalization contract harness	2026-07-13 00:31:13 +09:00
kjh2064	b694a101d1	feat(dotnet): add scheduler contract harness	2026-07-13 00:27:51 +09:00
kjh2064	14ced733f2	feat(dotnet): add provenance contract harness	2026-07-13 00:24:44 +09:00
kjh2064	eb3a33f124	feat(dotnet): add parity contract and wiring	2026-07-13 00:06:48 +09:00
kjh2064	ebbd42e4e0	feat(wbs): add execution plan validator and wiring	2026-07-13 00:01:07 +09:00
kjh2064	445715ded3	docs: add dotnet migration execution plan	2026-07-12 23:59:24 +09:00
kjh2064	e926a7af75	docs: add dotnet migration inventory	2026-07-12 23:55:00 +09:00
kjh2064	b3fb3a9eff	docs: align roadmap section names with wbs ids	2026-07-12 23:52:44 +09:00
kjh2064	5d02bdf5e6	docs: formalize wbs success data schema	2026-07-12 23:47:08 +09:00
kjh2064	5359300f8a	docs: add execution order to dotnet migration roadmap	2026-07-12 23:46:12 +09:00
kjh2064	9dc2323b9a	docs: map dotnet migration wbs to roadmap	2026-07-12 23:44:01 +09:00
kjh2064	91ece33518	docs: add dotnet migration roadmap wbs yaml	2026-07-12 23:42:57 +09:00
kjh2064	5589a0432b	feat(collection): wire KIS collection end-to-end, add price-history pipeline (WBS QE-M0/M1/M2) ... Critical re-review of the QuantEngine WBS evidence system found several regressions of the "no fake gates" discipline established by M0, plus a still-unwired M1 collection path. This closes 10 more WBS tasks (QE-M1-01..06, QE-M2-01/02/04/05/06 — see spec/60_quant_engine_wbs.yaml) with real, gate-verified evidence (18/34 total). M1 — real KIS data now lands in PostgreSQL end-to-end: - SchedulerService: load ticker universe from GatherTradingData.json instead of a hardcoded array; fix a Hangfire scoped-service resolution bug. - KisDataCollectionOrchestrator: restore logging on the lineage-event write path (was a bare `catch {}` swallowing all failures silently); persist daily OHLCV bars into quantengine.price_history_daily per run. - Verified live: POST /api/collection/run -> Hangfire -> orchestrator -> KIS mock API -> PostgreSQL, with Playwright DOM/API parity evidence. M2 — historical price-history pipeline: - CollectionRepository: SavePriceHistoryDailyAsync (idempotent upsert), GetPriceHistorySummaryAsync (per-ticker aggregation) + a new DateOnlyTypeHandler registered globally, since Dapper has no built-in System.DateOnly support in either direction (write threw NotSupportedException, read threw a constructor-mismatch InvalidOperationException — found by exercising both paths live). - tools/validate_price_history_integrity_v1.py: gap-freeness (vs KIS trading calendar) + price-sanity gate over collected history. - Admin Collection page: new "히스토리 현황" summary table + GET /api/collection/history-summary, with Playwright evidence. Governance/gate fixes: - validate_market_time_series_schema_v1.py mislabeled its own output "runtime_database_query": "DATA_GATED" despite never opening a DB connection (pure file/regex check) — relabeled "check_scope": "STATIC_STRUCTURAL_ONLY" and wired the node into the release DAG so it isn't only reachable from ci.yml, matching every other validator. Live-data authority for the same claim stays with QE-M2-01's pg_query gate (spec/60), documented in spec/64. - Fixed a WBS log_pattern check (QE-M1-06) that couldn't match its own multi-line target; loosened two depends_on edges (QE-M1-05/06, QE-M2-04/05) that encoded "needs X verified" when the real requirement was only "needs X's code merged." - Discovered and fixed admin-pages.spec.ts logging in with the wrong seeded password (admin/admin instead of admin/quant123!, per CLAUDE.md) — every test in that suite had been silently failing at the login step. Deferred: QE-M2-03 (2-year backfill) — the KIS mock/VTS token endpoint started returning 403 after the first successful call this session; looks like a token-issuance rate limit or credential issue on KIS's side, not a code defect. Backfilling at scale right now would just generate more 403s, so left QE-M2-03 PENDING pending KIS account/console verification. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>	2026-07-12 21:07:53 +09:00
kjh2064	2a46dd5503	docs(wbs): completely purge and replace all deprecated Blazor and MudBlazor references with Razor Pages and Tabler standards	2026-07-12 14:47:20 +09:00
kjh2064	c56dd7e35d	docs(wbs): correct WBS-10.12 Blazor reference to Razor Pages E2E	2026-07-12 14:44:07 +09:00
kjh2064	d2e9bbf9f0	docs(wbs): register WBS-8.11 and WBS-10.12 strategic pipeline cards	2026-07-12 14:42:39 +09:00
kjh2064	6348550149	docs(wbs): register newly completed optimization tasks under WBS-7 section	2026-07-12 14:38:59 +09:00
kjh2064	d833d386d0	feat: add postgres market time series schema	2026-07-12 12:11:18 +09:00
kjh2064	5d89c6ad02	feat: wire normalized learning store into dotnet	2026-07-12 11:48:32 +09:00
kjh2064	e7d1069222	feat: add quant engine WBS verification harness	2026-07-12 10:58:22 +09:00
kjh2064	f0e8ef9b4f	docs: Harness Gitea Actions debugging methodology ... Document the two-stage debugging pattern discovered while fixing prepare-release.yml (Run #1996-2000): 1. PowerShell harness for workflow_dispatch trigger + poll-to-completion - Working pattern for POST .../dispatches (204 = success) - Known PowerShell/HttpClient limitation: cannot read error response body via GetResponseStream() in PS7 2. SSH log-reading harness for when the Gitea API has no working /logs endpoint (404 on job logs): - Match runner container logs (task ID) to the triggered run - Locate actions_log/{owner}/{repo}/{shard}/{taskId}.log.zst - Stream-decompress with 'zstd -dc' and grep for 'Failure'/'exitcode' 3. Network debugging commands for dispatch 500s / stuck runners (docker network inspect, restart timing, exec connectivity test) 4. Table of real failure patterns hit and their fixes (YAML multiline notes, unset git identity, missing gh CLI in runner image)	2026-07-12 00:20:53 +09:00
kjh2064	e0af3c3d34	docs: Finalize Phase 4-5 CI/CD (Manual SSH deployment strategy, Gitea Actions reference) ... - Add Phase 4: CI/CD Pipeline Hardening status (80% complete) • deploy-prod.yml 4-stage pipeline (223 lines) ✓ • Workflow consolidation (ci.yml + deploy-prod.yml) ✓ • SSH_KEY secret registered ✓ • Note: Act runner network limitation (workaround: manual SSH) ⚠️ - Add Phase 5: Admin UI & Deployment Optimization (complete) • Tabler redesign (dashboard, sidebar, responsive) ✓ • Build: 0 errors, 0 warnings ✓ • E2E tests: 8/8 passing ✓ • Production: commit 30fb702 active since 21:00:55 KST ✓ - Update Deployment & Operations section: • Add complete manual SSH deployment procedure • Add rollback instructions • Document Gitea Actions limitation + workaround • Add health check and monitoring commands • Reference docs/GITEA_ACTIONS_API_GUIDE.md - Add docs/GITEA_ACTIONS_API_GUIDE.md: • Gitea API reference (Run/Job queries) • PowerShell/Bash examples • Troubleshooting guide • FAQ Decision: Option A (Current State Maintained) — Stable manual SSH deployment, infrastructure-limited auto-deployment. Co-Authored-By: Claude Haiku 4.5 <noreply@anthropic.com>	2026-07-11 22:49:29 +09:00
kjh2064	6221d5465f	docs: Add comprehensive deployment troubleshooting guide ... Complete troubleshooting guide for CI/CD deployment issues: - Pre-Deployment verification failures (SSH, artifacts, secrets) - Build artifact extraction errors (tar corruption) - Deployment structure normalization issues - Health check failures (service status, DB connection) - Automatic rollback procedures - Manual deployment management - Emergency recovery procedures - Performance optimization tips - Monitoring and notifications setup - FAQ with common issues and solutions This guide provides step-by-step diagnosis and resolution for all common deployment failure scenarios. Co-Authored-By: Claude Haiku 4.5 <noreply@anthropic.com>	2026-07-11 21:16:32 +09:00
kjh2064	14c9e3b5a5	docs: Phase 5 - CI/CD Monitoring Guide ... Complete CI/CD Pipeline Phases 1-5: Phase 1 (COMPLETE): - SSOT architecture (merge-to-main.yml) - Tier 1-5 gates (Fast → Critical → Integration → Build → Deploy) - Security: Password rotation + Gitea secret Phase 2 (COMPLETE): - Archived build.yml (GitHub Release incompatible) - Reduced duplicate builds on main push Phase 3 (COMPLETE): - CI pipeline to PR-only mode - Prevents duplicate validation on main Phase 4 (COMPLETE): - Deploy workflow to manual-only (workflow_dispatch) - Automatic deploy via merge-to-main.yml Stage 5 Phase 5 (COMPLETE): - Monitoring guide - Failure analysis hierarchy - Performance tracking - Weekly/monthly checklists Expected Outcome: - Success rate: 90% → >95% - Total time: 18-20 minutes (all sequential) - Single source of truth: merge-to-main.yml Co-Authored-By: Claude Haiku 4.5 <noreply@anthropic.com>	2026-07-11 20:40:07 +09:00
kjh2064	a559ed0a98	refactor: CI/CD 파이프라인 재설계 — SSOT + 계층화된 Quality Gates ... **근본적 개선사항**: 1️⃣ **Single Source of Truth (SSOT)** - 빌드은 한 곳에서만 실행 (_common/build-and-test.yml) - 아티팩트 중앙화 (GitHub Actions artifacts) - build.yml과 deploy-prod.yml의 중복 빌드 제거 2️⃣ **계층화된 Quality Gates** - Tier 1: Fast Gates (<2min) - YAML lint, secret scan, JSON validation - Tier 2: Critical Gates (5min) - KIS API governance, DB schema - Tier 3: Integration Gates (15min, 병렬) - 30+ Python validators 3️⃣ **명확한 Workflow 책임** - fast-validation.yml: PR 검증 (2분 내 피드백) - merge-to-main.yml: 전체 파이프라인 (순차 + 의존성) - _common/build-and-test.yml: 공유 빌드 로직 4️⃣ **Observability 강화** - 각 stage별 명확한 성공/실패 표시 - Artifact 추적 가능 - 최종 summary report 생성 **기대 효과**: - 빌드 시간: 3-4분 → 1-2분 (-60%) - 실패율: 90% → <10% - 실패 원인 파악: 30분 → 5분 (-83%) - PR 피드백: 5분 → 2분 (-60%) **다음 작업**: - [ ] 기존 build.yml / deploy-prod.yml 정리 - [ ] Gitea secret 설정 (QUANTENGINE_DB_PASSWORD) - [ ] Validator 병렬화 최적화 - [ ] Notification 채널 구성 **참조**: - docs/CICD_ANALYSIS_AND_ROADMAP.md - 상세 분석 및 로드맵 Co-Authored-By: Claude Haiku 4.5 <noreply@anthropic.com>	2026-07-11 19:05:51 +09:00
kjh2064	3b6cc1fba6	docs: CI/CD 파이프라인 구현 완료 보고서 (최종 정리)	2026-07-11 18:32:58 +09:00