13.2.0 — Rich details, refined UI and localized dates

13.2.0 — Rich details, refined UI and localized dates

This minor release completes the K1–K5 implementation review on top of the existing optional Eloquent and multi-source board integration.

Highlights

• Optional CardDetailsProvider, CardDetailSectionData and CardDetailAction contracts for lazy, permission-scoped detail sections; the base DataProvider interface is unchanged.
• Bounded section paging, escaped text, sanitized links, trusted custom templates, independent section permissions and stable operation identities for domain-owned retry handling.
• Configurable drawer width, shared Board/List detail behavior, fixed header/footer, full-screen mobile layout, keyboard focus containment and background scroll locking.
• Improved toolbar, filters, cards/list rows, attachment covers, comments/checklists, member overflow and stage capacity display.
• Jalali dates with morilog/jalali, optional locale/timezone/Persian digits, and Workbench-wide theme/locale controls.
• Server-enforced CRM note transitions, optional archived-card deletion and configurable host create/edit page URLs.

Compatibility

PHP 8.3+, Laravel 13 and Livewire 4 remain supported. Existing providers and handlers do not need new mandatory methods. No commercial model or package migration is added. Host applications retain ownership of authorization, persistence, section actions, transactions and domain idempotency.

Run Composer update and rebuild or republish assets. Review published Blade overrides and the new date settings. The host demo loads Google fonts; the package itself inherits the host font. See upgrade notes and Drawer integration.

Local verification

• 264 PHP tests and 998 assertions passed.
• 21 Edge browser tests passed, including Reverb, multi-board/user isolation, touch, keyboard, RTL, themes and mobile.
• All 50 enterprise scenario reports were regenerated from executed test results.
• Composer validation, asset build and diff whitespace checks passed.
• A 100-card eager-loaded page used 3 queries; the 100k-row/10-column benchmark used 21 queries and hydrated 260 records for 250 visible cards.

Evidence and environment limits: implementation report, machine-readable results, and screenshots. Local verification used Windows, SQLite and Edge; other database/browser environments are reported by CI separately.

13.1.0 — Enterprise models and DaisyUI integration

13.1.0 — Enterprise model adapters and DaisyUI integration

This release adds optional Eloquent model integration and replaces the independent visual palette with DaisyUI components and host theme tokens.

Breaking changes and upgrade

• DaisyUI 5.7.50 and Tailwind CSS 4.3.3 are the verified frontend versions. The integration uses default DaisyUI configuration and an empty class prefix.
• Hosts already using DaisyUI should import resources/css/kanban.css from the Composer package into their global stylesheet. It includes package view source detection. Do not additionally load the standalone CSS bundle.
• The standalone resources/dist/kanban.css includes Tailwind/DaisyUI and a global reset. Hosts without DaisyUI may use it after checking its effect on the rest of the page.
• Inherited theme mode (system) no longer emits data-theme="system". Select data-kb-theme="system" instead. Explicit light/dark choices still set a local theme.
• Published Blade overrides need review for DaisyUI classes while retaining existing behavior hooks. Filters and appearance controls now require opening their disclosure panels.
• PHP 8.3+, Laravel 13 and Livewire 4 remain required. This release does not add Laravel 14 support. No package database migration is required.

Full migration: Upgrade guide. Host CSS, tokens and selectors: Customization guide.

Added

• Optional model trait, definitions and explicit source registry for per-board Eloquent integration.
• Scoped multi-source reads, authenticated keyset cursors, bounded eager loading, SQL counts and aggregate metrics.
• Transactional model actions, operation recovery/deduplication, numeric ranks with local rebalancing, version checks, WIP enforcement and atomic/partial bulk actions.
• Compact presentation, group selection, persistent column collapse, bounded card render windows, touch handles and drag auto-scroll.
• Runnable task, ticket, class, mixed-source and compact model demos.
• Model integration, multi-source, performance, workflow/ranking, metrics, calendar adapter and migration guides.

Changed and fixed

• Use host semantic colors, paired content colors, font inheritance and public DaisyUI radius tokens.
• Group secondary toolbar commands into filters/sorting and appearance disclosures.
• Improve shared metadata readability and pointer/touch control sizes.
• Add named dialog surfaces, keyboard focus containment/return, inert background content, Escape support and stage-form cancellation.
• Make floating forms scrollable and reserve layout space for the demo settings launcher.
• Preserve existing factory/provider/handler integration and stable package behavior selectors.
• Document the complete selector inventory and 31 critical design-review findings with their implementation status.

Validation

• PHP: 221 tests, 794 assertions passed.
• Microsoft Edge: 13 browser scenarios passed, including realtime, touch movement, window navigation, host token inheritance and modal focus.
• Adapter portability evidence: MariaDB and PostgreSQL, 3 tests / 9 assertions each passed.
• Frontend build and dependency audit passed; no dependency vulnerabilities reported by the local audit.
• Remote CI is reported separately on the release commit. Physical-device and full screen-reader conformance testing have not been completed.

Known limitations

• Some workflows still need refinement: internal stage-ID entry in the card form, programmatic field-error association, card-menu clipping near scroll edges and list/table accessibility semantics.
• Custom host palettes and provider-supplied stage colors need host-specific contrast validation. The release is not a WCAG conformance certification.
• The external Calendar package integration is documented as an adapter contract; it has not been verified against an external Calendar installation.
• See design audit and enterprise implementation status for the full limitations.