Problem
vimit already has stale cache fallback, offline duration tracking, and partial offline signaling, but the terminology and behavior are not fully aligned across TUI, JSON, and human-readable output.
Today the user can still see mixed concepts such as:
- stale cached response;
- offline API condition;
- human output wording that may not match JSON/TUI semantics.
What to do
Make degraded API state consistent and easy to understand without redesigning the whole cache layer.
Acceptance Criteria
- TUI, JSON, and human output use a consistent model for
stale vs offline.
- Human output does not confuse
(cached) and (offline).
- JSON clearly exposes degraded API state.
- Documentation explains the difference between stale cache fallback and offline mode.
What not to touch
- No generic retry framework rewrite.
- No unrelated TUI layout refactor.
- No AGENTS workflow changes.
Supersedes #8.
Problem
vimitalready has stale cache fallback, offline duration tracking, and partial offline signaling, but the terminology and behavior are not fully aligned across TUI, JSON, and human-readable output.Today the user can still see mixed concepts such as:
What to do
Make degraded API state consistent and easy to understand without redesigning the whole cache layer.
Acceptance Criteria
stalevsoffline.(cached)and(offline).What not to touch
Supersedes #8.