The week's subscription is spent by reset: the crew paces to it and pulls the next ranked issues in itself #8695

The owner: the subscription should be used up by the end of every week, with as little input as possible, and token efficiently. src/crew/pacing.ts only slows near a limit. Today's crew ran out of ready work with 54% of the week left because nothing pulled more in.

Done when:

• [x] A target burn is worked out from what's left and the time to reset, shown in one sentence on home: on pace, ahead or behind.
• [x] Behind pace with builders idle, the next ranked gated issue is released automatically, one at a time, each logged with why.
• [x] Ahead of pace, slots come down before the limit is hit, and /talk and a person's own request keep a reserve.
• [x] Efficiency is shown beside it: cost per real landing and runs per real landing per week, not counting pulls closed as already on the base.
• [x] The week's settings are plain values a person can read, and the same state gives the same decision (tested).

When behind pace, release the next piece of a backed bet (#8713), or offer the next bet to back, rather than the next gated issue by rank. Appetites sit inside the week's capacity.

Reviewed pull #8701 at its head: ticked A target burn is worked out from what's left and the time to reset, shown in one sentence on home: on pace, ahead or behind.; Behind pace with builders idle, the next ranked gated issue is released automatically, one at a time, each logged with why.; Ahead of pace, slots come down before the limit is hit, and /talk and a person's own request keep a reserve.; Efficiency is shown beside it: cost per real landing and runs per real landing per week, not counting pulls closed as already on the base.; The week's settings are plain values a person can read, and the same state gives the same decision (tested)..