docs: start wallet transaction extraction

2026-08-30 19:23:43 +03:30
parent 44cf2f131e
commit 7f58c31d6b
2 changed files with 8 additions and 1 deletions
@@ -405,3 +405,9 @@ Migration order implied by the map: isolate shared infrastructure constructors (
 - Auth has no active federation implementation; its wallet federation client is commented/dead code. Auth’s identity service should remain the owner of identity and national-ID data.
 - The proposed target is reasonable only after consumers are migrated: `user_id → identity_id → wallet_id`, with `wallet_id` still scoped to `asset_id` and Stellar key derivation/custody explicitly preserved. W013 must first identify whether federation addresses or transaction routing are actually supported in production, then remove or retain the model based on evidence and a data/API compatibility plan.
 - Per the requested migration, federation is fully removed from active Wallet/Auth/API code and the shared wallet protobuf: no federation creation/lookup, persistence adapter/model, wallet field, transaction field/filter, generated message, stale API route, or runtime reference remains. New wallet creation uses user/asset identity; wallet records remain asset-scoped. Wallet/Auth/API contracts were regenerated and all service tests pass. The database must be migrated separately to drop legacy federation columns/tables in deployed environments.
+
+### `W006` — deposit/withdrawal/transaction boundary checkpoint
+
+- Added `application/withdrawal` with the IRT amount reconciliation policy and focused tests for the one-unit balance threshold.
+- `WithdrawIRTInit` continues to own the gRPC/payment flow but delegates amount policy through the application package; full Wallet tests pass in `16ebd2d`.
+- Deposit/payment idempotency, transaction persistence, queue publication, and failure orchestration remain for subsequent W006 increments.