k-skill/scripts/fixtures/delivery-tracking-public-provenance.json
Jeffrey (Dongkyu) Kim 55542d2f0a Keep delivery doc provenance tied to verified smoke tests
The sample payload fixture already pins the published JSON bodies, but the dated provenance lines remained free text. This adds a tiny checked-in provenance fixture and a regression that requires both delivery-tracking docs to keep the verified date/invoice sentence immediately adjacent to each sample JSON block.

Constraint: Keep the docs regression offline and fixture-backed without adding live network calls to CI
Rejected: Inlining the expected date/invoice literals in the test | harder to keep the docs provenance contract explicit and reusable
Confidence: high
Scope-risk: narrow
Reversibility: clean
Directive: Update the provenance fixture whenever the published smoke-test date or invoice examples change
Tested: node --test scripts/skill-docs.test.js; npm run ci; python3 /tmp/cj_verify.py; npx --yes skills add . --list; architect verification
Not-tested: python3 /tmp/epost_verify.py (service.epost.go.kr timed out with curl exit 28 from this environment)
2026-03-27 04:02:14 +09:00

10 lines
161 B
JSON

{
"cj": {
"verified_at": "2026-03-27",
"invoice": "1234567890"
},
"epost": {
"verified_at": "2026-03-27",
"invoice": "1234567890123"
}
}