/*
Theme Name: Robovations - Twenty Twenty-Five Child
Theme URI: https://robovations.com
Description: Authority-first robotics publication child theme with proprietary evaluation frameworks - Autonomy Ladder, Robovations Score, and Human Readiness Criteria.
Author: Robovations
Author URI: https://robovations.com
Template: twentytwentyfive
Version: 1.0.0
License: GNU General Public License v2 or later
License URI: http://www.gnu.org/licenses/gpl-2.0.html
Text Domain: robovations
Tags: robotics, reviews, authority, evaluation
*/

/* All styles loaded via modular CSS files in /css/ directory.
   See functions.php (inc/theme-setup.php) for enqueue logic.

   NOTE ON !important USAGE
   ========================
   This child theme uses ~260 !important declarations. Most are unavoidable:

   1. WP block margins — WordPress constrained layouts inject margin-block-start/end
      on all children via .is-layout-constrained > * (0,1,1 specificity). Reset with
      !important inside rv-* components.

   2. WP utility classes — .has-*-color / .has-*-background-color use !important
      themselves. Dark mode overrides must escalate to match.

   3. Block editor inline styles — When blocks have padding/color/font set in the
      editor, WP outputs style="" attributes. Only !important can override those.

   4. Gutenberg block defaults — .wp-block-post-featured-image, .wp-block-separator
      etc. have opinionated sizing/border styles that need overriding.

   WHEN YOU CAN AVOID !important:
   - Increase selector specificity (e.g. .parent .child instead of .child)
   - Use double-class selectors (.block.block--modifier) to beat WP's (0,1,1) rules
   - Remove the conflicting value from the block editor template instead
   - If fighting your own CSS, refactor the cascade — don't add !important
*/