@appsbd/vue3-appsbd-ui 1.0.16 → 1.0.17

package/.ai/ai_ref_AbDateTimePicker.md

@@ -33,6 +33,9 @@ const datetime = ref(null);
 | `isRange` | `Boolean` | `false` | Enable date-range mode. |
 | `size` | `String` | `"md"` | Adjusts component size (`xs`, `sm`, `md`, `lg`, `xl`, `xxl`). |
 | `containerClass` | `String` | `"mb-3"` | Wrapper class. |
+| `width` | `String \| Number` | `undefined` | Explicit width on the `.apbd-date-time-container` wrapper. A number is treated as px (e.g. `220` -> `220px`); a string is used as-is (e.g. `"50%"`). |
+| `minWidth` | `String \| Number` | `undefined` | `min-width` on the wrapper (same number/string rules as `width`). |
+| `maxWidth` | `String \| Number` | `undefined` | `max-width` on the wrapper (same number/string rules as `width`) — caps growth inside a flex/grid parent without a fixed `width`. |
 | `hints` | `String` | `""` | Helper text. |
 | `isDisable` | `Boolean` | `false` | Disable the picker. |
 | `visibility` | `String` | `"click"` | v-calendar popover trigger. |

package/.ai/ai_ref_AbFilterPanel.md

@@ -4,6 +4,12 @@ Advanced filter panel for list and table views. Supports quick/advance modes, si
 
 `isMultiple` is functional in `isQuickAdvance` mode for `dd` fields: selections toggle on/off and render as removable tag chips on the popover trigger (no `AbMultiSelect` involved). The popover's option list is searchable — locally against `options`, or via `isAjaxSearch` + `onSearch` for server-side search.
 
