ultimate-jekyll-manager 1.9.5 → 1.9.7

package/_notes/TODO-FileStructure.md

@@ -1,249 +0,0 @@
-⏺ Based on my analysis, here's my comprehensive naming and organization proposal for your Ultimate Jekyll
-  template system:
-
-  Proposed Naming Convention
-
-  1. Layouts Structure
-
-  _layouts/
-  ├── core/              # (was: main/global/)
-  │   └── root.html      # (was: default.html) - Base HTML skeleton
-  ├── themes/            # Keep as-is - theme-specific layouts
-  │   └── {theme}/
-  │       ├── shell.html # (was: base.html) - Theme's main wrapper
-  │       ├── page.html  # (was: default.html) - Standard pages
-  │       ├── legal.html # Keep as-is - Legal pages
-  │       ├── blog.html  # Blog layouts
-  │       └── modal.html # (was: fullscreen.html) - Modal/overlay layouts
-  └── blueprints/        # (was: placeholder/) - Content templates
-      ├── legal/
-      │   ├── terms.md
-      │   └── privacy.md
-      └── blog/
-          ├── index.html
-          └── post.html
-
-  2. Includes Structure
-
-  _includes/
-  ├── parts/             # (was: components/global/) - Core page parts
-  │   ├── head.html
-  │   ├── body.html
-  │   ├── foot.html
-  │   ├── nav.html
-  │   └── footer.html
-  ├── widgets/           # (was: modules/) - Reusable components
-  │   ├── ads/           # (was: adunits/)
-  │   ├── forms/         # Contact forms, signups
-  │   ├── cards/         # Card components
-  │   └── media/         # Images, videos, embeds
-  └── themes/            # Keep as-is - theme-specific includes
-      └── {theme}/
-          └── blocks/    # (was: sections/) - Theme blocks
-
-  3. Assets Structure
-
-  assets/
-  ├── themes/
-  │   ├── _base/         # (was: _template/) - Base theme template
-  │   │   ├── theme.js   # (was: _theme.js)
-  │   │   ├── theme.scss # (was: _theme.scss)
-  │   │   ├── js/
-  │   │   └── scss/
-  │   └── {theme}/       # Actual themes
-  │       ├── theme.js
-  │       ├── theme.scss
-  │       ├── js/
-  │       └── scss/
-  ├── css/
-  │   ├── core.scss      # (was: ultimate-jekyll-manager.scss)
-  │   ├── main.scss      # User's main styles
-  │   └── pages/         # Page-specific styles
-  └── js/
-      ├── core.js        # (was: ultimate-jekyll-manager.js)
-      ├── main.js        # User's main scripts
-      └── pages/         # Page-specific scripts
-
-  Key Benefits of New Names
-
-  1. core/root.html - Makes it clear this is the foundational HTML document
-  2. shell.html - Better describes a theme's outer wrapper than "base"
-  3. blueprints - Clearer than "placeholder" for content templates
-  4. parts - More intuitive than "components" for page sections
-  5. widgets - Better describes reusable UI components than "modules"
-  6. blocks - Clearer than "sections" for theme-specific content blocks
-  7. _base - More descriptive than "_template" for the theme template
-
-  Hierarchy Flow Example
-
-  Using the terms page example:
-  1. src/pages/legal/terms.md → uses layout blueprints/legal/terms
-  2. blueprints/legal/terms.md → uses layout themes/bootstrap/legal
-  3. themes/bootstrap/legal.html → uses layout themes/bootstrap/shell
-  4. themes/bootstrap/shell.html → uses layout core/root
-  5. core/root.html → includes parts/head, parts/body, parts/foot
-
-  Additional Organizational Improvements
-
-  1. Remove __temp directory - Clean up legacy files
-  2. Standardize file extensions - Use .html consistently (no .html copy)
-  3. Create a docs/architecture.md - Document the naming system
-  4. Add .keep files - In empty directories to maintain structure
-  5. Theme consistency - Ensure all themes follow the same structure
-
-  This naming system uses single, descriptive words that clearly indicate each component's purpose while
-  maintaining the flexibility for users to create their own layouts without conflicts.
-
-⏺ Update Todos
-  ⎿  ☒ Analyze current template structure and naming patterns
-     ☒ Examine the layout hierarchy and component relationships
-     ☒ Propose new naming conventions for layouts, includes, and components
-     ☒ Suggest organizational improvements for the directory structure
-
-> ok what should i name "src/defaults/dist/_layouts/modules/redirect.html"? I have
-  "src/defaults/dist/_includes/modules/adunits/adsense.html" notice how it is in an adsense subfolder. give me subfolder name
-
-⏺ Looking at your structure and the new naming convention I proposed, for src/defaults/dist/_layouts/modules/redirect.html, I would
-   suggest:
-
-  src/defaults/dist/_layouts/utilities/redirect/redirect.html
-
-  Or if you want to keep it flatter:
-
-  src/defaults/dist/_layouts/utilities/redirect.html
-
-  The reasoning:
-  - utilities better describes technical/functional layouts (like redirects) vs content layouts
-  - It follows the pattern of your _includes/modules/adunits/adsense.html where the subfolder (adunits) categorizes the type
-  - Other utilities might include: utilities/error/404.html, utilities/maintenance/maintenance.html, etc.
-
-  If you specifically want just the subfolder name: utilities
-
-╭─────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────╮
-│ >                                                                                                                           │
-╰─────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────╯
-  ? for shortcuts                                                                                          ◯ IDE disconnected
-
-
-
-NEW
-
-⏺ Great question! For organizing layouts within a theme's frontend folder, I suggest a hybrid approach that groups related
-   layouts while keeping commonly-used ones at the root level:
-
-  src/defaults/dist/_layouts/themes/bootstrap/frontend/
-  ├── base.html          # Keep at root - the main theme wrapper
-  ├── page.html          # Keep at root - standard content pages
-  ├── modal.html         # Keep at root - fullscreen/modal layouts
-  ├── pages/             # Specific page-type layouts
-  │   ├── legal.html     # Legal pages (terms, privacy)
-  │   ├── contact.html   # Contact form pages
-  │   ├── error.html     # Error pages (404, 500)
-  │   ├── blog.html      # Blog listing/archive
-  │   └── post.html      # Individual blog posts
-  └── formats/           # Alternative content formats
-      ├── bare.html      # Minimal layout (no nav/footer)
-      ├── print.html     # Print-optimized layout
-      └── embed.html     # For embedded content
-
-  Rationale:
-  1. Root level - Keep the most fundamental layouts (base, page, modal) easily accessible
-  2. pages/ subfolder - Group content-specific layouts that correspond to actual page types
-  3. formats/ subfolder - Group presentation variants that could apply to any content
-
-  This way:
-  - base.html remains the foundation all others extend from
-  - Common layouts are easy to find at the root
-  - Specific page layouts are logically grouped
-  - It's clear where to add new layouts as the theme grows
-
-  For your current files:
-  - legal.html → pages/legal.html
-  - fullscreen.html → modal.html (at root, since it's a common pattern)
-
-
-
-
-
-
-
-
-
-
-
-ok so for the theme-specific layouts, theres a  couple things and that leads me to a question
-
-So a theme's layouts will live in a folder like (for frontend) "src/defaults/dist/_layouts/themes/bootstrap/frontend"
-- A theme will always have a base.html layout that is the main layout for all pages in that theme
-- However, the placeholder/blueprint pages will need to use specific layouts like legal.html "src/defaults/dist/_layouts/themes/bootstrap/frontend/legal.html" and eventually even more like a 404 layout, a contact layout etc.
-- but there are also some more generic layouts like "src/defaults/dist/_layouts/themes/bootstrap/frontend/fullscreen.html"
-
-HOW DO I ORGANIZE THESE LAYOUTS inside a theme?
-
-
-
-
-
-
-
-
-
-I need help re-organizing some things in my lib.
-
-Review "src/gulp/tasks/webpack.js" to see how the files are being bundled and loaded and the path aliases used.
-
-src/assets/js/ultimate-jekyll-manager.js
-* This is the file that the CONSUMING project will load
-
-src/assets/js/utilities
-* This directory is DIRECTLY COPIED to the CONSUMING project so that scripts SUCH AS "src/assets/js/utilities/popupads.js" can be DIRECTLY LOADED IN A SCRIPT TAG (no webpack is run on these files)
-
-src/assets/js/libs
-* This directory is not copied to the consuming project OR packed with webpack. It is JUST FILES THAT ARE IMPORTED BY THE ULTIMATE JEKYLL LIBRARY ITSEF. An example is "src/assets/js/libs/dev.js" which is imported during development and has some logging and debugging features.
-
-NOW HERES THE PART I NEED HELP WITH:
-
-1. I have "src/assets/js/redirect.js" which is loaded by "src/defaults/dist/_layouts/modules/utilities/redirect.html". I would like it to be WEBPACKED but i want to put it in a folder that is AUTOMATICALLY WEBPACKED that is distinctly separate from the main library. I need help naming that folder or deciding on a better strategy for this.
-2. While youre at it, help me decide if "src/assets/js/libs" and "src/assets/js/utilities" are good names or if they should be changed.
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-{% assign page-url-stripped = page.url | replace: 'index.html', '' %}
-{%- if page-url-stripped == '/' -%}
-  {% assign page-url-stripped = '' %}
-{% endif %}
-
-page.canonical: {{ page.canonical }}|
-
-            {% capture action_icon %}{% if action.icon %}{{ site.icons[action.icon] }}{% endif %}{% endcapture %}
-
-METHOD 1
-html class=h-100
-body class=d-flex flex-column h-100
-main class=flex-shrink-0
-footer class=mt-auto
-
-METHOD 2
-html class=
-body class=d-flex flex-column min-vh-100
-main class=flex-fill
-footer class=
-
-
-DONT FORGET THE FLOW (goes from top to bottom)
-
-│   src/defaults/dist/_layouts/placeholder/app.html\                                                    │
-│   src/defaults/dist/_layouts/themes/bootstrap/frontend/fullscreen.html\                               │
-│   src/defaults/dist/_layouts/themes/bootstrap/frontend/core/base.html\                                     │
-│   src/defaults/dist/_layouts/core/root.html\

package/_notes/TODO-checkout.md

@@ -1,33 +0,0 @@
-Build a checkout page @ src/defaults/dist/_layouts/themes/bootstrap/frontend/pages/purchase/checkout.html
-CSS: src/assets/css/pages/purchase/checkout/index.scss
-JS: src/assets/js/pages/purchase/checkout/index.js
-If you need inspiration for how to build a page, look at src/defaults/dist/_layouts/themes/bootstrap/frontend/pages directory.
-* Use bootstrap 5.3.1
-
-The checkout page should include:
-* cards and sections for each step of the checkout process
-* a summary of the items being purchased
-* a place for a discount code (if user enters a correct code, apply discount)
-* Support multiple payment methods (credit card, PayPal, Cypto.)
-
-* We should be able to get a JSON object and dynamically alter the page contents, like adding some form fields
-* when the user lands on the page, a query parameter with the product id is there to help us load the product details.
-* use the product ID along with the {{ site.brand.app}} id to make a fetch request to https://api.itwcreativeworks.com/app/{app id} to get the product details, price, etc, (its in the response.products[product_id] key), use test data for now. but add the fetch request and jsut assume we use the test data no matter what.
-* the product data will also include whether it is a subscription or one-time purchase.
-* if its a subcripiton were gonna display some slighly different UI,
-  * like a toggle for monthly or yearly billing (and show the prices ad how much they are saving by using the yearly billing option)
-  * a message that either says "YOu are eligible for a free trial" or "You are not eligible for a free trial" based on the product data in green or red ralert espectively.
-  * A message like "You will be charged $X {monthky/annually} starting on {date}" if they have a free trial, or "You will be charged $X today and {annually\monthly} starting {date}" if they do not have a free trial.
-
-* IN JS, we should calculate the price after the discount code is applied, and update the total price dynamically, consider also whether they are elgiible for a free trial.
-
-* A banner that is fixed to the top of the page that says "FLash sale! Use code FLASH20 for 20% off your purchase!".
-
-Next, build a quick /purchase/confirmation.html,
-* The confirmation page should show a summary of the purchase and a thank you message.
-
-
-
-
-
-and a /purchase/cart.html that just redirects to the checkout page for now and is meant for sending analytics events and ensuring the user is signed in.

package/_notes/TODO-frontend.md

@@ -1,61 +0,0 @@
-Frontend TODO
-- sentry in WM
-- chatsy
-  - remake chatsy into a module that we can install here and then users can load it via cdnjs instead of our website
-- contact form with tracking and form-manager and slapform
-
-- save utm tags, send during checkout, signup, etc
-
-- token redirect for auth system (for auth with desktop apps, etc)
-
-ensure blog, article, posts, etc all use proper HTML semantics tags, aria, etc
-
-js refactor
-- make all fns await asyn operations
-- order the fn definitions in the order they are called (most import/toplevel first then the rest. put all tracking fns at the bottom)
-- move export to top and do not use init() fn, just call all fns inside dom.ready OR the main export (depends on the structure)
-- track errors w sentry, not ga4/fb/tiktok
-- add Manager, options back to each index.js for standardization
-- for stanndardization, also ALWAYS set webManager = Manager.webManager in the index.js
-
-pages
-- blog + post
-- about
-- contact
-- team + member
-- extension and download
-
-MAKE OUR CUSTOM THEME CLASSY!!
-
-for pages like pricing, home, about etc
-- put default frontmatter in the default pages so user can override
-
-NEW PLAN NAME STANDARD
-1. Basic, Starter, Pro, Max
-1. Basic, Starter, Plus, Pro
-
-Implement account resolver
-
-https://docs.stripe.com/payments/link/express-checkout-element-link
-
-// // Load page specific scripts
-// if (url.includes('/pricing')) {
-//   dom.loadScript({src: 'https://cdn.itwcreativeworks.com/assets/general/js/pricing-page-handler/index.js'})
-// } else if (url.includes('/download')) {
-//   dom.loadScript({src: 'https://cdn.itwcreativeworks.com/assets/general/js/download-page-handler/index.js'})
-// } else if (url.includes('/browser-extension') || url.includes('/extension')) {
-//   dom.loadScript({src: 'https://cdn.itwcreativeworks.com/assets/general/js/browser-extension-page-handler/index.js'})
-// } else if (window.location.pathname.endsWith('.html')) {
-//   // Redirect and remove .html
-//   window.location.pathname = window.location.pathname.replace('.html', '');
-// }
-
-
-
-// // Save user auth data
-// Manager.auth().ready(function (user) {
-//   setupTracking(user);
-
-//   storage.set('user.auth.uid', user.uid);
-//   storage.set('user.auth.email', user.email);
-// })

package/_notes/TODO-legacy.md

@@ -1,18 +0,0 @@
-Make themes layout folder
-geeks (with subfolders)
-- frontend
-- backend
-- docs
-
-global changes
-- rename placeholder files
-  layout: themes/placeholder --> layout: themes/placeholder
-
-- mayeb actually move placeholder outside of themes?
-- maybe move themes into master? idk
-
-- fix auth-signedin-false-element
-- auth-state-listener = loading, signedin, signedout
-dashboard-status-listenerdata-status="success"
-
-- make plugins for each theme, like navbar account dropdown?

package/_notes/TODO-template-system.md

@@ -1,73 +0,0 @@
-I have this tempalte system setup so making sites instantly is possible, with the option to further customize each page. It takes advantage of a multi-tier theme system.
-
-Here's an example:
-
-src/defaults/src/pages/legal/terms.md
-* This page is autmatically created in the CONSUMING project's pages at pages/legal/terms.md
-* You can see it uses "placeholder/legal/terms" layout
-
-src/defaults/dist/_layouts/placeholder/legal/terms.md
-* This is the layout used by the page above
-* Looking at it, you can see it uses a SECOND layout "themes/[ site.theme.id ]/frontend/default"
-* The theme ID is dynamically inserted by the gulp preprocessor as set in _config.yml
-
-src/defaults/dist/_layouts/themes/bootstrap/frontend/default.html
-* This is the layout used by the page above (in this example, the bootstrap theme)
-* You can see that it includes a nav.html and footer.html as well as the {{ content }} tag (special processing for markdown vs HTML using a custom "page.extension" check)
-
-What i want to do is create some more layouts in the "src/defaults/dist/_layouts/themes/bootstrap/frontend" directory, such as a legal layout, which would be used by terms, privacy, and cookies pages.
-
-Can you help me create the legal layout and do it in a way that doesnt duplicate too much existing code? Can we somehow take advantage of the existing default.html layout?
-
-I want to make even more layouts, such as a "full screen" layout that that would be for pages that want the content to be centered and take up the full width and height of the screen with no header or footer, just the content.
-
-
-
-
-
-
-
-
-
-
-
-
-
-I have this tempalte system setup so making sites instantly is possible, with the option to further customize each page. It takes advantage of a multi-tier theme system.
-
-Here's an example:
-
-src/defaults/src/pages/legal/terms.md
-* This page is autmatically created in the CONSUMING project's pages at pages/legal/terms.md
-* You can see it uses "placeholder/legal/terms" layout
-
-src/defaults/dist/_layouts/placeholder/legal/terms.md
-* This is the layout used by the page above
-* Looking at it, you can see it uses a SECOND layout "themes/[ site.theme.id ]/frontend/legal"
-* The theme ID is dynamically inserted by the gulp preprocessor as set in _config.yml
-
-src/defaults/dist/_layouts/themes/bootstrap/frontend/legal.html
-* Uses "themes/bootstrap/frontend/core/base"
-
-src/defaults/dist/_layouts/themes/bootstrap/frontend/core/base.html
-* Uses "core/root"
-
-src/defaults/dist/_layouts/core/root.html
-* Includes "components" src/defaults/dist/_includes/core/body.html, src/defaults/dist/_includes/core/nav.html, src/defaults/dist/_includes/core/footer.html
-* This is the final layout that is used to render the page and includes all the head meta tags styles, scripts, and some body html like modals and warnings that are dynamically displayed.
-
-
-Each theme should have a central file that the various other theme layouts use, like in this example
-* "src/defaults/dist/_layouts/themes/bootstrap/frontend/legal.html" USES "themes/bootstrap/frontend/core/base.html"
-
-Each theme's central file will always use "core/root.html"
-* And this file will always include the components that are used by all themes, like the header, footer, and body.
-
-
-I need your help naming ALL these things because i feel like my names are not really fitting or consistent. AND ALSO ORGANIZING THEM.
-
-I initially organized the "themes" and "main" layouts in their own folders because this leaves the ability for the user to created layouts that DONT CONFLICT with the ULTIMATE JEKYLL template layouts.
-
-The only requirement is that each "name" is a SINGLE word. I like short descriptive words.
-
-So for example, i feel like "default" and "base" and "global" are all thrown around a lot and not consistent. Very confusing.

package/_notes/TODO-theme.md

@@ -1,17 +0,0 @@
-> Im going to have you build a custom bootstrap theme. We are using bootstrap 5.3.1.
-
-  The theme is called Classy, you can make your changes to "src/assets/themes/classy/_theme.scss"
-
-
-  The theme is a simple, yet modern, clean, and elegant design suitable for various types of websites, but
-  witha primary focus on modern tech, AI, and marketing.
-
-  I've attached some screenshots of the design for reference, go crazy and make it SUPER SEXY!
-
-  [Image #1]\
-  notice how when you scroll, the top bar stays withy ou and also shrinks a little\
-  [Image #2]\
-  [Image #3]\
-  \
-  Since we're using bootstrap, DO NOT MAKE CUSTOM CSS FOR ANYTHING UNLESS ABSOILUTELY NECESSARY. Obviously,
-  you can make it for the visual changes but DO NOT REINVENT THE WHEEL!

package/logs/test.log

@@ -1,144 +0,0 @@
-# ujm log — 2026-06-22T21:31:38.629Z — pid=3348
-[14:31:38] 'test': Running tests (layer=all)
-[14:31:38] 'test': Test mode: normal (external APIs skipped)
-
-  Ultimate Jekyll Manager Tests
-
-  Framework Tests
-    ⤷ attach-log-file — tee stdout/stderr to a file
-      ✓ exports the expected surface (0ms)
-      ✓ stripAnsi removes color escape codes (0ms)
-hello world
-colored line
-      ✓ attach + stdout.write + detach: file contains the writes (0ms)
-      ✓ idempotent: attaching twice with same name returns same fd (1ms)
-      ✓ attach with falsy name returns null and does nothing (0ms)
-    ⤷ CLI alias resolution
-      ✓ cli.js exports a Main class (0ms)
-      ✓ all expected commands exist on disk (0ms)
-      ✓ each command module exports an async function (4ms)
-    ⤷ collectTextNodes (utils/collectTextNodes.js)
-      ✓ extracts page title (101ms)
-      ✓ skips <script> and <style> (0ms)
-    ✓ spellcheck dictionary (utils/dictionary.js) (0ms)
-    ⤷ expect() matcher set
-      ✓ toBe + toEqual basics (0ms)
-      ✓ .not negates (0ms)
-      ✓ toContain works on arrays and strings (0ms)
-      ✓ toThrow catches sync + async throws (0ms)
-      ✓ toBeGreaterThan / toBeLessThan (0ms)
-      ✓ failing assertions throw AssertionError (0ms)
-    ✓ package.json exports resolve to real files in dist/ (0ms)
-    ⤷ Logger (src/lib/logger.js)
-      ✓ Logger constructor stores name (0ms)
-      ✓ Logger exposes log/error/warn/info methods (0ms)
-      ✓ Logger.format is chalk (0ms)
-      ✓ Logger output goes through console with prefix (0ms)
-    ⤷ Manager (build.js) public surface
-      ✓ Manager constructor is a function (0ms)
-      ✓ static methods match prototype methods (0ms)
-      ✓ isBuildMode reflects UJ_BUILD_MODE env (0ms)
-      ✓ isQuickMode reflects UJ_QUICK env (0ms)
-      ✓ isServer reflects UJ_IS_SERVER env (0ms)
-      ✓ getEnvironment maps to development/testing/production (0ms)
-      ✓ actLikeProduction is true when isBuildMode OR UJ_AUDIT_FORCE (0ms)
-      ✓ getRootPath("package") points at UJM root (0ms)
-      ✓ getMemoryUsage returns shape with MB-sized numbers (0ms)
-      ✓ getArguments returns object with _ array + boolean defaults (1ms)
-      ✓ logger returns object with log/error/warn/info methods (0ms)
-      ✓ processBatches processes items in chunks and returns flat results (0ms)
-    ⤷ mergeJekyllConfigs (utils/merge-jekyll-configs.js)
-      ✓ merges collections from both configs (project additions win) (3ms)
-      ✓ dedups defaults by scope key (project wins) (1ms)
-      ✓ returns null when there is nothing to merge (0ms)
-    ⤷ mode-helpers (isTesting / isDevelopment / isProduction / getVersion)
-      ✓ helpers attach to Manager statically AND on prototype (1ms)
-      ✓ isTesting reflects UJ_TEST_MODE env (0ms)
-      ✓ isDevelopment false / isProduction true when UJ_BUILD_MODE=true (and not testing) (0ms)
-      ✓ environments are mutually exclusive — testing wins under UJ_TEST_MODE (0ms)
-      ✓ invariant: is*() exactly matches getEnvironment() + mutually exclusive (every scenario) (0ms)
-      ✓ getVersion returns a non-empty string when run from a package (0ms)
-    ⤷ createTemplateTransform (utils/template-transform.js)
-      ✓ replaces [site.theme.id] with config value in .html files (1ms)
-      ✓ leaves non-matching extensions untouched (e.g. .css) (0ms)
-      ✓ passes directories through untouched (0ms)
-    ⤷ node-powertools templating brackets ({} and [])
-      ✓ default { } brackets resolve nested keys (0ms)
-      ✓ [ ] brackets resolve nested keys when explicitly configured (0ms)
-      ✓ [ ] brackets leave Jekyll {{ }} placeholders alone (0ms)
-    ⤷ theme contract (structure, swappability, cross-theme JS contracts)
-      ✓ _template: entry files + config contract (1ms)
-      ✓ classy: entry files + config contract (0ms)
-      ✓ neobrutalism: entry files + config contract (1ms)
-      ✓ newsflash: entry files + config contract (0ms)
-      ✓ _template: layouts swappable, markup clean (1ms)
-      ✓ classy: layouts swappable, markup clean (15ms)
-      ✓ neobrutalism: layouts swappable, markup clean (1ms)
-      ✓ newsflash: layouts swappable, markup clean (4ms)
-      ✓ _template: cross-theme JS contracts (0ms)
-      ✓ classy: cross-theme JS contracts (0ms)
-      ✓ neobrutalism: cross-theme JS contracts (1ms)
-      ✓ newsflash: cross-theme JS contracts (0ms)
-      ✓ page asset files match a declared asset_path shape (3ms)
-    ⤷ validateYAMLFrontMatter (utils/_validate-yaml.js)
-      ✓ returns { valid: true } for a file with valid frontmatter (0ms)
-      ✓ returns { valid: true } when no frontmatter present (1ms)
-      ✓ flags malformed YAML frontmatter as invalid with error message (0ms)
-    ⤷ page-layer baseline (DOM + fetch + storage)
-      ✓ document is interactive or complete (1ms)
-      ✓ fetch() works against the local harness server (7ms)
-      ✓ localStorage is available (1ms)
-    ⤷ FormManager getData / setData / input groups
-      ✓ _setNested builds nested objects from dot paths (1ms)
-      ✓ _setNested accumulates duplicate keys into arrays (0ms)
-      ✓ _getNested reads nested values and returns undefined for missing paths (0ms)
-      ✓ _flattenObject converts nested objects to dot paths (1ms)
-      ✓ getData collects text, select, radio, and textarea values with dot notation (5ms)
-      ✓ getData handles single checkbox (boolean) and checkbox groups (object) (0ms)
-      ✓ getData excludes honeypot fields (0ms)
-      ✓ input group filter includes matching + global fields, excludes others (0ms)
-      ✓ input group filter with multiple groups includes all matching (0ms)
-      ✓ setData populates text, select, textarea fields (1ms)
-      ✓ setData sets radio group to matching value (0ms)
-      ✓ setData sets single checkbox boolean and checkbox group values (0ms)
-    ⤷ FormManager disabled-state snapshot
-      ✓ snapshot captures disabled non-submit elements, ignores submit buttons (1ms)
-      ✓ setDisabled(true) disables everything (0ms)
-      ✓ setDisabled(false) re-enables managed elements but keeps snapshotted ones disabled (0ms)
-      ✓ survives multiple disable/enable cycles (1ms)
-      ✓ onsubmit="return false" blocks native submission before FM loads (10ms)
-    ⤷ FormManager validation + honeypot + file-accept
-      ✓ required text field fails when empty, passes when filled (0ms)
-      ✓ required checkbox fails when unchecked (0ms)
-      ✓ required radio group fails when none checked (0ms)
-      ✓ email validation rejects invalid formats and accepts valid ones (1ms)
-      ✓ number min/max validation catches out-of-range values (2ms)
-      ✓ minlength and maxlength validation (0ms)
-      ✓ pattern attribute validation (0ms)
-      ✓ honeypot detection catches [data-honey] and [name="honey"] fields (0ms)
-      ✓ honeypot detects data-honey without name="honey" (0ms)
-      ✓ file-accept matching: extension, wildcard MIME, exact MIME (0ms)
-      ✓ field error display adds is-invalid class and feedback element (1ms)
-      ✓ query param population skips UTM/tracking params (0ms)
-      ✓ data-form-state attribute reflects state transitions (0ms)
-    ⤷ harness globals (window.Configuration + dataset)
-      ✓ window.Configuration has brand + theme + web_manager (0ms)
-      ✓ document.documentElement.dataset.pagePath is set (0ms)
-      ✓ UJ_TEST_MODE is signalled on globalThis (0ms)
-    ⤷ prerendered icons template lookup
-      ✓ template#prerendered-icons exists and has the test icon (1ms)
-      ✓ looking up a missing icon returns null (0ms)
-    ⤷ boot tests (consumer _site/)
-      ✓ /service-worker.js served with javascript content type (74ms)
-      ✓ index.html registers SW and reaches activated state (169ms)
-      ✓ SW responds to get-cache-name message with brand-id pattern (75ms)
-      ✓ home page renders with title + body content (176ms)
-      ✓ /about resolves via Jekyll-style .html fallback (67ms)
-      ✓ build.json is served with brand metadata (69ms)
-      ✓ CSS bundle served with text/css content type (62ms)
-
-  Results
-    110 passing
-
-    Total: 110 tests in 2945ms
-