jekyll-theme-zer0 1.29.0 → 1.31.0

data/_data/README.md

@@ -7,6 +7,8 @@ This directory contains YAML data files that power the Zer0-Mistakes Jekyll them
 | File | Purpose | Auto-Generated |
 |------|---------|----------------|
 | `navigation/` | Site navigation menus | No |
+| `ai.yml` | The one place the AI model is configured (read by the hub's `bamr87/bamr87/.github/actions/claude-run@main` runner, consumed by reference) | No |
+| `ai_pricing.yml` | API list prices used to *estimate* AI spend for calls that report tokens but no cost (part of the shared `ai-runner` kit) | No |
 | `authors.yml` | Author profile information | No |
 | `content_statistics.yml` | Site content analytics | **Yes** |
 | `roadmap.yml` | Single source of truth for the project roadmap (drives the README mermaid diagram and the `/roadmap/` Jekyll page) | No |

data/_data/ai.yml

@@ -1,9 +1,11 @@
 # =============================================================================
 # _data/ai.yml — one place the AI model is configured for zer0-mistakes agents
 # -----------------------------------------------------------------------------
-# Read by .github/actions/claude-run (the issue-autopilot's AI step). Change the
-# model here and every autopilot agent call uses it. Auth is NOT here — it comes
-# from the CLAUDE_CODE_OAUTH_TOKEN (preferred) or ANTHROPIC_API_KEY secret.
+# Read by the fleet's ai-runner kit — bamr87/bamr87/.github/actions/claude-run
+# (consumed by reference; the issue-autopilot's AI step). Change the model
+# here and every agent call uses it; AI_MODEL (or the action's `model` input)
+# overrides it for one run. Auth is NOT here — it comes from the
+# CLAUDE_CODE_OAUTH_TOKEN (preferred) or ANTHROPIC_API_KEY secret.
 # =============================================================================
 provider: anthropic
 model: claude-opus-4-8

data/_data/ai_pricing.yml

@@ -0,0 +1,36 @@
+# =============================================================================
+# ai_pricing.yml — API list prices used to ESTIMATE AI spend (per million tokens)
+# -----------------------------------------------------------------------------
+# The telemetry layer (scripts/ai/usage.rb) prefers the cost the Claude Code CLI
+# itself reports (`total_cost_usd`) — that number is authoritative and this file
+# is never consulted for it. This table exists for the paths that report tokens
+# but no dollars: the raw Claude API fallback (scripts/ai/api_call.rb) and any
+# execution log that predates cost reporting. Those records get cost_source:
+# "estimated", computed as
+#
+#   input×in + output×out + cache_read×(0.1×in)
+#     + cache_write_5m×(1.25×in) + cache_write_1h×(2×in)
+#
+# which reproduces the CLI's own arithmetic to the cent (validated 2026-07-14
+# against a live run). Prices are USD per MTok at standard API list rates —
+# subscription (OAuth) runs have no marginal dollar cost, so every published
+# figure is labeled "API-equivalent". Source: platform.claude.com/docs/en/pricing
+# (cached 2026-07-14). Update this file when Anthropic changes list prices;
+# estimates are marked as such everywhere they surface.
+# =============================================================================
+multipliers:
+  cache_read: 0.1        # × input price
+  cache_write_5m: 1.25   # × input price (5-minute TTL — the CLI default)
+  cache_write_1h: 2.0    # × input price (1-hour TTL)
+
+# Matched by longest model-id prefix, so dated snapshots (claude-haiku-4-5-20251001)
+# resolve to their family row. `default` catches unknown models (opus-tier, so an
+# unknown model over- rather than under-estimates).
+models:
+  claude-opus-4-8:   { input: 5.00,  output: 25.00 }
+  claude-opus-4-7:   { input: 5.00,  output: 25.00 }
+  claude-opus-4-6:   { input: 5.00,  output: 25.00 }
+  claude-sonnet-5:   { input: 3.00,  output: 15.00 }
+  claude-sonnet-4-6: { input: 3.00,  output: 15.00 }
+  claude-haiku-4-5:  { input: 1.00,  output: 5.00 }
+  default:           { input: 5.00,  output: 25.00 }

data/_data/backlog.yml

@@ -62,8 +62,8 @@
 
 meta:
   title: "zer0-mistakes Backlog"
-  updated: 2026-08-18
-  next_id: 46
+  updated: 2026-09-05
+  next_id: 52
 
 tasks:
   # --- Housekeeping (seeded so the loop has work on day one) ------------------
@@ -866,7 +866,7 @@ tasks:
 
   - id: T-033
     title: "Retire legacy test_installation.sh after equivalence audit against the installer harness"
-    status: open
+    status: done
     priority: P2
     area: tests
     risk: standard
@@ -880,6 +880,10 @@ tasks:
       uncovered into test_install_*.sh, then delete the legacy suite and remove the
       `installation` routing from test_runner.sh, ci.yml, and nightly-extended.yml.
       Until then it runs nightly and on install-path PRs only (2026-07 CI tiering).
+      Done 2026-10-02: the suite is deleted, its scenarios live in
+      test_install_legacy_flags.sh (marked "Ported from retired
+      test_installation.sh"), test_runner.sh routes no `installation` suite, and
+      the CI/nightly suite lists no longer name it.
     acceptance:
       - "Every test_installation.sh scenario is mapped to a harness equivalent or ported."
       - "test_installation.sh deleted; test_runner.sh no longer routes an `installation` suite."
@@ -887,7 +891,7 @@ tasks:
       - "Nightly extended run green after removal."
     links: { issue: null, pr: null, roadmap: null }
     created: 2026-07-06
-    updated: 2026-07-06
+    updated: 2026-10-02
   - id: T-034
     title: "Remove the dead preview_image_generator.rb Jekyll plugin and its test surface"
     status: done
@@ -951,7 +955,7 @@ tasks:
 
   - id: T-036
     title: "Remove hover transforms that cause pointer-edge flicker in the navbar"
-    status: open
+    status: done
     priority: P1
     area: feat
     risk: standard
@@ -968,17 +972,38 @@ tasks:
       _sass/components/_ui-enhancements.scss and card hover styles for the same
       pattern.
     acceptance:
-      - "No transform in any :hover rule under _sass/ (grep for translateY/scale in hover context returns nothing)."
-      - "Pointer parked on the top edge of any nav item or utility button does not flicker."
+      # Scoped to the navbar per the issue's Option A. Criterion 1 was
+      # originally "no transform in any :hover rule under _sass/" — that is 42
+      # rules across ~15 files (card lifts, book tilts, recipe hovers) and a
+      # visual redesign of a published theme, not this defect. It also flagged
+      # `transform: none`, which is the CORRECTIVE pattern this repo already
+      # uses in _post-navigation.scss and the prefers-reduced-motion blocks.
+      # A theme-wide motion policy belongs in its own task.
+      # Stated as the COMPUTED value, not "no matching rule": these controls
+      # are `.btn`s and _ui-enhancements.scss's theme-wide
+      # `.btn:hover { translateY(-2px) }` still matches them and always will.
+      # It is overridden by `transform: none`, not deleted, so a rule-existence
+      # check would be permanently red. That inherited lift is why deleting the
+      # navbar's own translateY was not sufficient on its own.
+      - "getComputedStyle(control).transform is `none` while hovered, for every navbar control."
+      # Direction corrected: translateY(-1px) moves the element UP, so the row
+      # it stops covering is the BOTTOM one. A test parked on the top edge
+      # passes without exercising the bug.
+      - "Pointer parked on the bottom edge of any nav item or utility button does not flicker."
+      # Note: `#bdNavbar .nav-link:hover`, named in the summary as the primary
+      # cause, was dead code — its lift sits inside a container query that never
+      # matches at desktop widths (measured 1040/1140/1200/1280px on the built
+      # site, `none` at every one, on main too). The observable flicker was on
+      # the utility buttons and the FABs.
       - "regression test added"
       - "before/after evidence committed"
-    links: { issue: null, pr: null, roadmap: null }
+    links: { issue: 404, pr: null, roadmap: null }
     created: 2026-08-18
-    updated: 2026-08-18
+    updated: 2026-09-03
 
   - id: T-037
     title: "Navbar width recovery: two clean label tiers, merged chevron, centered grid, no subtitle"
-    status: open
+    status: done
     priority: P2
     area: feat
     risk: standard
@@ -997,19 +1022,38 @@ tasks:
       the navbar subtitle (_includes/core/branding.html — home hero only).
       Clarify the three toggles: labeled "Menu" text button below lg, gear moves
       into the unified drawer on mobile so only two toggles coexist.
+      Done 2026-09-23: collapsed the three container-query tiers to two (icon+label
+      >=51rem, icon-only below — the old 41-50.99rem bare-label tier and its
+      text-overflow: ellipsis safety net are gone), merged the dropdown chevron
+      into the parent link's hover row, gave the desktop grid's side tracks a
+      shared floor (--zer0-navbar-side-min), moved site.subtitle to the home hero,
+      and labeled the mobile menu toggle "Menu" (with aria-label mirroring the
+      visible text for WCAG 2.5.3). `grid-template-columns: 1fr auto 1fr` as
+      literally proposed breaks the container queries (track 2 must stay a
+      definite 1fr for `.bd-navbar-nav-viewport`'s `width: 100%` to resolve) —
+      used a shared side-track minimum instead; documented in-source. A prior
+      attempt (#454) reached the same design but was closed as stale — its author
+      had no Docker/Jekyll to run the Playwright suite or regenerate evidence.
+      This finishes it against a real local build (bundle + jekyll build +
+      Playwright), and additionally caught and fixed a collision the earlier
+      attempt's tooling couldn't check: the new visible "Menu" text reused the
+      already-defined `ui.menu_label` ("Toggle menu"), which would have shipped
+      wrong text — added a dedicated `ui.nav_menu_toggle_label` key instead.
+      49/49 Playwright checks pass (37 existing navbar.spec.js + 12 new
+      navbar-tiers.spec.js).
     acceptance:
       - "At 1024px and 1280px with 5 nav items every label is fully visible or the whole row is icon-only — no ellipses anywhere."
       - "Dropdown chevron shares the parent row's hover zone; no dead zone between link and chevron."
       - "Navbar carries logo + title only; subtitle appears on the home hero."
       - "regression test added"
       - "before/after evidence committed"
-    links: { issue: null, pr: null, roadmap: null }
+    links: { issue: 405, pr: 495, roadmap: null }
     created: 2026-08-18
     updated: 2026-08-18
 
   - id: T-038
     title: "Language switcher: icon-only trigger and a compact, positive menu"
-    status: open
+    status: done
     priority: P2
     area: feat
     risk: standard
@@ -1029,10 +1073,9 @@ tasks:
       - "Trigger is icon-only at all widths with an accessible name."
       - "regression test added"
       - "before/after evidence committed"
-    links: { issue: null, pr: null, roadmap: null }
+    links: { issue: 406, pr: 431, roadmap: null }
     created: 2026-08-18
-    updated: 2026-08-18
-
+    updated: 2026-09-01
   - id: T-039
     title: "Eliminate page-transition layout shift (fixed-nav offset, scrollbar gutter, server-rendered slots)"
     status: open
@@ -1064,7 +1107,7 @@ tasks:
 
   - id: T-040
     title: "Setup wizard: live YAML preview, vertical stepper, draft persistence, stable panel height, inline validation"
-    status: open
+    status: done
     priority: P2
     area: feat
     risk: standard
@@ -1087,10 +1130,9 @@ tasks:
       - "Reload mid-wizard restores the draft; invalid email/URL flagged on blur."
       - "regression test added"
       - "before/after evidence committed"
-    links: { issue: null, pr: null, roadmap: null }
+    links: { issue: 408, pr: 432, roadmap: null }
     created: 2026-08-18
-    updated: 2026-08-18
-
+    updated: 2026-09-01
   - id: T-041
     title: "Admin layout: actions reachable on mobile, grouped sidebar, shared sticky offset, single heading"
     status: open
@@ -1216,7 +1258,7 @@ tasks:
 
   - id: T-045
     title: "Homepage snapshot baselines were regenerated without the 1967px drift being diagnosed"
-    status: open
+    status: done
     priority: P2
     area: tests
     risk: low
@@ -1267,6 +1309,138 @@ tasks:
       - "Any genuinely time- or build-varying content inside the snapshot region is masked or stubbed, so the tier cannot drift again."
       - "No baseline PNG is regenerated as part of this work; any diff is diagnosed in the PR before it is blessed."
       - "The y626 band is explained, or recorded as unrecoverable with the reason. (Recorded: artifacts past 14-day retention.)"
-    links: { issue: 417, pr: null, roadmap: null }
+    links: { issue: 417, pr: 425, roadmap: null }
     created: 2026-08-23
-    updated: 2026-08-25
+    updated: 2026-09-01
+
+  - id: T-046
+    title: "Retire the now-dead gotoBeforeScrollSpy fixture and cover the mobile offcanvas TOC spy"
+    status: open
+    priority: P3
+    area: tests
+    risk: low
+    effort: S
+    source: issue
+    route: test-author
+    summary: >-
+      Discovered while fixing the TOC scroll spy: test/visual/fixtures.js
+      exports gotoBeforeScrollSpy(), which strips data-bs-spy/data-bs-target
+      from <body> before Bootstrap auto-initializes so its native ScrollSpy
+      cannot clear server-rendered .active classes off admin sidebar links.
+      That attribute no longer exists — _layouts/root.html dropped it (and
+      _layouts/default.html dropped the second copy on .bd-main) so the theme's
+      own scroll-spy.js is the single owner of .active on TOC links — which
+      makes the fixture a no-op that still reads as load-bearing. Replace its
+      call sites in test/visual/features/admin.spec.js with the plain
+      waitForJekyll/gotoOrSkip helpers and delete it, keeping the admin
+      active-link assertions that motivated it. While there, add the coverage
+      test/visual/features/scroll-spy.spec.js deliberately left out: the mobile
+      offcanvas TOC, where .offcanvas-body rather than .bd-toc is the scroll
+      container the spy keeps the active link visible in.
+    acceptance:
+      - "gotoBeforeScrollSpy is removed from test/visual/fixtures.js and from its call sites; no spec references it."
+      - "The admin specs that used it still pass, asserting the same server-rendered active nav links."
+      - "A spec exercises the TOC scroll spy below the lg breakpoint with the offcanvas TOC open, asserting the active entry tracks scrolling and stays visible inside .offcanvas-body."
+      - "npm run test:smoke is green."
+    links: { issue: null, pr: null, roadmap: null }
+    created: 2026-09-05
+    updated: 2026-09-05
+
+  - id: T-047
+    title: "pages/_docs/features/toc.md documents a TOC API the theme does not implement"
+    status: open
+    priority: P3
+    area: docs
+    risk: low
+    effort: S
+    source: issue
+    route: content-reviewer
+    summary: >-
+      Discovered while correcting the scroll-spy sections of
+      pages/_docs/features/toc.md: the page's Implementation and Configuration
+      halves describe a table of contents this theme does not have. "TOC
+      Generation" shows a Kramdown `{{ content | toc_only }}` snippet and a
+      hand-rolled `page.content | split: '<h'` extractor, neither of which the
+      theme uses — the real TOC comes from _includes/content/toc.html (the
+      allejo/jekyll-toc parser) invoked by _includes/navigation/sidebar-right.html.
+      "Enable TOC" documents front-matter keys that nothing reads; the
+      `toc.min_level` / `toc.max_level` pair in the same section was already
+      corrected (grep confirms no include, layout, plugin or _config.yml
+      references either key). A reader following this page cannot reproduce the
+      theme's behaviour. Rewrite the two sections against the actual include,
+      its parameters, and the front-matter keys that really gate the panel.
+    acceptance:
+      - "Every Liquid snippet in toc.md matches an include the theme actually ships, verified by path."
+      - "Front-matter keys documented on the page are read somewhere in _includes, _layouts, _plugins or _config.yml."
+      - "scripts/content-review.rb still scores the page in the green band."
+      - "Jekyll build with the layered dev configs is green and the page's anchors keep resolving."
+
+  - id: T-048
+    title: "Site-level theme_color re-pins --zer0-color-primary over the active skin"
+    status: done
+    priority: P2
+    area: feat
+    risk: low
+    effort: S
+    source: issue
+    summary: "Done 2026-10-02 (#459): the skin wins. tokens-inline.html emits theme_color main/blue/purple only when no palette skin is active, the precedence is documented in docs/ui/design-tokens.md, and appearance.spec.js asserts it. Discovered while making Mermaid diagrams follow the skin (ZER0-013 rework): the skin mixin (_sass/theme/_skins.scss) writes both --bs-primary and --zer0-color-primary under [data-theme-skin], but _includes/core/tokens-inline.html emits `:root { --zer0-color-primary: <theme_color.main> }` AFTER main.css, and :root ties [data-theme-skin] on specificity, so the later inline rule wins. Result on this site: buttons/links follow the skin (#6fa8dc on air, #8338ec on neon) while every custom component that reads --zer0-color-primary (callouts, code-block accent border, focus rings) stays on the config #007bff regardless of skin. Mermaid works around it by reading --bs-primary first; the token layer should agree with itself instead."
+    acceptance:
+      - "With theme_color.main set, switching skin changes --zer0-color-primary as well as --bs-primary (probe getComputedStyle on <html>)."
+      - "Decide and document the precedence: skin over site theme_color (recommended) or the reverse — one rule, applied to every --zer0-color-* the mixin sets."
+      - "A smoke test asserts --zer0-color-primary === --bs-primary after setSkin('neon')."
+      - "before/after evidence committed"
+    links: { issue: null, pr: null, roadmap: null }
+    created: 2026-09-05
+    updated: 2026-10-02
+
+  - id: T-049
+    title: "test_core.sh: Liquid nested-tag check and gem-content check can never fail"
+    status: open
+    priority: P3
+    area: tests
+    risk: low
+    effort: S
+    source: audit
+    summary: "Found while reviewing CI logs for PR #455: test/test_core.sh prints '[ERROR] Nested Liquid output tags found in _includes/navigation/sidebar-pagetree.html' on every run and still reports the Liquid validation as passed. Two defects: (1) the check is `grep -q \"{{.*{{\"`, which flags any line with two output tags — sidebar-pagetree.html:65 is `{{ _base }}{{ _section }}` inside a capture, valid Liquid — and the `return 1` sits inside a `find | while read` pipeline subshell, so it can never fail the function; (2) the gem-content check runs `tar -tzf` on the .gem, but a gem is an uncompressed tar (metadata.gz, data.tar.gz, checksums.yaml.gz), so gzip prints 'stdin: not in gzip format' four times and both branches always fall through to the 'Gem may not contain…' warnings without inspecting anything."
+    acceptance:
+      - "The nested-tag check only flags a genuinely nested output tag (e.g. `{{ a {{ b }} }}`), not two sibling tags on one line, and a positive match fails the test (no subshell swallowing the return)."
+      - "The gem-content check lists data.tar.gz inside the .gem (`tar -xOf … data.tar.gz | tar -tzf -`) and asserts _layouts/ and assets/ are present; a gem missing them fails the test."
+      - "./test/test_core.sh runs clean: no '[ERROR]' line on a passing run and no gzip/tar noise."
+    links: { issue: null, pr: null, roadmap: null }
+    created: 2026-09-05
+    updated: 2026-09-05
+
+  - id: T-050
+    title: "Visual Snapshots tier: LiveReload reloads the page mid-test because npm ci lands after Jekyll starts watching"
+    status: open
+    priority: P2
+    area: tests
+    risk: low
+    effort: S
+    source: audit
+    summary: "The snapshots project shows a retried test on most CI runs — '[snapshots] › appearance-snapshot.spec.js › skin: <random> › homepage visual snapshot' fails with 'page.evaluate: Execution context was destroyed, most likely because of a navigation' and passes on retry (aqua on PR #455, mint on main 5ff38bf). Nothing on the homepage navigates; the likely trigger is Jekyll's LiveReload. test/update-snapshots.sh runs `docker compose up -d` (jekyll serve --watch --livereload, repo bind-mounted at /site) and only then starts the Playwright container, which runs `npm ci` into the same bind mount. jekyll-watch 2.2.1 registers an ignore pattern only for exclude paths that EXIST when serve starts (`next unless absolute_path.exist?` in listen_ignore_paths), and a fresh CI checkout has no node_modules/, so the thousands of files npm ci writes fire the watcher, the site regenerates, and LiveReload pushes a reload to every open page over localhost:35729 (reachable: the Playwright container uses --network host). Whichever skin is mid-step when the regeneration finishes fails; Playwright's CI retry (retries: 1) masks it, at the cost of one retry per run and a false 'flaky' signal that would hide a real regression."
+    acceptance:
+      - "Jekyll in the snapshot stack cannot reload the browser during a run: either node_modules/ exists before `docker compose up` (run `npm ci` first, or `mkdir -p node_modules`) or the test stack serves without --livereload (compose override or a JEKYLL_LIVERELOAD toggle)."
+      - "Confirmed with the Playwright trace or `docker compose logs jekyll` showing no 'Regenerating' during a run."
+      - "Ten consecutive CI runs of the snapshots project report 0 flaky tests."
+      - "Root cause noted in the header of test/update-snapshots.sh so the ordering is not undone."
+    links: { issue: null, pr: null, roadmap: null }
+    created: 2026-09-05
+    updated: 2026-09-05
+
+  - id: T-051
+    title: "Preview-image engine: the xAI default model grok-2-image is retired — default to grok-imagine-image-2.0"
+    status: open
+    priority: P2
+    area: infra
+    risk: low
+    effort: S
+    source: issue
+    summary: "Discovered while adding the xAI provider to the chat proxy and Site Builder (ZER0-087): scripts/lib/preview_generator.py's XAIProvider.default_model() still returns 'grok-2-image', which xAI has retired in favour of the Grok Imagine family (grok-imagine-image-2.0, per docs.x.ai release notes). A site with preview_images.provider: xai and no explicit model gets an upstream error. The Site Builder now writes preview_images.model explicitly for generated sites, so only the engine default (and the .env.example comment for IMAGE_MODEL) is stale. scripts/lib/ is CODEOWNERS-owned, so this is a human-review change."
+    acceptance:
+      - "XAIProvider.default_model() returns grok-imagine-image-2.0 and the provider table comment in the engine header matches."
+      - "The image request keeps working with the current xAI response shape (data[0].url or b64_json)."
+      - "scripts/lib/README.md / .env.example mention the new default."
+    links: { issue: null, pr: null, roadmap: null }
+    created: 2026-09-07
+    updated: 2026-09-07

data/_data/consumers.yml

@@ -44,6 +44,28 @@
 #                       version; tracked so a bump doesn't miss the config that
 #                       activates it
 #   path_gem            local path gem, unversioned (development only)
+#   gem_unconstrained   `gem 'jekyll-theme-zer0'` with no version — resolves
+#                       whatever RubyGems has at `bundle update` time; tracked
+#                       only (like resolved_lockfile), never reports drift
+#
+# ------------------------------------------------------------------------------
+# Stack fields (optional; informational — scripts/bin/propagate ignores them)
+# ------------------------------------------------------------------------------
+#   How far each consumer is aligned with the zer0 stack (one theme, one image
+#   engine, one CMS — templates/consumer/README.md § The zer0 stack). A dated
+#   snapshot of each consumer's default branch, not a live reading: refresh it
+#   from `zer0-cms doctor <checkout>` (bamr87/zer0-CMS), never from memory.
+#
+#   stack:
+#     checked             date the default branch was read
+#     image_gem           Gemfile requires zer0-image-generator
+#     preview_images      _config.yml has a preview_images: block
+#     vendored_generator  copies of the image engine the gem replaces
+#                         (_plugins/preview_*.rb forks, scripts/lib/
+#                         preview_generator.py, scripts/generate-preview-images.sh);
+#                         a deliberate local generator is NOT listed
+#     zer0_json           a zer0.json (zer0-CMS project file) is committed
+#     doctor              .github/workflows/zer0-doctor.yml caller is committed
 # ==============================================================================
 
 version: 1
@@ -74,6 +96,16 @@ consumers:
       hook, enabled by `user_overrides: true`, not a shadow — and no fix
       numbered #338 could be substantiated in that repo. Keep this field
       derived from audit-consumer output, not hand-maintained estimates.
+    stack:
+      checked: "2026-09-14"
+      image_gem: true
+      preview_images: true
+      vendored_generator:
+        - _plugins/preview_image_generator.rb
+        - _plugins/preview_generator.rb
+        - scripts/lib/preview_generator.py
+      zer0_json: false
+      doctor: false
     pins:
       - file: _config.yml
         kind: remote_theme
@@ -87,6 +119,14 @@ consumers:
     risk: >-
       Unpinned, same exposure as it-journey. Small override surface (2 includes).
       Recommend pinning and joining the fan-out.
+    stack:
+      checked: "2026-09-14"
+      image_gem: true
+      preview_images: true
+      vendored_generator:
+        - scripts/generate-preview-images.sh
+      zer0_json: false
+      doctor: false
     pins:
       - file: _config.yml
         kind: remote_theme
@@ -103,6 +143,15 @@ consumers:
       Gemfile.azure + _config.azure.yml, and local dev mounts a path gem. A bump
       must move the remote_theme tag and the gem constraint together or the two
       production stacks render different theme versions.
+    stack:
+      checked: "2026-09-14"
+      image_gem: false
+      preview_images: true
+      vendored_generator:
+        - _plugins/preview_image_generator.rb
+        - scripts/generate-preview-images.sh
+      zer0_json: true
+      doctor: false
     pins:
       - file: _config.yml
         kind: remote_theme
@@ -117,6 +166,48 @@ consumers:
         kind: path_gem
         note: line 40 — dev checkout via ZER0_MISTAKES_PATH; never bumped
 
+  # ---------------------------------------------------------------------------
+  - repo: amr-bash/bash-365.com
+    mode: remote_theme_floating
+    site: https://bash-365.com
+    dispatch: false
+    note: >-
+      BASH Consulting's site, forked from bamr87/bashconsultants (which stays
+      registered above) and carrying the same three-stack shape: GitHub Pages
+      via remote_theme, Azure Static Web Apps via Gemfile.azure +
+      _config.azure.yml, local dev via a path gem. Unlike its parent, nothing
+      here carries a version any more — remote_theme is untagged and
+      Gemfile.azure names the gem with no constraint — so there is no pin for a
+      bump PR to rewrite. Declares its intentional forks in .theme-overrides.yml.
+    risk: >-
+      Unpinned on Pages; the Azure stack advances only when someone runs
+      `bundle update jekyll-theme-zer0`, so the two production stacks can
+      render different theme versions with nothing here to notice. Recommend
+      pinning remote_theme and constraining Gemfile.azure together and joining
+      the fan-out.
+    stack:
+      checked: "2026-09-14"
+      image_gem: false
+      preview_images: true
+      vendored_generator:
+        - _plugins/preview_image_generator.rb
+        - scripts/generate-preview-images.sh
+      zer0_json: true
+      doctor: false
+    pins:
+      - file: _config.yml
+        kind: remote_theme
+        note: line 33, no tag — floats main
+      - file: Gemfile.azure
+        kind: gem_unconstrained
+        note: line 10 — no version; `bundle update jekyll-theme-zer0` advances it
+      - file: _config.azure.yml
+        kind: theme_name
+        note: line 3 — activates the gem; no version of its own
+      - file: Gemfile
+        kind: path_gem
+        note: line 59 — dev checkout via ZER0_MISTAKES_PATH; never bumped
+
   # ---------------------------------------------------------------------------
   - repo: year-of-ai/year-of-ai.github.io
     mode: remote_theme_pinned
@@ -129,6 +220,14 @@ consumers:
       so one bump here re-rolls the whole org (12 sites). The hub's own
       _config.yml and hub.yml must move together — they are read by different
       code paths and drift silently otherwise.
+    stack:
+      checked: "2026-09-14"
+      image_gem: true
+      preview_images: true
+      vendored_generator:
+        - scripts/generate-preview-images.sh
+      zer0_json: false
+      doctor: false
     pins:
       - file: _config.yml
         kind: remote_theme
@@ -139,20 +238,35 @@ consumers:
 
   # ---------------------------------------------------------------------------
   - repo: ai-world-view/ai-world-view.github.io
-    mode: remote_theme_pinned
+    mode: remote_theme_floating
     site: https://ai-world-view.github.io
-    dispatch: true
+    dispatch: false
     fans_out_to_members: true
     note: >-
       Same two-file hub shape as year-of-ai; members join by auto_discover, so
-      the member count grows without this file changing.
+      the member count grows without this file changing. Was registered as
+      remote_theme_pinned until the 2026-09 fleet harmonization, but both its
+      _config.yml remote_theme and its hub.yml theme_repo carry NO tag — the
+      hub and every member it stamps float on this theme's main.
+    risk: >-
+      Unpinned, and an org hub: a theme break here reaches every auto-discovered
+      member site at once. Recommend pinning both files together and joining
+      the fan-out (dispatch: true) like year-of-ai.
+    stack:
+      checked: "2026-09-14"
+      image_gem: true
+      preview_images: true
+      vendored_generator:
+        - scripts/generate-preview-images.sh
+      zer0_json: false
+      doctor: false
     pins:
       - file: _config.yml
         kind: remote_theme
-        note: line 35
+        note: line 36, no tag — floats main
       - file: _data/hub.yml
         kind: hub_registry
-        note: "line 39 (pages.theme_repo) — re-roll members after bumping"
+        note: "line 39 (pages.theme_repo), no tag — members float too"
 
   # ---------------------------------------------------------------------------
   # The four entries below were missing entirely until the 2026-08 fleet audit.
@@ -177,6 +291,13 @@ consumers:
       Gemfile.lock resolved 1.25.0 while the Gemfile constraint (~> 1.25)
       already permitted 1.28.0 — stale purely because nothing was nudging it.
       Keeps two deliberate include forks, declared in its .theme-overrides.yml.
+    stack:
+      checked: "2026-09-14"
+      image_gem: true
+      preview_images: true
+      vendored_generator: []
+      zer0_json: false
+      doctor: false
     pins:
       - file: Gemfile
         kind: gem_constraint
@@ -203,6 +324,13 @@ consumers:
       Unpinned, and with no local preview path a contributor cannot see a theme
       break before pushing. Keeps three deliberate overrides, declared in its
       .theme-overrides.yml.
+    stack:
+      checked: "2026-09-14"
+      image_gem: false
+      preview_images: false
+      vendored_generator: []
+      zer0_json: false
+      doctor: false
     pins:
       - file: _config.yml
         kind: remote_theme
@@ -221,6 +349,13 @@ consumers:
     risk: >-
       Unpinned, and its only build runs on push to main (jekyll-gh-pages.yml),
       so a break ships before anyone sees it.
+    stack:
+      checked: "2026-09-14"
+      image_gem: false
+      preview_images: false
+      vendored_generator: []
+      zer0_json: false
+      doctor: false
     pins:
       - file: _config.yml
         kind: remote_theme
@@ -246,6 +381,13 @@ consumers:
       "unreachable" rather than reading its pin — drift reporting needs a token
       here even though it is read-only. CI already supplies one; a bare local
       run will not.
+    stack:
+      checked: "2026-09-14"
+      image_gem: false
+      preview_images: false
+      vendored_generator: []
+      zer0_json: false
+      doctor: false
     pins:
       - file: _config.yml
         kind: remote_theme