+`isBuilderFilter` is a Shopify-style filter builder: no field is visible until the user clicks the `+` button. That opens a popover which first lists every not-yet-applied `filterOptions` entry by `name`; picking one swaps the same popover to a value editor matching that field's `type` (`dd`→`AbMultiSelect`, `t`→`AbInputField`, `tr`→min/max inputs, `d`/`dr`→`AbDateTimePicker`) plus Cancel/Apply Filter buttons. Apply pushes it in as a removable chip (e.g. "Email contains gmail") and immediately fires `searchFilter` — there's no global Search button in this mode, only Reset (clears every applied chip and value at once). A field's `operators` is fixed by its schema entry, same as other modes — this mode does not add an is/is-not/contains operator picker, only the value input changes per `type`.
+
+Standard-search, advance-search, and quick-advance field layouts are all plain flex (`d-flex flex-wrap gap-2`) — no Bootstrap grid. Each field grows/shrinks on its own, which means a field left alone on the last row will stretch to fill the remaining row width; give a `filterOptions` entry a `width`, `minWidth`, and/or `maxWidth` key (`String | Number` — a number is px, e.g. `maxWidth: 280`, or a CSS string like `"50%"`) to control that specific field's size. All three are forwarded straight to the underlying `AbInputField`/`AbMultiSelect`/`AbDateTimePicker`'s own same-named props, and also constrain that field's flex-item wrapper directly (`width` sets `flex: 0 0 <width>` so it stops growing/shrinking; `minWidth`/`maxWidth` clamp it while it keeps growing/shrinking with its siblings).
+
+The standard-mode property-selector (and the scan field it swaps for) isn't part of `filterOptions` — it's not tied to one field, it lists all of them — so it has no `width`/`minWidth`/`maxWidth` key to set. It's also the only item in its row until a property is picked (or whenever `showScanFld` is on), so without sizing it it'll stretch to fill the row the same way an unsized `filterOptions` field would. Use the panel-level `propertySelectWidth`/`propertySelectMinWidth`/`propertySelectMaxWidth` props for that slot instead.
+
 ## Usage
 
 ```vue
@@ -37,6 +43,7 @@ function handleSearch(data) {
 | -------------------------- | --------- | --------------- | ---------------------------------------------------------- |
 | `isAdvance`                | `Boolean` | `false`         | Show all filters in an expanded layout.                    |
 | `isQuickAdvance`           | `Boolean` | `false`         | Quick advance mode.                                        |
+| `isBuilderFilter`          | `Boolean` | `false`         | Shopify-style "+" add-filter builder — see mode description above. |
 | `isSingle`                 | `Boolean` | `false`         | Single-field search mode.                                  |
 | `isAutoSearch`             | `Boolean` | `false`         | Auto search on input change (single mode).                 |
 | `isAllowed`                | `Boolean` | `false`         | Permission flag consumed by the template.                  |
@@ -49,7 +56,10 @@ function handleSearch(data) {
 | `isSearchable`             | `Boolean` | `false`         | Allow searching within option lists.                       |
 | `isMaxDate`                | `Boolean` | `true`          | Limit date pickers to today as max.                        |
 | `size`                     | `String`  | `"xs"`          | Control size.                                              |
-| `advanceContainerClass`    | `String`  | `"col-6"`       | Grid column class for inputs in advance mode.              |
+| `advanceContainerClass`    | `String`  | `""`            | Extra class on each field's flex-item wrapper in advance mode (base sizing is `flex: 1 1 240px`, wraps as needed — not a Bootstrap grid). To fix a single field's width instead, use that field's own `width` prop (`AbInputField`/`AbMultiSelect`/`AbDateTimePicker`). |
+| `propertySelectWidth`      | `String` \| `Number` | `undefined` | Width of the standard-mode property-selector / scan-field slot (number = px). |
+| `propertySelectMinWidth`   | `String` \| `Number` | `undefined` | `min-width` of that same slot. |
+| `propertySelectMaxWidth`   | `String` \| `Number` | `undefined` | `max-width` of that same slot — it's the only item in its row until a property is picked (or in scan mode), so it stretches to fill it without one. |
 | `isQuickAdvanceAutoSearch` | `Boolean` | `false`         | Fire search automatically on field change (quick advance). |
 | `defaultFilterId`          | `String` \| `Number` | `""` | Pre-selects a default filter property in standard search mode (when `!isSingle && !isAdvance && !isQuickAdvance`). |
 

package/.ai/ai_ref_AbInputField.md

@@ -37,6 +37,9 @@ const form = reactive({ email: '' });
 | `size` | `String` | `undefined` | Adjusts component size (`xs`, `sm`, `md`, `lg`, `xl`, `xxl`). |
 | `rules` | `String \| Object` | `""` | VeeValidate rules. |
 | `containerClass` | `String` | `undefined` | Class on the wrapper `<div>`. |
+| `width` | `String \| Number` | `undefined` | Explicit width on the wrapper `<div>`. A number is treated as px (e.g. `220` -> `220px`); a string is used as-is (e.g. `"50%"`). |
+| `minWidth` | `String \| Number` | `undefined` | `min-width` on the wrapper `<div>` (same number/string rules as `width`). |
+| `maxWidth` | `String \| Number` | `undefined` | `max-width` on the wrapper `<div>` (same number/string rules as `width`) — caps growth inside a flex/grid parent without a fixed `width`. |
 | `hints` | `String` | `""` | Helper text beneath the input. |
 | `prefix` | `String` | `""` | Prefix text/icon (shortcut for `#prefix` slot). |
 | `postfix` | `String` | `""` | Postfix text/icon. |

package/.ai/ai_ref_AbMultiSelect.md

