Nothing to try yet
Policy limits client for the agents view is now lazily loaded at startup behind an internal gate
What
A new startup routine checks a catalog decision setting, and if it isn't already set, dynamically loads a policy-limits client module for the agents view. It only actually composes the client when an internal condition is true and a storageV5 option is present; failures are caught and logged as a warning rather than crashing. It always waits for a "cold start" step to finish before continuing.
Why
This defers loading policy-limits code until it's needed and guards startup against failures in that composition step, so a problem there produces a warning instead of breaking the agents view.
Something disagreesSomething we can check disagrees with this entry, or the writer said they could not settle it.
The writer flagged doubt
What the internal gate condition and `catalogDecision` setting actually control is not established by the evidence.