@networkpro/web 1.12.3 → 1.12.4

package/CHANGELOG.md

@@ -1,10 +1,20 @@
+<!-- =====================================================================
+CHANGELOG.md
+
+Copyright © 2025 Network Pro Strategies (Network Pro™)
+SPDX-License-Identifier: CC-BY-4.0 OR GPL-3.0-or-later
+This file is part of Network Pro.
+====================================================================== -->
+
 # Changelog
 
 <!-- markdownlint-disable MD024 -->
 
+<!-- Use sections: Added, Changed, Deprecated, Removed, Fixed, Security -->
+
 All notable changes to this project will be documented in this file.
 
-This project attempts to follow [Keep a Changelog](https://keepachangelog.com/en/1.0.0/), though versioning and formatting may vary.
+This project attempts to follow [Keep a Changelog](https://keepachangelog.com/en/1.1.0/), though versioning and formatting may vary.
 
 ---
 
@@ -12,6 +22,28 @@ This project attempts to follow [Keep a Changelog](https://keepachangelog.com/en
 
 ---
 
+## [1.12.4] - 2025-06-05
+
+### Added
+
+- Introduced `.md-smart-quotes.js` script for use with markdownlint to flag "smart quotes" in Markdown files.
+
+### Changed
+
+- Cleaned up `IGNORE_PATHS` in `src/service-worker.js`: removed the `static/docs/` entry, as the directory no longer exists.
+- Upgraded development dependencies:
+  - `@vitest/coverage-v8`
+  - `posthog-js`
+  - `vitest`
+- Corrected the "Effective Date" in `LICENSE.md`.
+- Refactored `.markdownlint.jsonc` into `.markdownlint.mjs` to support the custom linting script.
+
+### Removed
+
+- Removed the entire `static/docs/` directory; its contents have been migrated to the [Wiki](https://github.com/netwk-pro/netwk-pro.github.io/wiki).
+
+---
+
 ## [1.12.3] - 2025-06-04
 
 ### Added
@@ -25,7 +57,7 @@ This project attempts to follow [Keep a Changelog](https://keepachangelog.com/en
 
 ---
 
-## [1.12.2] – 2025-06-04
+## 1.12.2 – 2025-06-04
 
 ### Changed
 
@@ -52,7 +84,7 @@ This project attempts to follow [Keep a Changelog](https://keepachangelog.com/en
 
 ---
 
-## [1.12.0] – 2025-06-04
+## 1.12.0 – 2025-06-04
 
 ### Added
 
@@ -77,3 +109,10 @@ This project attempts to follow [Keep a Changelog](https://keepachangelog.com/en
 - Deprecated `shouldTrackUser()` logic and legacy cookie checks.
 
 ---
+
+<!-- Link references -->
+
+[Unreleased]: https://github.com/netwk-pro/netwk-pro.github.io/compare/v1.12.4...HEAD
+[1.12.4]: https://github.com/netwk-pro/netwk-pro.github.io/releases/tag/v1.12.4
+[1.12.3]: https://github.com/netwk-pro/netwk-pro.github.io/releases/tag/v1.12.3
+[1.12.1]: https://github.com/netwk-pro/netwk-pro.github.io/releases/tag/v1.12.1

package/LICENSE.md

@@ -14,7 +14,7 @@ This file is part of Network Pro.
 # Legal, Copyright, and Licensing
 
 **Network Pro Strategies**  
-**Effective Date:** May 28, 2025
+**Effective Date:** June 4, 2025
 
 **Official Version Notice**  
 This document is provided for convenience only. In the event of any discrepancy, the authoritative version is the one published at [https://netwk.pro](https://netwk.pro).

package/package.json

@@ -1,8 +1,8 @@
 {
   "name": "@networkpro/web",
   "private": false,
-  "version": "1.12.3",
-  "description": "Locking Down Networks, Unlocking Confidence | Security, Networking, Privacy — Network Pro Strategies",
+  "version": "1.12.4",
+  "description": "Locking Down Networks, Unlocking Confidence™ | Security, Networking, Privacy — Network Pro Strategies",
   "keywords": [
     "advisory",
     "consulting",
@@ -16,7 +16,7 @@
   ],
   "homepage": "https://netwk.pro",
   "bugs": {
-    "url": "https://github.com/netwk-pro/netwk-pro.github.io/issues"
+    "url": "https://github.com/netwk-pro/netwk-pro.github.io/issues/new/choose"
   },
   "repository": {
     "type": "git",
@@ -77,7 +77,7 @@
   },
   "dependencies": {
     "dompurify": "^3.2.6",
-    "posthog-js": "^1.249.3",
+    "posthog-js": "^1.249.4",
     "semver": "^7.7.2",
     "svelte": "5.33.14"
   },
@@ -91,7 +91,7 @@
     "@sveltejs/vite-plugin-svelte": "5.1.0",
     "@testing-library/jest-dom": "^6.6.3",
     "@testing-library/svelte": "^5.2.8",
-    "@vitest/coverage-v8": "^3.2.1",
+    "@vitest/coverage-v8": "^3.2.2",
     "autoprefixer": "^10.4.21",
     "browserslist": "^4.25.0",
     "eslint": "^9.28.0",
@@ -119,7 +119,7 @@
     "vite": "^6.3.5",
     "vite-plugin-lightningcss": "^0.0.5",
     "vite-tsconfig-paths": "^5.1.4",
-    "vitest": "^3.2.1"
+    "vitest": "^3.2.2"
   },
   "overrides": {
     "@sveltejs/kit": {

package/src/service-worker.js

@@ -27,23 +27,15 @@ const CACHE = `cache-${version}`;
 /** @type {string[]} */
 const excludedAssets = [];
 
-//TODO: Remove files in docs once migrated to documentation subsite
-
 const IGNORE_PATHS = new Set([
-  "/docs/extensions.md",
-  "/docs/Home.md",
-  "/docs/pgp-email.md",
-  "/docs/pgp-win.md",
-  "/docs/pgp.md",
-  "/docs/tracking.md",
   "/img/banner-1280x640.png",
   "/img/logo-transparent.png",
   "/img/logo.png",
   "/img/svelte.png",
+  "/screenshots/desktop-foss.png",
   "/webfonts/fa-brands-400.ttf",
   "/webfonts/fa-solid-900.ttf",
   "/robots.txt",
-  "/screenshots/desktop-foss.png",
   "/sitemap.xml",
   "/CNAME",
 ]);

package/static/docs/Home.md

@@ -1,63 +0,0 @@
-# 🧠 Network Pro — Developer Wiki
-
-> Internal documentation and contributor onboarding resources for the [Network Pro™ Web Presence](https://github.com/netwk-pro/netwk-pro.github.io) project.  
-> **Note:** Most of the below links are currently non-functional and serve solely as placeholders. Once pages are added, the placeholder links will be removed.
-
----
-
-## 📌 Overview
-
-This wiki provides documentation, conventions, and internal tooling references to support development, testing, and deployment workflows across the Network Pro stack.
-
----
-
-## 📁 Sections
-
-### 🛠 Setup & Tooling
-
-- [Environment Requirements](Environment-Requirements.md)  
-  Node, npm, version managers, OS-specific notes.
-- [Editor Configuration](Editor-Configuration.md)  
-  Workspace settings, recommended VS Code/VSCodium extensions.
-- [CLI Scripts Reference](CLI-Scripts.md)  
-  `npm run` scripts explained with tips for usage.
-
-### 🚧 Development
-
-- [Local Development](Local-Development.md)  
-  Running the project, debugging, hot reload, ENV_MODE behavior.
-- [Testing & Audits](Testing-&-Audits.md)  
-  Vitest, Playwright, Lighthouse, CI reports.
-- [Styling & Components](Styling-&-Components.md)  
-  Design system, reusable components, naming conventions.
-
-### 🚀 CI/CD
-
-- [GitHub Actions Workflows](CI-CD-Workflows.md)  
-  How our deploy/audit pipelines are structured.
-- [Versioning & Releases](Versioning-&-Releases.md)  
-  Publishing, changelog generation, NPM tagging conventions.
-
-### 📚 Documentation Maintenance
-
-- [Contributing to the Wiki](Contributing-to-the-Wiki.md)  
-  Format, tone, and content guidelines for internal docs.
-- [MkDocs Subsite Overview](MkDocs-Subsite.md)  
-  How the public documentation repo is built and deployed.
-
----
-
-## 📎 Related Repositories
-
-- [Main Site (Web)](https://github.com/netwk-pro/netwk-pro.github.io)
-- [Documentation Site](https://github.com/netwk-pro/docs)
-- [Blog Subsite](https://github.com/netwk-pro/blog)
-- [GitHub Wiki](https://github.com/netwk-pro/netwk-pro.github.io/wiki)
-
----
-
-## 🤝 Contributing
-
-If you're new to the project, start with [Environment Requirements](Environment-Requirements.md) and [Local Development](Local-Development.md). See [Contributing to the Wiki](Contributing-to-the-Wiki.md) for how to add or edit content.
-
----

package/static/docs/extensions.md

@@ -1,58 +0,0 @@
-# 🧩 Recommended VS Code Extensions
-
-To streamline development and align with project conventions, we recommend the following [VSCodium](https://vscodium.com/) and [Visual Studio Code](https://code.visualstudio.com/) (VS Code) extensions. These tools enhance productivity, enforce code quality, and ensure consistency across the codebase.
-
-> Note: While these extensions are optional, they are thoughtfully curated to complement our development workflow.
-
-<!-- cspell:disable -->
-
-| Extension Name            | Identifier                              | Description                                                                 |
-| ------------------------- | --------------------------------------- | --------------------------------------------------------------------------- |
-| Prettier - Code formatter | `esbenp.prettier-vscode`                | Formats code consistently across various languages.                         |
-| ESLint                    | `dbaeumer.vscode-eslint`                | Integrates ESLint into VS Code for JavaScript and TypeScript linting.       |
-| Stylelint                 | `stylelint.vscode-stylelint`            | Lints CSS/SCSS and enforces consistent styling conventions.                 |
-| Markdownlint              | `DavidAnson.vscode-markdownlint`        | Provides linting and style checking for Markdown files.                     |
-| EditorConfig for VS Code  | `EditorConfig.EditorConfig`             | Maintains consistent coding styles between different editors and IDEs.      |
-| Svelte for VS Code        | `svelte.svelte-vscode`                  | Offers syntax highlighting, code completion, and error checking for Svelte. |
-| Code Spell Checker        | `streetsidesoftware.code-spell-checker` | Inline spell checking (comments, Markdown, etc.)                            |
-
-## 🛠 Installation
-
-To install these extensions, you can use the following command in your terminal:
-
-```bash
-code --install-extension esbenp.prettier-vscode
-code --install-extension dbaeumer.vscode-eslint
-code --install-extension stylelint.vscode-stylelint
-code --install-extension DavidAnson.vscode-markdownlint
-code --install-extension EditorConfig.EditorConfig
-code --install-extension svelte.svelte-vscode
-code --install-extension volta.volta
-code --install-extension eamodio.gitlens
-code --install-extension github.vscode-pull-request-github
-```
-
-<!-- cspell:enable -->
-
-Alternatively, you can search for each extension by name in [Open VSX Registry](https://open-vsx.org/) and/or the [VS Code Extensions Marketplace](https://marketplace.visualstudio.com/vscode) and install them individually.
-
-## 📁 Workspace Recommendations
-
-Our repository includes a `.vscode/extensions.json` file that specifies these recommended extensions. When you open the project in VS Code, you'll be prompted to install any missing recommended extensions. This ensures a consistent development environment across all contributors.
-
-## 🔧 Configuration
-
-The `.vscode/settings.json` file in the repository contains workspace-specific settings that align with our coding standards and practices. These settings include formatter configurations, linting rules, and other preferences to maintain code quality and consistency.
-
----
-
-<div style="font-size: 12px; text-align: center;">
-
-Copyright &copy; 2025  
-**[Network Pro Strategies](https://netwk.pro) (Network Pro&trade;)**
-
-Network Pro&trade;, the shield logo, and the "Locking Down Networks&trade;" slogan are [trademarks](https://netwk.pro/license#trademark) of Network Pro Strategies.
-
-Licensed under **[CC BY 4.0](https://netwk.pro/license#cc-by)** and the **[GNU GPL](https://netwk.pro/license#gnu-gpl)**, as published by the [Free Software Foundation](https://www.fsf.org), either version 3 of the License, or (at your option) any later version.
-
-</div>

package/static/docs/pgp-email.md

@@ -1,152 +0,0 @@
-# 📧 Encrypting Email with PGP
-
-> This guide walks you through using PGP (Pretty Good Privacy) to encrypt email using both graphical and client-based tools.
-
-PGP encryption ensures that only the intended recipient can read your email content — even if it's intercepted.
-
----
-
-## 🔹 Option A: Outlook (Windows) with GpgOL
-
-GpgOL is a plugin included with **Gpg4win** that integrates directly into Microsoft Outlook (desktop only).
-
-### ✅ Requirements
-
-- Gpg4win (with GpgOL selected during installation)
-- Outlook 2010 or newer (desktop version)
-- Recipient’s **public key**
-
-> ⚠️ GpgOL does not work with Outlook for Microsoft 365 Web or Outlook Mobile. It is only compatible with the **desktop edition of Outlook** on Windows.
-
-### 📥 Encrypting an Email in Outlook
-
-1. Open Outlook and compose a new message
-2. Enter the recipient’s email address (must match imported key)
-3. Click the `Encrypt` button on the **GpgOL ribbon** tab
-4. Send your email
-
-> ✉️ Outlook will encrypt the email contents using the recipient's public key.
-
-### 📥 Decrypting an Email in Outlook
-
-When receiving an encrypted message:
-
-- GpgOL will automatically prompt to decrypt it using your private key
-- You may need to enter your key passphrase
-
-> 💡 Tip: Manage keys with **Kleopatra** — launch from Start Menu
-
----
-
-## 🔹 Option B: Thunderbird (Windows/macOS/Linux)
-
-Thunderbird includes **built-in OpenPGP** support and is often preferred for privacy-focused users.
-
-### ✅ Setup
-
-1. [Download Thunderbird](https://www.thunderbird.net)
-2. Add your email account
-3. Go to: `Account Settings → End-to-End Encryption`
-4. Generate a new key, or import your existing one
-5. Import your recipient’s **public key**
-
-### 🔐 Sending Encrypted Email
-
-When composing a message:
-
-- Click the **padlock** icon to enable encryption
-- Click **sign** if you also want to verify authenticity
-- Send as usual
-
----
-
-## 🔹 Option C: Webmail with Mailvelope
-
-**Mailvelope** adds OpenPGP support to Gmail, Outlook.com, Yahoo, and others.
-
-### 🔧 Setup
-
-1. Install [Mailvelope](https://www.mailvelope.com/) for Chrome or Firefox
-2. Import your keys or generate a new pair
-3. Use the Mailvelope overlay when composing encrypted emails
-
----
-
-## Alternative PGP-Compatible Email Clients
-
-In addition to widely used options like Outlook (via GpgOL) and Thunderbird, several other desktop email clients offer OpenPGP support—either natively or through plugins.
-
-Notable alternatives include:
-
-- **[Betterbird](https://www.betterbird.eu/):**  
-  A privacy-focused Thunderbird fork with full PGP support.  
-  ▸ Available on Windows, Linux, and macOS.
-
-- **[eM Client](https://www.emclient.com/):**  
-  A feature-rich client with native OpenPGP integration and calendar/task support.  
-  ▸ Available on Windows, macOS, Android, and iOS.  
-  ▸ _Free tier supports 2 email accounts after a 30-day trial._
-
-> 💡 **Note:** Be sure to verify the client’s compatibility with your GPG keyring (e.g., Gpg4win or Kleopatra on Windows).
-
----
-
-## 📱 Mobile Email Clients with OpenPGP Support
-
-For secure email on Android, the following apps support OpenPGP encryption via [**OpenKeychain**](https://www.openkeychain.org/):
-
-- **[FairEmail](https://email.faircode.eu/)**  
-  A lightweight, privacy-first email client for Android, offering built-in OpenPGP support, rich customization, and a modern, privacy-respecting interface.
-
-- **[K-9 Mail](https://k9mail.app/)**  
-  A veteran open-source Android mail client known for its simplicity and transparency. K-9 is now maintained by the Thunderbird team as part of their mobile strategy.
-
-- **[Thunderbird Mobile](https://www.thunderbird.net/en-US/mobile/)**  
-  A mobile adaptation of Thunderbird, currently built on K-9 Mail and maintained by the same team. Provides end-to-end encryption and an open-source, user-friendly experience.
-
-> ⚠️ OpenPGP support on iOS is limited due to platform restrictions.  
-> Most options are proprietary or require external tools, and may not provide full compatibility with standard PGP workflows.
-
----
-
-## 📤 Exporting and Sharing Public Keys
-
-You can export your public key from **Kleopatra**, Thunderbird, or the command line, and share it via:
-
-- Your website
-- A keyserver (e.g., [keys.openpgp.org](https://keys.openpgp.org))
-- Your GitHub profile (e.g., in `SECURITY.md` or a `PGP-KEY.asc` file)
-
-### 🔧 Export via Command Line
-
-If you’re using GnuPG directly:
-
-```sh
-gpg --armor --export your@email.com > publickey.asc
-```
-
-This creates a text-formatted (`.asc`) version of your public key that’s easy to upload or embed.
-
-> 💡 Replace `your@email.com` with the email associated with your PGP key.
-
----
-
-## 🛠 Troubleshooting Tips
-
-- Ensure email address in key matches recipient’s address
-- Key must be **trusted/imported** before encryption works
-- For Outlook, restart if GpgOL ribbon does not appear
-- Thunderbird may require re-indexing of OpenPGP keyring
-
----
-
-## 📚 Learn More
-
-- [Gpg4win Documentation](https://gpg4win.org/documentation.html)
-- [How to Encrypt Emails with OpenPGP in Thunderbird (2022)](https://www.linuxbabe.com/security/encrypt-emails-gpg-thunderbird)
-- [Mozilla OpenPGP Docs](https://support.mozilla.org/en-US/kb/openpgp-thunderbird-how-does-it-work)
-- [Mailvelope Overview](https://www.mailvelope.com/help)
-
----
-
-> 🔐 PGP protects your communication, but both parties must be using it correctly. Always test before sending sensitive content.

package/static/docs/pgp-win.md

@@ -1,67 +0,0 @@
-# 💻 Using PGP on Windows (Gpg4win & Kleopatra)
-
-## This section walks through encrypting a message or file using **Gpg4win** and its GUI tool **Kleopatra**
-
-### 📦 1. Install Gpg4win
-
-- Download from: [https://gpg4win.org](https://gpg4win.org)
-- During setup, make sure **Kleopatra** is selected.
-
----
-
-### 🔑 2. Import the Recipient’s Public Key
-
-1. Open **Kleopatra**
-2. Click `File` → `Import Certificates…`
-3. Select the `.asc` or `.gpg` file you downloaded
-4. Confirm the fingerprint matches the published value
-
----
-
-### ✍️ 3. Encrypt a Message (Text)
-
-1. In Kleopatra, go to `Tools` → `Clipboard` → `Encrypt`
-2. Paste your message
-3. Select the recipient’s public key
-4. Click **Encrypt**
-5. Copy or save the armored output (begins with `-----BEGIN PGP MESSAGE-----`)
-
-You can now send that encrypted message via email or any communication platform.
-
----
-
-### 📁 4. Encrypt a File
-
-1. Right-click on any file (e.g., PDF or TXT)
-2. Choose **More GpgEX options** → **Encrypt**
-3. Select the recipient key
-4. The encrypted file will be saved with a `.gpg` extension
-
----
-
-### 🔓 5. Decrypt a Message or File
-
-To decrypt a file:
-
-- Right-click `.gpg` file → **Decrypt and verify**
-
-To decrypt a clipboard message:
-
-- In Kleopatra, go to `Tools` → `Clipboard` → `Decrypt/Verify`
-- Paste the encrypted message
-- Kleopatra will prompt for your private key if needed
-
----
-
-### 🧠 Tips for Windows Users
-
-- Your private key is protected by a passphrase — never share it.
-- You can export your public key for others to encrypt messages to you.
-- Kleopatra also supports **signing** files and messages to verify your identity.
-
----
-
-📘 For full walkthroughs, see:
-
-- [Gpg4win Documentation](https://gpg4win.org/documentation.html)
-- [Kleopatra User Guide (PDF)](https://files.gpg4win.org/doc/gpg4win-compendium-en.pdf)

package/static/docs/pgp.md

@@ -1,71 +0,0 @@
-# 🔐 How to Encrypt Messages Using PGP
-
-This guide explains how to encrypt a message or file using PGP (Pretty Good Privacy) for secure communication with **Network Pro Strategies** or any contact with a published PGP key.
-
----
-
-## 📥 1. Obtain the Recipient's Public Key
-
-You can find the official public key at:
-
-- [https://netwk.pro/pgp](https://netwk.pro/pgp)
-- Or via GitHub, Keybase, or direct contact
-
-Make sure the key fingerprint matches what the recipient advertises.
-
----
-
-## 🔧 2. Import the Public Key
-
-Save the public key as a `.asc` or `.gpg` file, then run:
-
-```bash
-gpg --import path/to/public-key.asc
-```
-
-You can confirm the key is imported:
-
-```bash
-gpg --list-keys
-```
-
-## 🔏 3. Encrypt a Message
-
-To encrypt a plain text file (e.g. message.txt) for the recipient:
-
-```bash
-gpg --encrypt --armor --recipient recipient@example.com message.txt
-```
-
-- --armor creates ASCII-formatted output
-- Output is saved as message.txt.asc
-
-## 🔏 4. Encrypt a File (Binary or Attachment)
-
-```bash
-gpg --encrypt --recipient recipient@example.com file.pdf
-```
-
-This will create file.pdf.gpg, which you can send securely.
-
-## 🔓 Optional: Decrypting (For Testing)
-
-If you're the recipient and want to decrypt a file:
-
-```bash
-gpg --decrypt file.txt.asc
-```
-
-## 🔐 Tips
-
-- Always verify the recipient’s key fingerprint.
-- Never share your private key.
-- Use a strong passphrase to protect your keypair.
-
----
-
-📘 For more help, see:
-
-- [GnuPG Documentation](https://gnupg.org/documentation/)
-- [A Practical Guide to GPG](https://www.linuxbabe.com/security/a-practical-guide-to-gpg-part-1-generate-your-keypair)
-- [OpenPGP Best Practices](https://help.riseup.net/en/security/message-security/openpgp/best-practices)

package/static/docs/tracking.md

@@ -1,63 +0,0 @@
-# Tracking Preferences & Privacy Signals
-
-<!-- markdownlint-disable MD018 -->
-
-## Overview
-
-This document explains how Network Pro handles analytics tracking in a privacy-aware, user-consented, and standards-compliant manner. It covers:
-
-- Tracking preference storage (cookies)
-- Browser signals (DNT and GPC)
-- Reconsent logic
-- Reactive store architecture
-
-### 🔐 Principles
-
-- **Privacy by default**: Tracking is disabled when browser signals indicate user preference (DNT/GPC).
-- **Explicit consent**: Users may opt-in or opt-out manually, overriding signals.
-- **Persistent choice**: Consent state is remembered via first-party cookies.
-- **Transparency**: The tracking status is shown to users in the UI.
-
-### 🧠 Architecture Summary
-
-- **Store**: `src/lib/stores/trackingPreferences.js`
-  - Consolidates logic for cookie preferences, browser signals, and consent state.
-  - SSR-safe, reactive, and fully declarative.
-- **Deprecated**:
-  - `utils/privacy.js` → replaced by derived store logic.
-  - `utils/trackingCookies.js` → merged into the store with SSR-safe cookie APIs.
-
-### Reactive State
-
-| Store                   | Type                      | Description                                                             |
-| ----------------------- | ------------------------- | ----------------------------------------------------------------------- |
-| `trackingPreferences`   | `Readable<TrackingState>` | Contains current tracking metadata (opt-in/out, DNT, GPC, status, etc). |
-| `trackingEnabled`       | `Writable<boolean>`       | Exposed to toggle or query PostHog tracking state reactively.           |
-| `remindUserToReconsent` | `Readable<boolean>`       | Indicates whether a consent renewal prompt should be shown.             |
-| `showReminder`          | `Writable<boolean>`       | Used by PostHog to conditionally display a reminder or banner.          |
-
-### ⏳ Reconsent Logic
-
-The derived store `remindUserToReconsent` evaluates whether a user should be reminded to re-consent to tracking.
-
-It checks for:
-
-- Manual opt-in or opt-out
-- A valid `tracking_consent_timestamp` cookie
-- Whether 6+ months have elapsed since that timestamp
-
-### ⚙️ Developer Notes
-
-- Changes to tracking preferences update cookies and reactive state
-- Reconsent timestamp is written/cleared via store utility functions
-- Use `$trackingPreferences` and `remindUserToReconsent` wherever reactive values are needed
-
-### 💡 Related Components
-
-| File                            | Purpose                                                                          |
-| ------------------------------- | -------------------------------------------------------------------------------- |
-| `+layout.svelte`                | Initializes PostHog client and service worker; references `trackingPreferences`. |
-| `PrivacyDashboard.svelte`       | UI control panel for opt-in/out toggles and consent status display.              |
-| `PrivacyContent.svelte`         | Informational content rendered in modals, footers, and standalone pages.         |
-| `stores/trackingPreferences.js` | Primary source of truth; tracks and derives tracking state.                      |
-| `stores/posthog.js`             | Encapsulates privacy-safe analytics setup and event capture logic.               |