Jeffrey (Dongkyu) Kim e257ab39a0 Avoid leaking CJ contact details in published tracking examples ... The first delivery-tracking draft exposed too much of the raw CJ event payload in the public examples. This follow-up keeps the examples useful for status checks while normalizing them to non-PII fields only, and locks that expectation in the docs regression suite so the raw field is not reintroduced. Constraint: Must preserve the verified official CJ flow while removing avoidable personal-contact leakage from the shipped examples Constraint: Follow-up had to stay docs-first and scoped to the existing feature/#4 PR branch Rejected: Keep raw CJ payload output and rely on users to ignore | published examples should not leak names/phone numbers unnecessarily Rejected: Drop CJ example detail entirely | loses practical verification value for the main carrier path Confidence: high Scope-risk: narrow Reversibility: clean Directive: Any future CJ example update must continue to avoid printing raw or other contact-bearing fields in public docs Tested: node --test scripts/skill-docs.test.js Tested: npm run ci Tested: python3 normalized CJ official endpoint verification for 1234567890 Tested: python3 우체국 follow-up verification for 1234567890123 Not-tested: Real non-placeholder customer waybills with different event shapes		2026-03-27 00:48:02 +09:00
..
SKILL.md	Avoid leaking CJ contact details in published tracking examples	2026-03-27 00:48:02 +09:00