fix: surface durable hourly attempt in accounts and income meta (WealthLedger/backend#58) #91

Closed

codex-bot wants to merge 2 commits from fix/58-hourly-resource-metadata into develop

pull from: fix/58-hourly-resource-metadata

merge into: :develop

:develop

:refactor/55-rub-only-squashed

:refactor/55-rub-only

:main

:release/2.4.1

Conversation 0 Commits 2 Files Changed 6

+80 -4

codex-bot commented 2026-10-14 16:20:48 +03:00

Owner

Copy Link

Copy Source

Closes WealthLedger/backend#58

Что изменено

• hourlyAttempt принимает один раздел или список разделов (relevance без второй status registry).
• Accounts resource: meta.lastAttempt теперь из durable hourly projection по разделам membership+portfolio (все счёта connection); top-level sync сохранён.
• Income ranges (collectRanges): добавлено lastAttempt: hourlyAttempt(hourly, 'operations', accountId) — тот же контур, что и у operations resource.
• Income analytics top-level: lastAttempt переиспользуется из operations meta (current.meta.lastAttempt); source work остаётся техническим наблюдением и не подменяет hourly attempt.
• Fallback маппера без изменений: отсутствие hourly attempt отличается от успешной попытки (none с null timestamps), failed source work больше не называется membership у Income.

Verification

• Новый SQLite HTTP тест: seeded partial hourly row с проблемами portfolio/operations → Accounts meta.lastAttempt даёт state/time и только portfolio-problem, Income — только operations-problem (section relevance).
• tbank-income-local: ожидание после repo.fail без hourly изменено на none (нет состоявшейся попытки обхода), data/timestamp assertions прежние.
• Suites: local-reads, income-local, hourly-lifecycle, upcoming-events, portfolio-structure, tbank-connection, app — все exit 0.
• Полный npm run verify — exit 0.

Guarantees

• Source payload, lastSuccessfulAt/freshness неизменны; metadata read не создаёт RPC/work (только read-only hourly projection).
• Privacy/revision fencing прежняя: replacement/logout/foreign account не раскрывает old-generation attempt (TbankSyncRepository.hourly проверяет current connection).

Closes WealthLedger/backend#58 ## Что изменено - `hourlyAttempt` принимает один раздел или список разделов (relevance без второй status registry). - Accounts resource: `meta.lastAttempt` теперь из durable hourly projection по разделам `membership`+`portfolio` (все счёта connection); top-level `sync` сохранён. - Income ranges (`collectRanges`): добавлено `lastAttempt: hourlyAttempt(hourly, 'operations', accountId)` — тот же контур, что и у operations resource. - Income analytics top-level: `lastAttempt` переиспользуется из operations meta (`current.meta.lastAttempt`); source work остаётся техническим наблюдением и не подменяет hourly attempt. - Fallback маппера без изменений: отсутствие hourly attempt отличается от успешной попытки (`none` с null timestamps), failed source work больше не называется `membership` у Income. ## Verification - Новый SQLite HTTP тест: seeded `partial` hourly row с проблемами `portfolio`/`operations` → Accounts meta.lastAttempt даёт state/time и только portfolio-problem, Income — только operations-problem (section relevance). - `tbank-income-local`: ожидание после `repo.fail` без hourly изменено на `none` (нет состоявшейся попытки обхода), data/timestamp assertions прежние. - Suites: local-reads, income-local, hourly-lifecycle, upcoming-events, portfolio-structure, tbank-connection, app — все exit 0. - Полный `npm run verify` — exit 0. ## Guarantees - Source payload, `lastSuccessfulAt`/freshness неизменны; metadata read не создаёт RPC/work (только read-only hourly projection). - Privacy/revision fencing прежняя: replacement/logout/foreign account не раскрывает old-generation attempt (`TbankSyncRepository.hourly` проверяет current connection).

codex-bot added 1 commit 2026-10-14 16:20:49 +03:00

fix: surface durable hourly attempt in accounts and income meta (WealthLedger/backend#58) d47dfee208

codex-bot added 1 commit 2026-10-14 17:03:02 +03:00

Merge branch 'develop' into fix/58-hourly-resource-metadata 8cc63b3ba5

codex-bot closed this pull request 2026-10-14 18:00:46 +03:00

Pull request closed

This pull request cannot be reopened because the branch was deleted.

Sign in to join this conversation.

Reviewers

No Reviewers

Labels

Clear labels

Kind/Dependencies

Dependency update or dependency-management work

Kind/Investigation

Research or decision required before implementation

Kind/Process

Developer workflow, CI/CD, tooling, or process improvement

Kind/Refactor

Internal code or configuration restructuring without new product behavior

audit/2026-10-11

Technical Audit Remediation — 2026-10-11

kind/investigation

Нужна проверка evidence до решения; runtime-дефект не утверждается

Compat/Breaking

Breaking change that won't be backward compatible

Kind/Bug

Something is not working

Kind/Documentation

Documentation changes

Kind/Enhancement

Improve existing functionality

Kind/Feature

New functionality

Kind/Security

This is security issue

Kind/Testing

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

No labels

Milestone

No items

No Milestone

Projects

Clear projects

No projects

Assignees

Clear assignees

codex-bot hermes-agent ksv741 publisher-bot renovate-bot

No Assignees

1 Participants

Notifications

Subscribe

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: WealthLedger/backend#91