/*
Theme Name:     Private Spaces (Frost Child)
Theme URI:      https://strategicdigitalpartners.com/
Description:    Child theme of Frost for Private Spaces. v0.4.2 fixes the footer active-link color: v0.4.1 painted them dark ink (#0f1720) which was invisible on the dark slate footer background. v0.4.2 paints footer active links gold (#b89a5b) so they read against the dark backdrop. Top nav and READ DEEPER stack remain dark ink + gold underline. Sub nav remains gold text + gold underline. Single CSS rule split, no architecture change. ~2 KB inline footer payload, zero external requests.
Author:         Strategic Digital Agency — Keith Bennett
Author URI:     https://strategicdigitalagency.com/
Template:       frost
Version:        0.4.2
Requires at least: 6.4
Tested up to:   6.7
Requires PHP:   7.4
License:        GNU General Public License v2 or later
License URI:    http://www.gnu.org/licenses/gpl-2.0.html
Text Domain:    private-spaces-child
Tags:           block-theme, full-site-editing
*/

/*
 * v0.4.2 ships with no CSS rules in this file. The file exists only so
 * WordPress recognizes the child theme. All styling still lives in:
 *   - Per-page inline CSS (legacy, Phase 3 will migrate it)
 *   - The runtime-injected <style id="ps-active-nav-css-theme"> created by
 *     private_spaces_child_active_nav_script() in functions.php
 *
 * Why no CSS in this file:
 *   - The active-nav rules need to win the cascade against existing
 *     per-page !important rules and WordPress wp:navigation block CSS.
 *     Injecting them at runtime puts them late in the <head>, which
 *     gives them cascade priority over earlier-loaded stylesheets.
 *   - When this child theme's style.css is enqueued via wp_enqueue_style,
 *     it loads relatively early. Rules placed here would lose to rules
 *     that load later (other plugins, block CSS, etc.) even with
 *     !important. Runtime injection sidesteps that ordering problem.
 *
 * v0.4.2 splits the active-link color rule by container background:
 *   - Light-background containers (top nav, READ DEEPER): dark ink
 *   - Dark-background containers (footer): gold
 *   - Section sub-nav: gold (unchanged)
 *
 * v0.1.0 attempted a full design system in theme.json. Broke the homepage.
 * v0.2.0 reduced to font enqueue + contentSize: 1080px. Still broke the
 * homepage. The cause turned out to be a per-page CSS rule on the homepage
 * (body.page-id-273 { background-color: #0f1720 !important }) interacting
 * badly with Frost's recompiled global stylesheet under any active child
 * theme.
 *
 * v0.3.0 shipped only the font enqueue. No theme.json beyond schema/version.
 * Confirmed clean on activation.
 *
 * v0.4.0 added the active-nav indicator script. Covered nav.ve-primary,
 * nav.ps-nav, nav.ps-subnav. Installed 2026-05-16.
 *
 * v0.4.1 extended coverage to div.ve-about (READ DEEPER vestibule) and
 * footer.site-footer / footer.ps-footer-wrap. Installed 2026-05-16.
 *
 * v0.4.2 fixes footer active-link visibility (gold text, not dark ink).
 */
