hailin 034fb53674 refactor: use accountSequence as unified user identifier across all services ... - planting-service: extract accountSequence from JWT, pass to referral-service - referral-service: query by accountSequence instead of userId - reward-service: add accountSequence field to schema and all layers - wallet-service: prioritize accountSequence lookup over userId - authorization-service: change userId from String to BigInt, add accountSequence This change ensures consistent cross-service user identification using accountSequence (8-digit unique business ID) instead of internal database IDs. 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>		2025-12-10 13:55:03 -08:00
..
commands	refactor: use accountSequence as unified user identifier across all services	2025-12-10 13:55:03 -08:00
dto	feat(authorization): add community assessment progress to profile page	2025-12-10 06:44:13 -08:00
schedulers	refactor(mpc-system): migrate to party-driven architecture with PartyID-based routing	2025-12-05 08:11:28 -08:00
services	refactor: use accountSequence as unified user identifier across all services	2025-12-10 13:55:03 -08:00