[Bug] Различать banking read error/empty и восстанавливать отдельные sections #57
Closed
opened 2026-10-11 21:48:56 +03:00 by codex-bot
·
1 comment
No Branch/Tag Specified
Labels
Clear labels
Kind/Dependencies
Kind/Investigation
Kind/Process
Kind/Refactor
audit/2026-10-11
kind/investigation
Compat/Breaking
Kind/Bug
Kind/Documentation
Kind/Enhancement
Kind/Feature
Kind/Security
Kind/Testing
Dependency update or dependency-management work
Research or decision required before implementation
Developer workflow, CI/CD, tooling, or process improvement
Internal code or configuration restructuring without new product behavior
Technical Audit Remediation — 2026-10-11
Нужна проверка evidence до решения; runtime-дефект не утверждается
Breaking change that won't be backward compatible
Something is not working
Documentation changes
Improve existing functionality
New functionality
This is security issue
Issue or pull request related to testing
Priority
Critical
1
The priority is critical
Priority
High
2
The priority is high
Priority
Medium
3
The priority is medium
Priority
Low
4
The priority is low
Reviewed
Confirmed
1
Issue has been confirmed
Reviewed
Duplicate
2
This issue or pull request already exists
Reviewed
Invalid
3
Invalid issue
Reviewed
Won't Fix
3
This issue won't be fixed
Status
Blocked
1
Something is blocking this issue or pull request
Status
Need More Info
2
Feedback is required to reproduce issue or to continue work
Status
Abandoned
3
Somebody has started to work on this but abandoned work
Milestone
No items
No Milestone
Technical Audit Remediation — 2026-10-11
Projects
Clear projects
No projects
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: WealthLedger/frontend#57
Reference in New Issue
Block a user
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Problem
Cards cold failure возвращает null/blank; Card/history/summary retry не проходит presentation API, cached warnings подавляются при data. Успешные balances сохраняются, но failure не видна.
Expected Behavior
Cold error отличается от empty; cached error оставляет exact data и даёт section GET retry без потери draft/URL.
Evidence
Audit date
2026-10-11; 05, FE-004. Revisionc8821200ce699dab1ce65360d1968d5877a2e78b; Confidence High; Verification status static.Affected: CardsPage.view.tsx:31–77; CardPage.vm.ts:95–145; CardHistory.view.tsx:38–123; BankSummary.view.tsx:17–23,84–125; CardPage.test.tsx:315–341.
Scope
In scope
Page-owned state/retry, existing BankFeedback, independent sections.
Out of scope
Optimistic financial success, bank error manager, replay/version/refund changes, edit on placeholder rows.
Proposed Approach
Named retries из query owner, cold branch + cached warning, successful sibling sections не скрывать. NotFound не предлагает повторить write/create duplicate.
Acceptance Criteria
Verification
Existing CardsPage/CardPage/BankSummary RTL/MSW cold/cached/independent failure и successful retry cases после settled response; full frontend final verify.
Dependencies
Нет.
Traceability
Campaign WealthLedger/main#23 . Finding FE-004. WealthLedger/frontend; T22.
Закрывается: работа выполнена и принята в
develop.Доказательство — коммит
e38ecd8с текстомCloses #56, #57, слитый PR #80 (mergeedc7097):Acceptance Criteria закрыты телом коммита:
notFoundпо-прежнему не предлагает retry CTA.Тесты: CardsPage/CardPage/BankSummary — cold/cached cards error с retry, summary failure с retry, восстановление списка карт.
Парная Issue
#56закрыта 2026-10-14 тем же коммитом;#57осталась открытой по недосмотру — расхождение статуса, а не незавершённая работа.