git_dates_rate_cap

Katz 0.123

Git history analysis is expensive ( `git log -L` and follow logs per idea ).
Do not start a git_dates wave on every `.rq` save or catalog notify.
Catalog and index-status events must debounce ( quiet period after the last notify )
and must wait a minimum gap after a wave that actually filled dates.
Editor-switch priority and draining a capped wave may use the short idle delay.
Distinct from indexing_trigger_filesave: the ideas
index still updates on save; only git analysis is rate-capped.
Related: git_dates_background_indexing, git_dates,
idea_index_triggers, git_information_capture,
consumption_silence.

implementation

git-dates-background.ts, register-git-dates-background.ts

status

done

tests

git-dates-background.test.ts:catalog events debounce and do not follow the short editor delay, git-dates-background.test.ts:catalog waves wait for the min gap after a fill

Interactive page: git_dates_rate_cap