/*
Theme Name:   SOAR-GC
Theme URI:    https://ruppertmarketing.com/soar-os
Description:  SOAR OS General Contractor kit — Divi 5 child theme. Holds the flagship design system in files, not in post_content. Built for AAA Home Improvements as the proof case; white-labels to any design-build contractor by editing assets/css/_tokens.css and the constants in functions.php.
Author:       Ruppert Marketing LLC
Author URI:   https://ruppertmarketing.com
Template:     Divi
Version:      1.0.9
License:      Proprietary — Ruppert Marketing LLC. Not for redistribution.
Text Domain:  soar-gc
*/

/*  This file is intentionally almost empty.

    The design system lives in three cascading partials, enqueued by functions.php
    in this exact order:

      assets/css/_tokens.css      the ONLY file you edit to re-brand a Pod
      assets/css/_components.css  the flagship component layer
      assets/css/_fixes.css       defensive rules for WordPress/Divi behaviours

    WHY IT IS BUILT THIS WAY
    The previous AAA build stored the whole design system inline in post_content,
    duplicated across 14 pages. That produced eight distinct failure classes in
    two weeks: Divi stripping <style> on module edit, wpautop injecting <p> into
    CSS, wrapper divs lost on clone, page-id-scoped CSS cloned to the wrong page,
    site-wide Divi block conversion, a backslash lost from a unicode escape, a
    component vocabulary invisible to whoever authored against it, and finally
    deletion of the only copy.

    Every one of those is a consequence of the design system living in the
    database instead of in a file. This theme is the fix.

    RULES
    1. No page may carry an inline <style> block. If a page needs a rule, the rule
       belongs in _components.css.
    2. No raw hex outside _tokens.css.
    3. Never open a SOAR page in the Divi builder. REST API only.
*/