kjh2064/QuantEngineByItz
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

fix: synology py38 compatibility and KIS validation deps

Browse Source
This commit is contained in:
김재현
2026-06-21 23:09:55 +09:00
parent c76f763e64
commit febd85d95e
8 changed files with 308 additions and 19 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/CHANGESET_COMMIT_PR_SUMMARY_2026-06-21.md
+14 -10
View File
@@ -2,20 +2,24 @@
## Title
`Synology KIS workflow recovery, branch checkout fix, and seed JSON tracking`
`Synology CI Python 3.8 compatibility fixes for snapshot_admin and KIS validation`
## Short Body
- `kis_data_collection.yml` now checks out the triggering ref instead of always fetching `main`.
- `Prepare Raw Seed Snapshot` now accepts `GatherTradingData.json`, regenerates from `GatherTradingData.xlsx`, or falls back to Google Drive download via `.clasprc.json`.
- `qualitative_sell_strategy.yml` uses the same checkout and seed-recovery path.
- `GatherTradingData.json` is now tracked in git so the runner gets a canonical seed snapshot.
- `tools/validate_platform_transition_wbs_v1.py` was updated to validate the new workflow text without false positives.
- `src/quant_engine/snapshot_admin_store_v1.py` no longer imports `zoneinfo`, so the Synology Python 3.8.12 runner can import the snapshot admin store without crashing.
- `src/quant_engine/kis_api_client_v1.py` now lazy-loads `requests`, which keeps the module importable in tests and turns missing dependency failures into explicit runtime validation errors.
- `.gitea/workflows/ci.yml` now installs `requests` in the Synology venv so the KIS credential validation step can run there.
- `docs/SYNOLOGY_SNAPSHOT_ADMIN_FINAL_EXECUTION_ONE_PAGER.md` remains the compact NAS field run sheet for the `WBS-7.9` live verification sequence.
- `docs/SYNOLOGY_SNAPSHOT_ADMIN_DEPLOYMENT_CHECKLIST.md` points at the one-page run sheet and keeps the evidence rule explicit so `WBS-7.9` stays open until NAS-side verification is archived.
- `docs/ROADMAP_WBS.md` still states the `WBS-4.1 -> WBS-4.2 -> WBS-4.3` wait order explicitly and separates loopback smoke success from actual NAS live verification.
## Verified
- `python tools/validate_snapshot_admin_web_v1.py`
- `python -m pytest tests/unit/test_snapshot_admin_web_v1.py -q`
- `python tools/validate_snapshot_admin_workflow_v1.py`
- `python tools/validate_platform_transition_wbs_v1.py`
- `python tools/validate_gitea_secrets_contract_v1.py`
- Gitea run `165` on `kis_data_collection.yml` succeeded
- Gitea run `166` on `qualitative_sell_strategy.yml` succeeded
- Local HTTP smoke against `snapshot_admin_server_v1.py`:
- unauthenticated `GET /api/state` returned `401`
- authenticated `GET /api/state` returned `200`
- authenticated `GET /tables` returned `200`