jekyll-theme-zer0 1.29.0 → 1.30.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) ------------------
@@ -951,7 +951,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,13 +968,34 @@ 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"
@@ -1009,7 +1030,7 @@ tasks:
 
   - 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 +1050,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 +1084,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 +1107,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 +1235,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 +1286,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: open
+    priority: P2
+    area: feat
+    risk: low
+    effort: S
+    source: issue
+    summary: "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-09-05
+
+  - 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,9 @@
 #                       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
 # ==============================================================================
 
 version: 1
@@ -117,6 +120,39 @@ 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.
+    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
@@ -139,20 +175,27 @@ 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.
     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.

data/_data/features.yml

@@ -1,7 +1,7 @@
 # zer0-mistakes Theme Features Registry
 # Comprehensive feature tracking for the zer0-mistakes Jekyll theme
-# Version: 1.26.0
-# Last Updated: 2026-07-17
+# Version: 1.29.0
+# Last Updated: 2026-09-07
 
 features:
   # ============================================================================
@@ -435,22 +435,25 @@ features:
   
   - id: ZER0-013
     title: "Mermaid Diagram Support"
-    description: "Client-side Mermaid.js integration for 10+ diagram types. GitHub Pages compatible with no build plugins required"
+    description: "Client-side Mermaid.js diagrams for 10+ diagram types, rendered as accessible figures: a zoom / fullscreen / copy-source / SVG-export toolbar, accTitle captions, an error card that keeps the source visible, and colours derived from the live design tokens so diagrams follow the colour mode and skin. GitHub Pages compatible with no build plugins required"
     implemented: true
-    version: "0.3.0"
-    link: "/"
+    version: "1.30.0"
+    link: "/docs/features/mermaid-diagrams/"
     docs: "/docs/features/mermaid-diagrams/"
-    tags: [mermaid, diagrams, visualization, documentation]
-    date: 2025-01-27
+    tags: [mermaid, diagrams, visualization, documentation, accessibility, ui]
+    date: 2026-09-05
     provenance:
       introduced_in: "0.3.0"
       pr: null
       commit: "1a6184b"
       issue: null
     tests:
-      - "test/test_core.sh"
+      - "test/visual/features/mermaid.spec.js"
     references:
       include: "_includes/components/mermaid.html"
+      script: "assets/js/mermaid-diagrams.js"
+      styles: "_sass/components/_mermaid.scss"
+      evidence: "test/visual/mermaid-evidence.mjs"
       config: "_config.yml"
     diagram_types:
       - "Flowchart (graph TD)"
@@ -1753,14 +1756,14 @@ features:
       includes:
         - "_includes/content/backlinks.html"
   - id: ZER0-060
-    title: "AI Chat Assistant (Claude + GitHub)"
-    description: "Claude-powered floating chat grounded in the current page: streaming replies, GitHub issue/PR actions (after confirmation), and a dev-only mode that edits the page source file live"
+    title: "AI Chat Assistant (Claude or Grok + GitHub)"
+    description: "Floating chat grounded in the current page, answered by Claude or Grok through the proxy: streaming replies, GitHub issue/PR actions (after confirmation), and a dev-only mode that edits the page source file live"
     implemented: true
-    version: "1.18.0"
+    version: "1.30.0"
     link: "/docs/features/ai-chat-assistant/"
     docs: "/docs/features/ai-chat-assistant/"
-    tags: [ai, chatbot, claude, github, proxy, accessibility]
-    date: 2026-06-13
+    tags: [ai, chatbot, claude, grok, github, proxy, accessibility]
+    date: 2026-09-07
     provenance:
       introduced_in: "1.18.0"
       pr: 33
@@ -1771,7 +1774,7 @@ features:
     references:
       includes: ["_includes/components/ai-chat.html"]
       layouts: ["_layouts/root.html"]
