1. The slide reordering and navigation buttons should be disabled when only a single slide is present. This prevents unnecessary actions, avoids confusing UI behavior and protects history from polluting with the unnecessary mutations. The disabling logic is handled by conditionally adding the "disabled" class based on the current slide count.

2. When the active slide is first then "**Move to first**" reordering button should be disabled. Similarly, when the active slide is last then "**Move to last**" reordering button should be disabled.

task-5363601


1. 
| Before | After |
|-----------------------------|---------------------------------|
| <img width="292" height="283" alt="image" src="https://github.com/user-attachments/assets/b89a810f-f5fe-4db4-a98b-036d6b1a6568" /> | <img width="284" height="273" alt="image" src="https://github.com/user-attachments/assets/c4ce2e7d-1fef-4186-bea0-ad00834a8680" /> |


2.
| Before | After |
|-----------------------------|---------------------------------|
| <img width="285" height="179" alt="image" src="https://github.com/user-attachments/assets/d0b6833f-a66f-4f80-8e18-c7ea2245fce1" /> | <img width="289" height="208" alt="image" src="https://github.com/user-attachments/assets/e0ef23fb-83ca-45c2-929b-2e86133c0789" /> |

Forward-Port-Of: odoo/odoo#237718

This PR introduces a bunch of UI/UX improvments as well as some refactoring to the existing behaviours.

Among the UI improvments, it adds:
- a new `AudioVisualizer` component which can be sized dynamically,
- uses the standard `blockquote` block for rendering transcriptions,
- Completely change the controls of the component on mobile to make it more reactive and usable. Specifically by making the navigation and configuration controls use the `Dropdown` component when on mobile,
- The transcription visuals are now divided in three main steps: listening step to add the "AI is listening..." text, delta step where the transcription bits are added to the current paragraph, and the completed step which happens on longer breaks to create a new paragraph.

As for the refactoring:
- Removal of all the embedded states, keeping them internal to the component and using standard browser API's to observe changes (i.e. the `MutationObserver` to notify changes on the summary),
- The component now relies on the descendents to apply changes during the transcription process, getting rid of the ids,
- Splitting of the `VADAudioRecorder` into separate classes: `AudioProcessor` and `RealtimeClient`. Performing audio recording, and WebSocket operations respectively,
- Making the audio processing, and websocket operation rely on singletons to avoid issues when the editor has to be reloaded in case of synchronisation issues,
- The audio processing was also simplified, and merged with the `PCM16AudioProcessor` using two new events: "vad" for client voice detection, and "audio" for sending the regular audio information. The buffer size was tweaked from 6000 to 2400, to prevent early cut-off of the audio by the server_vad. All the pre-filtering of the audio was also removed which improves the overall quality of the transcript.

task-5153836

**Description of the issue/feature this PR addresses:**
----------------------------------------------
In saas-18.2, the unread message separator can visually overlap with the
message jump/highlight animation when navigating to unread messages.
This issue was not present in 18.0 and results from reduced vertical spacing
between the unread separator and the first unread message.

**Current behavior before PR:**
----------------------------------------------
- Clicking the “X new messages” banner triggers a jump highlight animation
- The highlighted message overlaps the unread red separator line
- The separator becomes partially or fully obscured during the animation

**Desired behavior after PR is merged:**
----------------------------------------------
- The unread separator remains clearly visible during message jump/highlight
- No overlap occurs between the separator and the highlighted message
- Highlight animation behavior remains unchanged
- Visual behavior matches the stable experience observed in 18.0

This PR restores sufficient vertical spacing for the unread separator line,
preventing overlap without altering message animation or interaction logic.

Task-5420965

I confirm I have signed the CLA and read the PR guidelines at https://www.odoo.com/submit-pr

Forward-Port-Of: odoo/odoo#241294

