SubMiner/backlog/tasks/task-204.1 - Restore-stale-only-startup-known-word-cache-refresh.md at af74102964cef5813f6c3938974c8790dceca6a5 - SubMiner

mirror of https://github.com/ksyasuda/SubMiner.git synced 2026-03-20 12:11:28 -07:00

Files

Show anime progress from latest session position

- include anime ID in media detail data
- use latest session position for episode progress
- update stats UI and lookup tests

2026-03-19 21:57:04 -07:00

3.1 KiB

Raw Blame History

id, title, status, assignee, created_date, updated_date, labels, dependencies, references, parent_task_id, priority

title

status

assignee

created_date

updated_date

labels

dependencies

references

parent_task_id

priority

TASK-204.1

Restore stale-only startup known-word cache refresh

Done

@Codex

2026-03-20 02:52

2026-03-20 03:02

anki

cache

bug

src/anki-integration/known-word-cache.ts

src/anki-integration/known-word-cache.test.ts

docs/plans/2026-03-19-known-word-cache-incremental-sync-design.md

TASK-204

high

Description

Follow up on the incremental known-word cache change so startup still performs a refresh when the persisted cache is older than the configured refresh interval, while leaving fresh persisted state untouched.

Acceptance Criteria

#1 Startup refreshes known words immediately when persisted cache state is stale for the configured interval.
#2 Startup skips the immediate refresh when persisted cache state is still fresh.
#3 Regression tests cover both stale and fresh startup paths.

Implementation Plan

Add focused known-word cache lifecycle tests that distinguish fresh startup state from stale startup state and verify the stale path currently fails.
Update startup scheduling in src/anki-integration/known-word-cache.ts so persisted cache still loads immediately, but startup only triggers an immediate refresh when the cache is stale for the configured interval or the cache scope/config changed.
Run focused known-word cache tests and targeted SubMiner verification for the touched cache/runtime lane, then update the task with results.

Implementation Notes

Verified current lifecycle behavior: fresh persisted known-word cache already skips immediate startup refresh when the cache scope/config matches; stale persisted cache already refreshes immediately. Added regression coverage for both startup paths plus a proxy integration test showing addNote responses return without waiting for background enrichment.

Final Summary

Added regression coverage for known-word cache startup behavior and proxy response timing. The cache tests now lock in the intended lifecycle: fresh persisted state stays load-only on startup, while stale persisted state refreshes immediately. Added a proxy integration test proving addNote responses return without waiting for background enrichment. Verification: targeted Bun tests passed (bun test src/anki-connect.test.ts src/anki-integration/anki-connect-proxy.test.ts src/anki-integration/known-word-cache.test.ts src/anki-integration/note-update-workflow.test.ts src/anki-integration/runtime.test.ts) and direct bun run test:fast passed. The subminer-change-verification helper repeatedly reported bun run test:fast as failed in its isolated lane despite the direct command passing, so that helper lane remains a flaky/blocking verification artifact rather than a reproduced code failure.

3.1 KiB Raw Blame History