@umituz/react-native-subscription 2.37.39 → 2.37.40

package/src/domains/wallet/README.md

@@ -1,51 +0,0 @@
-# Wallet Domain
-
-Credit balance management, transaction history tracking, and product metadata management.
-
-## Location
-
-`src/domains/wallet/`
-
-## Strategy
-
-Implements layered architecture for credit management with domain layer (entities, value objects, errors), infrastructure layer (repositories, Firebase services, mappers), and presentation layer (hooks, components). Handles initialization, operations, and transaction history with real-time updates.
-
-## Restrictions
-
-### REQUIRED
-
-- All operations require authenticated user
-- Credit operations MUST be validated server-side
-- All credit changes MUST be recorded in transaction history
-- MUST handle insufficient credits gracefully
-
-### PROHIBITED
-
-- MUST NOT allow client-side credit modifications without server validation
-- MUST NOT deduct credits without sufficient balance
-- MUST NOT expose internal repository logic to UI
-- MUST NOT store credit balance in AsyncStorage (use secure backend)
-
-### CRITICAL
-
-- Always validate credit amounts (must be positive)
-- Always implement optimistic updates with rollback
-- Never trust client-side credit balance for security decisions
-- Must implement retry logic for failed operations
-- Always sanitize transaction reasons to prevent injection attacks
-
-## AI Agent Guidelines
-
-When implementing credit operations:
-1. Always check balance before deducting
-2. Always provide transaction reason and metadata
-3. Always handle insufficient credits gracefully
-4. Always implement optimistic updates with rollback
-5. Never trust client-side balance for security
-
-## Related Documentation
-
-- [Credits Repository](infrastructure/README.md)
-- [useCredits Hook](../../presentation/hooks/README.md)
-- [UserCredits Entity](domain/entities/README.md)
-- [Transaction Errors](domain/errors/README.md)

package/src/domains/wallet/domain/README.md

@@ -1,41 +0,0 @@
-# Wallet Domain
-
-## Location
-Wallet domain containing credits and transaction management logic.
-
-## Strategy
-The wallet domain manages user credits, transactions, and credit allocation strategies with duplicate protection, transactional operations, and complete audit trail.
-
-## Restrictions
-
-### REQUIRED
-- Must check credit balance before operations
-- Must handle credit exhaustion gracefully
-- Must track all credit transactions
-- Must reset credits on subscription renewal
-
-### PROHIBITED
-- DO NOT perform operations without balance check
-- DO NOT allow duplicate credit allocations
-- DO NOT skip transaction logging
-- DO NOT bypass credit exhaustion handling
-
-### CRITICAL SAFETY
-- Credit allocations MUST be protected against duplicates
-- All credit operations MUST be transactional
-- Transaction history MUST be complete and accurate
-- Credit exhaustion MUST trigger upgrade flow
-
-## AI Agent Guidelines
-1. Always verify credit balance before performing operations
-2. Handle credit exhaustion with clear upgrade path
-3. Log all credit transactions for audit trail
-4. Implement monthly credit reset on subscription renewal
-5. Test edge cases: zero credits, max credits, duplicates
-6. Use ACCUMULATE mode for renewals, REPLACE for new purchases
-7. Provide optimistic updates with rollback capability
-
-## Related Documentation
-- [Credits README](./README.md)
-- [Credits Entity](./domain/entities/Credits.md)
-- [useCredits Hook](../../presentation/hooks/useCredits.md)

package/src/domains/wallet/infrastructure/README.md

@@ -1,41 +0,0 @@
-# Wallet Infrastructure
-
-## Location
-Infrastructure layer for wallet and credits functionality.
-
-## Strategy
-This directory contains implementations for credit persistence, transactions, and credit operations with duplicate protection and optimistic updates.
-
-## Restrictions
-
-### REQUIRED
-- Must check credit balance before deducting
-- Must handle errors appropriately
-- Must use transactions for data consistency
-- Must log all credit operations
-
-### PROHIBITED
-- DO NOT deduct credits without balance check
-- DO NOT allow duplicate credit allocations
-- DO NOT skip transaction boundaries
-- DO NOT ignore credit operation errors
-
-### CRITICAL SAFETY
-- Duplicate allocations MUST be prevented based on purchaseId
-- Credit operations MUST be atomic
-- All operations MUST be logged for debugging
-- Input validation MUST be performed
-
-## AI Agent Guidelines
-1. Always verify credit balance before deduction operations
-2. Implement comprehensive error handling for credit operations
-3. Use transactions to ensure data consistency
-4. Track all credit operations with detailed logging
-5. Test edge cases: zero credits, max credits, duplicates
-6. Validate all input parameters before processing
-7. Implement duplicate protection based on purchaseId
-
-## Related Documentation
-- [Wallet Domain](../domain/README.md)
-- [Credits Entity](../domain/entities/README.md)
-- [useCredits Hook](../../presentation/hooks/useCredits.md)

