@appsbd/vue3-appsbd-ui 1.0.15 → 1.0.17

package/.ai/ai_ref_AbChatInput.md

@@ -89,21 +89,57 @@ a native file picker and routes the selection through `addFiles`) among other me
 Uses the browser's native Web Speech API (`SpeechRecognition`) — no extra dependency, no API key. A built-in mic
 button renders in the `right` area (before the `right` slot and the send button) whenever `showVoiceButton` is
 `true` (default).
-Clicking it (or calling `startRecording()`) swaps the whole composer row for a full-width recording bar — a live
-audio-reactive waveform (via `getUserMedia` + `AnalyserNode`) plus three controls:
 
-- **✕ cancel** — discards everything spoken this session, reverting `modelValue` to what it was before recording started.
-- **■ stop** — stops recording and keeps the transcribed text in the textarea (no submit).
-- **↑ submit** — stops recording, keeps the text, then fires `submit` immediately.
+The composer layout never changes while recording, on every platform — no full-width recording bar swap: the
+textarea stays visible **and stays fully editable** (typing/deleting mid-recording works normally) and fills with
+the transcribed text live as it's recognized. The mic button shows a Google Assistant-style listening cue: its
+circle fills with the theme's primary color (icon turns white to read against it), with a few rings pulsing
+outward from behind it on a loop (`.apbd-chat-input__voice-ring`, staggered so they overlap continuously). Clicking
+it (or calling `stopRecording()`) stops and keeps the text — there's no dedicated cancel button in this UI
+(`cancelRecording()` is still available programmatically via a template ref), and the default send button (or
+`submit()`/Enter generally) stops recording first when called mid-listening, then fires `submit` immediately.
 
-Recognized speech is appended to the existing `modelValue` (not replaced), one final phrase at a time — interim
-(still-speaking) text is not shown live.
+On every platform, the textarea is refocused automatically the moment listening ends (stop, cancel, or a
+voice-triggered submit) — the cursor lands right back in it so the user can keep typing without an extra tap.
+
+Recognized speech is appended to the existing `modelValue` (not replaced), converting instantly as the user speaks
+on every platform — interim results drive `modelValue` live so the text is already there before the user taps the
+mic to stop, not just once they do (see below).
 
 A small language-code badge (e.g. `EN`, `BN`) sits on the mic button's corner. Clicking it opens an `AbPopover`
 with a searchable list of ~130 BCP-47 locales; picking one sets that recognition session's `SpeechRecognition.lang`
 and persists the choice to `localStorage` (key `apbd-chat-input-voice-lang`) so it's remembered next visit. This
 never touches the browser's own language/locale settings — only this component's own recognizer instance.
 