-      scripts: ["assets/js/ai-chat.js", "templates/deploy/chat-proxy/worker.js", "templates/deploy/chat-proxy/dev-proxy.mjs", "templates/deploy/chat-proxy/page-store.mjs"]
+      scripts: ["assets/js/ai-chat.js", "templates/deploy/chat-proxy/worker.js", "templates/deploy/chat-proxy/providers.js", "templates/deploy/chat-proxy/dev-proxy.mjs", "templates/deploy/chat-proxy/page-store.mjs"]
       config: "_config.yml"
       instructions: ".github/instructions/ai-chat.instructions.md"
 
@@ -1918,25 +1921,27 @@ features:
 
   - id: ZER0-067
     title: "Setup Wizard"
-    description: "Multi-step in-browser wizard that assembles a complete _config.yml and lets you download or copy it, lowering first-run setup friction"
+    description: "Nine-step in-browser wizard that assembles a complete starter project — _config.yml, dev config, Gemfile, docker-compose, navigation, first pages — with per-file download and a self-extracting bundle; the form half of the Site Builder"
     implemented: true
-    version: "0.22.7"
+    version: "1.30.0"
     link: "/setup/"
-    docs: "/docs/quickstart/bare-minimum/"
+    docs: "/docs/features/site-builder/"
     tags: [setup, onboarding, configuration]
-    date: 2026-04-03
+    date: 2026-09-05
     provenance:
       introduced_in: "0.22.7"
       pr: 51
       commit: "a70ae8a5"
       issue: null
     tests:
-      - na: "Client-side config generator; exercised manually and via the build"
+      - "test/visual/features/setup-wizard.spec.js"
     references:
       include: "_includes/setup/wizard.html"
       scripts:
         - "assets/js/setup-wizard.js"
+      styles: ["_sass/components/_setup-wizard.scss"]
       layout: "_layouts/setup.html"
+      data: "_data/site_builder.yml"
 
   - id: ZER0-068
     title: "Table CSV Copy"
@@ -2219,7 +2224,7 @@ features:
     features:
       - "Zero-config default: explicit /favicon.ico link on every page (fixes silent 404s and baseurl project sites)"
       - "Optional SVG favicon, PNG sizes, apple-touch-icon, and web manifest links"
-      - "theme-color meta sourced from favicon.theme_color with fallback to theme_color.main design token"
+      - "scheme-aware theme-color metas tracking --bs-body-bg (light #ffffff / dark #212529), emitted even with no config; favicon.theme_color pins a single value"
 
   - id: ZER0-080
     title: "Books Collection — Children's Picture-Book Publishing"
@@ -2413,3 +2418,124 @@ features:
       - "Volume↔weight conversion driven by _data/ingredient_densities.yml, overridable per ingredient with grams_per_cup"
       - "Baker's-percentage ratio table computed at build time, so percentages are correct with JavaScript disabled"
       - "Progressive enhancement: quantities render as authored by Jekyll; the control bar stays hidden until the script reveals it"