package/src/domains/wallet/presentation/components/README.md

@@ -1,41 +0,0 @@
-# Wallet Presentation Components
-
-## Location
-UI components for wallet and credit display.
-
-## Strategy
-This directory contains React Native components for displaying credits, transactions, and wallet information with clear visual hierarchy and status indicators.
-
-## Restrictions
-
-### REQUIRED
-- Must show loading states appropriately
-- Must provide empty state messages
-- Must allow manual refresh capability
-- Must display transaction history clearly
-
-### PROHIBITED
-- DO NOT hide credit balance from users
-- DO NOT show technical errors directly
-- DO NOT skip loading indicators
-- DO NOT obscure transaction details
-
-### CRITICAL SAFETY
-- Credit balance MUST always be visible
-- Status indicators MUST be color-coded appropriately
-- Transaction history MUST be complete and accurate
-- Purchase links MUST be easily accessible
-
-## AI Agent Guidelines
-1. Emphasize important information with visual hierarchy
-2. Use color coding to indicate status (low/warning/good)
-3. Show skeleton screens while loading data
-4. Provide helpful empty state messages
-5. Allow users to manually refresh credit data
-6. Display complete transaction history
-7. Make credit purchases easily accessible
-
-## Related Documentation
-- [Credit Row](../../../presentation/components/details/CreditRow.md)
-- [Credits Hook](../hooks/README.md)
-- [Wallet Domain](../../domain/README.md)

package/src/domains/wallet/presentation/hooks/README.md

@@ -1,41 +0,0 @@
-# Wallet Presentation Hooks
-
-## Location
-React hooks for wallet and credit functionality.
-
-## Strategy
-This directory contains React hooks specifically for credit management and wallet operations with optimistic updates and proper error handling.
-
-## Restrictions
-
-### REQUIRED
-- Must check balance before deducting
-- Must handle loading states appropriately
-- Must handle deduction failures gracefully
-- Must log all credit operations
-
-### PROHIBITED
-- DO NOT deduct credits without balance check
-- DO NOT skip error handling
-- DO NOT ignore loading states
-- DO NOT perform operations without tracking
-
-### CRITICAL SAFETY
-- Balance checks MUST precede all deductions
-- Deduction failures MUST be handled gracefully
-- Optimistic updates MUST support rollback
-- All operations MUST be logged
-
-## AI Agent Guidelines
-1. Always check credit balance before deducting
-2. Show appropriate loading states during operations
-3. Handle deduction failures with graceful recovery
-4. Use optimistic updates for better user experience
-5. Log all credit operations for debugging
-6. Initialize credits automatically after premium purchase
-7. Test edge cases: zero credits, max credits, failures
-
-## Related Documentation
-- [useCredits Hook Documentation](../../../presentation/hooks/useCredits.md)
-- [useDeductCredit Hook Documentation](../../../presentation/hooks/useDeductCredit.md)
-- [Credits Entity](../../domain/entities/README.md)

package/src/shared/application/ports/README.md

@@ -1,48 +0,0 @@
-# Application Ports
-
-Interfaces defining contracts between application layer and external dependencies.
-
-## Location
-
-`src/application/ports/`
-
-## Strategy
-
-Port interfaces define how the application layer interacts with external services and repositories, enabling dependency inversion and testability through clear contracts.
-
-## Restrictions
-
-### REQUIRED
-
-- MUST use interface segregation (keep interfaces focused)
-- MUST document behavior thoroughly
-- MUST use domain entities in return types
-- MUST make all I/O operations async
-- MUST define clear contracts between layers
-
-### PROHIBITED
-
-- MUST NOT couple interfaces to specific implementations
-- MUST NOT include infrastructure concerns in port definitions
-- MUST NOT leak implementation details through interfaces
-
-### CRITICAL
-
-- Keep interfaces focused and segregated
-- Document all behavior thoroughly
-- Use domain entities in return types
-- Ensure all I/O operations are async
-
-## AI Agent Guidelines
-
-When working with application ports:
-1. Interface Segregation - keep interfaces focused
-2. Clear Contracts - document behavior thoroughly
-3. Return Types - use domain entities in return types
-4. Async Operations - all I/O operations should be async
-
-## Related Documentation
-
-- [Application Layer](../README.md)
-- [Infrastructure Services](../../infrastructure/services/README.md)
-- [Infrastructure Repositories](../../infrastructure/repositories/README.md)