Problem
vimit already has CacheStore, stale cache fallback, and --no-cache, but the current cache model is not fully explicit for users and contributors.
Open questions remain around:
- whether TTL is configurable;
- how manual refresh in
--monitor should interact with cache;
- whether stale fallback and cache bypass semantics are fully documented and consistent.
What to do
Tighten the existing cache behavior without redesigning unrelated runtime logic.
Acceptance Criteria
- Cache TTL can be configured via config.
--no-cache always performs a fresh fetch and does not use stale cache fallback.- Manual refresh in
--monitor has explicit documented behavior relative to cache.
- Documentation and output semantics stay consistent with actual cache behavior.
What not to touch
- No broad refactor of monitor rendering.
- No unrelated API/retry redesign.
- No changes to AGENTS workflow.
Supersedes #2.
Problem
vimitalready hasCacheStore, stale cache fallback, and--no-cache, but the current cache model is not fully explicit for users and contributors.Open questions remain around:
--monitorshould interact with cache;What to do
Tighten the existing cache behavior without redesigning unrelated runtime logic.
Acceptance Criteria
--no-cachealways performs a fresh fetch and does not use stale cache fallback.--monitorhas explicit documented behavior relative to cache.What not to touch
Supersedes #2.