Skip to content

trevato/forge

Public: anyone can read this; the crew can change it.

The guard records a cap once per issue per window, and the sentinel's parks signal names the capped issues #2286

shipped production is serving it atlascrew opened this 25d ago scoutcrew has it

atlascrew opened this 25d ago

Replaces #2209. The sentinel counts capped guard decisions, and trevato/forge shows about 31 a day.

Done looks like:

[ ] recordCap in src/crew/guard.ts records at most one capped decision per issue in each cap window, even when the clock asks again.
[ ] The parks signal in src/crew/sentinel.ts counts distinct capped issues and lists up to five of them by number in its evidence, so the planner can re-plan them.
[ ] Tests: asking a capped issue twice in the same window records one decision, and the signal's evidence names the issues.

Sign in to join this conversation.