bitcode-wallets

Each wallet is a one-to-one ledger tied to a `person`, holding a running balance built from individual credit/debit transactions rather than a single mutable number — every change to a student's Bitcode balance is recorded as its own auditable row with a type, amount, and optional description. The admin-facing `BitcodeWalletController` (`/lms/bitcode-wallets`) covers wallet CRUD and lets an operator post manual transactions directly.

A second, self-service path exists outside this submodule's own controller: the Platforma student portal exposes `GET /lms/platforma/bitcodes/wallet` and `POST /lms/platforma/bitcodes/transactions`, letting an authenticated student view their own wallet and create their own transactions using a dedicated `CreateCurrentBitcodeWalletTransactionDto` (which adds an optional `source` field not present on the admin DTO, for tagging where a self-service credit originated). An `UpdateBitcodeWalletTransactionDto` also exists in source but has no controller route anywhere in the codebase — individual transactions can be created but never edited or listed on their own; the wallet's transaction history is presumably surfaced as part of the wallet-detail response instead.