Bridge Bootstrap breakpoints into theme.json settings.viewport

[Schmandarine]

WP 7.1 makes core's viewports configurable, so Bootstrap's breakpoints and the editor can finally use the same numbers instead of agreeing by coincidence.

This is higher leverage than it looks. assets/src/scss/components/gutenberg-blocks.scss is 258 lines with 11 !important declarations, and a large part of it exists purely because WordPress hardcodes column stacking at 781px while our layouts stack at Bootstrap lg (991px). With settings.viewport, WordPress stacks where we tell it to and that override stops being necessary.

Core only accepts plain px/em/rem and silently ignores calc() or a Sass variable — so this belongs to the token pipeline, not a hand-kept file.

• Emit settings.viewport.mobile / .tablet from the token source
• Audit components/gutenberg-blocks.scss for the :where() change — 7.1 wraps more preset selectors in :where(), and rules in that file were written to just barely beat WordPress. They will now beat it by more than intended. This file is the audit target, not "the override layer" in general
• Shrink the bridge where 7.1 makes it unnecessary — do not delete it; delivered sites depend on that contract (see ARCHITECTURE: absorb the CLI into this repo as a published devDependency #8 for how presets make this safe)
• Decide whether /sync-tokens pulls breakpoints from Figma or keeps them theme-side

Needs WP 7.1. Can be developed against the RC now.

Agent surface

/sync-tokens + tools/sync-tokens.mjs (new theme.json viewport emitter) → needs a @brmbh/cli release.

---

Context: vault .../Development/WP-7.1-Impact.md and Stack-Assessment-2026.md