+### Voice punctuation
+
+Two independent behaviors, each its own boolean prop, **both default `true`**:
+
+- **`voicePunctuationCommands`** — saying a punctuation word inserts the actual mark, same idea as Google/Apple
+  dictation: English `"period"`/`"full stop"` → `.`, `"comma"` → `,`, `"question mark"` → `?`; Bengali
+  `"পূর্ণচ্ছেদ"` → `।`, `"কমা"` → `,`, `"প্রশ্নবোধক"` → `?`. Matched against the recognized transcript text itself
+  (not `voiceLang`), so it works regardless of which recognition language is selected. Matching uses
+  script-agnostic lookaround (not `\b`, which only understands ASCII letters — a no-op for Bengali) so a command
+  word only triggers standalone, never as a substring of a longer word (e.g. saying "দাঁড়িপাল্লা" doesn't trigger
+  on the "দাড়ি" inside it). `"দাড়ি"` itself (an earlier alternate trigger, same meaning as `"পূর্ণচ্ছেদ"`) was
+  dropped entirely rather than just boundary-guarded — it's also ordinary vocabulary (beard), so a sentence
+  actually about a beard would still lose that word every time. `"কমা"` keeps a similar, smaller risk (it's also
+  a common verb, "to decrease") — left as-is, since removing every word with *any* plausible double meaning
+  would leave nothing left to trigger on.
+- **`voiceAutoPunctuate`** — when a new utterance is about to be appended onto existing text, a sentence-ending
+  mark is inserted first if the existing text doesn't already end with one — `.` normally, `।` when `voiceLang`
+  starts with `bn`. Applies between pauses (each per-utterance restart, see below), not mid-utterance.
+
+Set either to `false` to disable it independently; both keep working with the default Web Speech transcript as-is
+when off.
+
+Both also auto-capitalize the sentence start they create: `voiceAutoPunctuate` capitalizes the first letter of a
+new utterance right after it inserts a boundary mark (and always capitalizes the very first letter of the whole
+message, regardless of this prop); `voicePunctuationCommands` capitalizes the letter right after any mark it
+inserts mid-utterance (`"hello period how are you"` → `"Hello. How are you"`). Same script-agnostic approach as the
+punctuation matching above — plain `toUpperCase()` on the matched letter, which is a no-op for scripts without a
+case concept (Bengali, Arabic, CJK, …), so it needs no per-language list.
+
 Not supported in Firefox. On iOS, only Safari itself gets it — Chrome/Firefox/Edge/Opera on iOS run on the same
 underlying WebKit engine and expose the same `webkitSpeechRecognition` constructor, but iOS never grants the mic
 permission for it outside of Safari's own app (no permission prompt ever appears; `.start()` would otherwise fail
@@ -111,10 +147,28 @@ with a confusing, prompt-less "permission denied"), so these are detected via us
 too. The mic button still renders in all of these cases but is `disabled`, with a tooltip explaining why. Where it
 is supported, requires the browser's mic permission prompt to be accepted.
 
-On Android, the live waveform is skipped (bars stay flat) — recognition and transcription work normally. Android's
-mic hardware only allows one exclusive audio-capture session at a time; a second concurrent `getUserMedia` stream
-for the waveform would starve `SpeechRecognition` of audio (no error, no transcript, ever). This is detected via
-user-agent, not feature-tested.
+Some browsers/builds hold back `isFinal` results until `.stop()` is called instead of firing them per pause segment
+— waiting for that would mean the transcript only shows up once the user taps stop, not while they're actually
+speaking (and on some builds it never reliably fires at all). `interimResults` is on by default to sidestep that,
+converting speech to text instantly instead of only once recording stops — **except on Safari** (desktop and iOS
+both), where it's kept `false`: Safari's engine has a bug where enabling it can fail to (re)start the recognizer
+entirely, surfacing as a generic "Microphone permission denied" error indistinguishable from an actually-denied
+permission. Safari still converts per finished phrase (not mid-utterance), just not keystroke-by-keystroke live.
+
+`continuous`+`interimResults` together is also unreliable across browsers/builds in a way delta-tracking
+`e.results` (via `resultIndex` or position) can't fully work around — it's been observed restating/duplicating
+earlier words in a later result with no restart involved at all. So `recognition.continuous` is always `false` —
+each internal session covers exactly one utterance, and a transparent onend-restart (also covers Safari's own
+quirk of ending a `continuous: true` session early) picks the next utterance back up automatically, so it still
+reads as continuous listening. Within one utterance's `onresult`, only the latest `e.results` entry is read — no
+cross-event bookkeeping needed, since there's nothing earlier in that same array to conflict with.
+
+Because the textarea stays editable during recording, `onresult` can't just privately accumulate a running
+transcript either — that would silently clobber whatever the user just typed or deleted. Instead it reads the
+current `modelValue`, strips back off the exact suffix it itself inserted last time (if that suffix is still there
+untouched), and rebuilds from that stable base with the freshly recognized text appended; if the suffix isn't
+there anymore, whatever's currently in the field — including the user's edit — becomes the new base instead of
+being overwritten.
 
 ## Props
 
@@ -140,6 +194,8 @@ user-agent, not feature-tested.
 | `filePreviewHeight` | `Number` | `24` | Height (px) of each attached file's thumbnail/icon in the chip. |
 | `showFileName` | `Boolean` | `true` | Show/hide the filename text next to the chip thumbnail. |
 | `showVoiceButton` | `Boolean` | `true` | Show/hide the built-in mic button (see "Voice input" below). Set `false` to build custom voice UI via slots instead. |