- Before saas-18.4, the [out-of-stock](https://github.com/odoo/odoo/blob/saas-18.3/addons/website_sale_stock/static/src/xml/website_sale_stock_product_availability.xml#L8) message was rendered as plain text without
any layout-specific classes, allowing the message to wrap naturally.

**Reference of version saas-18.3**
<img width="1920" height="768" alt="2025-12-16_18-53" src="https://github.com/user-attachments/assets/d7670fa4-6808-40d7-9bad-768d0637f366" />

- From saas-18.4, the [out-of-stock](https://github.com/odoo/odoo/blob/saas-18.4/addons/website_sale_stock/static/src/xml/website_sale_stock_product_availability.xml#L13-L16) message is rendered using `t-out`, which outputs plain text and collapses line breaks, causing the message to appear on a single line and overflow when used with `d-inline-flex`.
See screenshots in the PR description (Before fix).
<img width="1920" height="672" alt="2025-12-16_14-28" src="https://github.com/user-attachments/assets/927080cd-f2b0-45cd-ae0a-2917699c05f6" />

- Updated the layout to replace `d-inline-flex` with `d-flex` and apply `text-break` on the message container so long and dynamic texts wrap correctly inside the badge.
See screenshots in the PR description (After fix).
<img width="1918" height="682" alt="2025-12-16_14-31" src="https://github.com/user-attachments/assets/2cafdc61-e494-468a-9d41-08ab3c83b041" />


opw-5274850

Description of the issue/feature this PR addresses:

Current behavior before PR:

Desired behavior after PR is merged:




---
I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr

Forward-Port-Of: odoo/odoo#240235

### Context:
In the Manufacturing app, users can create Manufacturing Orders to
create multiple products while assigning a unique serial number to each.
Users can either generate a list of serial numbers starting from a
first serial number, or provide a list of serial numbers themselves.

### Issue:
When providing a list of serial numbers without modifying the first
serial number field (`mrp.production.serials.lot_name`), the inputted
list is not used. Instead, another list starting with the unmodified
`lot_name` is generated and used.

### Cause:
In the `MrpProductionSerials.action_apply` method, the serial numbers
are updated if the first serial number field (`self.lot_name` in the
following code snippet) is left unchanged. This behavior overwrites
the list of serial numbers provided by the user.

https://github.com/odoo/odoo/blob/ac6960dc553088894e688bcc0f4a49245aa02d6c/addons/mrp/wizard/mrp_production_serial_numbers.py#L63-L67

### Steps to reproduce:
1. Install *Manufacturing* (`mrp`)
2. In Settings > Inventory, toggle *Lots & Serial Numbers*
3. Create a product tracked *By Unique Serial Number*
4. Create a Bill of Materials for the product
    - The BoM is required but its content is not relevant.
    Adding a single component with a quantity of one is enough.
5. Update the quantity of the component to be able to produce two products.
6. In *Manufacturing*, create a new *Manufacturing Order*.
    - Select the product and set the quantity to 2, then *Confirm*
7. Click *Generate Serial* or *Produce All*
8. **Do not** modify the *First SN* field, but write two serial numbers
(one per line) in the field below, then click *Apply*.
9. Click the *Serial Numbers (2)* smart button. The serial numbers we
used in step 8 were overwritten by the default *First SN* and its following SN.

### Solution:
This commit addresses the second bug described in https://github.com/odoo/odoo/commit/20158a115ef3dfb9fe2dd5103d3bed7e87e37940 without ever renaming
the serial numbers used for the MO. Now, the `product_id.next_serial`
matches a serial number from the list of provided/generated serial numbers.
The list of serial numbers is sorted to correctly handle cases such as:
```
First SN (self.lot_name) = '0000001'
self.serial_numbers = ['0000003', '0000002', '0000001']
```
In this scenario, we expect the *First SN* of the next MO to start at '0000004'.

The `else` clause of the condition was removed, as it would only be executed
if the `stock.sequence_production_lots` were removed. In that case,
`next_by_code('stock.lot.serial')` would return `False`, preventing
`lot_name` (or `next_serial`) from being updated correctly.

### Reason for second commit

The issue fixed by the first commit was replicated by https://github.com/odoo/odoo/commit/2548fd8d7f3b53a62089ac9122bd17524500ea1a in the subcontracting module (`mrp_subcontracting`). 
The first commit fixes the issue in the Manufacturing app (`mrp`), while the second commit fixes the issue in the subcontracting module (`mrp_subcontracting`). The fix and the test are similar in both commits.

opw-5373745

Forward-Port-Of: odoo/odoo#238678

Steps to reproduce:
===================
-  Add a product categories block with a search bar in the inner content of the block, like "s_product_list".
- Drag a "Search" snippet inside of the block in top of products categories
- Change the layout to "Grid" & Save.
- Type in the search bar to trigger autocomplete suggestions. -> The suggestions appear behind the product categories and are not visible.

Cause:
======
When a searchbar snippet is placed inside a section using grid mode, the autocomplete dropdown was hidden behind sibling grid items. This occurred because the grid layout applies inline z-index to each column (via `_placeColumns` `in grid_layout_utils.js` (See [1])), creating stacking contexts that trapped the dropdown.
So once you change to grid mode layout `_toggleGridMode` function will be triggered which will call  `_placeColumns` that will assign z-index; (See [2])

Solution:
=========
Override the inline z-index on grid items containing a searchbar

[1]: https://github.com/odoo/odoo/blob/d4411c27b469e5dcc526b5b1f8ea4498f2b08567/addons/web_editor/static/src/js/common/grid_layout_utils.js#L225

[2]: https://github.com/odoo/odoo/blob/d4411c27b469e5dcc526b5b1f8ea4498f2b08567/addons/web_editor/static/src/js/common/grid_layout_utils.js#L138

opw-5392011

---
I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr

Forward-Port-Of: odoo/odoo#241478
Forward-Port-Of: odoo/odoo#239607

Issue before this commit:
=========================
The batch and wave names were generated with an extra '/' before the sequence number. Example: `BATCH/WH/OUT//00001`.

Steps to Reproduce:
=========================
- Install the stock_picking_batch module.
- Go to Operations → Batch Transfers.
- Observe existing batch names containing an extra /.

Cause of the issue:
=========================
In this [PR](https://github.com/odoo/odoo/pull/190305), the 'sequence_code' field was changed to be 'related' to 'sequence_id.prefix', which already includes the warehouse and operation parts defaults(e.g., WH/OUT/).

However, in the _prepare_name method, an additional / was still appended after picking_type.sequence_code, leading to the duplicate slash in the name.

With This Commit:
=========================
The redundant '/' insertion in _prepare_name has been removed.
Since picking_type.sequence_code already defines the separator, this
change ensures that batch and wave names are generated correctly and remain clean.