k-skill/docs
Jeffrey (Dongkyu) Kim 448b008522 Clarify the shared delivery output contract in published docs
The approved issue-4 follow-up was already on the branch, so this pass tightened the regression suite first and then made the shared schema explicit in both delivery-tracking docs. The docs now name the normalized keys directly and state that recent_events is capped at the latest three entries, matching the verified CJ and 우체국 examples.

Constraint: Keep the published examples aligned with the verified carrier flows and the existing normalized output contract

Rejected: Broader refactor of the delivery-tracking examples | unnecessary for this follow-up and would widen review scope

Confidence: high

Scope-risk: narrow

Reversibility: clean

Directive: Keep the docs and regression test aligned whenever the normalized tracking schema changes

Tested: node --test scripts/skill-docs.test.js

Tested: npm run ci

Tested: npx --yes skills add . --list

Tested: Live CJ official flow for 1234567890

Tested: Live 우체국 flow for 1234567890123
2026-03-27 01:29:32 +09:00
..
assets Prepare k-skill for packaged releases and broader skill discovery 2026-03-25 23:57:53 +09:00
features Clarify the shared delivery output contract in published docs 2026-03-27 01:29:32 +09:00
install.md Make official parcel tracking available without aggregator services 2026-03-27 00:30:09 +09:00
releasing.md Prepare k-skill for packaged releases and broader skill discovery 2026-03-25 23:57:53 +09:00
roadmap.md Keep parcel-tracking guidance aligned with the verified carrier flows 2026-03-27 00:35:54 +09:00
security-and-secrets.md Prepare k-skill for packaged releases and broader skill discovery 2026-03-25 23:57:53 +09:00
setup.md Clarify the supported setup flow for installed skills 2026-03-26 00:50:23 +09:00
sources.md Keep parcel-tracking guidance aligned with the verified carrier flows 2026-03-27 00:35:54 +09:00