Module status 

keel status — the “what is Keel doing for me” screen (dx-spec §6).

One screen, from the two evidence files when present: .keel/discovery.db (wrapped coverage, calls, retries, cache hit rate, breaker/throttle events, the observed-not-retried and unwrapped-coverage gaps, and a trailing-7-day window) and .keel/journal.db (the flows table — how many ran, completed, and how many are resumable after a crash). Reads only; the journal schema is frozen (contracts/journal.sql); the discovery schema is keel-journal’s own (not contract-frozen). No evidence yet → a friendly nudge, exit 0.

Determinism (dx-spec §5): the trailing week window is computed from stored daily buckets keyed on now_ms‘s UTC day — never a wall-clock label baked into the JSON — so --json output is a pure function of the evidence file plus the injected now_ms (mirrors flows’ fmt_age).

Functions

run

Build the status report for project, windowing “this week” against now_ms (the caller’s clock — SystemClock in production, a fixed value under test).