fix: monitoring colors under themes, daisyUI light/dark, final v0.4.0.0 fixes

[tanhtm]

Summary

Second follow-up to #18. #19 was merged with its first two commits only (sidebar branding, changelist toolbar and pagination). This PR carries the rest of that work, the fixes from a final review, and release hardening before tagging v0.4.0.0.

Monitoring dashboard colors under daisyUI themes

• Problem: the toolbar, selected time range, method badges, share bars and chart lines were hand-styled with Unfold's primary-600/500 and white text, so several themes were unreadable:
  • luxury: white text on a white primary;
  • black and business: accents nearly invisible on a near-black page;
  • cupcake: pale teal on white.
• Controls now use daisyUI components, so they follow the active theme:
  • host and auto-refresh selects: ui-select;
  • time range: a ui-join of ui-btn, with ui-btn-primary on the selected one;
  • Live indicator: ui-badge-success;
  • banner: ui-alert;
  • endpoint methods: solid ui-badge info/warning/error;
  • share bars: ui-progress.
• Matching Unfold's controls: unselected buttons and selects get a panel background and an input border through daisyUI's --ui-btn-bg/--ui-btn-border, like Unfold's own controls.
• Contrast choices:
  • Solid badge variants are used because daisyUI only guarantees contrast for color/-content pairs. The soft badges vanished in black and bumblebee.
  • The soft alert keeps its tint but uses the theme's text color, because its yellow text was unreadable on light themes.
• Lines and bars on the page (chart lines, share bars, toolbar icon) use --mon-accent, the theme primary mixed with the text color. dashboard.js resolves it through the DOM for Chart.js. If the browser can't compute it (no color-mix()), the old palette is used.
• Accessibility:
  • the Live dot pulses only when motion is allowed, and is hidden server-side when auto refresh is off;
  • the status banner is rewritten only when its text changes, so screen readers don't re-read it every refresh;
  • share bars are aria-hidden;
  • the row-header focus ring falls back to currentColor.

daisyUI in the default light/dark modes

Plain dark is Unfold's palette, not a daisyUI theme. daisyUI kept its stock gray-slate base there, so its components showed as gray blocks on Unfold's navy background.

• gen-themes.mjs now points daisyUI base-100/200/300 and base-content at UNFOLD["COLORS"] for light/dark, as it already did for primary. The other 33 themes are unchanged.

Admin fixes from the final review

• Admin index: flash messages were rendered twice, because admin/base.html already has the messages block.
• Pagination:
  • Previous/Next were stuck disabled when Django ignores ?all (more rows than list_max_show_all). The ?all check now also requires can_show_all.
  • The buttons moved to unfold/helpers/wn_page_button.html and get page passed explicitly, so a page variable in the changelist context can't leak in.
  • The soft primary buttons no longer change their text color on hover. Before this, the label turned the same color as the button.
• Changelist toolbar: it renders only when one of its controls will show. Admins with only horizontal filters no longer get an empty row.
• Admin index template extends admin/base_site.html instead of copying its branding block.

Release hardening

• django-unfold>=0.109.0,<0.111: the package overrides about 15 Unfold templates, so an untested Unfold release could break the admin of every project that installs it. Raise the cap after re-testing; 0.110.0 is file-for-file identical to 0.109.0.
• CI for pull requests (.github/workflows/ci.yml). The repo only had a publish workflow, so PRs had no checks. It runs:
  • check, makemigrations --check, msgfmt and the test suite;
  • a job that rebuilds the themes and Tailwind CSS and fails if daisy-themes.css, themes.py or styles.css differ from the committed files.
• Reproducible Tailwind build:
  • The md2html_tailwind4 @source used a python3.* directory glob, which Tailwind doesn't expand. As a result, the classes the markdown preview emits (admonitions etc.) were never compiled; this predates v0.4.0.0: daisyUI themes, server monitoring dashboard, Unfold 0.109, security & performance #18. scripts/tailwind.sh now links the installed package to .tw-md2html, which is gitignored and removed after the build.
  • Markdown prose (docs/, *.md) is no longer scanned. Before this, words in the changelog added utilities, so editing release notes changed styles.css.

Release notes

CHANGELOG.md, README.md and docs/reports/releases/2026-10-13-v0.4.0.0.md now cover all of the above.

Validation

• manage.py test whiteneuron: 42 tests pass in three setups:
  • the test project;
  • the package's own settings;
  • a clean venv with the built wheel, which resolves django-unfold 0.110.0.
• New regression tests each fail without their fix:
  • flash message shown once;
  • Next disabled on the last full page;
  • ?all above list_max_show_all;
  • ?all honored;
  • Previous disabled on page 1.
• Both CI jobs were run by hand in a fresh clone (uv sync --frozen, npm ci, scripts/tailwind.sh): the tests pass and the rebuilt CSS matches the committed files.
• check is clean and makemigrations reports no changes. msgfmt --check passes and makemessages finds no untranslated Vietnamese strings.
• uv build: the wheel contains the new templates, static files, .mo files and migrations.
• Swept 101 admin URLs in a project configured like the README. All return 200 and render the site branding; views the user lacks permission for return 403.
• Checked in Chromium:
  • the monitoring toolbar, banner and endpoints table under all 35 themes, including default light/dark and dark from the OS setting;
  • login, users grid, pagination (including hover) and the theme picker in light/dark;
  • reduced motion;
  • no JS errors.

After merge

Create a GitHub Release for tag v0.4.0.0 on main2.0; the publish workflow uploads it to PyPI. If the release is not dated 2026-10-13, update the date in the release notes.