jekyll-theme-zer0 1.31.3 → 1.32.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (63) hide show
  1. checksums.yaml +4 -4
  2. data/CHANGELOG.md +131 -0
  3. data/_data/backlog.yml +97 -28
  4. data/_data/features.yml +164 -15
  5. data/_data/navigation/admin.yml +26 -8
  6. data/_data/navigation/docs.yml +2 -8
  7. data/_data/theme-manifest.yml +63 -47
  8. data/_data/ui-text.yml +9 -0
  9. data/_includes/README.md +2 -1
  10. data/_includes/components/ai-chat.html +2 -2
  11. data/_includes/components/author-bio.html +3 -1
  12. data/_includes/components/author-card.html +9 -9
  13. data/_includes/components/author-eeat.html +13 -3
  14. data/_includes/components/collection-manager.html +2 -2
  15. data/_includes/components/component-showcase.html +7 -7
  16. data/_includes/components/cookie-consent-needed.html +37 -0
  17. data/_includes/components/cookie-consent.html +15 -5
  18. data/_includes/components/page-feedback.html +9 -5
  19. data/_includes/components/post-card.html +2 -2
  20. data/_includes/components/theme-customizer.html +1 -1
  21. data/_includes/content/comments.html +46 -0
  22. data/_includes/content/giscus.html +22 -13
  23. data/_includes/content/intro.html +17 -1
  24. data/_includes/content/jsonld-software.html +4 -9
  25. data/_includes/core/footer.html +36 -14
  26. data/_includes/navigation/admin-nav.html +110 -63
  27. data/_includes/navigation/section-sidebar.html +20 -20
  28. data/_includes/navigation/sidebar-config.html +17 -8
  29. data/_includes/navigation/sidebar-right.html +16 -2
  30. data/_layouts/README.md +1 -1
  31. data/_layouts/admin.html +49 -20
  32. data/_layouts/article.html +10 -10
  33. data/_layouts/book-story.html +3 -7
  34. data/_layouts/default.html +55 -1
  35. data/_layouts/news.html +8 -7
  36. data/_layouts/note.html +2 -6
  37. data/_layouts/notebook.html +2 -6
  38. data/_layouts/recipe.html +3 -7
  39. data/_layouts/root.html +7 -4
  40. data/_layouts/section.html +43 -42
  41. data/_sass/components/_page-feedback.scss +1 -1
  42. data/_sass/components/_ui-enhancements.scss +22 -0
  43. data/_sass/core/_nav-tree.scss +10 -2
  44. data/_sass/core/_navbar.scss +19 -5
  45. data/_sass/core/_obsidian.scss +19 -3
  46. data/_sass/core/_sidebar-categories.scss +4 -2
  47. data/_sass/core/_sidebar-extras.scss +3 -2
  48. data/_sass/layouts/_admin.scss +60 -0
  49. data/_sass/layouts/_navbar-extras.scss +7 -2
  50. data/_sass/theme/_skins.scss +124 -32
  51. data/_sass/tokens/_color.scss +3 -0
  52. data/_sass/tokens/_layers.scss +12 -5
  53. data/assets/css/main.scss +1 -0
  54. data/assets/js/code-copy.js +30 -2
  55. data/assets/js/setup-wizard.js +2 -2
  56. data/assets/js/ui-enhancements.js +46 -0
  57. data/scripts/ai/README.md +1 -1
  58. data/scripts/bin/audit-consumer +155 -8
  59. data/scripts/bin/manifest +27 -8
  60. data/scripts/bin/validate +3 -2
  61. data/scripts/lib/audit.sh +156 -0
  62. data/scripts/validate-features.rb +20 -2
  63. metadata +5 -2
checksums.yaml CHANGED
@@ -1,7 +1,7 @@
1
1
  ---
2
2
  SHA256:
3
- metadata.gz: 816ebacaa328a7680e39d49a7e2b8e05defcf855b78e45f4c6389f0aa3d20215
4
- data.tar.gz: cf16d9cbfd9f909a7164ce66ccc6ce4fab4ec3c788922b38b93dfc3243e3e4ff
3
+ metadata.gz: f498dc2e942c0b6c025e0070e87e7cfb88993ab97c2ec655aa4331613ba31584
4
+ data.tar.gz: 157a2272966c0a619a45ddc6f76ea30f55d48ec15fac49c634278505b3899341
5
5
  SHA512:
6
- metadata.gz: 90b19505b5d0946020b8ea49e8440ccc61697f56181902a72ffba7dd860ac82555d1f33ab71f2b28e0c9627ec311a155d9f652b4f04367f1f095a05ab3084f3f
7
- data.tar.gz: 4d59a4d83ec78332e125dc5d45c09b747de729bf16d6c77c365ffc89074c7c9db5deeb3def0d27c8dc91d779dd932e8e3a2f2c3970ac9be231627a4dad5bbeae
6
+ metadata.gz: d72396bd8631be4cc02938a6799bf39b71d055ed970dcb679c4931595c912d1e59369201b4631d977cfaeefb52de6882b4b51a743dac5393914df172d5b50936
7
+ data.tar.gz: 40c0bd42ebb833f685ccb8bcb1872dbb98e8d3bb3b3e896675f574ada0d686d942462a49a9f53192555d8509d8682be86e30b5695e431cbcd6d49566d6bb0840
data/CHANGELOG.md CHANGED
@@ -12,6 +12,40 @@ hand-written prose covering the same releases in more depth; they sit below
12
12
  their version because release-please inserts each new release at the top of the
13
13
  file. Only `## [Unreleased]` describes work that has not shipped yet.
14
14
 
