## Parent work Implements the shared Pixie Dark capability needed by Pixie Works GitHub issues [#442](https://github.com/naoi/pixie.works/issues/442) and [#443](https://github.com/naoi/pixie.works/issues/443). Those site-specific issues remain separate and will enable the capability through their own configuration changes and PRs. ## Problem PixieFlow and PixieCore visitors need a normal footer control to revisit the existing EU Cookie Compliance choice after Accept or Reject. The persistent floating "Privacy settings" tab must stay disabled. The existing EUCC 1.29.0 button block requires `withdraw_enabled` and opens a withdraw banner; that is not the desired behavior. The supported `Drupal.eu_cookie_compliance.withdrawAction()` API clears the current preference and reloads, allowing the original Accept/Reject prompt to appear again. ## Scope - Canonical project: https://www.drupal.org/project/pixie_dark - Target branch: `1.x` - Add an opt-in, localized Cookie settings link to the existing PixieFlow and PixieCore footer variants. - On explicit visitor activation, call only the supported EUCC public `withdrawAction()` API; do not manipulate cookies, local storage, or consent state directly. - Keep the link absent by default so nonparticipating sites and other Pixie Dark variants are unchanged. PixieFlow and PixieCore site opt-in is tracked separately in GitHub [#442](https://github.com/naoi/pixie.works/issues/442) and [#443](https://github.com/naoi/pixie.works/issues/443). - No custom module, new theme, contributed module, persistent tab, GA/GTM changes, analytics cookies, ads, or production deployment. ## Implementation steps 1. Inspect the exact Pixie Dark 1.x theme settings, PixieFlow/PixieCore footer templates, translations, library attachment patterns, and EUCC public API behavior. 2. Create or reuse this Work Item issue fork, grant `yas_ai` push access, and create a dedicated branch from the confirmed `1.x` head. 3. Add an optional per-site theme setting and a keyboard-accessible footer link in the PixieFlow and PixieCore variants. Supply English `Cookie settings` and Japanese `Cookie の設定` labels using Drupal translation conventions. 4. Attach narrowly scoped JavaScript only when the opt-in setting is enabled. On activation, verify the public EUCC API exists, invoke `Drupal.eu_cookie_compliance.withdrawAction()`, and allow the module to clear its own consent state and reload. Do not set `withdraw_enabled` or `settings_tab_enabled` to true. 5. Add focused tests for opt-in/off behavior, both variants, both translations, API-unavailable handling, keyboard activation, and visible focus. Do not load GA/GTM or create analytics cookies in tests. 6. Run project checks, inspect the final diff and test results, and open one issue-fork MR to official `1.x`. Record the GitHub dependencies and exact verification. Stop at MR creation for human review. ## Acceptance criteria - The PixieFlow and PixieCore footers can each opt in to one localized Cookie settings control; the setting defaults off. - English and Japanese labels render correctly; the control is keyboard reachable with visible focus. - Activating it calls the EUCC public `withdrawAction()` API and leads to the module's normal choice prompt after reload. - No floating/persistent Privacy settings tab is enabled or reintroduced. - No custom module/theme, direct cookie/storage edits, GA/GTM configuration, unrelated variant changes, or production changes are included. - Automated tests and project checks cover the listed behavior, and one issue-fork MR targets `1.x`. - No RTBC, Approve, merge, release, or production deployment occurs without the applicable later authorization.