npm - @ecomconsult/consentkit - Versions diffs - 0.5.10 → 0.5.12 - Mend

@ecomconsult/consentkit 0.5.10 → 0.5.12

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 (7) hide show

package/README.md CHANGED Viewed

@@ -1,6 +1,6 @@
 # ConsentKit
-![status: prototype v0.3](https://img.shields.io/badge/status-prototype%20v0.3-orange)
+![status: prototype v0.5](https://img.shields.io/badge/status-prototype%20v0.5-orange)
 ![license: MIT](https://img.shields.io/badge/license-MIT-blue)
 ![dependencies: 0](https://img.shields.io/badge/dependencies-0-brightgreen)
 ![no build step](https://img.shields.io/badge/build-none-lightgrey)
@@ -24,17 +24,18 @@ Vanilla ES2020, zero dependencies, no build step.
   (e.g. a direct GA4 `gtag/js` tag) cannot be intercepted before the request
   leaves — mark those up manually; the SaaS install check points at the exact tag
 - **UI:** banner (`bar` / `box` / `modal`), preferences panel, floating re-open
-  button, light/dark, 30+ locales
+  button, light/dark, 34 locales
 - **SSR-safe:** importing on the server never touches the DOM
 - **Equal-weight buttons, no pre-ticked boxes** — the consent invariants are
-  fixed by design, see [CONTRIBUTING.md](CONTRIBUTING.md)
+  fixed by design, see [CONTRIBUTING.md](https://github.com/vermoh/ConsentKit/blob/main/CONTRIBUTING.md)
-> **Status: prototype (v0.3).** The core, the UI and the demo are verified in a
-> browser; several distribution paths are not yet tested against live systems.
-> See [Project status](#project-status) before shipping this to production.
+> **Status: prototype (v0.5.12).** The core, the UI and the demo are verified in
+> a browser and covered by an automated suite (`npm test`); several distribution
+> paths are not yet tested against live systems. See
+> [Project status](#project-status) before shipping this to production.
 **Не программист?** Пошаговая инструкция по-русски, с картинками и разбором по
-кликам: **[INSTALL.ru.md](INSTALL.ru.md)**.
+кликам: **[INSTALL.ru.md](https://github.com/vermoh/ConsentKit/blob/main/INSTALL.ru.md)**.
 ## Install
@@ -42,10 +43,11 @@ Four ways to add ConsentKit to a site, from simplest to most integrated.
 | # | Method | Best for | Docs |
 |---|---|---|---|
+| 0 | **Prebuilt block** — copy one file from `ready/` into `<head>`, nothing to install | Tilda and other site builders; no developer needed | [`ready/README.md`](https://github.com/vermoh/ConsentKit/blob/main/ready/README.md) |
 | 1 | **Script tags** — copy `src/` to your server, three `<script>` tags in `<head>` | Any site you control | [Quickstart below](#quickstart--script-tags) |
 | 2 | **npm** — `npm install @ecomconsult/consentkit` | Bundled apps, React | [Quickstart below](#quickstart--npm) |
-| 3 | **WordPress plugin** — copy the plugin folder to `wp-content/plugins/`; rewrites static tracker tags server-side | WordPress / WooCommerce | [`plugins/wordpress/consentkit/`](plugins/wordpress/consentkit/) |
-| 4 | **Google Tag Manager** — import the container, trigger tags on consent events | Sites already running GTM | [`integrations/gtm/README.md`](integrations/gtm/README.md) |
+| 3 | **WordPress plugin** — copy the plugin folder to `wp-content/plugins/`; rewrites static tracker tags server-side | WordPress / WooCommerce | [`plugins/wordpress/consentkit/`](https://github.com/vermoh/ConsentKit/tree/main/plugins/wordpress/consentkit) |
+| 4 | **Google Tag Manager** — import the container, trigger tags on consent events | Sites already running GTM | [`integrations/gtm/README.md`](https://github.com/vermoh/ConsentKit/blob/main/integrations/gtm/README.md) |
 ```sh
 npm install @ecomconsult/consentkit
@@ -201,6 +203,7 @@ Pass any subset to `init()`. Nested objects merge with the defaults.
 | `hostdb` | `Record<string, Category>` | — | Extra `host: category` pairs merged into the tracker database, applied before the initial scan. SaaS mode fills this from the service; `ConsentKit._extendHostDb()` does the same at any later point |
 | `cookieTable` | `CkCookieTableEntry[]` | `[]` | Declared cookies, listed per category in the panel |
 | `services` | `CkService[]` | `[]` | v0.5.8. Third-party services the site declares. Each gets its own toggle inside its category group in the panel, and can be refused individually — see [Services](#services). At most 50 |
+| `branding` | `object` | absent | v0.3.5. The attribution line (and optional logo) at the foot of the banner, rendered by `src/ck-ui-branding.js`. Absent from the defaults: omit the key and nothing renders — see [Branding](#branding) |
 `cookieTable` entries:
@@ -230,6 +233,26 @@ services: [{
 }]
 ```
+**How the list is laid out (v0.5.12).** A group's «N services · M cookies» line
+is a disclosure **button**, and it is **collapsed by default** — eight services
+no longer push the switches the visitor came for off the screen. Opening it
+reveals the group's services and, at the end, the group's own «Which cookies
+(N)» table. Each service is **one line**: name, vendor, and its switch on the
+right. Everything else — the purpose, the privacy link, «Cookies it sets (N)» —
+lives behind that row's own small «Details» disclosure. Both controls are real
+focusable controls with a visible focus ring, and both are translated in ru, ro
+and en (every other language falls back to en, as elsewhere).
+A group with **no services** is unchanged from 0.5.7: no counter, no disclosure,
+and its cookie table sits at the top level where it always did.
+**A service in the `necessary` group gets no switch** (v0.5.12). That group
+cannot be refused, so a control that could only ever sit at «off» would be
+telling the visitor something untrue — the «always on» badge is rendered in its
+place. `allowedService(id)` answers `true` for such a service unconditionally,
+and a refusal for one is stripped from the denial map on every read and write,
+including a record written by hand or by an older client.
 What the toggle does:
 - **Group off** — every service of that group is off and blocked, as before.
@@ -245,7 +268,8 @@ the block map under the row's own category, so a service host ConsentKit has
 never heard of is still held back.
 Refusals are stored in `ck_consent` as `services: { '<id>': false }` — denials
-only. An id absent from the map is allowed, subject to its category.
+only. An id absent from the map is allowed, subject to its category. A
+`necessary` service is never in the map.
 ### Button appearance
@@ -281,8 +305,8 @@ border rule apply to *derived* values — the automatic text on a filled button,
 the border and text an `outline` button takes from `theme.accent`, the link
 colour read off the accent. A `fg`, `border` or `onAccent` you wrote yourself
 is never repainted, however low it measures: the debug panel reports the ratio
-and warns («контраст 4.32 — ниже рекомендуемых 4.5»), and the choice stays
-yours. Concretely:
+and warns that it is below the recommended floor (for example, "contrast 4.32 —
+below the recommended 4.5"), and the choice stays yours. Concretely:
 - a `fg` you set is painted as set and only measured against the fill behind
   it; the *derived* text on a filled button still becomes white or `#161616`,
@@ -299,6 +323,13 @@ The card is `#ffffff` in light mode and `#1c1c1e` in dark. A colour the
 arithmetic cannot read — a CSS colour name, an `rgb()` string — is left exactly
 as you wrote it rather than being silently replaced.
+**The preferences panel follows the banner, with no settings of its own**
+(v0.5.11): the panel's «save choice» button is styled as `accept`, the panel's
+own accept and reject as `settings`, and the floating button takes the
+`accept` button's fill
+(its border colour when `accept` is `outline`), while the category and service
+switches keep `theme.accent`.
 The same arithmetic is exposed as pure functions on `ConsentKit._contrast`
 (`relativeLuminance`, `contrastRatio`, `ensureContrast`, `stepToContrast`,
 `resolveButtonStyles`, `resolveRadius`, `resolveFont`, `resolveDetails`,
@@ -344,16 +375,16 @@ safe to call before the banner has mounted: a call that arrives while the UI
 file is still loading is remembered and honoured on mount, so a link clicked
 during a slow page load still works.
-The same panel has an address. Ссылка «Изменить выбор cookie» →
-`https://site/#ck-settings`: любая ссылка на страницу сайта с этим хвостом
-открывает окно настроек — и при загрузке страницы, и при переходе по ссылке на
-уже открытой странице. Хвост убирается из адреса через `history.replaceState`,
-поэтому перезагрузка или «назад» не открывают окно повторно. Это тот адрес, на
-который ведёт кнопка «Изменить выбор cookie» на странице декларации cookie, и
-его же удобно поставить в подвал сайта:
+The same panel also has an address. Any link to a page of the site ending in
+`#ck-settings` opens the preferences panel — both when the page loads with that
+fragment and when the link is followed on an already-open page. The fragment is
+then removed from the address with `history.replaceState`, so a reload or a
+«back» does not reopen the panel. This is the address the «change your cookie
+choice» button on a cookie declaration page points at, and the one to put in a
+site footer:
 ```html
-<a href="#ck-settings">Изменить выбор cookie</a>
+<a href="#ck-settings">Change your cookie choice</a>
 ```
 ### Placeholders for blocked embeds
@@ -362,7 +393,7 @@ When the engine holds back an `<iframe>` before consent — a known tracker, or
 any third-party frame in strict mode — the visitor would otherwise see an empty
 hole where a video or a map should be. Since 0.5.7 ConsentKit draws a card in
 its place: the name of the service, the category the embed is waiting for, a
-primary button «Разрешить и показать» that grants **that one category** and
+primary button ("Allow and show") that grants **that one category** and
 loads the embed, and a link to the full settings panel.
 The card is sized from the frame's own `width`/`height` (or its computed size),
@@ -402,8 +433,9 @@ decide. Membership is a claim that a host delivers the site's own assets, not
 that it is harmless in general — anything that *measures* keeps a real consent
 category instead, which is why `static.cloudflareinsights.com` (Cloudflare Web
 Analytics) is classified as `analytics` and blocked before consent even though
-the rest of Cloudflare's CDN is infrastructure. Both lists are matched by suffix
-and returned as copies, so reading them cannot widen what strict mode allows.
+the rest of Cloudflare's CDN is infrastructure. The list holds **37 entries**.
+Both lists are matched by suffix and returned as copies, so reading them cannot
+widen what strict mode allows.
 ## API
@@ -442,6 +474,44 @@ All methods are safe to call at any time and never throw.
 Already-loaded scripts are not unloaded by `withdraw()` — cookies are cleared
 and the next page load is clean.
+### Introspection
+Members prefixed with `_` are **not** private-by-convention placeholders: they
+are a deliberate read-only surface for tooling — the debug panel, the hosted
+cabinet's theme editor, and tests — and they are documented because those
+consumers depend on them. They are stable within a minor version, and every one
+of them returns a copy, so reading can never widen what the engine allows.
+| Member | Returns | Description |
+|---|---|---|
+| `_blocked()` | `array` | What the engine is currently holding back, plus a sweep of blocked markup. Drives the debug panel's list |
+| `_categoryForUrl(url)` | `string \| null` | The category the database gives a URL — the same lookup the engine uses |
+| `_categories` | `string[]` | The four category names, as a copy |
+| `_services()` | `array` | The normalised service rows from the config |
+| `_serviceForUrl(url)` | `object \| null` | Which declared service a URL belongs to |
+| `_deniedServices()` | `string[]` | Ids the visitor refused individually |
+| `_extendHostDb(map)` | `number` | Merge extra `host: category` pairs; returns how many were accepted — see [Extending the tracker database](#extending-the-tracker-database) |
+| `_infra()` | `string[]` | The 37 infrastructure hosts, as a copy |
+| `_isInfra(url)` | `boolean` | Is this URL or hostname infrastructure? |
+| `_baseAllow` | `object` | The built-in strict-mode allowlist (hosts plus path-scoped entries), as a copy |
+`ConsentKit._contrast`, published by `src/ck-ui.js`, exposes the theme
+arithmetic as pure functions so a theme editor can show exactly the numbers the
+banner paints rather than reimplementing them. Nothing in it touches the DOM, so
+it is safe to call in Node:
+| Group | Functions |
+|---|---|
+| Colour maths | `relativeLuminance`, `contrastRatio`, `ensureContrast`, `stepToContrast` |
+| Resolution | `resolveButtonStyles`, `resolveRadius`, `resolveFont`, `pickPageFont`, `resolveDetails`, `buildThemeCss` |
+| Font probing | `nextProbeDelay`, `shouldReprobe` |
+| Placeholders | `placeholderText`, `placeholdersEnabled` |
+| Services panel | `cookieRowsForService`, `looseCookies`, `servicePurpose`, `groupCountLabel`, `serviceSignature`, `signature` |
+| Wording | `plural`, `pluralIndex`, `buildStrings`, `localeTable`, `resolveLang` |
+`ConsentKit._resolvePageFont()` reports the font family the banner resolved from
+the page.
 ## Events
 All are `CustomEvent` on `document`, with the payload in `detail`.
@@ -464,6 +534,20 @@ document.addEventListener('ck:change', (e) => {
 The core never touches the UI directly; it only dispatches these events, and the
 UI layer only calls the public API.
+### dataLayer events (GTM)
+Separately from the DOM events above, `integrations.gtmDataLayer` (on by
+default) pushes to `window.dataLayer`, which is what GTM triggers listen to:
+| Push | When |
+|---|---|
+| `ck_consent_update` with `ck_consent: { necessary, functional, analytics, marketing }` and `ck_method` | Every decision, including `withdraw()` |
+| `ck_consent_functional` / `ck_consent_analytics` / `ck_consent_marketing` | Once per granted category, on the decision and again on a return visit when stored consent is restored. Each fires at most once per page |
+The per-category events exist so a GTM tag can trigger on exactly the category
+it needs without reading the payload. See
+[`integrations/gtm/README.md`](https://github.com/vermoh/ConsentKit/blob/main/integrations/gtm/README.md).
 ## Blocking trackers
 ### Manual markup
@@ -511,9 +595,23 @@ document.head.appendChild(s);
 ```
 Blocked elements are marked `data-ck-blocked` and their URL is remembered, so
-granting consent later loads them without a reload. Recognised hosts include
-Google Analytics, Google Tag Manager, Facebook, Yandex Metrica, Hotjar, TikTok
-and DoubleClick.
+granting consent later loads them without a reload.
+The database ships **116 hosts** and **11 path rules**, matched by suffix (a
+bare registrable domain also covers its subdomains) and by substring
+respectively:
+| Table | Entries | By category |
+|---|---|---|
+| `HOST_DB` | 116 | 40 `functional`, 32 `marketing`, 31 `analytics`, 13 `necessary` |
+| `PATH_DB` | 11 | 4 `marketing`, 3 `functional`, 2 `analytics`, 2 `necessary` |
+| `INFRA_DB` | 37 | not a category — see [Infrastructure](#infrastructure) |
+Recognised hosts include Google Analytics, Facebook, Yandex Metrica, Hotjar,
+TikTok and DoubleClick. The GTM **container** is deliberately not blocked (the
+tags inside it obey Consent Mode); `/gtag/js` is blocked by path instead. The
+same tables are exported to the WordPress plugin, so server and browser
+classify a host identically.
 Because the patches install at parse time, `ck-core.js` must load before any
 tracker — put it first in `<head>` and do not add `defer`.
@@ -601,8 +699,8 @@ Two limits are worth stating plainly:
 Runtime injection is covered by the patches above. A tracker tag written
 **directly into the HTML** is not: the parser starts that request before the
-first line of `ck-core.js` runs. The gap was measured (debt Д9: request at
-14 ms, our script at 18 ms) and it is negative — no client-side technique
+first line of `ck-core.js` runs. The gap was measured (debt D9 in SPEC.md:
+request at 14 ms, our script at 18 ms) and it is negative — no client-side technique
 closes it. Such tags need either manual markup, or a server that rewrites them
 before the page is sent.
@@ -643,10 +741,38 @@ Outside WordPress the same idea applies to any server-side template: emit the
 ## Google Consent Mode v2
-With `integrations.gcm` (default), the core pushes `consent: default` with every
-signal `denied` at parse time, then `consent: update` after each choice:
-`analytics` → `analytics_storage`; `marketing` → `ad_storage`, `ad_user_data`,
-`ad_personalization`.
+With `integrations.gcm` (the default), the core pushes `consent: default` at
+parse time — before any tag can load — with every signal `denied` and
+`wait_for_update: 500`, then `consent: update` after each choice. Seven signals
+are set, always as one block:
+| Signal | Follows |
+|---|---|
+| `analytics_storage` | `analytics` |
+| `ad_storage`, `ad_user_data`, `ad_personalization` | `marketing` |
+| `functionality_storage`, `personalization_storage` | `functional` |
+| `security_storage` | always `granted` |
+`integrations.gtmDataLayer` (also on by default) is an independent gate: it
+pushes a `ck_consent_update` event carrying `ck_consent` (the four categories)
+and `ck_method`, so GTM triggers work even with `gcm: false`.
+**What "denied" actually means.** Consent Mode is Google's own mechanism, not a
+block: a Google tag that runs under denied signals sets **no cookies and no
+identifiers**, but it still sends *cookieless pings* to Google, and those pings
+carry the **page URL, the referrer and the user agent**, from an IP address
+Google necessarily sees. That is enough for Google to see the
+visit, and in the EU an IP address is personal data. Consent Mode alone is
+therefore not the same as not being measured.
+ConsentKit's blocking engine is the part that makes the difference: a tag it
+holds back never runs at all, so it sends nothing — no ping, no URL, no IP. The
+two work together, and Consent Mode is the fallback for the case the engine
+cannot cover (a tag inside a GTM container, or a static `<script src>` the
+parser requested before ConsentKit loaded — see
+[Static tags](#static-tags-what-the-browser-cannot-catch)). If you need "nothing
+reaches Google before consent", rely on the blocking engine and mark such tags
+up; do not rely on Consent Mode by itself.
 ## Storage
@@ -690,36 +816,31 @@ hosting, the cabinet and the scanner — not the line itself.
 For site builders that will not let you upload files, `ready/` holds
 ready-to-paste `<script>` blocks — copy one wholesale into `<head>`. Zero
 external requests. Rebuild them with `tools/build-inline.mjs` (see
-[`tools/README.md`](tools/README.md)); each block's header records the exact
+[`tools/README.md`](https://github.com/vermoh/ConsentKit/blob/main/tools/README.md)); each block's header records the exact
 command that produced it.
-ConsentKit 0.5.0, rebuilt 2026-09-05, uncompressed — gzip on the server cuts
-this roughly three- to fourfold. Every block includes the branding extension
-and the attribution line; `--no-branding` drops both the code and the config
-and takes **~24 KB** back off:
+ConsentKit 0.5.12, rebuilt 2026-09-07, uncompressed — gzip on the server cuts
+this roughly threefold. Every block includes the branding extension and the
+attribution line; `--no-branding` drops both the code and the config and takes
+**~26 KB** back off:
 | Block | Languages | Bytes | gzip | `--no-branding` |
 |---|---|---|---|---|
-| `ready/en-bar.txt` | en | 160,388 | 48,950 | 136,326 |
-| `ready/ru-bar.txt` | ru, ro, en | 162,009 | 49,711 | 137,927 |
-| `ready/ru-box.txt` | ru, ro, en | 162,024 | 49,718 | 137,942 |
-| `ready/ru-box-right.txt` | ru, ro, en | 162,033 | 49,718 | 137,945 |
-| `ready/ru-modal.txt` | ru, ro, en | 162,017 | 49,713 | 137,933 |
-| `ready/eu-bar.txt` | 34 languages | 210,663 | 68,094 | 186,601 |
-0.5.0 adds roughly 18.5 KB over 0.4.1 (about 6.1 KB gzipped): the contrast
-engine, the per-button token resolution, the new stylesheet rules and the
-comments explaining the rules the arithmetic implements. 0.4.1 had added
-roughly 6.3 KB over 0.4.0 (the infrastructure list), and 0.4.0 roughly 16.1 KB
-over 0.3.6: iframe interception, strict mode (same-site detection, the
-allowlists, the public-suffix table) and the extensible tracker database.
-Size is driven almost entirely by the bundled languages: `en` and `ru` are
-built into the UI and cost nothing extra, while layout, position, theme and
-accent change only a few bytes of config.
+| `ready/en-bar.txt` | en | 264,816 | 82,798 | 238,438 |
+| `ready/ru-bar.txt` | ru, ro, en | 266,806 | 83,673 | 240,242 |
+| `ready/ru-box.txt` | ru, ro, en | 266,821 | 83,682 | 240,257 |
+| `ready/ru-box-right.txt` | ru, ro, en | 266,830 | 83,687 | 240,266 |
+| `ready/ru-modal.txt` | ru, ro, en | 266,814 | 83,679 | 240,250 |
+| `ready/eu-bar.txt` | 34 languages | 315,460 | 101,998 | 288,916 |
+The blocks are dominated by the core and the UI (roughly 97 KB and 129 KB of
+source respectively, comments included — the builder concatenates the sources
+as they are and does not minify). Bundled languages account for the rest:
+`en` and `ru` are built into the UI and cost nothing extra, while layout,
+position, theme and accent change only a few bytes of config.
 The debug panel is **not** in these numbers. Blocks carry a ~5.1 KB loader
-(`src/ck-debug-loader.js`) which fetches the 33 KB panel only when someone opens
+(`src/ck-debug-loader.js`) which fetches the ~54 KB panel only when someone opens
 the page with `?ck_debug=1` — see [Debug mode](#debug-mode). An ordinary visitor
 downloads the loader and nothing more.
@@ -762,7 +883,7 @@ a support ticket.
 ### How the panel gets onto the page
-The panel is ~33 KB, and on any given page exactly one person will ever open
+The panel is ~54 KB, and on any given page exactly one person will ever open
 it. So `ready/*.txt` and the WordPress plugin ship **`src/ck-debug-loader.js`**
 (~5.1 KB) instead, and the loader fetches the panel on demand. With no flag set
 the loader creates no DOM, installs no observers and makes **no network
@@ -871,6 +992,24 @@ When the configuration contains a `log` endpoint, each decision is POSTed with
 via `sendBeacon` on `pagehide`. Withdrawals are sent with `method: "withdraw"`.
 No other network requests are made.
+The payload is a **closed schema** — anything outside this list is rejected by
+the server as a 400:
+| Field | Always? | Value |
+|---|---|---|
+| `siteId`, `key` | yes | The site id and the log key from the config |
+| `cfg` | yes | Version of the config the decision was made under |
+| `id`, `ts` | yes | uuid and ISO timestamp of the record. A withdrawal gets a fresh pair |
+| `categories` | yes | Exactly three booleans: `functional`, `analytics`, `marketing`. `necessary` is not part of the schema |
+| `method` | yes | `accept_all` \| `reject_all` \| `custom` \| `withdraw` |
+| `lang`, `layout` | when resolved | The language and layout the visitor actually saw |
+| `services` | only on `custom` | v0.5.8. The ids the visitor refused, sent only when the list is non-empty. Capped at 50 ids of at most 64 characters |
+The client puts no page URL, referrer or user agent in the body. The request
+itself is still an ordinary HTTP request to the API host, so that host sees the
+connection's IP address like any server would — what the *payload* carries is
+the list above and nothing more.
 To try it locally, a mock API is included:
 ```sh
@@ -878,10 +1017,130 @@ node demo/mock-api.mjs          # http://localhost:8788
 # serve the repo root, then open demo/saas.html
 ```
+## Changelog
+Client versions. The WordPress plugin tracks the same numbers and keeps its own
+notes in
+[`plugins/wordpress/consentkit/readme.txt`](https://github.com/vermoh/ConsentKit/blob/main/plugins/wordpress/consentkit/readme.txt).
+### 0.5.12
+- **Services in the preferences panel are collapsed by default and compact.**
+  The group's «N services · M cookies» line became a disclosure button; opening
+  it reveals the services and the group's cookie table. Each service row is one
+  line — name, vendor, switch — with the purpose, the privacy link and its
+  cookie list behind a small «Details» disclosure inside the row.
+- **A service in the «necessary» group has no switch.** It carries the «always
+  on» badge instead, `allowedService()` is unconditionally `true` for it, and a
+  refusal for such a service is stripped from the denial map on read and write.
+- Tracker database: `c.bing.com`.
+### 0.5.11
+- The preferences panel and the floating button follow the **banner's** buttons
+  by role, with no theme settings of their own: «save choice» is styled as
+  `accept`, the panel's own accept and reject as `settings`, and the floating
+  button takes the `accept` fill (its border colour when `accept` is `outline`).
+### 0.5.10
+- **A colour the site owner set is painted as set.** The 4.5:1 text rule and the
+  3:1 border rule now correct only *derived* colours; an explicit `fg`, `border`
+  or `onAccent` is left alone however low it measures.
+- `theme.light.onAccent` — the light-mode mirror of `theme.dark.onAccent`.
+- The debug panel reports the measured ratio and warns, instead of claiming a
+  value was fixed automatically.
+### 0.5.9
+- Tracker database: +42 entries — YouTube, Vimeo, Facebook and Instagram embeds,
+  chats and CRM (Freshworks, Viber, Telegram, Bitrix24, amoCRM), forms and
+  scheduling (Calendly, Typeform), payments (Stripe, PayPal, paynet.md, MAIB),
+  Sentry, 999.md. Vercel and Netlify are classified as infrastructure.
+- The debug panel is honest about Consent Mode: "no cookies, but the page
+  address and browser type are sent".
+### 0.5.8
+- **Services** (`services`): a site declares individual third parties, each of
+  which gets its own toggle inside its category group in the panel, with its own
+  vendor, purpose, privacy link and cookies. A visitor can accept a category and
+  still refuse one service; the refusal survives the group being switched off
+  and on again. Refusals are stored in `ck_consent` as `services: { id: false }`
+  and, in SaaS mode, reported in the beacon's `services` field.
+- `ConsentKit.allowedService(id)`.
+### 0.5.7
+- Placeholders for blocked embeds: a card in place of a held-back video or map,
+  with an "Allow and show" button that grants just that category
+  (`blocking.placeholders`, on by default).
+- `#ck-settings` in a page address opens the preferences panel;
+  `ConsentKit.openSettings()` is safe to call before the UI has mounted.
+- `texts.detailsAction: "declaration"` and `texts.declarationUrl`.
+### 0.5.6
+- The attribution line follows the banner's language
+  (`branding.poweredBy.texts`).
+### 0.5.5
+- Banner and panel texts rewritten in plain language (ru, ro, en).
+### 0.5.4
+- Database: Google Maps is `functional`; Tilda platform services and
+  `fonts.google.com` are infrastructure; Google Ads pings
+  (`/pagead/1p-user-list`, `/ads/ga-audiences`) are `marketing`.
+### 0.5.3
+- The banner re-resolves the page font after full load (on Tilda a reload from
+  cache left the banner in Times), and falls back to the system stack when the
+  page font cannot be determined.
+### 0.5.2
+- The banner takes its font from the page's real text rather than from `body`.
+### 0.5.1
+- Database: general CDNs (gstatic.com, aspnetcdn.com, kxcdn.com, jsDelivr,
+  cdnjs, unpkg, CloudFront and others) are infrastructure, not trackers; Google
+  reCAPTCHA is `necessary`; Searchanise and iuteCredit are `functional`.
+### 0.5.0
+- **The theme engine.** `theme.font` (the banner takes the site's font by
+  default, `'system'` restores the old stack), `theme.radius: { card, button }`
+  in px, and `theme.buttons` — variant, background, text, border and border
+  width per button. Accept and reject are always equal in size, weight and
+  variant, by construction. Contrast is checked automatically: text below 4.5:1
+  and borders below 3:1 are corrected.
+- `texts.policyUrl` and `texts.detailsAction` (`policy` / `settings` / `hide`):
+  «Learn more» now does something. Before 0.5.0 it was `<a href="#">` with no
+  handler — any site on 0.4.x or earlier has a dead link.
+- The corner card gained its reference geometry: up to 540px wide, 24px padding,
+  buttons in a row with an 8px gap and stacked on narrow screens.
+### 0.4.1
+- Infrastructure list (`ConsentKit._infra()`): builder CDNs, Google Fonts and
+  captcha, never intercepted by strict mode.
+  `static.cloudflareinsights.com` is deliberately excluded — it is analytics.
+### 0.4.0
+- **Strict mode** (`blocking.mode: 'strict'`): before consent, any third-party
+  script or iframe that is not same-site, allow-listed or in the built-in
+  allowlist is held back and filed as `marketing`.
+- `ConsentKit._extendHostDb()` and the `hostdb` config key.
+- `<iframe src>` is intercepted, not just scripts.
+### 0.3.6
+- Branding moved to `src/ck-ui-branding.js`, so `--no-branding` drops the code
+  as well as the config (~26 KB off a block).
+### 0.3.5
+- **Server-side tracker markup in the WordPress plugin, on by default** — the
+  one case the browser engine cannot cover. The database shipped to PHP is
+  generated from `src/ck-core.js`, and a test fails when the two drift.
+- The debug panel became a lazily-loaded file behind a ~5 KB loader.
+### 0.3.2
+- The GTM container is no longer blocked: tags inside it obey Consent Mode, and
+  blocking the container breaks that. `/gtag/js` is still blocked by path.
 ## Project status
-**This is a prototype (v0.3), not a released product.** It is honest about what
-has been verified and what has not.
+**This is a prototype (v0.5.12), not a released product.** It is honest about
+what has been verified and what has not.
 ### Verified
@@ -893,6 +1152,11 @@ has been verified and what has not.
 - `dataLayer` event trace for consent restore, upgrade and withdrawal.
 - npm entry points and TypeScript types: syntax and import smoke tests in Node
   without a DOM.
+- An automated suite runs under `npm test` (`node --test test/*.test.mjs`):
+  blocking engine, tracker-database classification and its PHP export, services,
+  the theme and contrast arithmetic, the settings panel, branding, the debug
+  loader and panel, the generated site, and a version guard that fails when
+  `package.json`, `src/ck-core.js` and the blocks in `ready/` drift apart.
 - PHP files of the WordPress plugin pass `php -l` on 7.4, 8.3 and 8.5.
 - The server-side rewriting engine has its own suite of 61 cases
   (`plugins/wordpress/consentkit/tests/rewrite.test.php`), green on PHP 7.4,
@@ -910,16 +1174,20 @@ has been verified and what has not.
   and structurally modelled on the documented export format, but Tag Manager has
   not accepted it in practice; some field names (notably GA4 config
   `measurementId` vs `tagId`) may need correction on first import.
-- **Translations beyond `en`, `ru`, `de` and `fr` are drafts.** They are usable
-  but have not been reviewed by native speakers. Legal wording — "Reject all",
-  "always active" — should be checked by someone who knows the local regulator's
-  language before you rely on it.
+- **The 32 locales of the language pack are drafts.** Only `en` and `ru` — the
+  two built into the UI — are authored rather than translated. The rest are
+  usable but have not been reviewed by native speakers (the weakest are `mt`,
+  `ga`, `is`, `sq`, `mk`; `pl` mixes politeness forms). Legal wording — "Reject
+  all", "always active" — should be checked by someone who knows the local
+  regulator's language before you rely on it.
 - **There is no server-side consent log.** Consent lives only in the visitor's
   browser (cookie plus `localStorage`). GDPR accountability may require you to
   be able to *demonstrate* that consent was given; that record-keeping is not
   part of this prototype and you would have to build it yourself.
-- No automated test suite and no CI beyond the Pages deployment; verification is
-  the manual smoke checklist in [CONTRIBUTING.md](CONTRIBUTING.md).
+- **No end-to-end browser tests and no CI beyond the Pages deployment.** The
+  `npm test` suite runs in Node against DOM stubs, not a real browser; browser
+  verification is still the manual smoke checklist in
+  [CONTRIBUTING.md](https://github.com/vermoh/ConsentKit/blob/main/CONTRIBUTING.md).
 - Not audited by a lawyer. ConsentKit is a technical building block, not legal
   advice, and it cannot make a site compliant on its own — your privacy policy,
   your cookie inventory and your record-keeping are still yours.
@@ -927,7 +1195,7 @@ has been verified and what has not.
 ### Contributing
 Structure of the repository, the GDPR invariants that must not change, and how
-to run the checks: [CONTRIBUTING.md](CONTRIBUTING.md).
+to run the checks: [CONTRIBUTING.md](https://github.com/vermoh/ConsentKit/blob/main/CONTRIBUTING.md).
 ## License
@@ -935,8 +1203,8 @@ Copyright (c) 2026 E-COM CONSULT PLUS.
 | Part | Licence |
 |---|---|
-| Client (`src/`), npm package, inline builder, demo | [MIT](LICENSE) |
-| WordPress plugin (`plugins/wordpress/consentkit/`) | [GPL-2.0-or-later](plugins/wordpress/consentkit/LICENSE) |
+| Client (`src/`), npm package, inline builder, demo | [MIT](https://github.com/vermoh/ConsentKit/blob/main/LICENSE) |
+| WordPress plugin (`plugins/wordpress/consentkit/`) | [GPL-2.0-or-later](https://github.com/vermoh/ConsentKit/blob/main/plugins/wordpress/consentkit/LICENSE) |
 The client is MIT so it can be embedded anywhere without licence friction. The
 WordPress plugin ships under GPLv2+ because the WordPress ecosystem effectively
@@ -944,4 +1212,4 @@ requires it; MIT permits the plugin to bundle copies of the client in its
 `assets/` directory.
 Contributions require a `Signed-off-by` line (DCO) — see
-[CONTRIBUTING.md](CONTRIBUTING.md).
+[CONTRIBUTING.md](https://github.com/vermoh/ConsentKit/blob/main/CONTRIBUTING.md).

package/npm/index.d.ts CHANGED Viewed

@@ -141,6 +141,12 @@ export interface CkThemeConfig {
   mode?: 'auto' | 'light' | 'dark';
   /** v0.2. Overrides the built-in dark palette. */
   dark?: CkDarkTheme;
+  /**
+   * v0.5.10. The light-mode mirror of `dark`, for one value: an `onAccent` the
+   * owner set for the filled buttons' text in light mode. A typed value is
+   * painted as typed (contrast is a warning, never a correction).
+   */
+  light?: { onAccent?: string };
 }
 /** v0.5.0 (SPEC V1.6 §2). Copy and the «Learn more» control. */

package/npm/internal-stub.mjs CHANGED Viewed

@@ -28,7 +28,7 @@ export function undecidedState() {
  */
 export function createStub() {
   const stub = {
-    version: '0.5.10',
+    version: '0.5.12',
     config: {},
     init: function () { return undecidedState(); },
     allowed: function (cat) { return cat === 'necessary'; },

package/package.json CHANGED Viewed

@@ -1,6 +1,6 @@
 {
   "name": "@ecomconsult/consentkit",
-  "version": "0.5.10",
+  "version": "0.5.12",
   "description": "GDPR cookie consent core with blocking engine, Shadow DOM UI and Google Consent Mode v2. Zero dependencies, no build step.",
   "repository": {
     "type": "git",

package/src/ck-core.js CHANGED Viewed

@@ -108,6 +108,7 @@
     'ct.pinterest.com': 'marketing',          // subdomain: pinterest.com is a normal site
     'sc-static.net': 'marketing',             // Snapchat pixel CDN
     'bat.bing.com': 'marketing',              // subdomain: bing.com is a normal site
+    'c.bing.com': 'marketing',                // Bing pixel (/c.gif) fired by UET and Clarity
     'adroll.com': 'marketing',
     'hs-analytics.net': 'marketing',          // HubSpot tracking
     'hs-scripts.com': 'marketing',
@@ -796,13 +797,26 @@
   // key that is not a service id — is dropped rather than trusted: this record
   // is attacker-writable (it lives in a cookie and in localStorage), and a
   // malformed entry must not be able to widen or narrow what gets blocked.
+  //
+  // 0.5.12 — a service in the `necessary` group is ALSO dropped, on read and on
+  // write alike. Such a service has no switch in the panel (the group is always
+  // on, so a control that could only ever refuse it would be a lie), and
+  // allowedService() answers `true` for it unconditionally — so a denial for one
+  // could only ever be dead weight that survives in the record and confuses the
+  // beacon and the debug report. The filter is safe here because init() runs
+  // buildServices() BEFORE loadRecord(), so SERVICE_BY_ID is already populated
+  // when a stored map is read back; an id the registry does not know is left
+  // alone, exactly as before, because nothing can be claimed about its category.
   function readServices(raw) {
     var out = {};
     if (!isPlainObject(raw)) { return out; }
     var keys = Object.keys(raw);
     for (var i = 0; i < keys.length && i < SERVICE_MAX; i++) {
       var k = keys[i];
-      if (raw[k] === false && SERVICE_ID_RE.test(k)) { out[k] = false; }
+      if (raw[k] !== false || !SERVICE_ID_RE.test(k)) { continue; }
+      var s = SERVICE_BY_ID[k];
+      if (s && s.category === 'necessary') { continue; }
+      out[k] = false;
     }
     return out;
   }
@@ -1201,6 +1215,14 @@
   // silent block of something the visitor was never asked about.
   function serviceDenied(id) {
     if (!id || typeof id !== 'string') { return false; }
+    /* 0.5.12 — a service in the `necessary` group is NEVER denied, whatever the
+       map says. readServices() already strips such an entry on every read and
+       write, so this is the single choke point that also covers a map mutated
+       by some other path: deniedForSrc() (the blocking patches), and
+       deniedServiceIds() (the beacon field and the debug report) both ask this
+       question, so answering it once here keeps the three from drifting. */
+    var s = SERVICE_BY_ID[id];
+    if (s && s.category === 'necessary') { return false; }
     return state.services[id] === false;
   }
@@ -1212,6 +1234,13 @@
   function allowedService(id) {
     var s = SERVICE_BY_ID[id];
     if (!s) { return true; }                  // unknown id: nothing to withhold
+    /* 0.5.12 — a `necessary` service is allowed, full stop. The group cannot be
+       switched off (allowed('necessary') is always true), the panel renders no
+       switch for it, and readServices() drops any denial that reaches the map.
+       This is the belt to that braces: a denial arriving by some path neither
+       covers — a stale in-memory map, a caller reaching past accept() — must
+       still not be able to hold back something the visitor cannot re-enable. */
+    if (s.category === 'necessary') { return true; }
     if (!allowed(s.category)) { return false; }
     return !serviceDenied(id);
   }
@@ -1229,7 +1258,10 @@
   function deniedServiceIds() {
     var out = [];
     for (var i = 0; i < SERVICES.length; i++) {
-      if (state.services[SERVICES[i].id] === false) { out.push(SERVICES[i].id); }
+      // Through serviceDenied(), not the raw map: that is the one place the
+      // `necessary` rule lives, so the beacon and the debug report can never
+      // name a service the blocking engine is in fact allowing.
+      if (serviceDenied(SERVICES[i].id)) { out.push(SERVICES[i].id); }
     }
     return out;
   }
@@ -1941,7 +1973,7 @@
   // Public API
   // ---------------------------------------------------------------------------
   var ConsentKit = {
-    version: '0.5.10',
+    version: '0.5.12',
     config: config,
     init: function (userConfig) {

package/src/ck-locales.js CHANGED Viewed

@@ -584,6 +584,10 @@
     ckCount: ['{n} cookie', '{n} cookie-uri', '{n} de cookie-uri'],
     svcPolicy: 'Politica',
     svcCookies: 'Ce cookie-uri pune',
+    // 0.5.12 — dezvăluirea din rând. NU `more`, care aici este o propoziție
+    // («Aflați mai multe»), nu un control de rând.
+    svcDetails: 'Detalii',
+    svcListLabel: 'Servicii și cookie-uri din acest grup',
     cat: {
       necessary: { title: 'Necesare', desc: 'Sunt necesare pentru funcționarea site-ului: autentificare, securitate, reținerea alegerii dumneavoastră. Nu pot fi dezactivate.' },
       functional: { title: 'Funcționale', desc: 'Rețin alegerile dumneavoastră: limba, coșul, chatul.' },

package/src/ck-ui.js CHANGED Viewed

@@ -44,6 +44,14 @@
       // The service's own cookies, listed under it rather than in the group's
       // «Which cookies» table.
       svcCookies: 'Cookies it sets',
+      // 0.5.12 — the per-row disclosure. A row is one line until this is opened;
+      // the purpose, the policy link and the service's cookie table live behind
+      // it. NOT `more`: that string is the banner's «Подробнее» and reads
+      // «Aflați mai multe» in ro, which is a sentence, not a row control.
+      svcDetails: 'Details',
+      // The group's own disclosure: how many services are hidden behind the
+      // «N services · M cookies» button. Only ever read by a screen reader.
+      svcListLabel: 'Services and cookies in this group',
       // SPEC V1.10 §2 — the blocked-embed placeholder. {host} is the vendor
       // label when the database knows one and the bare host otherwise; {cat} is
       // the localized category title, taken from cat.<name>.title below, so the
@@ -97,6 +105,8 @@
       ckCount: ['{n} cookie', '{n} cookie', '{n} cookie'],
       svcPolicy: 'Политика',
       svcCookies: 'Какие cookie ставит',
+      svcDetails: 'Подробнее',
+      svcListLabel: 'Сервисы и cookie этой группы',
       phText: 'Здесь содержимое от {host}. Оно загрузится после согласия на «{cat}».',
       phAllow: 'Разрешить и показать',
       phSettings: 'Настроить cookie',
@@ -142,7 +152,12 @@
     // branch in buildStrings() — listing them here would be a bug, because this
     // loop only copies values that are `typeof === 'string'` and would leave
     // every external locale on the English plurals.
-    'svcPolicy', 'svcCookies'
+    'svcPolicy', 'svcCookies',
+    // 0.5.12 — the per-row «Подробнее» disclosure and the accessible name of the
+    // group's own one. Both are plain strings, so they belong here: a key left
+    // out of this list is `undefined` for all 32 external locales and renders
+    // the literal word "undefined" on the card.
+    'svcDetails', 'svcListLabel'
   ];
   // Plural-form keys, filled separately from STR_KEYS (see above).
@@ -420,15 +435,11 @@
     'border-color:var(--ck-reject-bd);border-width:var(--ck-reject-bw)}',
     '.ck-btn--settings{background:var(--ck-settings-bg);color:var(--ck-settings-fg);',
     'border-color:var(--ck-settings-bd);border-width:var(--ck-settings-bw)}',
-    /* Kept for the preferences panel's own footer, which is not themable. */
+    /* Unused by the UI since 0.5.11: the preferences panel's footer moved to
+       the accept/settings role classes above, so it follows the banner. Kept
+       as a compatibility shim for integrator CSS and older inline blocks that
+       still name these classes — nothing in this file emits them any more. */
     '.ck-btn--filled{background:var(--ck-accent);border-color:var(--ck-accent);color:var(--ck-on-accent)}',
-    /* Live, not a fallback: these paint the preferences panel's own Accept
-       all / Reject all. Transparent fill means the LABEL sits on the card, so
-       it takes --ck-link like every other accent-coloured text; the BORDER is
-       non-text and answers to 3:1, so it keeps the raw accent. The footer's
-       background is --ck-soft rather than --ck-bg, but soft is a 5% ink mix of
-       the card — the ratio difference is well inside the noise, and a second
-       link token per background would break «один код — одни числа». */
     '.ck-btn--outline{background:transparent;border-color:var(--ck-accent);color:var(--ck-link)}',
     '.ck-btn--ghost{min-width:0;border-color:var(--ck-line);color:var(--ck-ink);font-weight:500}',
@@ -465,21 +476,50 @@
     /* SPEC V1.12 §3 — «N сервисов · M cookie». --ck-muted, like every other
        secondary label on the card, and it is measured for AA against the card
        background by the same rule the description above answers to. */
+    /* 0.5.12 — the counter is now the group's disclosure BUTTON. It keeps the
+       muted label's size and colour (it is still a secondary label, measured
+       for AA against the card background by the same rule as the description),
+       and gains a caret and a hit area. `border:0;background:transparent` is
+       needed because the panel's reset styles buttons, not because a link is
+       being faked — it is a real button and the global :focus-visible rule
+       gives it a visible ring. */
     '.ck-cat__count{font-size:12px;font-weight:500;color:var(--ck-muted)}',
+    '.ck-cat__toggle{border:0;background:transparent;padding:2px 0;cursor:pointer;',
+    'display:inline-flex;align-items:center;gap:5px;font-family:inherit;text-align:left}',
+    '.ck-cat__caret{width:0;height:0;flex:none;border:4px solid transparent;',
+    'border-left-color:currentColor;border-right:0}',
+    '.ck-cat__toggle[aria-expanded="true"] .ck-cat__caret{transform:rotate(90deg)}',
-    /* ---- services inside a group (SPEC V1.12 §3) ---- */
+    /* ---- services inside a group (SPEC V1.12 §3, compacted in 0.5.12) ---- */
     /* Indented and rule-separated so the nesting reads without colour: a
        service belongs to the group above it, and its own cookie table belongs
        to it. The left border is the only decoration; everything else is
        spacing, which survives forced-colours mode intact. */
-    '.ck-svcs{margin:12px 0 0;padding-left:12px;border-left:2px solid var(--ck-line)}',
-    '.ck-svc{padding:10px 0;border-bottom:1px solid var(--ck-line)}',
+    '.ck-cat__region{margin-top:12px}',
+    '.ck-svcs{padding-left:12px;border-left:2px solid var(--ck-line)}',
+    '.ck-svc{padding:8px 0;border-bottom:1px solid var(--ck-line)}',
     '.ck-svc:first-child{padding-top:2px}',
     '.ck-svc:last-child{border-bottom:0;padding-bottom:2px}',
-    '.ck-svc__top{display:flex;gap:12px;align-items:flex-start}',
+    /* One line: name, vendor, then the switch pinned to the right. `center`
+       rather than flex-start, because the row is a single line of text now and
+       the switch reads as belonging to it. */
+    '.ck-svc__top{display:flex;gap:10px;align-items:center}',
     '.ck-svc__txt{flex:1 1 auto;min-width:0}',
-    '.ck-svc__name{font-size:14px;font-weight:600}',
-    '.ck-svc__vendor{margin:2px 0 0;font-size:12.5px;color:var(--ck-muted)}',
+    /* The name and the vendor share a line and WRAP rather than truncate: at
+       320px a long «Google Analytics · Google Ireland Limited» becomes two
+       lines and the switch stays where it is, still reachable. */
+    '.ck-svc__name{display:flex;align-items:baseline;gap:6px;flex-wrap:wrap;',
+    'font-size:14px;font-weight:600;line-height:1.35}',
+    '.ck-svc__vendor{margin:0;font-size:12.5px;font-weight:400;color:var(--ck-muted)}',
+    /* «всегда активны» on a necessary service's row, where its switch used to
+       be: the same pill the group header wears, one step smaller. */
+    '.ck-svc__badge{font-size:11px;font-weight:500;color:var(--ck-muted);',
+    'border:1px solid var(--ck-line);border-radius:999px;padding:0 7px}',
+    /* The row's own «Подробнее». Tighter than a group's <details> — it sits
+       inside a row, not between two of them. */
+    '.ck-svc__det{margin-top:2px}',
+    '.ck-svc__det>summary{font-size:12.5px}',
+    '.ck-svc__body{padding:2px 0 4px}',
     '.ck-svc__desc{margin:4px 0 0;font-size:13px;color:var(--ck-muted)}',
     /* --ck-link, not --ck-accent: accent-coloured TEXT goes through the same
        >= 4.5:1 rule as «Подробнее» — see the note on the `a{}` rule above. */
@@ -516,8 +556,12 @@
     '.ck-empty{margin:8px 0 0;font-size:13px;color:var(--ck-muted)}',
     /* ---- floating button ---- */
+    /* 0.5.11 — the floating button wears the ACCEPT button's colours, so the
+       one control that outlives the banner still reads as the owner's brand.
+       Both tokens are resolved once in resolveButtonStyles (`fab`) and only
+       read here — «один код — одни числа». */
     '.ck-fab{position:fixed;left:16px;bottom:16px;z-index:2147482999;width:48px;height:48px;',
-    'border-radius:50%;border:1px solid var(--ck-line);background:var(--ck-bg);color:var(--ck-link);',
+    'border-radius:50%;border:1px solid var(--ck-line);background:var(--ck-fab-bg);color:var(--ck-fab-fg);',
     'display:inline-flex;align-items:center;justify-content:center;padding:0}',
     '.ck-fab svg{width:24px;height:24px;display:block}',
@@ -898,7 +942,7 @@
   /* Config values are interpolated into the TEXT of a generated stylesheet, so
      an unvalidated value can close the declaration and open rules of its own
-     ("10px;}.ck-btn--filled{display:none" hides "Reject all"). config.theme is
+     ("10px;}.ck-btn--reject{display:none" hides "Reject all"). config.theme is
      not trusted input: in standalone mode it comes straight from the embedding
      page or an integrator's admin panel, with no server-side validation
      anywhere in the path. So every value is matched against a strict grammar
@@ -1271,9 +1315,10 @@
     };
     /* The accent as TEXT on the card. Same >= 4.5 rule, same function, one
-       number: links, «Подробнее», the cookie-table summary and the floating
-       button's icon all read the token this produces, so none of them can
-       drift from what the debug panel and the cabinet quote. Note the
+       number: links, «Подробнее» and the cookie-table summary all read the
+       token this produces, so none of them can drift from what the debug
+       panel and the cabinet quote. (The floating button left this token in
+       0.5.11 — it now follows the accept button; see `fab` below.) Note the
        measurement is against cardBg — an accent that is fine inside a filled
        button can still be unreadable on the card behind it.
@@ -1414,6 +1459,46 @@
       }
       out.buttons[role] = rec;
     }
+    /* The floating button (0.5.11). It is a filled circle that outlives the
+       banner, and the owner's rule is that it wears the ACCEPT button's
+       colours — no setting of its own.
+       accept FILLED: take its bg/fg verbatim. That inherits the 0.5.10 rule
+       for free — a typed low-contrast fg stays exactly as typed here too, and
+       is reported through `low` rather than corrected.
+       accept OUTLINE: there is no fill to borrow, so the button's BORDER
+       colour becomes the circle and the CARD colour becomes the icon — the
+       outline button's two real colours, swapped. Both are derived for the
+       fab (nobody typed "the floating button is this colour"), so the icon
+       goes through the >= 4.5 rule; ensureContrast picks the readable member
+       of the pair, which on a dark border is the card itself and on a pale
+       one steps away from it. When accept's border is itself derived it is
+       already the accent stepped to 3:1, so this is also the accent/on-accent
+       fallback the brief describes. */
+    var acc = out.buttons.accept;
+    if (acc.variant === 'filled') {
+      out.fab = {
+        bg: acc.bg,
+        fg: acc.fg,
+        ratio: acc.ratio,
+        adjusted: acc.adjusted,
+        low: acc.low,
+        against: acc.bg
+      };
+    } else {
+      var fabBg = acc.border;
+      var fabRes = ensureContrast(cardBg, fabBg, 4.5);
+      out.fab = {
+        bg: fabBg,
+        fg: fabRes.color,
+        ratio: fabRes.ratio,
+        adjusted: fabRes.adjusted,
+        low: below(fabRes.ratio, 4.5),
+        against: fabBg
+      };
+    }
     return out;
   }
@@ -1438,6 +1523,12 @@
     // same way as __buttons: one pass per mode, so the light and dark blocks
     // each carry their own contrast-checked link colour.
     if (p.__link) d.push('--ck-link:' + p.__link.color);
+    // The floating button's pair, resolved from the accept button in the same
+    // pass, so light and dark each carry their own (0.5.11).
+    if (p.__fab) {
+      d.push('--ck-fab-bg:' + p.__fab.bg);
+      d.push('--ck-fab-fg:' + p.__fab.fg);
+    }
     var btns = p.__buttons;
     if (btns) {
       for (var i = 0; i < BTN_ROLES.length; i++) {
@@ -1511,17 +1602,20 @@
     light.__buttons = lightBtn.buttons;
     dark.__buttons = darkBtn.buttons;
-    // `--ck-on-accent` paints the text of every filled surface that is NOT a
-    // banner button — the panel's «Сохранить выбор» and the floating button —
-    // straight from the palette. A derived onAccent therefore has to pass the
-    // same >= 4.5 rule against the accent, or a white accent gets white text
-    // (the owner saw exactly that). Done AFTER the buttons are resolved, so
+    // `--ck-on-accent` paints the text of the remaining filled surfaces that
+    // are not banner buttons — since 0.5.11 that is the blocked-embed
+    // placeholder's button, the panel foot and the floating button having
+    // moved onto the accept button's own tokens. A derived onAccent still has
+    // to pass the >= 4.5 rule against the accent, or a white accent gets white
+    // text (the owner saw exactly that). Done AFTER the buttons are resolved, so
     // the accept button still records `adjusted:true` for the same correction.
     // An onAccent the owner set is painted as set — the 0.5.10 rule.
     if (!light.onAccentExplicit) light.onAccent = ensureContrast(light.onAccent, light.accent, 4.5).color;
     if (!dark.onAccentExplicit) dark.onAccent = ensureContrast(dark.onAccent, dark.accent, 4.5).color;
     light.__link = lightBtn.link;
     dark.__link = darkBtn.link;
+    light.__fab = lightBtn.fab;
+    dark.__fab = darkBtn.fab;
     var mode = theme.mode;
     if (mode !== 'light' && mode !== 'dark') mode = 'auto';
@@ -1658,7 +1752,23 @@
     }
   }
+  /* SPEC V1.12 §3, reshaped in 0.5.12 — one service, on ONE line.
+     0.5.8 rendered the name, the vendor, the purpose paragraph, the policy link
+     and a cookie table for every service, all at once. Eight services filled the
+     panel and the visitor scrolled past the switches they came for. The row is
+     now: name (bold) · vendor (muted) · switch, and nothing else until the row's
+     own «Подробнее» is opened — behind which the purpose, the policy link and
+     «Какие cookie ставит (N)» live, unchanged.
+     `cat === 'necessary'` renders NO switch. The group is always on and cannot
+     be refused, so a control that could only ever sit at «off» (which is what
+     0.5.11 showed, because syncGroup() only ever ran for the opt-in groups)
+     tells the visitor a lie about what they can change. The «всегда активны»
+     badge the group header already carries says the true thing instead. */
   function buildService(svc, cat, rows) {
+    var locked = cat === 'necessary';
     var wrap = el('div', 'ck-svc');
     var top = el('div', 'ck-svc__top');
     var txt = el('div', 'ck-svc__txt');
@@ -1668,45 +1778,68 @@
     var nameSpan = el('span', null, svc.name);
     nameSpan.id = nameId;
     name.appendChild(nameSpan);
+    // Vendor on the SAME line as the name now, not a paragraph under it. The
+    // row wraps rather than truncates, so a long pair still reads at 320px.
+    if (svc.vendor) name.appendChild(el('span', 'ck-svc__vendor', svc.vendor));
+    if (locked) name.appendChild(el('span', 'ck-svc__badge', T.alwaysOn));
     txt.appendChild(name);
-    if (svc.vendor) txt.appendChild(el('p', 'ck-svc__vendor', svc.vendor));
+    top.appendChild(txt);
-    var descId = null;
-    var purpose = servicePurpose(svc);
-    if (purpose) {
-      descId = nameId + '-desc';
-      var p = el('p', 'ck-svc__desc', purpose);
-      p.id = descId;
-      txt.appendChild(p);
-    }
-    /* «Политика» — target=_blank rel=noopener, per §3. The URL is already
-       http(s)-validated by the core's normalizeService(), which is where a
-       javascript: address is dropped; nothing unvalidated reaches an href. */
-    if (svc.privacyUrl) {
-      var a = el('a', 'ck-svc__policy', T.svcPolicy);
-      a.href = svc.privacyUrl;
-      a.target = '_blank';
-      a.rel = 'noopener noreferrer';
-      // The link text is the same word on every row, so a screen reader needs
-      // the service name to tell them apart.
-      a.setAttribute('aria-label', T.svcPolicy + ' — ' + svc.name);
-      txt.appendChild(a);
-    }
-    var sw = makeServiceSwitch(svc, cat);
-    sw.setAttribute('aria-labelledby', nameId);
-    if (descId) sw.setAttribute('aria-describedby', descId);
-    if (!serviceSwitches[cat]) serviceSwitches[cat] = [];
-    serviceSwitches[cat].push(sw);
+    /* No switch for a necessary service — and no entry in serviceSwitches[],
+       which is what keeps readSwitches() from ever writing such an id into the
+       denial map. (It iterates OPT_IN, so it could not today; not registering
+       the switch means it still cannot if that loop ever widens.) */
+    if (!locked) {
+      var sw = makeServiceSwitch(svc, cat);
+      /* aria-labelledby only. 0.5.8 also pointed aria-describedby at the purpose
+         paragraph; in 0.5.12 that paragraph lives inside a CLOSED <details>, and
+         a description a screen reader cannot reach until the visitor opens
+         something else is worse than none — the name and the switch's own state
+         are what the control has to announce. The purpose is still there, one
+         «Подробнее» away, as its own readable text. */
+      sw.setAttribute('aria-labelledby', nameId);
+      if (!serviceSwitches[cat]) serviceSwitches[cat] = [];
+      serviceSwitches[cat].push(sw);
+      top.appendChild(sw);
+    }
-    top.appendChild(txt);
-    top.appendChild(sw);
     wrap.appendChild(top);
+    /* Everything else goes behind the row's own disclosure. <details>/<summary>
+       rather than a button: the keyboard behaviour, the focus ring and the
+       expanded state come from the browser, and it is the same control the
+       cookie tables have used since 0.5.7. */
+    var purpose = servicePurpose(svc);
     var own = cookieRowsForService(rows, svc);
-    if (own.length) wrap.appendChild(cookieTable(own, T.svcCookies + ' (' + own.length + ')'));
+    if (purpose || svc.privacyUrl || own.length) {
+      var det = el('details', 'ck-det ck-svc__det');
+      var sum = el('summary');
+      sum.appendChild(document.createTextNode(T.svcDetails));
+      // The word is the same on every row, so a screen reader needs the service
+      // name to tell one «Подробнее» from the next.
+      sum.setAttribute('aria-label', T.svcDetails + ' — ' + svc.name);
+      det.appendChild(sum);
+      var body = el('div', 'ck-svc__body');
+      if (purpose) body.appendChild(el('p', 'ck-svc__desc', purpose));
+      /* «Политика» — target=_blank rel=noopener, per §3. The URL is already
+         http(s)-validated by the core's normalizeService(), which is where a
+         javascript: address is dropped; nothing unvalidated reaches an href. */
+      if (svc.privacyUrl) {
+        var a = el('a', 'ck-svc__policy', T.svcPolicy);
+        a.href = svc.privacyUrl;
+        a.target = '_blank';
+        a.rel = 'noopener noreferrer';
+        a.setAttribute('aria-label', T.svcPolicy + ' — ' + svc.name);
+        body.appendChild(a);
+      }
+      if (own.length) body.appendChild(cookieTable(own, T.svcCookies + ' (' + own.length + ')'));
+      det.appendChild(body);
+      wrap.appendChild(det);
+    }
     return wrap;
   }
@@ -1748,6 +1881,27 @@
     return det;
   }
+  /* 0.5.12 — the group's disclosure button.
+     «N сервисов · M cookie» was a static label in 0.5.8; it is now the control
+     that reveals the group's services and its cookie list, COLLAPSED by default.
+     A real <button aria-expanded> rather than a <details>, because the panel
+     already owns the region it toggles — the services list and the loose-cookie
+     table are siblings that must move together, and wrapping both in a
+     <details> would put a second summary line above the one the header already
+     has. Keyboard and focus come free with a button; the ring is the panel's
+     own :focus-visible rule. */
+  function makeGroupToggle(cat, label, regionId) {
+    var b = el('button', 'ck-cat__count ck-cat__toggle');
+    b.type = 'button';
+    b.setAttribute('aria-expanded', 'false');
+    b.setAttribute('aria-controls', regionId);
+    b.appendChild(el('span', 'ck-cat__caret'));
+    b.appendChild(document.createTextNode(label));
+    b.dataset.cat = cat;
+    return b;
+  }
   function buildCategory(cfg, cat) {
     var meta = T.cat[cat] || { title: cat, desc: '' };
     var locked = cat === 'necessary';
@@ -1779,9 +1933,11 @@
        «0 сервисов · 3 cookie». The cookie half counts the whole group, services
        and loose rows alike: it answers «сколько cookie в этой группе», which is
        the question the line is there to answer. */
+    var toggle = null;
+    var regionId = nameId + '-svcs';
     if (svcs.length) {
-      name.appendChild(el('span', 'ck-cat__count',
-        groupCountLabel(svcs.length, rows.length, T, LANG)));
+      toggle = makeGroupToggle(cat, groupCountLabel(svcs.length, rows.length, T, LANG), regionId);
+      name.appendChild(toggle);
     }
     var sw = makeSwitch(cat, locked);
@@ -1793,23 +1949,47 @@
     top.appendChild(sw);
     wrap.appendChild(top);
+    // «Cookie в этой группе (N)» keeps its old meaning: what is left once each
+    // service has claimed its own. With no services that is the whole table and
+    // the summary line is byte-for-byte what 0.5.7 rendered.
+    var loose = looseCookies(rows, svcs);
     if (svcs.length) {
+      /* Both halves live inside the collapsed region: the services and, at the
+         end, the group's own «Какие cookie (N)». `hidden` rather than a class,
+         so the region is out of the accessibility tree and out of the tab order
+         while collapsed — a class that only sets display:none would leave the
+         switches focusable to a keyboard user who cannot see them. */
+      var region = el('div', 'ck-cat__region');
+      region.id = regionId;
+      region.hidden = true;
       var list = el('div', 'ck-svcs');
       // A list, so a screen reader announces «3 items» before reading them.
       list.setAttribute('role', 'list');
+      list.setAttribute('aria-label', T.svcListLabel);
       for (var s = 0; s < svcs.length; s++) {
         var item = buildService(svcs[s], cat, rows);
         item.setAttribute('role', 'listitem');
         list.appendChild(item);
       }
-      wrap.appendChild(list);
-    }
+      region.appendChild(list);
-    // «Cookie в этой группе (N)» keeps its old meaning: what is left once each
-    // service has claimed its own. With no services that is the whole table and
-    // the summary line is byte-for-byte what 0.5.7 rendered.
-    var loose = looseCookies(rows, svcs);
-    if (loose.length) {
+      if (loose.length) {
+        region.appendChild(cookieTable(loose, T.cookiesIn + ' (' + loose.length + ')'));
+      }
+      toggle.addEventListener('click', function () {
+        var open = toggle.getAttribute('aria-expanded') === 'true';
+        toggle.setAttribute('aria-expanded', open ? 'false' : 'true');
+        region.hidden = open;
+      });
+      wrap.appendChild(region);
+    } else if (loose.length) {
+      // No services: the cookie table sits where it always did, top level and
+      // never behind a disclosure — a pre-0.5.8 config renders as it did in
+      // 0.5.7, which is what «старый конфиг рендерится как раньше» asks for.
       wrap.appendChild(cookieTable(loose, T.cookiesIn + ' (' + loose.length + ')'));
     }
@@ -1997,11 +2177,21 @@
     p.appendChild(body);
     var foot = el('div', 'ck-panel__foot');
-    var save = el('button', 'ck-btn ck-btn--filled', T.save);
+    /* 0.5.11 — the panel follows the BANNER's buttons, with no setting of its
+       own: «Сохранить выбор» is the same role as «Принять всё» and wears the
+       accept class, «Принять всё»/«Отклонить всё» here are secondary and wear
+       the settings («Настроить») class. Reusing the role classes means the
+       filled/outline split stays a VALUE change in the tokens — the panel
+       never picks a class from the resolved variant, so a theme.buttons edit
+       is still applyTheme()-only and signature() still need not see buttons.
+       Panel layout is untouched: `.ck-panel__foot .ck-btn{flex:1 1 150px}`
+       (0,2,0) outranks `.ck-btn{flex:1 1 auto}` and the role classes set no
+       flex of their own. */
+    var save = el('button', 'ck-btn ck-btn--accept', T.save);
     save.type = 'button';
-    var acc = el('button', 'ck-btn ck-btn--outline', T.acceptAll);
+    var acc = el('button', 'ck-btn ck-btn--settings', T.acceptAll);
     acc.type = 'button';
-    var rej = el('button', 'ck-btn ck-btn--outline', T.rejectAll);
+    var rej = el('button', 'ck-btn ck-btn--settings', T.rejectAll);
     rej.type = 'button';
     save.addEventListener('click', function () { doSave(); });