This snapshots the current repository updates as a coherent release-prep
baseline: workspace/package scaffolding, release automation docs and
workflows, refreshed skill/setup documentation, roadmap expansion, and
the README thumbnail polish.
Constraint: Node packages in this repo must use npm workspaces and Changesets for releases
Constraint: Python release automation stays scaffold-only until a real package exists
Rejected: Split the current work into multiple commits | user asked to commit the current changes together
Confidence: medium
Scope-risk: moderate
Reversibility: clean
Directive: Keep release docs, workflows, and package metadata aligned when adding future packages
Tested: npm run ci
Not-tested: GitHub Actions execution on remote after push
KBO, lotto, and Seoul subway arrival are good v1 complements to train booking because they provide obvious Korean-local utility without requiring a thick integration layer. The subway skill still enforces secret injection because the official Open API key should never be handled as plaintext.
Constraint: v1 should prefer thin wrappers over existing packages and official APIs
Rejected: Add SmartStore or Kakao flows in the first pass | auth and policy surfaces are too heavy for a fast v1
Confidence: medium
Scope-risk: narrow
Reversibility: clean
Directive: Keep live-data skills compact and timestamped so answers do not overclaim freshness
Tested: bash scripts/validate-skills.sh
Not-tested: Live upstream responses from kbo-game, korean-lotto, and Seoul Open Data
