Problem
npm test only runs test/scoring.test.ts, test/shared.test.ts, test/wasm-runtime.test.ts, and test/behavioral.test.ts; test/api.integration.test.ts covers the HTTP layer. Nothing under src/indexer/, src/registry/ (reports.ts, review.ts, propagation.ts), src/safetynet/ (claims.ts, tracing.ts, exchange-alerts.ts, oracle.ts), src/verification/kyc/, or src/verification/reserves/ has direct unit tests. That includes the two-person confirmation rule (registry/review.ts) and the claims state machine (safetynet/claims.ts) — both security/financially sensitive logic.
Location
test/ directory vs. src/ module layout
Suggested fix
Prioritize unit tests for registry/review.ts (two-person rule edge cases: self-endorse, self-confirm, same-analyst endorse+confirm, invalid state transitions) and safetynet/claims.ts (state machine transitions) first, since those guard the most consequential logic errors.
Problem
npm testonly runstest/scoring.test.ts,test/shared.test.ts,test/wasm-runtime.test.ts, andtest/behavioral.test.ts;test/api.integration.test.tscovers the HTTP layer. Nothing undersrc/indexer/,src/registry/(reports.ts,review.ts,propagation.ts),src/safetynet/(claims.ts,tracing.ts,exchange-alerts.ts,oracle.ts),src/verification/kyc/, orsrc/verification/reserves/has direct unit tests. That includes the two-person confirmation rule (registry/review.ts) and the claims state machine (safetynet/claims.ts) — both security/financially sensitive logic.Location
test/directory vs.src/module layoutSuggested fix
Prioritize unit tests for
registry/review.ts(two-person rule edge cases: self-endorse, self-confirm, same-analyst endorse+confirm, invalid state transitions) andsafetynet/claims.ts(state machine transitions) first, since those guard the most consequential logic errors.