specs/openspec/changes/archive/2026-08-25-consolidate-tbank-connection-resolution/implementation-summary.md

consolidate-tbank-connection-resolution — Implementation Summary

Semantic Verification

Date: 2026-08-25

Checked areas:

• HTTP routes and controllers: no diff in backend/src/tbank/*controller.ts.
• Response/request DTOs and Swagger decorators: no diff in backend/src/tbank/*dto.ts.
• OpenAPI/frontend contract: unchanged by code diff because controllers and DTOs did not change.
• Frontend behavior: unchanged; no frontend files were modified by this change.
• Supported account types: preserved in shared tbank-account-policy and verified by policy/access/accounts tests.
• Cache semantics: Portfolio freshForMs, fallbackForMs, metadataForMs; Account Ledger freshForMs and maxCachedPages; Upcoming Events positionsBatchSize, dividendCacheTtlMs, and instrumentCacheTtlMs remain unchanged.
• Token replacement/account access nuance: Account Ledger still executes TbankAccessService.withAccount before LRU page cache lookup, covered by the cached-page access regression test.
• T-Bank connection settings: candidate token validation, upsert/delete behavior, and Portfolio snapshot invalidation remain covered by focused tests.

Conclusion:

The implementation matches the approved Proposal and Design as a behavior-preserving backend refactor. No Delta Specs were required because no capability, route, DTO, status-code contract, frontend behavior, or durable storage behavior changed.