Problem
MAPPING in scripts/verify_test_fidelity.py currently covers 8 of 17 packages/chat/src/*.test.ts files. The 9 unmapped files (~229 TS it() cases) are not checked by --strict, so the "0 missing" claim is really "0 missing for mapped core files" (see 0.4.26.2 CHANGELOG wording after PR #72 follow-up commit).
Unmapped files
packages/chat/src/cards.test.ts
packages/chat/src/modals.test.ts
packages/chat/src/message.test.ts
packages/chat/src/message-history.test.ts
packages/chat/src/jsx-runtime.test.ts
packages/chat/src/errors.test.ts
packages/chat/src/emoji.test.ts
packages/chat/src/chat-singleton.test.ts
packages/chat/src/logger.test.ts
Proposed work
- For each unmapped TS file, find the Python counterpart (if any) — e.g.
grep -rln "from chat_sdk.cards" tests/.
- Add a
MAPPING entry for each file with a Python equivalent.
- Run
verify_test_fidelity.py --strict and either (a) port any newly-surfaced gaps, or (b) document an intentional divergence in docs/UPSTREAM_SYNC.md.
- Drop the "for mapped core files" qualifier in
CHANGELOG.md, CLAUDE.md, scripts/fidelity_baseline.json, and docs/UPSTREAM_SYNC.md once MAPPING covers all 17 files.
Why it matters
Strict fidelity is only as meaningful as the mapping that feeds it. Extending to the full core package is the durable fix for the accuracy gap flagged in PR #72.
Related
Problem
MAPPINGinscripts/verify_test_fidelity.pycurrently covers 8 of 17packages/chat/src/*.test.tsfiles. The 9 unmapped files (~229 TSit()cases) are not checked by--strict, so the "0 missing" claim is really "0 missing for mapped core files" (see0.4.26.2CHANGELOG wording after PR #72 follow-up commit).Unmapped files
packages/chat/src/cards.test.tspackages/chat/src/modals.test.tspackages/chat/src/message.test.tspackages/chat/src/message-history.test.tspackages/chat/src/jsx-runtime.test.tspackages/chat/src/errors.test.tspackages/chat/src/emoji.test.tspackages/chat/src/chat-singleton.test.tspackages/chat/src/logger.test.tsProposed work
grep -rln "from chat_sdk.cards" tests/.MAPPINGentry for each file with a Python equivalent.verify_test_fidelity.py --strictand either (a) port any newly-surfaced gaps, or (b) document an intentional divergence indocs/UPSTREAM_SYNC.md.CHANGELOG.md,CLAUDE.md,scripts/fidelity_baseline.json, anddocs/UPSTREAM_SYNC.mdonceMAPPINGcovers all 17 files.Why it matters
Strict fidelity is only as meaningful as the mapping that feeds it. Extending to the full core package is the durable fix for the accuracy gap flagged in PR #72.
Related