15
+ ## [1.32.0](https://github.com/bamr87/zer0-mistakes/compare/v1.31.3...v1.32.0) (2026-11-18)
16
+
17
+
18
+ ### Features
19
+
20
+ * **audit-consumer:** detect stale vendored theme _data ([#629](https://github.com/bamr87/zer0-mistakes/issues/629)) ([e128dfa](https://github.com/bamr87/zer0-mistakes/commit/e128dfab42edee035f7eed0dbc2eeddea00bf105))
21
+ * **includes:** configurable giscus theme, mapping and language ([#634](https://github.com/bamr87/zer0-mistakes/issues/634)) ([9d50a02](https://github.com/bamr87/zer0-mistakes/commit/9d50a02098fccc80b2439a5c78e5cb66981aa119)), closes [#574](https://github.com/bamr87/zer0-mistakes/issues/574)
22
+ * **includes:** show the footer newsletter form only when a provider is configured ([#633](https://github.com/bamr87/zer0-mistakes/issues/633)) ([646e0ba](https://github.com/bamr87/zer0-mistakes/commit/646e0bac1b400e19180f861323cbe3598908ae39))
23
+ * **layouts:** keep admin actions reachable on mobile and group the admin sidebar ([#630](https://github.com/bamr87/zer0-mistakes/issues/630)) ([cb9b313](https://github.com/bamr87/zer0-mistakes/commit/cb9b313c6f1b096520113e45528a092eba0e3cf2))
24
+ * **studio:** zer0 studio — the Rails workbench beside the theme ([#560](https://github.com/bamr87/zer0-mistakes/issues/560)) ([8817fbe](https://github.com/bamr87/zer0-mistakes/commit/8817fbe84e7d643668a689a941018319e38c549a))
25
+
26
+
27
+ ### Bug Fixes
28
+
29
+ * **a11y:** author-card social links name the author ([#568](https://github.com/bamr87/zer0-mistakes/issues/568)) ([#603](https://github.com/bamr87/zer0-mistakes/issues/603)) ([2dfa4bb](https://github.com/bamr87/zer0-mistakes/commit/2dfa4bbae6473f59c27732fbfaab8c67a0a53f33))
30
+ * **a11y:** label and lay out GFM task-list checkboxes ([#587](https://github.com/bamr87/zer0-mistakes/issues/587)) ([ce1c35d](https://github.com/bamr87/zer0-mistakes/commit/ce1c35d8d00915b2724a5cb1424dd82630aa7d6d))
31
+ * **a11y:** meet WCAG AA contrast in every skin; 24px sidebar toggles ([#632](https://github.com/bamr87/zer0-mistakes/issues/632)) ([3ca3415](https://github.com/bamr87/zer0-mistakes/commit/3ca34159560d966351eda84642f1b9907f8be653))
32
+ * **a11y:** name section-page navigation landmarks, mark the current section ([#567](https://github.com/bamr87/zer0-mistakes/issues/567)) ([863192b](https://github.com/bamr87/zer0-mistakes/commit/863192b5f86bcda05cdde407cf3164b71f77aa58))
33
+ * **a11y:** name the icon-only controls and drop dead links flagged by the UI audit ([#639](https://github.com/bamr87/zer0-mistakes/issues/639)) ([be36ff8](https://github.com/bamr87/zer0-mistakes/commit/be36ff8521eb62770f713f22de767024904606c5))
34
+ * **a11y:** one h1 per page, no duplicate banner, contentinfo or region landmarks ([#638](https://github.com/bamr87/zer0-mistakes/issues/638)) ([96013c6](https://github.com/bamr87/zer0-mistakes/commit/96013c6ad9daba8c5e03079bda14371ba692b233))
35
+ * **a11y:** section layout heading outline follows document depth ([#575](https://github.com/bamr87/zer0-mistakes/issues/575)) ([d47eb49](https://github.com/bamr87/zer0-mistakes/commit/d47eb49f7372c88e416350e5b5baa20994a1a825))
36
+ * **ci:** install libssl-dev so the latest-deps canary can build the openssl gem ([f02ec37](https://github.com/bamr87/zer0-mistakes/commit/f02ec37fa135fa0984ffac79edae12cea36c05c6))
37
+ * **ci:** tag the loaded image, not the runner's newest, in test-latest ([#619](https://github.com/bamr87/zer0-mistakes/issues/619)) ([4347b00](https://github.com/bamr87/zer0-mistakes/commit/4347b00e63a05478302105c70f1bd282ad8723d1))
38
+ * **deps:** open dependency PRs with FLEET_TOKEN so CI runs ([#628](https://github.com/bamr87/zer0-mistakes/issues/628)) ([bf42ae6](https://github.com/bamr87/zer0-mistakes/commit/bf42ae6e3f72be63d764d38ac1b0177dc905ab2a))
39
+ * **deps:** re-lock github-pages 233 to lift rubyzip to 3.7.0 (GHSA-47m2-wp7j-p9vc) ([#599](https://github.com/bamr87/zer0-mistakes/issues/599)) ([f223bd7](https://github.com/bamr87/zer0-mistakes/commit/f223bd7eee3c7df0f6b0a0e820dd531584fa833c))
40
+ * **fab:** move the local-graph FAB to slot 3 below lg when the sidebar FAB is present ([#589](https://github.com/bamr87/zer0-mistakes/issues/589)) ([bb013ab](https://github.com/bamr87/zer0-mistakes/commit/bb013aba64044a6fb9b6c3dede0db555e1e78e3e))
41
+ * **includes:** render the cookie-consent banner only when a tracker needs consent ([#583](https://github.com/bamr87/zer0-mistakes/issues/583)) ([1ac8164](https://github.com/bamr87/zer0-mistakes/commit/1ac816404de33fa0679feab294c5b664653db624))
42
+ * **navigation:** gate the offcanvas toggles on the layout chain ([#579](https://github.com/bamr87/zer0-mistakes/issues/579)) ([93e7062](https://github.com/bamr87/zer0-mistakes/commit/93e7062441ae7451ee752f85b2494bf086356799))
43
+ * **privacy:** cookie preferences default Analytics to off ([#578](https://github.com/bamr87/zer0-mistakes/issues/578)) ([0d4a517](https://github.com/bamr87/zer0-mistakes/commit/0d4a517aaf39c71c5d14c2ba464886ecc5e10752))
44
+ * **release:** let release-please bump the theme manifest version ([#618](https://github.com/bamr87/zer0-mistakes/issues/618)) ([746cc9b](https://github.com/bamr87/zer0-mistakes/commit/746cc9bb2ec984575bd2ca6bdba86559e55ddf78))
45
+ * **scripts:** accept status: planned catalog entries in validate-features ([#598](https://github.com/bamr87/zer0-mistakes/issues/598)) ([f206ad6](https://github.com/bamr87/zer0-mistakes/commit/f206ad6a63910ea378c11afe0256f0ab561774ff))
46
+ * **styles:** move the FAB layer band below the overlay surfaces ([#580](https://github.com/bamr87/zer0-mistakes/issues/580)) ([35eb01e](https://github.com/bamr87/zer0-mistakes/commit/35eb01ec4f1571852540c356a7bd71d20336a976))
47
+ * **toc:** scope the article TOC to the post body ([#576](https://github.com/bamr87/zer0-mistakes/issues/576)) ([6620b04](https://github.com/bamr87/zer0-mistakes/commit/6620b04dcf8985047816ccd22d0347dcd8f1b6aa))
48
+
15
49
  ## [1.31.3](https://github.com/bamr87/zer0-mistakes/compare/v1.31.2...v1.31.3) (2026-10-20)
16
50
 
17
51
 
@@ -445,6 +479,21 @@ feature docs with captured screenshots of both the broken widget and the giscus.
445
479
 
446
480
  ### Changed
447
481
 
482
+ - **The footer newsletter form renders only when a provider is configured** ([#554](https://github.com/bamr87/zer0-mistakes/issues/554)). Every page of every site used to show a disabled email field and a disabled "Subscribe" button whose tooltip read "Configure a newsletter endpoint in your site config", over a "Newsletter is a placeholder until you connect a provider" caption, and no config key changed that. The form now renders only when the new top-level `newsletter.endpoint` is set, falling back to `news.newsletter.endpoint` (the news band's key), and it then submits the address to that endpoint with an enabled, required email field. `method` and `email_field` are configurable, and `enabled: false` hides the form. With no endpoint the footer has no form and the policy links take the full row. The form's strings moved to `_data/ui-text.yml` (`newsletter_label`, `newsletter_email_label`, `newsletter_placeholder`, `newsletter_subscribe`). Regression tests: `test/test_newsletter_gate.rb` (run by `test_core.sh`) and `test/visual/core/footer-newsletter.spec.js`, which replaces the #522 hint checks. (evidence: [`test/visual/evidence/footer-newsletter/`](test/visual/evidence/footer-newsletter/README.md) — default site: newsletter form 1 → 0, disabled footer controls 2 → 0; with newsletter.endpoint: an enabled form that POSTs the address)
483
+ - **Admin pages keep every header action within reach on a phone, and the admin sidebar is grouped** ([#409](https://github.com/bamr87/zer0-mistakes/issues/409), T-041, ZER0-050). The `admin_actions` buttons sat in a `d-none d-md-flex` wrapper, so below 768px none rendered. The first action is now a button at every width and any others open from a "More actions" (⋯) dropdown; on narrow screens the group wraps onto its own line under the title. Items in `_data/navigation/admin.yml` take a `group:` key, and the sidebar lists them under small-caps Configure / System / Links labels: list labels that name their lists, not headings, while items without a group render as before. The collections count is a plain numeral and the analytics and environment statuses are a coloured dot plus a word instead of pill badges. The active item is a tint of the skin colour, semibold, with `aria-current`, instead of Bootstrap's solid primary pill. The desktop sidebar's "Administration" `<h6>` is gone, so the offcanvas title is the one "Administration" heading in the DOM. The sticky-offset part of T-041 moved to T-039. (evidence: [`test/visual/evidence/admin-layout/`](test/visual/evidence/admin-layout/README.md) — header actions reachable at 375px 0 → 2, "Administration" headings 2 → 1, sidebar groups 0 → 3)
484
+
485
+ - **The cookie-consent banner renders only when the site has something that needs consent** ([#566](https://github.com/bamr87/zer0-mistakes/issues/566)). The banner, its "Manage Cookies" modal and the footer "Cookie Preferences" button used to render on every page, so a site with no tracker asked first-time visitors to consent to analytics cookies it never sets. They now render only when `google_analytics`, `google_tag_manager` or `posthog.enabled` is configured (blank ids count as unset). The new `cookie_consent.enabled` key overrides this: `true` forces the banner on (for trackers added through `_includes/custom/` hooks) and `false` turns it off. The setup wizard no longer writes `enabled: true`. Regression test: `test/test_cookie_consent_gate.rb` (run by `test_core.sh`). (evidence: [`test/visual/evidence/cookie-consent-gate/`](test/visual/evidence/cookie-consent-gate/README.md) — no-tracker site: banner, modal and footer button 1 → 0)
486
+ - **CI stops re-downloading the Playwright browser on every run.** A new
487
+ `.github/actions/setup-playwright` composite action installs npm dependencies
488
+ and a **cached** chromium (`~/.cache/ms-playwright`, keyed on
489
+ `package-lock.json`), and `ci.yml`, `nightly-extended.yml`, `ui-audit.yml` and
490
+ the `playwright-tests` action all go through it. `codeql.yml` and
491
+ `install-matrix.yml` also gained a concurrency group that cancels superseded
492
+ pull-request runs (pushes to `main` and the scheduled scans are never
493
+ cancelled, so the Security tab's alert set is never replaced by a
494
+ half-finished analysis). Test coverage is unchanged — this is Actions-minute
495
+ cost only (ZER0-016, ZER0-027).
496
+
448
497
  - **Navigation start-up no longer runs as one long task.**
449
498
  `assets/js/modules/navigation/index.js` now wires sidebar state, keyboard
450
499
  shortcuts, focus management and the navbar first, then yields to the main
@@ -927,6 +976,83 @@ feature docs with captured screenshots of both the broken widget and the giscus.
927
976
 
928
977
  ### Fixed
929
978
 
979
+ - **A11y: one `<h1>` per page, and no second banner or contentinfo landmark** ([#593](https://github.com/bamr87/zer0-mistakes/issues/593)). `default.html` renders the page title as the intro hero's `<h1>`, and most Markdown pages open with their own `# Title`, so 225 of the 244 intro pages in the docs build had two. It now rewrites the body's first `<h1>`: dropped when it leads the body and repeats the title (its `id` stays on an empty `<span>`, so anchors and the TOC entry still land), demoted to `<h2>` otherwise. The page-feedback dialog's `<header>`/`<footer>` bars are `<div>`s now; as `<body>`-level elements they were a second `banner` and `contentinfo` whenever the dialog was open. `code-copy.js` numbers a language's code-block regions when a page has more than one ("bash code block 2"), which was the `landmark-unique` count axe reported on closed pages. Regression tests in `test/visual/core/heading-outline.spec.js` and `test/visual/core/landmarks.spec.js` (evidence: [`test/visual/evidence/fix-a11y-single-h1-landmarks/`](test/visual/evidence/fix-a11y-single-h1-landmarks/README.md)).
980
+ - **Accessibility: every palette skin meets WCAG AA contrast, and the sidebar toggles reach 24px** ([#410](https://github.com/bamr87/zer0-mistakes/issues/410), T-042). The skins painted text with the raw brand colour and left Bootstrap's white text on brand fills, so with the default `air` skin the current-page navbar link was 2.40:1 and `.btn-primary`, `.badge.bg-primary`, `.text-bg-primary` and the current dropdown item were 2.53:1, the failures the site-quality scans of the sites on this theme kept reporting. Each skin now passes an on-brand ink (`$on-brand`, exposed as `--zer0-color-on-primary`: `#000` on the light brands, `#fff` on dirt and neon) to every brand fill and every button state; brand text uses the skin's link colours, and selected and current states (navbar, quicklinks, nav-tree, category sidebar, tabs, breadcrumbs) use the stronger link-hover shade. mint's light link darkens from `#2d8059` to `#287652` (it was 4.45:1 on the card tint), and dirt's button hover and active states mix toward its dark brown. The gray archive and tag badges switch to `text-bg-secondary` (3.29:1 → 4.69:1), small meta text uses `text-body-secondary` instead of `text-body-tertiary` (3.12:1), and the chevron-only `.nav-tree-toggle` grows from 22px to 24px wide (axe `target-size`). The measured ratios sit beside each skin in `_sass/theme/_skins.scss`, and `test/visual/core/skin-contrast.spec.js` checks every palette skin in light and dark (evidence: [`test/visual/evidence/skin-contrast/`](test/visual/evidence/skin-contrast/README.md) — air current nav link 2.4:1 → 8.44:1, 103 → 0 component failures across 7 skins × light/dark).
981
+
982
+ - **Mobile TOC FAB, sidebar toggle and local-graph FAB reach consumer layouts**
983
+ ([#570](https://github.com/bamr87/zer0-mistakes/issues/570), follow-up to
984
+ [#373](https://github.com/bamr87/zer0-mistakes/issues/373), ZER0-008).
985
+ `navigation/sidebar-config.html` decided whether a page renders the
986
+ `#bdSidebar` / `#tocContents` offcanvases from a hard-coded list of the
987
+ theme's **own** layout names. That is correct for theme layouts and fails
988
+ closed for every consumer layout: a remote-theme site whose `quest` layout
989
+ declares `layout: default` got `#tocContents` and no `#tocFab`, so below `lg`
990
+ its table of contents was unreachable (about 216 pages on it-journey.dev),
991
+ and the header sidebar toggle and local-graph FAB were suppressed too. The
992
+ gate now asks the layout chain — `_layouts/default.html` declares
993
+ `renders_sidebar_offcanvas: true` and Jekyll's layout front-matter merge makes
994
+ it visible as `layout.renders_sidebar_offcanvas` at any depth, the same
995
+ mechanism `core/header.html` already uses for `skip_link_target`. #373's
996
+ fail-safe is intact: a layout that never reaches `default` declares nothing
997
+ and still gets no toggle and no dangling `aria-controls`. Consumer workarounds
998
+ that key on `sidebar_offcanvas_rendered == false` go inert on their own.
999
+ `test/test_core.sh :: test_sidebar_offcanvas_layout_gate` now pins the
1000
+ key-based gate instead of the list.
1001
+ - **Accessibility: GFM task lists are labelled and laid out** ([#573](https://github.com/bamr87/zer0-mistakes/issues/573)). kramdown renders `- [ ]` as `<li class="task-list-item"><input class="task-list-item-checkbox">Text` with no `<label>` and no whitespace, and the theme had no rule for it: each item kept its bullet, the box sat flush against its text, and axe `label` fired once per checkbox (WCAG 1.3.1 / 4.1.2; 3, 20 and 6 nodes on the it-journey.dev canary pages). `_sass/components/_ui-enhancements.scss` now drops the bullet and spaces the box while keeping wrapped lines on the list indent, and `assets/js/ui-enhancements.js` wraps each item's own text (stopping at a nested list) in a `<span id>` that the box names itself by through `aria-labelledby`; no `<label>` wrapper, so click behaviour is unchanged. `/notes/markdown-tips/` now renders a nested task list too. Pinned by `test/visual/core/accessible-names.spec.js` (accessible name, nested-item name, axe `label` = 0, computed style).
1002
+ - **A11y: author-card social links name the author** ([#568](https://github.com/bamr87/zer0-mistakes/issues/568)). The full author card ("About the Author", on every post) rendered its GitHub, LinkedIn, Website and Email buttons as icon-only links named by `title=` alone, and X by the bare `aria-label="X"`, so screen-reader and touch users got no reliable name and never learned *whose* profile it was (WCAG 2.4.4 / 4.1.2). Each link now carries an explicit `aria-label` such as "Vega on GitHub (opens in a new tab)" or "Email Vega", following the footer's #435 pattern; `title` stays as the tooltip, so nothing changes visually. Every Bootstrap Icons glyph in `_includes/components/author-card.html`, including the `bi-person*` avatar placeholders, is now `aria-hidden="true"`. Regression test: `test/visual/features/authors.spec.js` § "Author-card social link names (issue #568)".
1003
+ - **A11y: section pages name their navigation landmarks and mark the current section** ([#567](https://github.com/bamr87/zer0-mistakes/issues/567)). Every `layout: section` page added three unnamed `<nav>` landmarks beside the labelled primary nav and breadcrumbs, so a screen reader's landmark list read "navigation, navigation, navigation" (axe `landmark-unique`, WCAG 1.3.1). The active section-switcher pill was "current" only visually, and the Bootstrap Icons beside link text were exposed (4.1.2). Now the switcher `<nav>` is labelled "News sections" (new `ui-text` key `news_sections_label`), and the desktop Topics `<nav>` is "<Section> topics". The offcanvas Topics `<nav>` is `aria-labelledby` its drawer title. The two sidebar `<aside>`s are named, and the active pill carries `aria-current="page"`. Every decorative `bi` icon in `_layouts/section.html` and `_includes/navigation/section-sidebar.html` is `aria-hidden="true"`; the three icon-only status badges are unchanged. Two more unnamed `<nav>`s get labels: the news index's section switcher (`_layouts/news.html`, whose active "Home" pill also gets `aria-current`) and the listicle quick-nav in `_layouts/article.html`. Nothing changes visually. Regression tests: `test/visual/core/landmarks.spec.js` § "every navigation landmark is named". The source layer covers `_layouts/` and `_includes/navigation/`, and the rendered layer runs axe `landmark-unique` on `/news/technology/`.
1004
+ - **Docs: the safe-mode build overlay recipe is Pages-faithful** ([#565](https://github.com/bamr87/zer0-mistakes/issues/565)). [`/docs/deployment/build-overlay/`](pages/_docs/deployment/build-overlay.md) used to clone the whole theme repo into the build dir and copy the site on top. The theme's `_data/` (its `navigation/docs.yml` sidebar), its root pages (`/AGENTS/`, `/CLAUDE/`), `examples/`, `templates/`, `features/` and `fr/` all leaked into consumer CI builds that production never serves. The recipe now starts from the consumer site and copies in only `_layouts/`, `_includes/`, `_sass/` and `assets/` with `rsync --ignore-existing` (consumer files win), and it explains why an allowlist beats a denylist. The reusable `lh_overlay()` gets the same inversion, and it now writes to the caller's `_site` (`-d "$PWD/$out"` used to expand after the `cd`, so the site landed in the temp dir). `THEME_URL`/`THEME_REF` are overridable, and the "Verifying the overlay matches Pages" checklist gains the `/AGENTS/`, `/features/`, `/fr/` and theme-`_data` checks. Regression test: `test/test_build_overlay_recipe.sh` (run by `test_core.sh`) runs both code blocks verbatim against a minimal consumer.
1005
+ - **An open overlay now covers the floating action buttons**
1006
+ ([#572](https://github.com/bamr87/zer0-mistakes/issues/572), ZER0-081).
1007
+ The FAB band in `_sass/tokens/_layers.scss` sat *above* the overlay surfaces
1008
+ (back-to-top 1050, feedback 1051, chat 1052, toc 1055, local-graph 1060
1009
+ against backdrop 1040, offcanvas 1045, modal 1055), so with the search modal,
1010
+ the main-nav offcanvas or the TOC panel open the TOC and local-graph FABs
1011
+ painted over it undimmed and stayed hit-testable — `fab-toc` tied with `modal`
1012
+ and won on DOM order, because the FABs render after the footer. The band moved
1013
+ to 1031-1035, between the header (1030) and the backdrop (1040), which is the
1014
+ ordering the file's own header already promised. FABs never overlap the fixed
1015
+ header, so nothing else moved; the non-modal local-graph panel still opens
1016
+ over its own FAB and still has its close button. Stale `var(…, 1051)` /
1017
+ `var(…, 1052)` fallbacks in `_includes/components/ai-chat.html` and
1018
+ `_sass/components/_page-feedback.scss` were retuned with it. New source
1019
+ contract: `test/visual/features/fab-layer-order.spec.js`.
1020
+ - **Cookie preferences no longer pre-tick Analytics** ([#553](https://github.com/bamr87/zer0-mistakes/issues/553), ZER0-007).
1021
+ `#analyticsCookies` carried a hard-coded `checked` attribute, and the
1022
+ component synced the modal switches from stored consent *only* for returning
1023
+ visitors — so a first-time visitor who opened Cookie Preferences saw Analytics
1024
+ already on, and "Save Preferences" recorded `analytics: true` (and called
1025
+ `posthog.opt_in_capturing()`) without them touching the switch. Pre-ticked
1026
+ boxes are not valid consent (GDPR/ePrivacy Recital 32; CJEU *Planet49*,
1027
+ C-673/17), and the component's own `defaultConsent` already said off. The
1028
+ attribute is gone and `updateModalUI(existingConsent || defaultConsent)` now
1029
+ runs on every first paint, so the switches always mirror the state actually in
1030
+ force; `updateModalUI` became null-safe for consumers that ship the banner
1031
+ without the modal. Accept All is unchanged (explicit consent) and returning
1032
+ visitors still see their saved choices. Regression test:
1033
+ `test/visual/features/cookie-consent-defaults.spec.js`.
1034
+
1035
+ - **Accessibility: section landings have a continuous heading outline** ([#555](https://github.com/bamr87/zer0-mistakes/issues/555)). `layout: section` picked heading tags for their font size, so on `/news/<section>/` the sidebar's `<h5>`/`<h6>` came before the page `<h1>` and card titles jumped `h1 → h5` (WCAG 1.3.1). `_layouts/section.html` and `_includes/navigation/section-sidebar.html` now choose tags by document depth and keep each size with an `.h4`/`.h5`/`.h6` class (the #436 pattern); source order, and so focus order, is unchanged. Visual sizes are unchanged. Pinned by `test/visual/core/heading-outline.spec.js` for the grid, list and magazine styles (evidence: [`test/visual/evidence/section-heading-outline/`](test/visual/evidence/section-heading-outline/README.md)).
1036
+
1037
+ - **CI: the two recurring red/cancelled run sources on `main` are gone.**
1038
+ Over the five weeks to 2026-10-29, `main` decided 197 runs and only 2 of them
1039
+ actually failed; the repo's poor headline pass rate came from 37 cancelled and
1040
+ 166 skipped runs. Two fixable causes:
1041
+ - `Dependabot Updates` errored on every re-check of the `rubyzip` advisory
1042
+ (2026-09-26, 10-03, 10-07, 10-27): the fix needs `>= 3.4.0`, but
1043
+ `github-pages (232)` pins `rubyzip (>= 1.3.0, < 3.0)` via
1044
+ `jekyll-remote-theme (0.4.3)`, so `security_update_not_possible` failed the
1045
+ whole run. `.github/dependabot.yml` now carries a `bundler` entry — version
1046
+ updates off, so `update-dependencies.yml` keeps ownership of gems — whose
1047
+ only job is to ignore `rubyzip >= 3.0` until `github-pages` allows it. The
1048
+ advisory stays visible in the Security tab.
1049
+ - `🧭 Issue Autopilot` used a workflow-level concurrency group with a constant
1050
+ name, so every `issues: [labeled]` event — including the labels the pipeline
1051
+ applies itself — joined it even though `gate`'s job-level `if` skips them.
1052
+ With one pass running and one queued, each further no-op event cancelled the
1053
+ queued run: 13 of the 37 cancellations. Non-actionable label events now get
1054
+ their own group; real passes stay serialized.
1055
+
930
1056
  - **`require_consent` now means no analytics until the visitor accepts.** With `posthog.privacy.require_consent: true`, PostHog used to load opted-out on a first visit: the browser still fetched `array.js`, `config.js` and `surveys.js` and stored `ph_<key>_posthog` before any banner choice, and Google Analytics ignored consent entirely. `_includes/analytics/posthog.html` now boots PostHog only once analytics consent exists, and `_includes/analytics/google-analytics.html` follows the same flag (override per site with `google_analytics_require_consent`). Both load as soon as the visitor clicks Accept All or saves preferences with Analytics on, through the banner's `cookieConsentChanged` event, so no reload is needed. Reject All keeps them off. Sites without the flag load exactly as before. Regression test: `test/visual/features/analytics-consent.spec.js`.
931
1057
 
932
1058
  - **Color-mode toggle exposes the selected mode** ([#521](https://github.com/bamr87/zer0-mistakes/issues/521)).
@@ -1625,6 +1751,11 @@ off the `data-repo` attribute, not the page origin, so the iframe renders and re
1625
1751
  - **Back to top had no visible keyboard focus.** It now draws a 2px
1626
1752
  primary-color `:focus-visible` outline.
1627
1753
 
1754
+ ### Fixed
1755
+
1756
+ - **Docs-sidebar FAB reachable again below `lg` when the page has a local graph** ([#571](https://github.com/bamr87/zer0-mistakes/issues/571)): the Obsidian local-graph FAB moves to slot 3 of the left-side stack whenever `#sidebarFab` is on the page (`body:has(#sidebarFab)`, `<lg` only), so it no longer covers the sidebar FAB and swallows its taps; at `lg`+ it stays at slot 2 (evidence: [`test/visual/evidence/fab-stack-sidebar/`](test/visual/evidence/fab-stack-sidebar/README.md) — sidebar↔local-graph FAB overlap 3136px² → 0 below lg).
1757
+
1758
+
1628
1759
  ## [1.31.0](https://github.com/bamr87/zer0-mistakes/compare/v1.30.0...v1.31.0) (2026-10-07)
1629
1760
 
1630
1761
 
data/_data/backlog.yml CHANGED
@@ -62,8 +62,8 @@
62
62
 
63
63
  meta:
64
64
  title: "zer0-mistakes Backlog"
65
- updated: 2026-10-19
66
- next_id: 55
65
+ updated: 2026-11-15
66
+ next_id: 57
67
67
 
68
68
  tasks:
69
69
  # --- Housekeeping (seeded so the loop has work on day one) ------------------
@@ -1134,8 +1134,8 @@ tasks:
1134
1134
  created: 2026-08-18
1135
1135
  updated: 2026-09-01
1136
1136
  - id: T-041
1137
- title: "Admin layout: actions reachable on mobile, grouped sidebar, shared sticky offset, single heading"
1138
- status: open
1137
+ title: "Admin layout: actions reachable on mobile, grouped sidebar, single heading"
1138
+ status: done
1139
1139
  priority: P2
1140
1140
  area: feat
1141
1141
  risk: standard
@@ -1149,22 +1149,28 @@ tasks:
1149
1149
  the rest in a "..." dropdown. Group sidebar items under small-caps headers
1150
1150
  (Configure / System / Links) via a group: key in
1151
1151
  _data/navigation/admin.yml; counts as plain numerals, statuses as colored
1152
- dot + word; active item = tint + semibold, not solid primary fill. Replace
1153
- style="top: 5rem" with top: calc(var(--zer0-nav-height) + 1rem) (depends
1154
- on T-039). Keep the "Administration" heading in the offcanvas header only.
1152
+ dot + word; active item = tint + semibold, not solid primary fill. Keep
1153
+ the "Administration" heading in the offcanvas header only. The sticky
1154
+ offset clause (style="top: 5rem" to calc(var(--zer0-nav-height) + 1rem))
1155
+ moved to T-039, which already lists admin.html's top: 5rem among the
1156
+ offsets it derives from --zer0-nav-height. Done 2026-11-15: first action
1157
+ a button at every width, the rest in a "More actions" dropdown; sidebar
1158
+ grouped under list labels (not headings) with plain counts, dot + word
1159
+ statuses and a tinted active item carrying aria-current; one
1160
+ "Administration" heading. Tests in test/visual/features/admin.spec.js,
1161
+ evidence in test/visual/evidence/admin-layout/.
1155
1162
  acceptance:
1156
1163
  - "Every admin action reachable at 375px width."
1157
- - "Sidebar grouped; no solid-primary active fill; sticky offset uses the shared variable."
1164
+ - "Sidebar grouped; no solid-primary active fill."
1158
1165
  - "regression test added"
1159
1166
  - "before/after evidence committed"
1160
- links: { issue: null, pr: null, roadmap: null }
1167
+ links: { issue: null, pr: 630, roadmap: null }
1161
1168
  created: 2026-08-18
1162
- updated: 2026-08-18
1163
- depends_on: [T-039]
1169
+ updated: 2026-11-15
1164
1170
 
1165
1171
  - id: T-042
1166
1172
  title: "Skin contrast sweep: AA link params, tertiary meta text, per-skin badge/button audit"
1167
- status: open
1173
+ status: done
1168
1174
  priority: P1
1169
1175
  area: a11y
1170
1176
  risk: standard
@@ -1172,23 +1178,25 @@ tasks:
1172
1178
  source: user
1173
1179
  route: a11y
1174
1180
  summary: >-
1175
- _sass/theme/_skins.scss: several skins omit the zer0-skin-palette mixin's
1176
- $link-light/$link-dark params and fall back to $brand/$accent, which fail
1177
- 4.5:1 (yellow/orange/cyan brands on white, saturated brands on #212529) —
1178
- pass explicit AA-checked values for every skin with a comment table of
1179
- measured ratios. text-body-tertiary on 11-12px meta text (admin header
1180
- "Updated…", wizard hints) falls below AA — use --bs-secondary-color at
1181
- small sizes, tertiary only >= 16px. Audit .btn-primary text per skin
1182
- (auto-switch to dark text when brand luminance > 0.55 via color-contrast()
1183
- or a precomputed token).
1181
+ Done 2026-11-15 (PR #632). The zer0-skin-palette mixin painted text with the raw
1182
+ brand and left Bootstrap's white text on brand fills (air: current nav
1183
+ link 2.40:1, .btn-primary 2.53:1). Every skin now passes a measured
1184
+ $on-brand ink (--zer0-color-on-primary) for brand fills and all button
1185
+ states, brand text uses the AA link colours, selected/current states the
1186
+ link-hover shade, mint's light link is #287652 and dirt's button states
1187
+ mix darker; the measured-ratio table sits beside each skin. Gray badges
1188
+ use text-bg-secondary, small meta text text-body-secondary, and
1189
+ .nav-tree-toggle is 24px. test/visual/core/skin-contrast.spec.js checks
1190
+ the 7 palette skins in light and dark; evidence in
1191
+ test/visual/evidence/skin-contrast/. Follow-ups outside the mixin: T-056.
1184
1192
  acceptance:
1185
1193
  - "axe/Lighthouse contrast passes on light + dark for all skins."
1186
1194
  - "Every skin passes explicit link colors; measured-ratio table committed as comments."
1187
1195
  - "regression test added"
1188
1196
  - "before/after evidence committed"
1189
- links: { issue: null, pr: null, roadmap: null }
1197
+ links: { issue: null, pr: 632, roadmap: null }
1190
1198
  created: 2026-08-18
1191
- updated: 2026-08-18
1199
+ updated: 2026-11-15
1192
1200
 
1193
1201
  - id: T-043
1194
1202
  title: "Mermaid diagrams: render-in-place (no CLS), token-driven theming, figure shell, flash-free theme switch"
@@ -1348,7 +1356,7 @@ tasks:
1348
1356
 
1349
1357
  - id: T-047
1350
1358
  title: "pages/_docs/features/toc.md documents a TOC API the theme does not implement"
1351
- status: open
1359
+ status: done
1352
1360
  priority: P3
1353
1361
  area: docs
1354
1362
  risk: low
@@ -1356,6 +1364,13 @@ tasks:
1356
1364
  source: issue
1357
1365
  route: content-reviewer
1358
1366
  summary: >-
1367
+ Done 2026-11-15 (#637): the Implementation section now names
1368
+ default.html, navigation/sidebar-right.html and the vendored
1369
+ allejo/jekyll-toc parser, quotes the real include call and lists every
1370
+ include parameter; "Enable TOC" became "Showing and Hiding the Panel",
1371
+ documenting the `sidebar` / `post_type` gate that
1372
+ navigation/sidebar-config.html resolves; the Responsive and
1373
+ Troubleshooting sections match the shipped markup and gates.
1359
1374
  Discovered while correcting the scroll-spy sections of
1360
1375
  pages/_docs/features/toc.md: the page's Implementation and Configuration
1361
1376
  halves describe a table of contents this theme does not have. "TOC
@@ -1374,6 +1389,9 @@ tasks:
1374
1389
  - "Front-matter keys documented on the page are read somewhere in _includes, _layouts, _plugins or _config.yml."
1375
1390
  - "scripts/content-review.rb still scores the page in the green band."
1376
1391
  - "Jekyll build with the layered dev configs is green and the page's anchors keep resolving."
1392
+ links: { issue: null, pr: 637, roadmap: null }
1393
+ created: 2026-09-05
1394
+ updated: 2026-11-15
1377
1395
 
1378
1396
  - id: T-048
1379
1397
  title: "Site-level theme_color re-pins --zer0-color-primary over the active skin"
@@ -1430,20 +1448,20 @@ tasks:
1430
1448
 
1431
1449
  - id: T-051
1432
1450
  title: "Preview-image engine: the xAI default model grok-2-image is retired — default to grok-imagine-image-2.0"
1433
- status: open
1451
+ status: done
1434
1452
  priority: P2
1435
1453
  area: infra
1436
1454
  risk: low
1437
1455
  effort: S
1438
1456
  source: issue
1439
- 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."
1457
+ summary: "Done 2026-10-07 (#499): XAIProvider.default_model() and the engine header's provider table name grok-imagine-image-2.0, test/test_preview_generator.py pins the new default and keeps an explicit grok-imagine-image-2.0, and scripts/lib/README.md lists each renderer's default model. 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."
1440
1458
  acceptance:
1441
1459
  - "XAIProvider.default_model() returns grok-imagine-image-2.0 and the provider table comment in the engine header matches."
1442
1460
  - "The image request keeps working with the current xAI response shape (data[0].url or b64_json)."
1443
1461
  - "scripts/lib/README.md / .env.example mention the new default."
1444
- links: { issue: null, pr: null, roadmap: null }
1462
+ links: { issue: null, pr: 499, roadmap: null }
1445
1463
  created: 2026-09-07
1446
- updated: 2026-09-07
1464
+ updated: 2026-11-15
1447
1465
 
1448
1466
  - id: T-054
1449
1467
  title: "Footer prints the copyright notice twice"
@@ -1496,3 +1514,54 @@ tasks:
1496
1514
  links: { issue: 537, pr: 549, roadmap: null }
1497
1515
  created: 2026-10-18
1498
1516
  updated: 2026-10-18
1517
+
1518
+ - id: T-055
1519
+ title: "AI chat panel title is an <h6> at document depth 2 (heading skip on every page that ships the chat)"
1520
+ status: open
1521
+ priority: P2
1522
+ area: a11y
1523
+ risk: low
1524
+ effort: S
1525
+ source: issue
1526
+ route: theme-ui
1527
+ summary: "Discovered during the #555 fix: `_includes/components/ai-chat.html` renders `<h6 id=\"aiChatTitle\">Zer0 Assistant</h6>` outside <main>, after h3-level chrome, so the whole-page outline on every page that ships the chat jumps h3 -> h6 (WCAG 1.3.1). Same size-picked-tag pattern as #436 / #555."
1528
+ acceptance:
1529
+ - "The chat title is `<h2 class=\"h6 ...\">` (or the level matching its container) and keeps `id=\"aiChatTitle\"` for aria-labelledby."
1530
+ - "test/visual/core/heading-outline.spec.js covers the chat region the way CHROME_REGIONS covers the cookie dialog."
1531
+ - "No visual change (snapshot diff empty)."
1532
+ links: { issue: null, pr: null, roadmap: null }
1533
+ created: 2026-10-29
1534
+ updated: 2026-10-29
1535
+
1536
+ - id: T-056
1537
+ title: "Brand-colour contrast outside the skin mixin: text-white on bg-primary, brand hover text, sidebar count badge"
1538
+ status: open
1539
+ priority: P2
1540
+ area: a11y
1541
+ risk: standard
1542
+ effort: M
1543
+ source: issue
1544
+ route: a11y
1545
+ summary: >-
1546
+ Discovered during the T-042 sweep (#410), which fixed the zer0-skin-palette
1547
+ mixin and the navigation current states only. Still open: about a dozen
1548
+ `bg-primary text-white` sites (card headers, author-avatar fallbacks,
1549
+ feature and landing icons, an offcanvas header) keep white on the light
1550
+ brands (2.2-2.8:1); hover states that paint the raw brand as text
1551
+ (.nav-tree-link, the quicklinks chip over the gray outline-secondary
1552
+ hover fill, .sidebar-categories-link, #info-section tabs) and the
1553
+ $accent hover text on .nav-tabs / .list-group-item-action; brand text in
1554
+ _sass/notebooks.scss, _sass/layouts/_landing.scss, _sass/core/_obsidian.scss
1555
+ ([aria-pressed]) and white-on-primary in _setup-wizard.scss; the
1556
+ sidebar-categories count badge (`text-bg-secondary bg-opacity-25`, white on
1557
+ a 25% gray tint); and the contrast/dark skins keep Bootstrap's #0d6efd link
1558
+ (4.27:1 on the #f8f9fa navbar).
1559
+ acceptance:
1560
+ - "`bg-primary text-white` markup in _includes and _layouts uses text-bg-primary (or an equivalent that follows --zer0-color-on-primary)."
1561
+ - "Hover and focus text on skin-coloured controls reaches 4.5:1 in every palette skin, light and dark."
1562
+ - "The sidebar-categories count badge reaches 4.5:1."
1563
+ - "test/visual/core/skin-contrast.spec.js covers the new cases."
1564
+ - "before/after evidence committed"
1565
+ links: { issue: null, pr: null, roadmap: null }
1566
+ created: 2026-11-15
1567
+ updated: 2026-11-15