+| `voicePunctuationCommands` | `Boolean` | `true` | Say a punctuation word (e.g. "period", "পূর্ণচ্ছেদ") to insert the actual mark — see "Voice punctuation" above. |
+| `voiceAutoPunctuate` | `Boolean` | `true` | Auto-insert a sentence-ending mark between voice utterances when one isn't already there — see "Voice punctuation" above. |
 
 ## Events
 
@@ -154,8 +210,8 @@ user-agent, not feature-tested.
 | `file-remove` | `FileEntry` | A file chip's remove button was clicked. |
 | `file-reject` | `{ file: File, reason: string }` | A file failed `maxFileSize`/`allowedExtensions` validation. A `useToast` error is also shown. |
 | `voice-start` | — | Voice recording started (mic button clicked or `startRecording()` called). |
-| `voice-stop` | — | Recording stopped normally (■ button, ↑ submit button, `stopRecording()`, or the browser ending it on its own) — transcribed text is kept in `modelValue`. |
-| `voice-cancel` | — | Recording was cancelled (✕ button or `cancelRecording()`) — `modelValue` is reverted to what it was before recording started. |
+| `voice-stop` | — | Recording stopped normally (mic button tapped again, `stopRecording()`, or the browser ending it on its own) — transcribed text is kept in `modelValue`. |
+| `voice-cancel` | — | Recording was cancelled via `cancelRecording()` (no dedicated UI button — call it programmatically via a template ref) — `modelValue` is reverted to what it was before recording started. |
 | `voice-error` | `Error \| SpeechRecognitionErrorEvent` | Mic permission was denied, or the recognition engine errored. A `useToast` error is also shown (except benign `no-speech`/`aborted` errors). |
 
 ## Slots

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_AbVoiceButton.md

