194 Commits

Author	SHA1	Message	Date
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	fbb35c5296	feat(ci): wire dotnet migration roadmap validator	2026-07-12 23:51:32 +09:00
kjh2064	1a235a171d	fix(ci): paginate upstream ci lookup	2026-07-12 23:36:42 +09:00
kjh2064	d897438675	fix(ci): match upstream ci by release sha	2026-07-12 23:32:57 +09:00
kjh2064	5728a11fbd	fix(ci): compare release chain against short sha	2026-07-12 23:29:02 +09:00
kjh2064	7ff226d622	fix(ci): verify upstream ci before deploy	2026-07-12 23:12:33 +09:00
kjh2064	9df28ecaa2	fix(ci): block release on failed validator chain	2026-07-12 23:04:59 +09:00
kjh2064	2701f7bba5	fix(ci): skip non-ci reproducible wbs tasks	2026-07-12 23:00:35 +09:00
kjh2064	09ad1f64ab	fix(ci): serialize release and deploy chain	2026-07-12 22:58:43 +09:00
kjh2064	3c42eb402b	fix(ci): make workflow lint runner-managed	2026-07-12 22:52:52 +09:00
kjh2064	0f4e589cf1	fix(ci): guard wbs verdict coverage	2026-07-12 22:51:13 +09:00
kjh2064	add83a2a8f	fix(ci): add workflow lint harness	2026-07-12 22:49:03 +09:00
kjh2064	7e0d3ad5b0	fix(ci): avoid postgres host port collision	2026-07-12 22:45:54 +09:00
kjh2064	5bf24d4f66	Revert "fix(ci): harden deploy SSH verification" ... This reverts commit 9c01c60f7c.	2026-07-12 22:42:09 +09:00
kjh2064	9c01c60f7c	fix(ci): harden deploy SSH verification	2026-07-12 22:40:28 +09:00
kjh2064	ea9614be13	feat(qe-m3-05): complete scores frontend DOM verification E2E test and fix Gitea CI migration sequence	2026-07-12 22:17:45 +09:00
kjh2064	f698880aaa	build(harness): integrate TreatWarningsAsErrors into all csproj files and prioritize dotnet tests in CI	2026-07-12 21:57:36 +09:00
kjh2064	b0c9776601	feat(qe-m3-01): implement GetBarsAsOf with lookahead bias prevention and complete unit tests	2026-07-12 21:46:38 +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	24ec410f3d	feat(web): publish version.txt in build pipeline for deterministic live server versioning	2026-07-12 14:05:10 +09:00
kjh2064	c6f269e30a	ci(gitea): serialize pipeline into Validators -> Prepare Release -> Deploy sequence	2026-07-12 13:51:59 +09:00
kjh2064	97447a551f	ci(gitea): trigger deploy-prod workflow automatically after Validators pipeline finishes	2026-07-12 13:51:25 +09:00
kjh2064	f8ff3a2c46	ci: chain release build into production deploy	2026-07-12 12:59:27 +09:00
kjh2064	ecc7deed08	ci: deploy production on main pushes	2026-07-12 12:57:04 +09:00
kjh2064	ee0787683b	ci: package only generated report artifacts	2026-07-12 12:55:42 +09:00
kjh2064	f8d93de299	ci: emit contract-shaped missing-data artifacts	2026-07-12 12:53:28 +09:00
kjh2064	fbb56400af	ci: restore KIS collection credential contract	2026-07-12 12:45:23 +09:00
kjh2064	744e9d6a7a	ci: restore qualitative sell validation workflow	2026-07-12 12:43:19 +09:00
kjh2064	d49e45b308	ci: install dotnet sdk before core tests	2026-07-12 12:36:02 +09:00
kjh2064	15b9840204	ci: regenerate completed WBS verdicts	2026-07-12 12:30:44 +09:00
kjh2064	534582972d	ci: isolate snapshot admin python dependencies	2026-07-12 12:28:59 +09:00
kjh2064	890ed68a0f	fix: restore snapshot admin CI validation	2026-07-12 12:26:55 +09:00
kjh2064	cc001fa263	test: verify market time series schema contract	2026-07-12 12:20:44 +09:00
kjh2064	606664404b	chore: protect external runtime connection settings	2026-07-12 12:19:34 +09:00
kjh2064	a7f9b27a55	fix: require production database connection environment	2026-07-12 12:16:22 +09:00
kjh2064	34991eca2d	ci: enforce schema model evidence generation	2026-07-12 12:13:02 +09:00
kjh2064	c25e3bee7a	ci: install pytest for parallel storage checks	2026-07-12 11:39:31 +09:00
kjh2064	129e2ec2d7	ci: parallelize independent validation jobs	2026-07-12 11:14:58 +09:00
kjh2064	4cd1cab466	ci: export isolated Python dependencies	2026-07-12 11:12:19 +09:00
kjh2064	be043a85e3	ci: remove runner venv dependency	2026-07-12 11:11:55 +09:00
kjh2064	7f0c9b9a27	ci: harden Python environment bootstrap	2026-07-12 11:06:07 +09:00
kjh2064	42d45e85fb	ci: validate main pushes automatically	2026-07-12 11:03:52 +09:00
kjh2064	e7d1069222	feat: add quant engine WBS verification harness	2026-07-12 10:58:22 +09:00
kjh2064	4b29fafcff	fix: Use KST (Asia/Seoul) instead of UTC for release date component ... User caught this directly: it's already 2026-07-12 in Korea, but Run #2008's release was tagged quant_20260711.3.7150737 -- the wrong date. Confirmed: UTC was still 2026-07-11 16:2x when KST was already 2026-07-12 01:2x (9-hour offset). prepare-release.yml computed TODAY via `TZ=UTC date +%Y%m%d`, which is only "correct" if the team operates on UTC -- but this project's production server logs, deployment cadence, and team are all Korea Standard Time. Any release cut between midnight and 9am KST would silently tag itself with yesterday's date. Fixed by using `TZ=Asia/Seoul date +%Y%m%d` instead.	2026-07-12 01:29:14 +09:00
kjh2064	71507374ca	fix: Reset release sequence number to 0 on each new date ... Per spec: the sequence number is a per-day counter that resets on date change and starts at 0, not 1. The first release of a day is quant_YYYYMMDD.0.hash, the second .1, etc. Previous commit fixed *counting* today's releases via the Gitea API (instead of the always-empty local git tags from a shallow checkout), but still added +1 on top, which would have produced 1, 2, 3... for the first, second, third releases of a day instead of 0, 1, 2. DEPLOY_COUNT is now just RELEASES_TODAY directly.	2026-07-12 01:23:56 +09:00