@@ -27,6 +27,9 @@ Searchable single/multi/tag select. Custom built-in replacement for `@vueform/mu
 | `name` | `String` | `""` | VeeValidate field name. |
 | `rules` | `String \| Object` | `""` | VeeValidate rules. |
 | `containerClass` | `String` | `undefined` | Wrapper class. |
+| `width` | `String \| Number` | `undefined` | Explicit width on the wrapper `<div>`. A number is treated as px (e.g. `220` -> `220px`); a string is used as-is (e.g. `"50%"`). |
+| `minWidth` | `String \| Number` | `undefined` | `min-width` on the wrapper `<div>` (same number/string rules as `width`). |
+| `maxWidth` | `String \| Number` | `undefined` | `max-width` on the wrapper `<div>` (same number/string rules as `width`) — caps growth inside a flex/grid parent without a fixed `width`. |
 | `hints` | `String` | `""` | Helper text. |
 | `multiple` | `Boolean` | `false` | Deprecated — use `mode` instead. |
 | `searchable` | `Boolean` | `false` | Enable option search/filter. |

package/.ai/ai_ref_abTranslate.md

@@ -46,3 +46,13 @@ translateGetMsg("Error code: %{code}", { code: "404" });
 | `initTranslate(gettextInstance)` | `Function` | Registers an existing gettext instance for use outside Vue components. |
 | `translateGettext(msg, params)` | `Function` | Translates `msg` and interpolates `params`; also translates param values. |
 | `translateGetMsg(msg, params)` | `Function` | Interpolates `params` into `msg` without translating. |
+
+## Message-key convention
+
+`msg` doesn't have to be a literal English sentence — it can be any string used as the `translations` lookup key (`msgid`), including a short dotted key like `"field.required"`. This is the pattern the library's own [`abVeeRules`](./ai_ref_abVeeRules.md) uses internally, and is the recommended approach for any reusable code (composables, utils) that needs translated messages: pick stable keys once, then supply the actual text per language in `translations`. A key with no matching entry for the active language is returned as-is (untranslated), so an unmapped key fails visibly instead of silently.
+
+```javascript
+translateGettext("field.required", { fld_name: "Email" });
+// → looks up translations[currentLang]["field.required"], interpolates %{fld_name}
+// → falls back to the literal string "field.required" if that key isn't defined
+```

package/.ai/ai_ref_abVeeRules.md

@@ -19,15 +19,57 @@ Object.keys(abAllRules).forEach(rule => {
 
 Validation functions conforming to VeeValidate's custom rule signature `(value, params, field)`.
 
-Included rules:
-- `required`: Returns translated `%{fld_name} is required`.
-- `numeric`: Returns translated `%{fld_name} should be numeric`.
-- `email`: Returns translated `%{fld_name} not a valid email address`.
-- `min`: Native min validation.
-- `min_value`: Returns translated `%{fld_name} should be more than X`.
-- `max`: Native max validation.
-- `max_value`: Returns translated `%{fld_name} should be less than X`.
-- `confirmed`: Checks password confirmation match.
-- `url`: Validates URL format.
-- `isUnique`: Custom stub for async uniqueness check.
-- `isValid`: Custom stub for async validity check.
+On failure, each rule calls `translateGettext(key, params)` with a short, stable **message key** (not a literal English sentence) — the key is the `msgid` that must exist in the consuming app's `translations` object (see `abTranslate`) for that key to render translated; otherwise the raw key string is returned as-is (untranslated).
+
+Included rules and their message key:
+
+| Rule | Message key | Interpolation params |
+| --- | --- | --- |
+| `required` | `field.required` | `fld_name` |
+| `numeric` | `field.numeric` | `fld_name` |
+| `email` | `field.valid.email` | `fld_name` |
+| `min` | — (native `min` rule, no translated message) | — |
+| `min_value` | `field.min.value` | `fld_name`, `value` (the configured min) |
+| `max` | — (native `max` rule, no translated message) | — |
+| `max_value` | `field.max.value` | `fld_name`, `value` (the configured max) |
+| `confirmed` | `field.confirm.password` | `fld_name` |
+| `url` | `field.valid.url` | `fld_name` |
+| `isUnique` | Custom stub for async uniqueness check (currently always passes). |
+| `isValid` | Custom stub for async validity check; on the `'custom'` param path with too-short input, uses `field.valid.length` (`fld_name`). |
+
+## Adding/overriding these messages in a consuming app
+
+These keys are **not translated out of the box** — they resolve to the bare key unless the app's `abCreateGettext({ translations })` config defines them for the active language. Add one entry per key, per language, with the interpolation params above as `%{param}` placeholders:
+
+```javascript
+import { abCreateGettext } from "@vue3-appsbd-ui";
+
+const gettext = abCreateGettext({
+  availableLanguages: { bn_BD: "Bengali Bangladesh", en_EN: "English" },
+  defaultLanguage: "bn_BD",
+  translations: {
+    bn_BD: {
+      "field.required": "%{fld_name} প্রয়োজনীয়",
+      "field.valid.email": "%{fld_name} সঠিক ইমেইল নয়",
+      "field.numeric": "%{fld_name} সংখ্যা হতে হবে",
+      "field.min.value": "%{fld_name} অবশ্যই %{value} এর বেশি হতে হবে",
+      "field.max.value": "%{fld_name} অবশ্যই %{value} এর কম হতে হবে",
+      "field.confirm.password": "%{fld_name} পাসওয়ার্ড এর সাথে মিলছে না",
+      "field.valid.url": "%{fld_name} সঠিক ইউআরএল নয়",
+      "field.valid.length": "%{fld_name} এর দৈর্ঘ্য সঠিক নয়, দয়া করে এটি পরীক্ষা করুন",
+    },
+    en_EN: {
+      "field.required": "%{fld_name} required",
+      "field.valid.email": "%{fld_name} is not a valid email",
+      "field.numeric": "%{fld_name} must be a number",
+      "field.min.value": "%{fld_name} must be greater than %{value}",
+      "field.max.value": "%{fld_name} must be less than %{value}",
+      "field.confirm.password": "%{fld_name} password does not match",
+      "field.valid.url": "%{fld_name} is not a valid url",
+      "field.valid.length": "%{fld_name} length is not valid, please check it",
+    },
+  },
+});
+```
+
+Only override the keys actually needed — an omitted key just falls back to being displayed as the bare key string.

package/.ai/ai_ref_migration_guide.md

@@ -12,6 +12,29 @@
 
 ---
 
+## [Unreleased]
+
+### ⚠️ Action Required — Breaking
+
+- **`AbFilterPanel`'s standard-search and advance-search field layouts switched from a Bootstrap `.row`/`.col-*` grid to plain flex; `advanceContainerClass` default changed from `"col-6"` to `""`.**
+  - Find: `<AbFilterPanel ...>` usages in either default (standard) mode or `is-advance`/`isAdvance` mode that relied on the Bootstrap grid for field widths — either the default 2-columns-per-row layout, or an explicit `advance-container-class`/`advanceContainerClass` Bootstrap grid class (e.g. `"col-12 col-sm-6"`).
+  - Replace: nothing required to keep working — fields now lay out via flex (`flex: 1 1 240px`, wraps automatically), which also fixes long field labels getting clipped. A Bootstrap grid class passed to `advance-container-class` no longer has a `.row` ancestor to size against and should be replaced with either a plain width class/CSS, or the new `width` prop on the individual field component (`AbInputField`/`AbMultiSelect`/`AbDateTimePicker`) inside `filterOptions`.
+
+### ℹ️ Also shipped (no action needed)
+
+- `AbFilterPanel`'s `.apbd-filter-chip-group` (quick-advance multi-select popover trigger) height fixed to match input-field heights at every size (`xs`…`xxl`), and no longer changes height (grows or shrinks) once a tag is selected — a `min-height` per size acts as a floor while still allowing the box to grow when tags wrap onto a second line.
+- New `width`, `minWidth`, `maxWidth` props (`String | Number`) on `AbInputField`, `AbMultiSelect`, `AbDateTimePicker` for sizing a single field directly; `AbFilterPanel` forwards a `width`/`minWidth`/`maxWidth` key from any `filterOptions` entry to that field's props and its flex-item wrapper.
+- New `AbFilterPanel` `propertySelectWidth`/`propertySelectMinWidth`/`propertySelectMaxWidth` props for the standard-mode property-selector/scan-field slot, which isn't a `filterOptions` entry so the field-level keys above can't reach it.
+
+## [1.0.17] - 2026-08-30
+
+### ⚠️ Action Required — Breaking
+
+- **`abVeeRules` translation message keys renamed from literal English sentences to short dotted keys.**
+  - Find: any entry in a `translations[<lang>]` object (passed to `abCreateGettext`) keyed by one of the old literal sentences — `"%{fld_name} is required"`, `"%{fld_name} should be numeric"`, `"%{fld_name} not a valid email address"`, `"%{fld_name} should be more than " + <value>` (min), `"%{fld_name} should be less than " + <value>` (max), `"%{fld_name} does not match with its password"`, `"%{fld_name} is invalid"` (url), `"%{fld_name} length is not valid, please check it"`.
+  - Replace: rename the key to, respectively, `"field.required"`, `"field.numeric"`, `"field.valid.email"`, `"field.min.value"`, `"field.max.value"`, `"field.confirm.password"`, `"field.valid.url"`, `"field.valid.length"`. For `field.min.value`/`field.max.value`, the value is now a separate `%{value}` interpolation param instead of being concatenated into the key/message — the value text should include `%{value}` where the limit belongs (e.g. `"%{fld_name} should be more than %{value}"`), not a hardcoded number.
+  - See [`.ai/ai_ref_abVeeRules.md`](./ai_ref_abVeeRules.md) for the full key list and a working example.
+
 ## [1.0.15] - 2026-08-24
 
 ### ⚠️ Action Required — Breaking

package/CHANGELOG.md

@@ -2,6 +2,20 @@
 
 All notable changes to `@appsbd/vue3-appsbd-ui` are documented here. Format loosely follows [Keep a Changelog](https://keepachangelog.com/).
 
+## [1.0.17]
+
+- **Fixed**: `AbFilterPanel`'s `isBuilderFilter` popup editor was too narrow (`max-width: 320px`, no `width`) for longer values like a `"dr"` (date range) field's `"01/09/2026 - 15/09/2026"`-style text, which got clipped inside its input. Raising just `max-width` didn't help on its own — `AbPopover`'s content box is `position: absolute; width: auto`, which sizes to shrink-to-fit, and a shrink-to-fit box ignores a percentage-width child (`AbInputField`'s `.form-control` is `width: 100%`) when computing that fit, so the box never actually grew to use the extra ceiling. Giving it an explicit `width` fixed that, but the first pass (`340px`) was tuned tight enough against one specific date pair that it broke again on a different one — Bengali numeral glyphs (০-৯) aren't uniform-width (e.g. "৪"/"৬" render wider than "১"), so a range using wider digits needed more room than the one used to size it. Now `width: 400px` (`min-width: 280px` / `max-width: 440px` as clamps) with real margin instead of a pixel-exact fit; the popover's own default 400px cap is also raised to 480px so it isn't clipped from outside.
+- **Fixed**: `AbFilterPanel`'s `"tr"` (text range) field's Min/arrow/Max row (`.range-input-panel`, shared by standard, advance, and the new `isBuilderFilter` mode) was built from raw `<div class="input-group">` + `<input class="form-control">` markup instead of `AbInputField`, so it never scaled with the panel's `size` prop — the label/input join used a hardcoded `input-group-sm`, and a copy-paste bug hardcoded the **Max** input to `form-control-sm` specifically (while Min correctly used the dynamic size) — so Min and Max could literally render at two different heights. The row also had no flex layout CSS at all: each `.form-control`'s default `width: 100%` forced Min/Max onto separate stacked lines instead of sitting side by side, and the separator `<svg>` had no explicit size (rendering at the browser's 300×150px SVG default) since the `w-4`/`h-4` classes on it aren't real classes in this project (Bootstrap has no such utilities). Now built from two `AbInputField`s (the first carrying the field's name as its `prefix`, matching every other field type) in a proper flex row with `1em` icon sizing — sizes correctly with the panel's `size` prop like every other field. This had never been visually exercised before — no existing playground demo used a `"tr"` field until `isBuilderFilter`'s "Revenue" example.
+- **Added**: `AbFilterPanel` `isBuilderFilter` prop — a Shopify-style filter builder mode. No field is shown until the user clicks a `+` button; that opens a popover which first lists every not-yet-applied `filterOptions` entry, then (once one is picked) swaps to a value editor matching that field's `type` plus Cancel/Apply Filter buttons. Apply adds it as a removable chip (e.g. "Email contains gmail") and immediately fires `searchFilter`; there's no global Search button in this mode, only Reset (clears every applied chip/value at once). A field's `operators` stays fixed by its schema entry, same as other modes — this mode doesn't add an is/is-not/contains operator picker. The applied-filter chip's height/padding scales with the panel's `size` prop, same as its `+`/Reset buttons.
+- **Fixed**: `AbPopover`'s outside-click-to-close listened on `click`, which races with anything inside its content that reacts on `mousedown` and removes/moves itself before that later `click` fires — e.g. `AbMultiSelect` selecting a single option closes its own dropdown on `mousedown`, so by the time `click` arrived its real target was already whatever sat behind the now-collapsed dropdown, closing the outer popover too (hit when nesting an `AbMultiSelect` with `append-to-body="false"` inside an `AbPopover`, as `AbFilterPanel`'s new `isBuilderFilter` mode does for its dropdown-type fields). Outside detection now runs on `mousedown`, before such handlers can react, and reads `event.composedPath()` instead of `event.target` + `.contains()` so it's also correct when a same-tick handler swaps out the clicked element.
+- **Fixed**: `AbPopover` closed immediately (with no selection) when clicking inside a *nested* `AbPopover` in its content — e.g. an `AbDateTimePicker` (which opens its calendar through its own `AbPopover`) placed inside `AbFilterPanel`'s `isBuilderFilter` editor: any date click, or even changing the calendar's month, closed the outer popover before the inner one could react, because the inner popover's floating content always renders through its own `<Teleport to="body">` and so never sits inside the outer popover's own floating element in the DOM. `AbPopover` now tracks every mounted popover (via the existing `popoverManager`) and treats a click as "inside" when it lands on another popover's floating content whose trigger is nested inside its own — so a calendar (or any `AbPopover`-based control) opened from within another popover's content no longer closes its parent.
+- **Fixed**: `AbFilterPanel`'s `.apbd-filter-chip-group` (the quick-advance multi-select popover trigger) had an inconsistent height across sizes — only `xs`/`sm` had explicit padding, `md`/`lg`/`xl`/`xxl` fell through to browser-default padding/line-height. Every size (`xs` `sm` `md` `lg` `xl` `xxl`) now computes to the same height as `AbInputField`/`AbMultiSelect` at that size (28/36/40/44/48/60px) through the shared padding + line-height tokens — never a hardcoded `height` — and the font-size is now constant across all sizes instead of shrinking at `xs`/`sm`. Border-radius and background also switched from an undefined CSS variable (silently falling back to a hardcoded value) to the real `--#{$prefix}border-radius*`/`--#{$prefix}apbd-input-bg-color` tokens, matching input fields in dark mode too.
+- **Fixed**: `AbFilterPanel`'s `.apbd-filter-chip-group` didn't keep a consistent height once a tag was selected — the selected-tag pill (`.apbd-filter-tag`) inheriting the container's line-height plus its own border + padding first made the box grow taller than its siblings; capping the tag to `line-height: 1` then let the box shrink *shorter* than its siblings instead, since the container has no explicit `height` and was sizing itself off whatever child happened to be present. Each size class now also carries a `min-height` matching that size's target (28/36/40/44/48/60px for `xs`…`xxl`) as a floor — the box can still grow taller than that when tags wrap onto a second line, it just never renders shorter than a same-size input field regardless of what's inside it.
+- **Changed** (breaking): `AbFilterPanel`'s standard-search (default mode) and advance-search (`isAdvance` mode) field layouts — both used Bootstrap's `.row`/`.col-*` grid (nested two levels deep in standard mode); a `.col-*` class doesn't do anything meaningful without a `.row` ancestor, and `.row`'s negative margins could overflow the outer flex wrapper and clip long field labels. Both are now a plain `d-flex flex-wrap gap-2` layout with no grid columns at all — each field is a flex item (`flex: 1 1 240px`, class `apbd-advance-filter-item`) that grows/shrinks and wraps on its own; `advanceContainerClass` default changed from `"col-6"` to `""` since a grid column class no longer does anything useful here. To fix a specific field's width instead, use that field's own new `width` prop.
+- **Added**: `width`, `minWidth`, and `maxWidth` props (`String | Number`) on `AbInputField`, `AbMultiSelect`, and `AbDateTimePicker` — set an explicit width / `min-width` / `max-width` on the field's outer container (a number is treated as px, e.g. `width="220"` or `max-width="50%"`). `AbFilterPanel` forwards all three too: give any entry in `filterOptions` a `width`/`minWidth`/`maxWidth` key and it's passed straight to that field's own same-named prop *and* used to size that field's flex-item wrapper directly — the way to fix (or just bound) a specific field's size now that its layouts have no Bootstrap grid column to size against. Without one, a field left alone on the last row (nothing else to share the row with) stretches to fill it, since each field is a `flex: 1 1 240px` item.
+- **Added**: `AbFilterPanel` `propertySelectWidth`/`propertySelectMinWidth`/`propertySelectMaxWidth` props (`String | Number`) — the standard-mode property selector (and the scan field it swaps for) isn't one of the `filterOptions` entries, so the `width`/`minWidth`/`maxWidth` field keys above don't reach it; it's also the sole item in its row until a property is picked (or whenever `showScanFld` is on), so it stretches to fill the row the same way any unsized flex field does. These three props size that slot directly.
+- **Changed**: `abVeeRules`' built-in validation messages now translate through short, stable message keys (e.g. `field.required`, `field.numeric`, `field.valid.email`, `field.min.value`, `field.max.value`, `field.confirm.password`, `field.valid.url`, `field.valid.length`) instead of literal English sentences — `min_value`/`max_value` also now pass their configured limit as an interpolated `value` param instead of concatenating it directly into the message-key string (which previously produced a different, untranslatable key per limit value). Breaking change for any consumer whose `translations` object overrode these messages by their old literal-sentence key (e.g. `"%{fld_name} is required"`) — those entries must be renamed to the new keys, see `.ai/ai_ref_abVeeRules.md`.
+
 ## [1.0.16] - 2026-08-27
 
 - **Fixed**: WordPress theme conflict — `AbFormCheck`'s enhanced (`.apbd-radio-input-container`) checkbox/radio inputs now reset `margin: 0` to counter WordPress's default form-control margin. (Previously targeted `.is-flat-check`, which only covers the `card-flat-check` variant and missed the other enhanced variants.)