+
+  - id: ZER0-085
+    title: "Visual Evidence Autogen"
+    description: "CI produces a UI pull request's visual artifacts instead of only verifying them: before/after evidence from the PR's generator or a generic base-vs-head render, and 9-skin pixel baselines refreshed only when the reviewer agent judges the diff to be the change the PR describes"
+    implemented: true
+    version: "1.30.0"
+    link: "/"
+    docs: "/docs/development/testing/"
+    tags: [ci-cd, testing, automation, ai, quality]
+    date: 2026-09-05
+    provenance:
+      introduced_in: "1.30.0"
+      pr: 462
+      commit: "d0bfc0d1"
+      issue: null
+    tests:
+      - "scripts/ci/test_visual_evidence_autogen.py"
+    references:
+      workflow: ".github/workflows/visual-evidence-autogen.yml"
+      scripts:
+        - "scripts/ci/visual_evidence_autogen.py"
+        - "test/visual/pr-evidence.mjs"
+        - "test/visual/snapshot-diff-montage.mjs"
+        - "test/update-snapshots.sh"
+      agent: ".claude/agents/visual-evidence-reviewer.md"
+      docs: "docs/systems/continuous-evolution.md"
+    features:
+      - "Runs on every same-repo PR event: plans from the diff, brings Jekyll up with docker compose, and renders inside the same jammy Playwright image the snapshot gate compares with"
+      - "Evidence from the PR's own test/visual/*-evidence.mjs generators, or from the generic base-vs-head generator that renders the base branch and the head side by side — no hand-written unfixCss needed"
+      - "Pixel baselines are refreshed only on an 'intentional' verdict from the visual-evidence-reviewer agent, which views the expected | actual | diff montage; a code step disposes, the model only proposes (#417)"
+      - "Loop guard on its own [visual-autogen] commits, a three-commit budget per PR, per-folder manifests so author-made evidence is never overwritten, kill switch VISUAL_EVIDENCE_AUTOGEN_ENABLED=false, and the evidence gate's opt-out labels"
+      - "One sticky PR comment with the montages and the verdict; render output uploaded as an artifact on every run; the evidence gate now requires generated proof and ci-self-repair hands a red Visual Snapshots job to this lane"
+
+  - id: ZER0-086
+    title: "Claude-Guided Site Builder"
+    description: "An embedded Claude session that rides alongside the setup wizard: it sees every answer, fills in the forms, checks the machine, reads the theme's real source, writes the generated project to disk and starts Docker — through the local dev proxy, with a confirmation card before every action"
+    implemented: true
+    version: "1.30.0"
+    link: "/setup/"
+    docs: "/docs/features/site-builder/"
+    tags: [ai, claude, grok, setup, onboarding, docker, proxy]
+    date: 2026-09-07
+    provenance:
+      introduced_in: "1.30.0"
+      pr: null
+      commit: "331ae16c"
+      issue: null
+    tests:
+      - "test/visual/features/setup-wizard.spec.js"
+      - "test/test_wizard_store.mjs"
+    references:
+      includes:
+        - "_includes/setup/wizard.html"
+        - "_includes/setup/claude-session.html"
+        - "_includes/setup/prereq-checklist.html"
+      scripts:
+        - "assets/js/site-builder.js"
+        - "templates/deploy/chat-proxy/wizard-store.mjs"
+        - "templates/deploy/chat-proxy/dev-proxy.mjs"
+        - "test/visual/site-builder-walkthrough.mjs"
+        - "test/visual/site-builder-scenarios.mjs"
+      data: "_data/site_builder.yml"
+      config: "_config.yml"
+      instructions: ".github/instructions/ai-chat.instructions.md"
+      pages:
+        - "pages/_quickstart/site-builder.md"
+        - "pages/_docs/features/site-builder.md"
+    components:
+      - "Connect step — detects the dev proxy, shows the three commands to connect (claude setup-token → .env → node --env-file), re-checks every 15 s"
+      - "Prerequisites — live Docker/Git/gh/VS Code/Node/Claude CLI checks through a fixed command table, per-OS install commands from machine-setup, manual toggles offline"
+      - "Tools — get/set wizard fields, go to step, get/override generated files, read theme source, list theme dirs, search the docs index, resolve target, write project, docker compose up/ps/logs/down, check the site is live"
+      - "Context propagation — the whole wizard state, field schema and generated-file list are in the system prompt on every turn; the form is the single source of truth"
+      - "Safety — proxy-only (no credential in the page), escape-first rendering, confirmation cards for every mutation, scaffold confined to a new folder beside the theme"
+      - "Validation — test/visual/site-builder-walkthrough.mjs samples a random brief per site type (site-builder-scenarios.mjs), drives the wizard on video, builds the site with Docker and asserts routes/title/skin; replayable by seed"
+      - "Site plan — plan_schema in _data/site_builder.yml (JSON-Schema subset, validated in the browser) describes landing templates/sections, navigation style + sidebar, palette/font/radius overrides and example pages; set_site_plan applies it behind a confirmation card and the generators emit index.md + _data/landing.yml, navigation data, assets/css/user-overrides.css + _includes/custom/head.html and one file per planned page"
+      - "Providers, bring-your-own token, open sessions, project editing and image generation — see ZER0-087"
+
+  - id: ZER0-087
+    title: "Bring-Your-Own AI Provider (Claude or Grok) and Open Site Builder Sessions"
+    description: "The Site Builder and chat proxy answer with Claude (Anthropic) or Grok (xAI): users paste their own token on the Connect step, pick a model and an image renderer, and run a guided or open session that can also modify an existing site file by file and render images with Grok Imagine"
+    implemented: true
+    version: "1.30.0"
+    link: "/setup/"
+    docs: "/docs/features/site-builder/"
+    tags: [ai, claude, grok, xai, setup, onboarding, proxy, images]
+    date: 2026-09-07
+    provenance:
+      introduced_in: "1.30.0"
+      pr: null
+      commit: "b43a2bf6"
+      issue: null
+    tests:
+      - "test/test_providers.mjs"
+      - "test/test_wizard_store.mjs"
+      - "test/visual/features/setup-wizard.spec.js"
+    references:
+      includes:
+        - "_includes/setup/wizard.html"
+        - "_includes/setup/claude-session.html"
+      scripts:
+        - "assets/js/site-builder.js"
+        - "assets/js/setup-wizard.js"
+        - "templates/deploy/chat-proxy/providers.js"
+        - "templates/deploy/chat-proxy/credential-store.mjs"
+        - "templates/deploy/chat-proxy/worker.js"
+        - "templates/deploy/chat-proxy/dev-proxy.mjs"
+        - "templates/deploy/chat-proxy/wizard-store.mjs"
+        - "test/visual/site-builder-providers-evidence.mjs"
+      data: "_data/site_builder.yml"
+      config: "_config.yml"
+      instructions: ".github/instructions/ai-chat.instructions.md"
+      pages:
+        - "pages/_docs/features/site-builder.md"
+        - "pages/_quickstart/site-builder.md"
+    components:
+      - "Provider layer (providers.js, Worker + Node) — Anthropic Messages dialect translated to and from xAI's OpenAI-compatible chat API, streaming tool calls included, so ai-chat.js, site-builder.js and the feedback triage are unchanged; CHAT_PROVIDER / CHAT_MODEL / XAI_CHAT_MODEL pinned server-side, client models accepted only from the selected provider's family"
+      - "Connect step — Claude and Grok cards with masked key state, a password token field posted once to the localhost proxy (memory only, probed upstream, optional .env save with mode 600, Forget), model catalog, image renderer (Grok Imagine / OpenAI Images) and guided vs open session; the dev proxy starts without a credential"
+      - "Open session — chat-driven, any order, up to 24 tool rounds per turn with a Stop button; interrupted tool calls get synthetic results so the history stays valid"
+      - "Project session — list/open an existing site under WIZARD_TARGET_ROOT, tree/read, write/edit (unique snippet)/delete text files behind confirmation cards, git status/diff/log/init, jekyll build inside the container"
+      - "Image generation — generate_image renders with grok-imagine-image-2.0 (or gpt-image-2) into assets/ (PNG/JPEG/WebP sniffed, 8 MB cap) with a thumbnail card; generated sites carry ai_chat.provider, preview_images and the matching .env.example keys"
+      - "Validation — test/test_providers.mjs (mock xAI + Anthropic upstreams), test/test_wizard_store.mjs (project + asset rules), setup-wizard.spec.js (mocked proxy: connect as Grok, token never stored, open mode, existing sites), evidence in test/visual/evidence/site-builder-providers/"