rwadurian

Commit Graph

Author	SHA1	Message	Date
hailin	b3a3652f21	feat(transfer): 树转让功能全量实现（纯新增，零侵入）实现已认种果树所有权在用户间转让的完整功能。采用方案一：独立 transfer-service 微服务 + Saga 编排器模式。 === 架构设计 === - Saga 编排器 8 步正向流程：卖方确认 → 冻结资金 → 锁定树 → 变更所有权 → 调整算力 → 更新统计 → 结算资金 → 完成 - 补偿回滚：任一步骤失败自动反向补偿（解冻资金 → 解锁树） - 13 种状态：PENDING → SELLER_CONFIRMED → PAYMENT_FROZEN → TREES_LOCKED → OWNERSHIP_TRANSFERRED → CONTRIBUTION_ADJUSTED → STATS_UPDATED → PAYMENT_SETTLED → COMPLETED / CANCELLED / FAILED / ROLLING_BACK / ROLLED_BACK === Phase 1-2: transfer-service（独立微服务） === 新建文件： - Prisma Schema：transfer_orders + transfer_status_logs + outbox_events - Domain：TransferOrder 聚合根 + TransferFeeService（5% 手续费） - Application：TransferApplicationService + SagaOrchestratorService - Infrastructure：Kafka 事件消费/生产 + Outbox Pattern - API：TransferController（用户端）+ AdminTransferController（管理端） - External Clients：wallet/planting/identity-service HTTP 客户端 - Docker + 环境配置 === Phase 3: 现有微服务扩展（纯追加） === planting-service： - Prisma schema 追加 transferLockId 可空字段 - InternalTransferController：锁定/解锁/执行 3 个新端点 - Kafka handlers：transfer-lock/execute/rollback 事件处理 - main.ts 追加 Kafka consumer group 配置 referral-service： - PlantingTransferredHandler：处理转让后团队统计更新 - TeamStatisticsAggregate 追加 handleTransfer() 方法 - TeamStatisticsRepository 追加 adjustForTransfer() 方法 - ProvinceCityDistribution 追加 transferTrees() 方法 contribution-service： - TransferOwnershipHandler：处理所有权变更事件 - TransferAdjustmentService：算力调整（879 行核心逻辑） - Prisma schema 追加 transferOrderId 可空字段 - ContributionAccount 追加 applyTransferAdjustment() 方法 === Phase 4A: wallet-service（3 个新内部端点） === 新建文件： - FreezeForTransferDto / UnfreezeForTransferDto / SettleTransferDto - FreezeForTransferCommand / UnfreezeForTransferCommand / SettleTransferPaymentCommand - InternalTransferWalletController（POST freeze/unfreeze/settle-transfer）修改文件： - wallet-application.service.ts 追加 3 组方法（+437 行）： freezeForTransfer / unfreezeForTransfer / settleTransferPayment （乐观锁 + 3 次重试 + Prisma $transaction + 幂等检查） - 结算操作：单事务内更新 3 个钱包（买方扣减 + 卖方入账 + 手续费归集） === Phase 4B: admin-web（转让管理页面） === 新建文件： - transferService.ts：API 调用服务 + 完整类型定义 - useTransfers.ts：React Query hooks（list/detail/stats/forceCancel） - /transfers/page.tsx：列表页（统计卡片 + 搜索筛选 + 分页 + 13 种状态 badge） - /transfers/[transferOrderNo]/page.tsx：详情页（Saga 时间线 + 状态日志 + 强制取消） - transfers.module.scss：完整样式修改文件： - endpoints.ts 追加 TRANSFERS 端点配置 - Sidebar.tsx 追加「转让管理」菜单项 - hooks/index.ts 追加 useTransfers 导出 === Phase 4C: mobile-app（转让 UI） === 新建文件： - transfer_service.dart：Flutter API 服务 + Model（TransferOrder/Detail/StatusLog） - transfer_list_page.dart：转让记录列表（全部/转出/转入 Tab + 下拉刷新） - transfer_detail_page.dart：转让详情（Saga 时间线 + 确认/取消操作） - transfer_initiate_page.dart：发起转让表单（手续费自动计算）修改文件： - injection_container.dart 追加 transferServiceProvider - route_paths.dart + route_names.dart 追加 3 个路由 - app_router.dart 追加 3 个 GoRoute - profile_page.dart 追加「发起转让」+「转让记录」按钮行 === 基础设施 === - docker-compose.yml 追加 transfer-service 容器配置 - deploy.sh 追加 transfer-service 部署 - init-databases.sh 追加 transfer_db 数据库初始化 === 纯新增原则 === 所有变更均为追加式修改，不修改任何现有业务逻辑： - 新增 nullable 字段（不影响现有数据） - 新增 enum 值（不影响现有枚举使用） - 新增 providers/controllers（不影响现有依赖注入） - 新增页面/路由（不影响现有页面行为）回滚方式：删除 transfer-service 目录 + 移除各服务中带 [2026-02-19] 标记的代码 Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>	2026-02-19 03:44:02 -08:00
hailin	ed1f863919	fix(authorization): 修复团队升级竞态条件，改用事件链模式问题：authorization-service 和 referral-service 并行消费 TreePlanted 事件，导致升级检查时统计数据尚未更新完成。解决方案： - referral-service: 批量更新团队统计后发布 TeamStatisticsUpdatedEvent - authorization-service: 监听该事件触发升级检查，替代原有的即时检查 - TeamStatistics 聚合添加 accountSequence 字段用于事件发布 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>	2025-12-24 00:13:39 -08:00
hailin	747e4ae8ef	refactor(mpc-system): migrate to party-driven architecture with PartyID-based routing - Remove Address field from PartyEndpoint (parties connect to router themselves) - Update K8s Discovery to only manage PartyID and Role labels - Add Party registration and SessionEvent protobuf definitions - Implement PartyRegistry and SessionEventBroadcaster domain logic - Add RegisterParty and SubscribeSessionEvents gRPC handlers - Prepare infrastructure for party-driven MPC coordination This is the first phase of migrating from coordinator-driven to party-driven architecture following international MPC system design patterns.	2025-12-05 08:11:28 -08:00
Developer	7ae98c7f5b	feat(referral-service): Implement complete referral service with DDD architecture Implement the referral service microservice with comprehensive features: ## Domain Layer - ReferralRelationship aggregate: manages user referral relationships - TeamStatistics aggregate: tracks team statistics and leaderboard scores - Value Objects: UserId, ReferralCode, ReferralChain, LeaderboardScore, ProvinceCityDistribution - Domain Services: ReferralChainService, LeaderboardCalculationService - Domain Events: ReferralRelationshipCreated, TeamStatisticsUpdated ## Application Layer - ReferralService: create relationships, get user info, validate codes - TeamStatisticsService: update statistics, get leaderboard, province/city distribution - Commands: CreateReferralRelationship, UpdateTeamStatistics - Queries: GetUserReferralInfo, GetDirectReferrals, GetLeaderboard, GetProvinceCityDistribution - Event Handlers: UserRegisteredHandler, PlantingCreatedHandler ## Infrastructure Layer - Prisma repositories with PostgreSQL - Redis caching for leaderboard - Kafka messaging for domain events - JWT authentication guard ## API Layer - REST endpoints for referral management - Leaderboard endpoints with pagination - Team statistics endpoints - Health check endpoints ## Testing (127 unit + 35 integration + 16 E2E tests) - Domain layer unit tests (100% coverage) - Integration tests with mocks - E2E tests with supertest - Docker test environment with PostgreSQL, Redis, Redpanda 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <noreply@anthropic.com>	2025-12-01 00:18:20 -08:00

4 Commits