@@ -0,0 +1,112 @@
+# AbVoiceButton — AI Reference
+
+A standalone voice-to-text mic button — the same recognition engine and behavior as `AbChatInput`'s built-in mic,
+with no composer attached. Use it to bolt voice input onto any existing input, form field, search box, or custom
+UI via `v-model`; pick `AbChatInput` instead when you need the whole chat composer (textarea, file attachments,
+add/more dropdown) with voice input built in.
+
+## Installation
+
+Not globally registered — import it explicitly:
+
+```js
+import { AbVoiceButton } from 'vue3-appsbd-ui';
+```
+
+No extra peer deps beyond the library's own (`@lucide/vue` for the mic icon). Uses the browser's native Web
+Speech API (`SpeechRecognition`) — no dependency, no API key.
+
+## Usage
+
+```vue
+<template>
+  <AbVoiceButton v-model="message" />
+  <p>{{ message }}</p>
+</template>
+
+<script setup>
+import { ref } from 'vue';
+import { AbVoiceButton } from 'vue3-appsbd-ui';
+
+const message = ref('');
+</script>
+```
+
+Pin the recognition language explicitly (there's no built-in language picker here, unlike `AbChatInput`'s mic
+button — pass whichever locale your app already knows the user wants):
+
+```vue
+<AbVoiceButton v-model="message" lang="bn-BD" />
+```
+
+## Behavior
+
+Tapping the button (or calling `startRecording()`) starts listening; the mic icon stays the mic icon, but its
+circle fills with the theme's primary color (`--#{prefix}theme`) and the icon turns white, with a few rings
+pulsing outward from behind it on a loop — a Google Assistant-style listening cue, on every platform (same cue,
+same architecture as `AbChatInput`'s built-in mic — this component just has no composer/textarea attached to it).
+Tap it again (or call `stopRecording()`) to stop and keep the text.
+
+Recognized speech merges into `modelValue` live as the user speaks, via one internal recognition session per
+utterance (`continuous: false` + `interimResults: true`, restarted transparently between utterances) — on every
+platform except Safari (desktop and iOS both), where `interimResults` is kept `false`: Safari's engine has a bug
+where enabling it can fail to (re)start the recognizer entirely, surfacing as a generic "Microphone permission
+denied" error indistinguishable from an actually-denied permission. Safari still converts per finished phrase, just
+not keystroke-by-keystroke live. Reads the current `modelValue` on each update and replaces only the exact suffix
+it last inserted itself, so external edits to `modelValue` between voice updates (e.g. the consumer's own code, or
+a bound `<textarea>` the user is also typing into) are preserved rather than clobbered.
+
+Not supported in Firefox. On iOS, only Safari itself gets it — Chrome/Firefox/Edge/Opera on iOS run on the same
+underlying WebKit engine and expose the same `webkitSpeechRecognition` constructor, but iOS never grants the mic
+permission for it outside of Safari's own app, so these are detected via user-agent and treated as unsupported too
+(button `disabled`, tooltip explains why). Requires the browser's mic permission prompt to be accepted where
+supported.
+
+### Voice punctuation
+
+Two independent behaviors, each its own boolean prop, **both default `true`** (identical to `AbChatInput`'s):
+
+- **`voicePunctuationCommands`** — saying a punctuation word inserts the actual mark: English `"period"`/
+  `"full stop"` → `.`, `"comma"` → `,`, `"question mark"` → `?`; Bengali `"পূর্ণচ্ছেদ"` → `।`, `"কমা"` → `,`,
+  `"প্রশ্নবোধক"` → `?`. Matched against the transcript text itself, independent of `lang`. Matching uses
+  script-agnostic Unicode lookaround (not `\b`, a no-op for Bengali script), so a command word only triggers
+  standalone, never as a substring of a longer word.
+- **`voiceAutoPunctuate`** — a sentence-ending mark is inserted between voice utterances when the existing text
+  doesn't already end with one — `.` normally, `।` when `lang` (or the auto-detected language) starts with `bn`.
+
+## Props
+
+| Name | Type | Default | Description |
+| --- | --- | --- | --- |
+| `modelValue` | `String` | `""` | Two-way-bound transcribed text. |
+| `disabled` | `Boolean` | `false` | Disables the button. |
+| `size` | `Number` | `40` | Button diameter in px. Icon and listening rings scale with it. |
+| `lang` | `String` | `""` | BCP-47 recognition locale (e.g. `"bn-BD"`). Empty = auto-detect from `document.documentElement.lang` / `navigator.language`. |
+| `voicePunctuationCommands` | `Boolean` | `true` | Say a punctuation word (e.g. "period", "পূর্ণচ্ছেদ") to insert the actual mark — see "Voice punctuation" above. |
+| `voiceAutoPunctuate` | `Boolean` | `true` | Auto-insert a sentence-ending mark between voice utterances when one isn't already there — see "Voice punctuation" above. |
+
+## Events
+
+| Event | Payload | Description |
+| --- | --- | --- |
+| `update:modelValue` | `string` | v-model sync. |
+| `voice-start` | — | Voice recording started (mic tapped, or `startRecording()` called). |
+| `voice-stop` | — | Recording stopped normally (mic tapped again, `stopRecording()`, or the browser ending it on its own) — transcribed text is kept in `modelValue`. |
+| `voice-cancel` | — | Recording was cancelled via `cancelRecording()` — `modelValue` is reverted to what it was before recording started. |
+| `voice-error` | `Error \| SpeechRecognitionErrorEvent` | Mic permission was denied, or the recognition engine errored. A `useToast` error is also shown (except benign `no-speech`/`aborted` errors). |
+
+## Slots
+
+None.
+
+## v-model
+
+Yes — `modelValue` + `update:modelValue` (string).
+
+## Exposed methods
+
+| Method | Description |
+| --- | --- |
+| `startRecording()` | Starts voice input (same as tapping the button). No-op if unsupported/disabled/already recording. |
+| `stopRecording()` | Stops recording, keeping the transcribed text (same as tapping the button again). |
+| `cancelRecording()` | Stops recording and reverts `modelValue` to what it was before recording started. No dedicated UI for this — call it via a template ref. |

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
@@ -25,7 +48,8 @@
 
 - New `formatCurrency`/`formatAmount` utils + matching global config keys (`currency`, `currencyPosition`, `thousandSeparator`, `decimalSeparator`, `numberOfDecimals`, `round`) — optional to adopt for consumer-side number/currency formatting.
 - New `AbChatBox` component (wraps `AbChatInput` as a full chat UI) and new `AbScrollbar` exposed scroll methods.
-- `AbFormCheck` checked-state label color and `description-text` truncation CSS fixes; a WordPress `.is-flat-check` margin conflict fix.
+- `AbFormCheck` checked-state label color and `description-text` truncation CSS fixes; a WordPress `.apbd-radio-input-container` margin conflict fix (covers all enhanced variants, not just `card-flat-check`).
+- `AbSidebar` header no longer clamps to a fixed height and top-aligns its content instead of centering — lets multi-line header content grow the header instead of being clipped/centered.
 - Several `AbChatInput` voice-input (Safari/Android/iOS) and narrow-viewport layout fixes.
 
 ## [1.0.14] - 2026-08-19

package/AI_REFERENCE.md

@@ -61,6 +61,7 @@
 | `AbChatInput`                  |  —  | ChatGPT-style auto-growing composer with an item-count-driven add/more dropdown, internal file attachment preview, and built-in Web Speech API voice input.  | [.ai/ai_ref_AbChatInput.md](./.ai/ai_ref_AbChatInput.md)               |
 | `AbChatInputMenuItem`          |  —  | Presentational row (icon/name/description/action) for `AbChatInput`'s add/more dropdown.                               | [.ai/ai_ref_AbChatInputMenuItem.md](./.ai/ai_ref_AbChatInputMenuItem.md) |
 | `AbChatBox`                    |  —  | Full chat conversation container (header, message list, empty/typing states) built on `AbChatInput`; every part is slot-overridable. | [.ai/ai_ref_AbChatBox.md](./.ai/ai_ref_AbChatBox.md)                   |
+| `AbVoiceButton`                |  —  | Standalone Web Speech API voice-to-text mic button (v-model), no composer attached — same engine as `AbChatInput`'s built-in mic. | [.ai/ai_ref_AbVoiceButton.md](./.ai/ai_ref_AbVoiceButton.md)           |
 | `AbDarkModeToggler`            |  —  | Light / dark theme toggle (pairs with `useTheme`).                                                                     | [.ai/ai_ref_AbDarkModeToggler.md](./.ai/ai_ref_AbDarkModeToggler.md)   |
 | `useAlert`                     |  —  | Procedural API to trigger SweetAlert-based modal alerts, notifications, and confirmations.                             | [.ai/ai_ref_useAlert.md](./.ai/ai_ref_useAlert.md)                     |
 | `abEventBus` / `emitterObj`    |  —  | Lightweight global event bus using `tiny-emitter`.                                                                     | [.ai/ai_ref_abEventBus.md](./.ai/ai_ref_abEventBus.md)                 |

package/CHANGELOG.md

@@ -2,6 +2,37 @@
 
 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.)
+- **Fixed**: `AbSidebar` header (`.apbd-sidebar-header`) no longer clamps to a fixed `min-height`/`max-height` (now `unset`) and aligns its content to the top (`align-items: start` instead of `center`) — the header can grow to fit multi-line content instead of clipping/centering it within a fixed band.
+- **Changed**: `AbChatInput` voice recording on Android only — no longer swaps the composer for the full-width recording bar (every other platform keeps that unchanged: waveform + cancel/stop/submit buttons). On Android the textarea now stays visible and fully editable the whole time instead (typing/deleting mid-recording works normally) and fills with the transcribed text live, in place; the mic button gets a Google Assistant-style listening cue instead — its circle fills with the theme's primary color (icon turns white), with a few rings pulsing outward from behind it on a loop. Tap it to stop (keeps the text); the send button (and Enter) still submits immediately while listening by stopping first. There's no cancel button in this Android UI — `cancelRecording()` remains available programmatically via a template ref.
+- **Fixed**: `AbChatInput` voice input on Android — text was only appearing once the user tapped stop, and could double up when it did (words repeating mid-recording, not just at the end). Android's `continuous`+`interimResults` combination turned out unreliable across builds in a way delta-tracking `e.results` (by `resultIndex` or by position) can't fully work around — it can restate/duplicate earlier words in a later result with no restart involved at all. Android now runs one utterance per internal recognition session (`continuous: false`) instead, relying on the existing transparent onend-restart (added earlier for a Safari quirk) to pick the next utterance back up automatically — so `onresult` only ever needs that session's latest result, with no cross-event bookkeeping to get wrong. Combined with the textarea staying editable during recording (see above), `onresult` now also reads the current text and swaps out only the exact suffix it last inserted, so a manual edit mid-recording is preserved instead of being silently overwritten.
+- **Fixed**: `AbChatInput`'s Android listening cue (see above) — the solid circle and ring animation never actually rendered, in either light or dark mode. They referenced `--#{$prefix}apbd-primary`, a CSS variable that isn't defined anywhere in the project; with no fallback, `var()` resolves to nothing and the whole declaration is silently dropped. Now uses `--#{$prefix}theme` (the actual theme accent variable, defined per-skin for both modes), with a `#0d6efd` fallback for safety.
+- **Changed**: `AbChatInput`'s Android listening rings scaled down slightly (max `2.4` → `1.7`) — the previous size read as too large next to the language badge and send button. The textarea also refocuses automatically now the moment listening ends, on every platform (stop, cancel, or a voice-triggered submit) — the cursor lands back in it immediately instead of requiring an extra tap.
+- **Fixed**: `AbChatInput`'s mic button on touchscreens — its `:hover` background had no touch guard, so tapping it (e.g. to stop recording on Android) could leave a lingering gray circle behind, a well-known mobile quirk: touch has no real pointer to move away and clear `:hover` the way a mouse does. Wrapped in `@media (hover: hover)` so it only applies on devices with genuine hover capability.
+- **Added**: `AbChatInput` `voicePunctuationCommands` and `voiceAutoPunctuate` props (both `Boolean`, default `true`, independently toggleable) for voice input punctuation. `voicePunctuationCommands`: saying a punctuation word inserts the actual mark — English `"period"`/`"full stop"` → `.`, `"comma"` → `,`, `"question mark"` → `?`; Bengali `"পূর্ণচ্ছেদ"` → `।`, `"কমা"` → `,`, `"প্রশ্নবোধক"` → `?` — matched against the transcript text itself, independent of the selected recognition language. `voiceAutoPunctuate`: a sentence-ending mark (`.`, or `।` when `voiceLang` starts with `bn`) is inserted between voice utterances (each final phrase on non-Android, each per-utterance restart on Android) whenever the existing text doesn't already end with one.
+- **Fixed**: `AbChatInput`'s `voicePunctuationCommands` (see above) — command-word matching used `\b`, which only recognizes ASCII letters/digits as "word" characters and is effectively a no-op for Bengali script, so a Bengali trigger word could match as a substring inside an unrelated longer word (e.g. saying "দাঁড়িপাল্লা" — "scale/balance" — got mangled into "। পাল্লা"). Now uses script-agnostic lookaround instead, matching only when the word is actually standalone. `"দাড়ি"` was also dropped entirely as a trigger (not just boundary-guarded) — fixing the substring match doesn't fix it also being ordinary vocabulary (beard), so a sentence genuinely about a beard would still lose that word every time; `"পূর্ণচ্ছেদ"` (a purely technical term nobody says in normal conversation) remains as the sole Bengali trigger for `.`/`।`.
+- **Added**: `AbVoiceButton` — a standalone voice-to-text mic button, the same recognition engine as `AbChatInput`'s built-in mic with no composer attached. `v-model` for the transcribed text; `voice-start`/`voice-stop`/`voice-cancel`/`voice-error` events; `startRecording()`/`stopRecording()`/`cancelRecording()` exposed methods. `size` (px, default `40`) and `lang` (BCP-47, auto-detected when unset — no built-in language picker here) props, plus the same `voicePunctuationCommands`/`voiceAutoPunctuate` props as `AbChatInput`. Unlike `AbChatInput`, the Google Assistant-style listening cue (solid theme-color circle + pulsing rings) and the live, per-utterance recognition architecture run on every platform here, not just Android — this component has no legacy full recording-bar behavior to preserve, so there was no reason to keep the two paths.
+- **Changed**: `AbChatInput` voice recording — the Google Assistant-style listening cue (mic icon stays put with pulsing rings, textarea stays visible and live-editable the whole time) now runs on every platform, not just Android, matching `AbVoiceButton`'s architecture. The separate full-width recording bar (audio-reactive waveform + cancel/stop/submit buttons), previously kept for every platform except Android, is removed entirely — there's no dedicated cancel button in the UI anymore; `cancelRecording()` remains available programmatically via a template ref, and the default send button (or `submit()`/Enter) still stops-then-submits when used while listening.
+- **Fixed**: `AbChatInput` voice-to-text not reliably converting speech on non-Android platforms — the old pipeline only ever committed text off a `SpeechRecognition` result's `isFinal` flag, which some browsers/builds hold back indefinitely instead of firing per pause segment, so speech could go untranscribed until — or even past — the point the user stopped recording. Every platform now runs the same per-utterance (`continuous: false`) + `interimResults: true` architecture already proven on Android, merging every recognized chunk into the text live instead of waiting on `isFinal`; the now-unused `getUserMedia`/`AnalyserNode` waveform pipeline (mic-hardware-exclusive, and irrelevant once the waveform UI it drove is gone) was removed along with it.
+- **Fixed**: `AbChatInput` and `AbVoiceButton` mic button showing "Microphone permission denied" on Safari (desktop and iOS) after the `interimResults: true` change above — Safari's `SpeechRecognition` engine has a long-standing bug where turning on `interimResults` can fail to (re)start at all, surfacing as a generic `onerror('not-allowed')` indistinguishable from an actually-denied permission. Safari now keeps `interimResults: false` (final-only, its reliably-supported mode) while every other browser still gets live interim updates; `onresult`'s merge logic already handled final-only results correctly, so no other change was needed.
+- **Fixed**: `AbChatInput` voice input transcribing sentences entirely lowercase (e.g. "hello how are you. hello" instead of "Hello how are you. Hello") — recognized speech was inserted as-is with no capitalization pass. Both existing punctuation props now also auto-capitalize the sentence they start: `voiceAutoPunctuate` capitalizes the first letter of a new utterance right after inserting a boundary mark (and the very first letter of the whole message unconditionally); `voicePunctuationCommands` capitalizes the letter right after any mark it inserts mid-utterance (`"hello period how are you"` → `"Hello. How are you"`). Applied only to the freshly recognized chunk, never to already-committed text, so it can't fight a manual edit made to an earlier sentence while still recording. Uses plain `toUpperCase()` on the matched letter — a safe no-op for scripts without letter case (Bengali, Arabic, CJK, …), so it needs no per-language list to work for any cased script.
+
 ## [1.0.15] - 2026-08-24
 
 - **Added**: `AbChatBox` — a full chat conversation container built on top of `AbChatInput`: header (title/subtitle/avatar, or fully custom via the `header`/`header-actions` slots), a scrollable message list with a default bubble renderer (overridable per-message via `message`/`message-avatar`), empty and typing states (`empty`/`typing` slots), and the composer docked at the bottom. `v-model:messages` holds the conversation, `v-model` holds the composer text; submitting auto-appends the user's message and fires `send`. Every `AbChatInput` prop, event, and slot (`left`/`right`/`send-button`/`menu-trigger`/`single-input`/`multiple-input`) is forwarded straight through to the inner composer.