v2.0.85: Broker tried automatically first, transparent fallback for everyone else
What changed
Bedrock now automatically tries the central broker first on every AI request, with zero configuration.
- On infrastructure the broker recognizes (its own IP allow-list), AI works the moment the plugin is active — no wp-config.php changes needed at all.
- On any other site, this is invisible: the plugin falls straight through to that site's own configured AWS credentials, or the normal "not configured" message, exactly as before this existed.
- SSF_BEDROCK_BROKER_TOKEN remains available for individually granting a specific site access outside the recognized infrastructure.
Bulk/parallel AI runs now use the fast concurrent path whenever a site has its own AWS credentials configured, regardless of the broker — only a site with no credentials of its own falls back to the slower sequential-through-broker path.
Verified with a 19-assertion harness covering every combination (broker success, broker rejection with/without a fallback credential, a genuine Bedrock-side error correctly not triggering a fallback, and all three states of the configuration check), cross-checked against the live deployed broker.