melosh/mal
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

chore: format plans

Browse Source
This commit is contained in:
mkelvers
2026-06-27 17:46:05 +02:00
parent 549f964e8e
commit 177081edd0
4 changed files with 65 additions and 24 deletions
Download Patch File Download Diff File Expand all files Collapse all files

25
plans/012-expose-episode-availability-refresh-state.md
View File

@@ -1,7 +1,9 @@
---
finding: "Expose episode availability freshness / retry state"
catalog: "Direction"
impact: "Users cannot see stale, retrying, or failed episode availability state even though the app tracks it."
impact:
"Users cannot see stale, retrying, or failed episode availability state even though the app tracks
it."
base_commit: "0d31d46"
---
@@ -20,15 +22,24 @@ MED - the data exists, but product shape needs maintainer judgment.
## Evidence
- `internal/episodes/worker.go:12-31` refreshes due episode availability in the background.
- `internal/episodes/service/cache_store.go:50-65` stores next refresh, retry window, last attempt/success, failure count, and last error metadata through query parameters.
- `templates/components/anime_episode_count.gohtml` currently collapses availability to a compact episode/audio label.
- `internal/episodes/service/cache_store.go:50-65` stores next refresh, retry window, last
attempt/success, failure count, and last error metadata through query parameters.
- `templates/components/anime_episode_count.gohtml` currently collapses availability to a compact
episode/audio label.
## Resolution Approach
Start with the smallest useful user-facing surface: a per-title availability status detail near the existing episode-count/audio label. Show human-readable freshness such as last refreshed, next refresh, retrying soon, or temporarily unavailable. Avoid exposing raw provider errors unless they are sanitized and clearly useful.
Start with the smallest useful user-facing surface: a per-title availability status detail near the
existing episode-count/audio label. Show human-readable freshness such as last refreshed, next
refresh, retrying soon, or temporarily unavailable. Avoid exposing raw provider errors unless they
are sanitized and clearly useful.
Consider adding an authenticated manual refresh action only after the read-only status is useful. Manual refresh should be rate-limited or guarded to avoid hammering providers.
Consider adding an authenticated manual refresh action only after the read-only status is useful.
Manual refresh should be rate-limited or guarded to avoid hammering providers.
Add service/view-model tests that map cache metadata to user-facing states. Add template tests for fresh, stale, retrying, and failed states. If this becomes a maintenance page instead, split that into a separate design plan before implementation.
Add service/view-model tests that map cache metadata to user-facing states. Add template tests for
fresh, stale, retrying, and failed states. If this becomes a maintenance page instead, split that
into a separate design plan before implementation.
Verify with `go test ./internal/episodes/... ./templates ./...` and relevant lint/typecheck commands if UI scripts are added.
Verify with `go test ./internal/episodes/... ./templates ./...` and relevant lint/typecheck commands
if UI scripts are added.