Define the lifetime and scope of tool repetition limits

What problem would this solve?

Users can configure a maximum number of repeated tool calls. The behavior needs one contract across CLI construction, inspection, retries, parallel batches, and both agent loops.

What would a good outcome look like?

A selected finite limit is enforced consistently, without sharing another session's counters or silently resetting them on every inspection.

Possible approaches

Should the limit be per session, persist across assistant turns, count same-batch calls in order, and reset only at specified retry/session boundaries? Define concurrent inspection ordering, parameter changes, zero-limit semantics, and resume behavior. Keep the disabled default explicit. Verification should exercise the real CLI-to-inspector path and both loops, including allowed calls below the limit and denied calls above it.

Additional context

This is a state-ownership and configuration contract, not a request to change tool permissions or introduce a general resource quota.

• I have verified this does not duplicate an existing feature request

Do not begin implementation until the issue reaches Ready on the Goose Issues board.