# BlueBoxed 1.4.0 Compatibility Report

## Preserved Contracts

- Text domain: `blueboxed`.
- Menu locations: `primary`, `footer`.
- Widget IDs: `sidebar-1`, `footer-1`, `footer-2`, `footer-3`.
- Existing public `blueboxed_*` functions and extension hooks remain available.
- Existing template files and template-part identifiers remain in place.
- Existing block style `blueboxed-soft` and pattern `blueboxed/feature-callout` remain registered.
- Existing Customizer values are not renamed or overwritten.
- Existing defaults remain the default; new controls use opt-in or appearance-preserving defaults.
- WooCommerce support declarations and gallery behavior remain intact.

## Compatibility Fixes

The existing Customizer module is now loaded, its preview script is present, and Bootstrap declares the already-enqueued Popper dependency. These changes repair existing wiring without changing stored content or settings.

## Child Themes

The classic hierarchy, `get_template_part()` calls, hooks, filters, CSS class names, and public functions are retained. Child themes can continue overriding templates and styles. New markup is additive and uses the `blueboxed-` prefix.

## Known Limits

A complete upgrade test against a live 1.3.0 installation, child theme, WooCommerce site, and visual snapshots requires a WordPress runtime and browser harness not available in this workspace.
