hailin 9cf8b5305b feat(authorization): add community hierarchy API ... - Add internal referral-chain API in referral-service for getting ancestor path and team members - Extend ReferralServiceClient to call referral-chain API - Add findActiveCommunityByAccountSequences repository method - Add getCommunityHierarchy application service method - Add GET /authorizations/my/community-hierarchy endpoint - Update frontend with CommunityHierarchy model and getMyCommunityHierarchy method API returns: - myCommunity: user's own community authorization (if any) - parentCommunity: nearest parent community (defaults to 总部社区 if none) - childCommunities: nearest child communities in user's team 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>		2025-12-10 18:18:49 -08:00
..
app.e2e-spec.ts	refactor(mpc-system): migrate to party-driven architecture with PartyID-based routing	2025-12-05 08:11:28 -08:00
domain-services.integration-spec.ts	feat(authorization): add community hierarchy API	2025-12-10 18:18:49 -08:00
jest-e2e.json	refactor(mpc-system): migrate to party-driven architecture with PartyID-based routing	2025-12-05 08:11:28 -08:00
jest-integration.json	refactor(mpc-system): migrate to party-driven architecture with PartyID-based routing	2025-12-05 08:11:28 -08:00
setup-e2e.ts	refactor(mpc-system): migrate to party-driven architecture with PartyID-based routing	2025-12-05 08:11:28 -08:00
setup-integration.ts	refactor(mpc-system): migrate to party-driven architecture with PartyID-based routing	2025-12-05 08:11:28 -08:00