This commit introduces comprehensive logging for AI agent API interactions,
providing visibility into token usage, API calls, and tool execution patterns.

The logging system tracks:
- API calls with estimated token counts (input/output)
- Tool execution (sequential vs batch)
- Timing information for API calls and tool execution
- Summary statistics including total estimated tokens, API calls, tools, and batches

Append `--log-handler odoo.addons.ai:DEBUG` when starting the server to see the
detailed logs.

Example output:
```
DEBUG [AI Prompt] <context>
  <session-info>
    <user id="2" name="Mitchell Admin" model="res.users"/>
    <partner id="3" name="Mitchell Admin" model="res.partner"/>
    <company id="1" name="My US Company" model="res.company"/>
  </session-info>
</context>

<query>
pos orders from restaurant configs containing products from the food categ
</query>
DEBUG [AI Response] Starting generation for model 'gemini-2.5-flash'
DEBUG [AI API Call #1] Sending request with 44360 tokens
DEBUG [AI API Call #1 - →] Received single tool call (3.99s, 16 tokens)
DEBUG [AI Tool →] 'AI: Get Menu Details' with args (menu_ids=[613])
DEBUG [AI Tool - 0.02s] Completed 'AI: Get Menu Details'
DEBUG [AI API Call #2] Sending request with 45432 tokens
DEBUG [AI API Call #2 - ⚡] Received Batch #1, 4 tool calls (2.90s, 77 tokens)
DEBUG [AI Tool - Batch #1 ⚡] 'AI: Get Fields' with args (model_name='pos.order')
DEBUG [AI Tool - Batch #1 - 0.02s] Completed 'AI: Get Fields'
DEBUG [AI Tool - Batch #1 ⚡] 'AI: Get Fields' with args (model_name='pos.order.line')
DEBUG [AI Tool - Batch #1 - 0.01s] Completed 'AI: Get Fields'
DEBUG [AI Tool - Batch #1 ⚡] 'AI: Get Fields' with args (model_name='product.product')
DEBUG [AI Tool - Batch #1 - 0.06s] Completed 'AI: Get Fields'
DEBUG [AI Tool - Batch #1 ⚡] 'AI: Get Fields' with args (model_name='pos.category')
DEBUG [AI Tool - Batch #1 - 0.01s] Completed 'AI: Get Fields'
DEBUG [AI Tool Summary] Batch #1 completed, 4 tool calls
DEBUG [AI API Call #3] Sending request with 50602 tokens
DEBUG [AI API Call #3 - →] Received single tool call (2.98s, 86 tokens)
DEBUG [AI Tool →] 'AI: Open Menu List' with args (menu_id=613, model_name='pos.order', selected_filters=[], selected_groupbys=[], search=['config_id=restaurant'], custom_domain='[["lines.product_id.po
DEBUG [AI Tool - 0.02s] Completed 'AI: Open Menu List'
DEBUG [AI Summary] Total: 10.01s | API calls: 3 (9.87s) | Tools: 6 (0.13s) | Tokens: 140573 (in: 140394, out: 179) | Batches: 1
```

Before:
- If any signer used the eMSigner authentication method, the "Sign Now" option
  was disabled.
- eMSigner does not support signing multiple documents in a bundle, so a warning
  was shown when users tried to add more documents.
- After merging `sign_emsigner`, a traceback occurred when signing with the
 'sms' method because `_validate_auth_method` was called with an unexpected
 `frame` parameter.

After:
- The "Sign Now" option is now allowed when eMSigner is used only by the last
  signer.
- It remains blocked if eMSigner is used by any signer other than the last one.
- Instead of showing a warning, the "Add Document" button is now hidden when
  eMSigner is selected.
- Add `*(kwargs` while calling `_validate_auth_method` auth method when auth
  method is 'sms' which prevent the issue of parameter.

Impact:
- Users can complete signing even when the last signer uses eMSigner, improving
  workflow efficiency.
- The interface is cleaner and prevents confusion by hiding options that are not
  supported.
- The fix for the 'sms' method prevents errors and ensures smoother signing for
  all supported authentication methods.
- Overall, this change improves usability, reduces errors, and provides a better
  user experience.

task-4815486

There are 3 improvements here:
- Attaching PDF and other documents in closing entry moves (like previously)
- Showing the Accounting date by default on draft entries check
- Preventing the Opening Date field to be red when creating a Accounting Periods wizard

In version 18.2, when a closing entry move was generated, the PDF (and other files such as XML) would be send in the chatter. In version 18.3, the Tax returns were changed to have the attachment generated when marking the Tax return as submitted and would be available on the Tax return line. You would still be able to see the closing entry move by using the thre dots next to the Tax return line and selection "View entry" but the attachment wouldn't be included in the chatter anymore. Now, the same attachments from the Tax report line are included in the closing entry move and we made sure to not generate invoices lines from those attachments as they have been generated from the lines we had.

The second improvements was to display the Accounting Date on the Draft entries that needs to be reviewed in a Tax return line to give the user more context on why they need to review those specific Draft entries.

Lastly, when accessing Tax Returns it would ask for us to set the Accouting Periods through a wizard which prefilled informations such as the VAT Periodicity but the Opening Date needs to be filled by this user but this field would show as red when opening the wizard as it is required and no information was prevent. To allow the field to be red only if we try to submit the informations we are passing the informations to the wizard as default value which wouldn't trigger the wizard to try to save values when being created.

task-4784283

This PR introduces several enhancements aimed at improving the default template of the audit reports:

- Headings have been added to articles to establish a clearer content hierarchy and to automatically populate the table of contents.
- The "General Ledger" article has been removed, as it is rarely used in practice and typically not relevant to most audit reports.
- Some sections are now folded by default to avoid displaying contradictory content (for the attestations).
- Labels for foldable sections are no longer shown in the generated resulting in a cleaner and more professional appearance.
- The configuration of the "Balance Sheet" and "Profit and Loss" reports has been updated to provide more meaningful and contextual insights.
- The index of the root article now lists all articles in the report hierarchy.

Additionally, the root article of the audit report will now be named after the audit report itself. This change makes it easier for users to locate the article within the workspace.

Lastly, the "Audit Reports" menu item has been moved under the "Working Files" section of the "Audit" menu to better reflect its purpose and improve navigation.

Task-4999770

New customers starting out with odoo in Colombia have to go through a registration process where they send specific records to the DIAN via a specific endpoint. Currently, the process is:

1) Activate Certification process in settings.
2) Create 3 journals (SETP, NC, ND) for invoice, debit notes, and credit
   notes.
3) Create a specific product with a tax enabled.
4) Create the specific amount of invoices/debit notes/credit notes as
   required from within the DIAN portal.

This process is slow and for most of the users coming to Odoo, they will not have experience with accounting software or understand where to setup such records. As such, a one click setting has been added for certification where they input the number of records necessary, and it will automatically do everything they need.

Notes on implementation:
- This will perform changes that could be considered irreversible on customers databases. As such there is a warning that it should only occur on a staging/duplicated database.
- The values that are hard coded, Technical Key, Min/Max Range Values, and the Authorization Number all come from DIAN and are shared across all users, as such hard coding them to these values are not releasing any secrets.

  task-4366022

**Before this commit:**
When creating an invoice payment with the "automatic invoice" option enabled in Sales settings and using a saved payment token, an email is sent to the customer before the transaction move is posted and the invoice payment status is updated to "In Payment." This results in the email incorrectly asking the customer to remit payment, even though the payment is already being processed.

**Steps to Reproduce:**
1. Enable "Automatic Invoicing" from Sales settings.
2. Enable and publish any payment provider (e.g., Demo) in test mode.
3. Create an invoice and generate a payment link. Open the link in a new incognito tab and pay using any dummy card number (ensure the "Save my payment details" checkbox is checked). This saves the payment token for the partner.
4. Create a new invoice with the same partner, then register payment. Select the payment method and the previously saved token, then confirm.
5. Observe that the payment status is "In Payment," but the email sent to the customer incorrectly asks them to remit payment.

**Fix:**
This change prevents payment notification emails from being sent automatically when the payment is manually created from the payment register wizard.

opw-4850293

Forward-Port-Of: odoo/enterprise#91761
Forward-Port-Of: odoo/enterprise#91570

Fix the following issue that could be triggered quite randomly.
To reproduce it, the easiest way is to set a timeout  between
the 2 await functions in the function runCurrentReturnChecks()
and switching quickly from the audit kanban view to a return view
a few times.

The issue occurs because the refresh_check function might take
a few seconds to compute, and if the user leaves the view before
it finishes, the second await function was triggered on a
destroyed component.

UncaughtPromiseError
Uncaught Promise > Component is destroyed
Error: Component is destroyed
    at Object.original (http://localhost:8069/web/assets/debug/web.assets_web.js:47514:31) (/web/static/src/core/utils/hooks.js:109)
    at Object.fn (http://localhost:8069/web/assets/debug/web.assets_web.js:47507:21) (/web/static/src/core/utils/hooks.js:102)
    at ORM.call (http://localhost:8069/web/assets/debug/web.assets_web.js:47524:52) (/web/static/src/core/utils/hooks.js:119)
    at ORM.webRead (http://localhost:8069/web/assets/debug/web.assets_web.js:33931:21) (/web/static/src/core/orm_service.js:307)
    at props.list.model.load (http://localhost:8069/web/assets/debug/web.assets_web.js:227868:55) (/account_reports/static/src/components/account_return/views/account_return_check_kanban_renderer.js:87)
    at async props.list.model.load (http://localhost:8069/web/assets/debug/web.assets_web.js:227866:36) (/account_reports/static/src/components/account_return/views/account_return_check_kanban_renderer.js:85)
    at async Object.onClose (http://localhost:8069/web/assets/debug/web.assets_web.js:102138:29) (/web/static/src/views/view_button/view_button_hook.js:95)
    at async Object.doActionButton (http://localhost:8069/web/assets/debug/web.assets_web.js:106405:9) (/web/static/src/webclient/actions/action_service.js:1579)
    at async execute (http://localhost:8069/web/assets/debug/web.assets_web.js:102144:21) (/web/static/src/views/view_button/view_button_hook.js:101)
    at async executeButtonCallback (http://localhost:8069/web/assets/debug/web.assets_web.js:102072:15) (/web/static/src/views/view_button/view_button_hook.js:29)

task-4991558

Issue:
When the "Lock Confirmed Sales" setting is enabled, adding a product to a Field Service task would lock the associated sales order before its picking could be created. The confirmation process locks the order first , and the subsequent step to create stock moves (`_action_launch_stock_rule`) explicitly skips locked orders.

Reproducible on 17.0~master
[Task](https://www.odoo.com/odoo/action-4043/4633977)
Odoo 17:
https://drive.google.com/file/d/1qmAYhSu6gU91efuJEDF-Irn2cLGUQP0A/view?usp=drivesdk

Odoo 18:
https://drive.google.com/file/d/1x8IeXwT7ZFM7Av9Vp6GSvGIbOaEGfmVx/view?usp=drivesdk


Steps to reproduce:
1. In Sales > Configuration > Settings, enable "Lock Confirmed Sales".
2. Go to a Field Service task.
3. In the kanban view via the "Products" smart button, add a product.
4. Come back to the task, refresh the browser, open the linked Sales Order from the smart button.
5. **Before this fix:** The SO is locked, no picking is created, and SO lines will have delivered_qty set even though we haven't delivered anything.
6. **After this fix:** The SO is not locked, and a Delivery smart button is correctly displayed, linking to the generated picking.

This behavior left the sales order in an inconsistent state: it was locked, but had no corresponding delivery order. As a result, users were blocked from removing or modifying the products added to the task, as the system prevented edits on a locked order with no picking to cancel.

Let's step through what's going on here;

0. We enable "Lock Confirmed Sales" option.
1. Add a product to the Field Service(FS) task https://github.com/odoo/enterprise/blob/4256ea170c31209b83ff808e51145757571f8556/industry_fsm_sale/controllers/catalog.py#L19-L42
https://github.com/odoo/enterprise/blob/4256ea170c31209b83ff808e51145757571f8556/industry_fsm_sale/controllers/catalog.py#L38
2. set_fsm_quantity() is invoked, which will create a SO for the FS task https://github.com/odoo/enterprise/blob/35e1f47160d5840e8701fc0ad43ec42bbfaf9e36/industry_fsm_sale/models/product_product.py#L144
3. `_fsm_create_sale_order()` will immediately `action_confirm()` the new SO, because of the reasons in the function description. 
( Since we are immediately confirming newly created SO, I think we should consider not applying the "Lock Confirmed Orders" option to FSM SOs.)
https://github.com/odoo/enterprise/blob/2347dac2568dbcf83578f044f8fe41ab70a20f47/industry_fsm_stock/models/project_task.py#L124-L134 https://github.com/odoo/enterprise/blob/2347dac2568dbcf83578f044f8fe41ab70a20f47/industry_fsm_stock/models/project_task.py#L134
4. `odoo/addons/sale/models/sale_order.py/action_confirm()` will lock SO because we enabled 'Lock Confirmed Sales'
https://github.com/odoo/odoo/blob/863c064fd911cb4eeedad0abec82adb4690128f6/addons/sale/models/sale_order.py#L964
6. `_action_launch_stock_rule()` is invoked, is in charge of creating Pickings for SOs 
https://github.com/odoo/odoo/blob/3be83d363786526fe470e41122169e594b5467fb/addons/sale_stock/models/sale_order_line.py#L303
https://github.com/odoo/odoo/blob/3be83d363786526fe470e41122169e594b5467fb/addons/sale_stock/models/sale_order_line.py#L343-L344
7. But, since `line.order_id.locked` , the system do not create Pickings for the SOs. https://github.com/odoo/odoo/blob/3be83d363786526fe470e41122169e594b5467fb/addons/sale_stock/models/sale_order_line.py#L315-L316
The line was introduced by
https://github.com/odoo/odoo/commit/17bece3e797913bcba8dd7e07fc8541c0a45e3f7

This commit resolves the issue by passing a context key `fsm_create_sale_order=True` when confirming a sales order that is being created from a Field Service task. The `_should_be_locked` method on the sale order is overridden to check for this context key. If the key is present, it prevents the order from being locked within that specific transaction, allowing the stock rules to execute correctly and create the necessary picking. The order will be locked for any subsequent operations as intended.

Tradeoff here;
We are sacrificing the universal application of one feature (automatic lock on confirmed sales order) to fix a critical bug that makes the entire FSM delivery process unusable.

---
EDIT: 
Without this change, all of [test_fsm_stock](https://github.com/odoo/enterprise/blob/17.0/industry_fsm_stock/tests/test_fsm_stock.py)'s test cases that use `_fsm_ensure_sale_order()` will fail if the setting is on. (around ~20 test cases). 

[In the past, similar issue occurred for Subscription Orders, and the PO confirmed that the "Lock Confirmed Order" setting should never affect the subscriptions. ](https://github.com/odoo/enterprise/commit/e4f9d76c0a58f3cc226a2372f3936cea4547312e). This commit takes the same approach to ignore the setting upon SO confirmation. 

opw-4633977
opw-4749653
opw-4880664

Forward-Port-Of: odoo/enterprise#91799
Forward-Port-Of: odoo/enterprise#88855

After this commit https://github.com/odoo/enterprise/commit/40d3314d1b06c8110b476690d2264e86b3492b3e we are not able to cancel a sign request,
if user do not have read/write access on `hr.contract.salary.offer` model

**step to reproduce:**
- install `hr_contract_salary`
- create a new user with following right:
  `Sign        -> Administrator`
  `Contracts   -> Employee Manager`
 `Recruitment -> Interviewer`
- login with test user
- open sign -> All Documents (with demo data 2, there should be 2 documents)
- try to cancel one of them

<img width="1572" height="689" alt="config for user" src="https://github.com/user-attachments/assets/72e89ac7-fed3-4a38-918f-5dbb198bd1e3" />



**Observation:**
- even with Admin rights of Sign, we are not able to cancel a sign request
and we receive a Access Error
`You are not allowed to access 'Salary Package Offer' (hr.contract.salary.offer)
records`

**Fix:**
we use `sudo()` to allow everyone to cancel their sign request


opw-4859774

Forward-Port-Of: odoo/enterprise#91688
Forward-Port-Of: odoo/enterprise#89865

The aim of this commit is to prevent a sick day or any other type of time off taken on a public holiday to be deferred.

To reproduce:
- Create a public Holiday for previous month
- Regenerate the work entries for that month
- Compute a batch of payslip for last month, validate and mark it as paid --> The public holiday should be on the payslip
- OPTIONAL: run the cron `Payroll: Generate pdfs` to make create the payslip in document and make it available to the concerned employee.
- With the concerned employee, put a time off on the whole week of the last month. It should overlap with the public holiday.
- Validate the time off and defer it for next payslip
- Compute a batch of payslip for following month, validate and mark it as paid

Before this commit:
The overlapping sick day gets deferred completely ignoring the fact it was a public holiday.

After this commit:
The overlapping sick day doesn't get deferred.

opw-4903546

Forward-Port-Of: odoo/enterprise#91872
Forward-Port-Of: odoo/enterprise#89264

Currently a below occurs or content is not receiving to odoo WhatsApp when the user uploads a large file (tried with > 35 MB).

Stack Trace:
```
MemoryError: null
  File "odoo/http.py", line 2383, in __call__
    response = request._serve_db()
  File "odoo/http.py", line 1913, in _serve_db
    return self._transactioning(
  File "odoo/http.py", line 1976, in _transactioning
    return service_model.retrying(func, env=self.env)
  File "odoo/service/model.py", line 134, in retrying
    result = func()
  File "odoo/http.py", line 1943, in _serve_ir_http
    response = self.dispatcher.dispatch(rule.endpoint, args)
  File "odoo/http.py", line 2187, in dispatch
    result = self.request.registry['ir.http']._dispatch(endpoint)
  File "odoo/addons/base/models/ir_http.py", line 227, in _dispatch
    result = endpoint(**request.params)
  File "odoo/http.py", line 757, in route_wrapper
    result = endpoint(self, *args, **params_ok)
  File "home/odoo/src/enterprise/saas-17.4/whatsapp/controller/main.py", line 42, in webhookpost
    wa_account_id._process_messages(value)
  File "home/odoo/src/enterprise/saas-17.4/whatsapp/models/whatsapp_account.py", line 206, in _process_messages
    datas = wa_api._get_whatsapp_document(messages[message_type]['id'])
  File "home/odoo/src/enterprise/saas-17.4/whatsapp/tools/whatsapp_api.py", line 236, in _get_whatsapp_document
    file_response = self.__api_requests("GET", file_url, auth_type="bearer", endpoint_include=True)
  File "home/odoo/src/enterprise/saas-17.4/whatsapp/tools/whatsapp_api.py", line 46, in __api_requests
    if 'error' in res.json():
  File "requests/models.py", line 971, in json
    return complexjson.loads(self.text, **kwargs)
  File "requests/models.py", line 928, in text
    encoding = self.apparent_encoding
  File "requests/models.py", line 793, in apparent_encoding
    return chardet.detect(self.content)["encoding"]
  File "__init__.py", line 49, in detect
    detector.feed(byte_str)
  File "chardet/universaldetector.py", line 274, in feed
    if prober.feed(byte_str) == ProbingState.FOUND_IT:
  File "chardet/charsetgroupprober.py", line 70, in feed
    state = prober.feed(byte_str)
  File "chardet/hebrewprober.py", line 240, in feed
    byte_str = self.filter_high_byte_only(byte_str)
  File "chardet/charsetprober.py", line 73, in filter_high_byte_only
    buf = re.sub(b"([\x00-\x7F])+", b" ", buf)
  File "__init__.py", line 186, in sub
    return _compile(pattern, flags).sub(repl, string, count)
```

At line [1], the code `'error' in res.json()` is used, which reads all the json content of `res`, but at times users upload large files, it will cause the above error because the `json()` tries to read all bytes from res, which is a very large amount to handle in memory.

This commit will fix the above issue by returning a response if the response
contains content_length more than 10 MB.

[1] - https://github.com/odoo/enterprise/blob/aca7ae2a7cf4aad5427a60d5cad60d08774357d0/whatsapp/tools/whatsapp_api.py#L46

sentry-5810101850

Forward-Port-Of: odoo/enterprise#70001

Previously, the document layout wizard used when sending invoices included fields for Tax ID, Bank Account Number, and QR Code. However, these fields were missing from the wizard accessed via the `Print` button and from the layout
configurator under `General Settings > Configure Document Layout`. This was because only the send flow was using the inherited report layout from the `account` module, while the print and settings flows were using the base layout from `web` directly. Additionally, the preview template in web did not include the bank account number or QR code

With this **PR**:

1. The `Print` button now uses the inherited layout from `account`.
2. The settings configurator button also uses the correct layout from `account`.
3. The bank account number and QR code fields are now dependencies of the
   _compute_preview method, making the preview responsive to their changes.
4. Both fields are now shown in the preview when configuring the layout in
   settings.

This ensures the document layout behaves consistently across send, print, and settings configurator flows.

**task**-4954030

This commit fixes two issues related to project propagation from Sale Order to Purchase Order:

**1. Project not propagated when using MTO+Buy route**

**Steps to reproduce:**
- Install only `sale_project_stock` and `purchase`
- Enable multi-step routes and unarchive the "MTO" route
- Create a storable product "P1" with:
  - Routes: MTO + Buy
  - Vendor: any
- Create a Sale Order with:
  - 1 unit of P1
  - Any project set in "Other Info"
- Confirm the SO

**Issue:**
A Purchase Order is created but the project is not propagated to it. This propagation was previously ensured by `project_mrp_sale`, via:

https://github.com/odoo/odoo/blob/238a41e35280256382f6509182b9e900fb4f7aba/addons/project_mrp_sale/models/stock_move.py#L9

---

**2. Project not propagated when using drop-shipping**

**Steps to reproduce:**
- Enable drop-shipping
- Create a product "P2" with:
  - Route: Drop-Ship
- Create a Sale Order with:
  - 1 unit of P2
  - Any project set
- Confirm the SO

**Issue:**
A Purchase Order is created, but the project is again missing.

---

**Fix:**
- Move the `_prepare_procurement_values` override from `project_mrp_sale` to `sale_project_stock` to ensure project propagation regardless of the presence of `project_mrp_sale`
- Also adapt `sale_project` to ensure project is retrieved from the Sale Order if not set on the Sale Order Line.

opw-4976606

### Steps to reproduce:

- In the settings enable Multi-Steps routes
- Put your warehouse in delivery in 2 steps
- Create and confirm a sale order for 1 units of a storable product
#### > While the pick move was created and confirmed the forecast is still at 0 even tho it should be at -1 and the outgoing pick move should be matched with the SO line in the forecast report.

### Cause of the issue:

The issue has been introduced by commit 5b40fb086a0e5677678c312b42dc1f2c8991dc9e The issue being that since the `location_final_id` should not have been considered for the past forecast based on done move chains (because each done move of the chain will refer to the same external `final_dest_id`). The proposed fix was therefore to change the dest_loc_domain as such:
https://github.com/odoo/odoo/commit/5b40fb086a0e5677678c312b42dc1f2c8991dc9e#diff-1f24ce9f94c5795040749acca5924384d7d17c0ac39b1993cef3b484e4bd30afR324-R326 
However, the new domain:
https://github.com/odoo/odoo/blob/995a7072cb3315fc03544b281b1ed5ca4e81e901/addons/stock/models/product.py#L322-L326 ignores completely the part of the condition refering to `final_dest_id` for outgoing moves since the condition is negated here: https://github.com/odoo/odoo/blob/995a7072cb3315fc03544b281b1ed5ca4e81e901/addons/stock/models/product.py#L328-L333 The logical `OR` (`|`) becoming an `AND` (`&`) for the `domain_move_out_loc`.

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

**Steps to reproduce**:
- install the `accounting` module.
- Go to `Settings -> Technical -> Actions -> Reports -> Invoice or Invoice without payment`
- Change the printed report name
- Try to print the report via the print menu (gear icon -> print) -> The report is shown with the new updated name.
- Try sending the invoice the regular way -> the attached invoice has the default name, Odoo ignores the changes.

**Observation**:
When printing the invoice manually, the file name correctly reflects the custom name configured in the report action. However, when sending the invoice by email, the attachment file name does not match the updated name and remains hardcoded.

**Issue**:
The email attachment file name is hardcoded in the mail sending logic. in the method:
```python
def _get_invoice_report_filename(self, extension='pdf'):
        self.ensure_one()
        return f'{self.name.replace('/', '_')}.{extension}'
```
It does not dynamically fetch the updated report name from the configured report action.

**Solution**:
When a custom report template is configured on the customer on field `(invoice_template_pdf_report_id)`, the system now dynamically uses the corresponding name from the report action for the email attachment.

opw-4923035

### Steps to reproduce:

- Go to the To-Do app and type something in the editor.
- Select the typed text.
- Click on the Font Size Input and choose a value from the dropdown (e.g.,80).
- Try typing again in the editable area.
- Selection is still visible, the focus is no longer in the editable area.

### Description of the issue/feature this PR addresses:

- `focusEditable()` skipped restoring focus if the selection was inside the editor, even when the editor itself wasn’t focused.
- When the font size input (inside an iframe) is focused, editable loses focus.
- Selecting a value from the dropdown blurs the iframe input, but focus is not returned to the editable area.
- As a result, the selection is still visible but the user cannot type.

### Desired behavior after PR is merged:

- Does nothing if the editor or its descendants have focus.
- Focuses the editor if needed.
- Restores selection only when it's outside the editor.
- When the iframe input is blurred, focus is returned to the editable area.

task-4932364

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

**Steps to reproduce**:
1. Install the `account` module.
2. Create a Invoice using this any product.
3. add long descripition (approx. 40-45 lines).
4. Print the PDF of Invoice (via gear icon).

**Observation**:
The long product description overlaps with the table header when the table spans multiple pages in the generated PDF.

**Issue**:
wkhtmltopdf does not handle multi-page table headers properly by default. causing header/content overlap when the table breaks across pages.

**Solution**:
Apply a known wkhtmltopdf workaround by explicitly setting:
  `<thead style='display: table-row-group;'>`
This ensures headers will not repeat same as this. [#53909](https://github.com/odoo/odoo/pull/53909)

before:
<img width="818" height="231" alt="image" src="https://github.com/user-attachments/assets/8bcc6ced-5911-4abd-b91e-97ffa8fb735e" />

after:
<img width="821" height="253" alt="image" src="https://github.com/user-attachments/assets/2ccc6995-c239-4beb-8f68-53d548b7f2f2" />

opw-4982735

Forward-Port-Of: odoo/odoo#221681

### Steps to reproduce:

- Type some text and apply a large font-size.
- Select the text and apply the button style.
- Notice that the font-size is not reflected on the button.

### Description of the issue/feature this PR addresses:

- The `<a class=btn>` element was placed inside a font-size `<span>`.
- However, the `.btn` class defined its own font-size, causing the original styling to be overridden.

### Desired behavior after PR is merged:

- Improved the splitAroundUntil utility to correctly handle cases where the target node has no previous or next sibling. In such edge cases, the function now recursively splits up the inline ancestry until the specified limitAncestor, ensuring that the target node is fully isolated.
- The font-size `<span>` is moved inside `<a>` tag when applying a button style.
- This ensures the original font-size is preserved and correctly displayed.

task-4731416

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

If you made an order and tried to pay with a payment terminal (like Adyen) then canceled the payment on the terminal. Then leave the order and create a new order, add different products, and try to pay again, pay on the terminal, the payment will not be transmitted to the PoS and the order would still be waiting for payment.

Steps to reproduce:
------------------
* Create a pos payment method using adyen
* Open a PoS session
* Create an order with a product
* Pay with the adyen payment method
* Cancel the payment on the terminal
* Leave the order
* Create a new order with different products
* Try to pay with the adyen payment method
* Validate the payment on the terminal
> Observation: The payment will not be transmitted to the PoS and the
  order will still be waiting for payment.

Why the fix:
----------------
The issue occurs because the canceled payment line is still considered as a pending payment line. And when the payment will be receiven on the pos it would take the canceled payment line as the pending one.

opw-4805704

**Issue**
When creating a down payment invoice for a quotation that includes a reseller, an error is raised and the operation is aborted.

**Steps to Reproduce**
1. Install Accounting, Studio, and l10n_in_sale
2. Open the Quotation view in Studio
3. Set the "Referrer" field (i.e., l10n_in_reseller_partner_id) to be always visible and remove group restrictions
4. Create a new quotation and set a reseller in the Referrer field
5. Confirm the quotation
6. Click "Create Invoice"
7. Choose "Down Payment (percentage)" with 10%
8. Click "Create Draft"

**Root Cause**
The `_prepare_invoice_values()` method was assigning the full `res.partner` record to the `l10n_in_reseller_partner_id` field instead of its ID. Since the `account.move` model expects an integer ID for many2one fields, this caused a `psycopg2.ProgrammingError` due to the database adapter not being able to serialize a recordset.

**Fix**
Ensure the value passed to l10n_in_reseller_partner_id is the .id of the partner record, not the recordset itself.

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

**Description of the issue/feature this PR addresses**:
It is needed to ensure that the descriptions for the IIBB perceptions are consistent and correctly reflect the complete name of the jurisdictions they apply to.

**Steps to reproduce**:
1) Go to runbot odoo 18 instance, install l10n_ar module, take position on Argentinean company and activate "Spanish (Latin America)" language.
2) Go to "Accounting / Configuration / Accounting / Taxes", filter by "Sales" Tax Type (type_tax_use) and see that Perc IIBB San Juan, Perc IIBB San Luis and Perc IIBB Santa Fe don`t have the complete description. It is needed to show the complete description.

<img width="1825" height="307" alt="image" src="https://github.com/user-attachments/assets/f664e5ec-a4b5-4a8f-bbab-9ba3d824bd2b" />

**Current behavior before PR**:
Perc IIBB San Juan, Perc IIBB San Luis and Perc IIBB Santa Fe taxes don`t have the complete description.

**Desired behavior after PR is merged**:
Perc IIBB San Juan, Perc IIBB San Luis and Perc IIBB Santa Fe taxes have the complete description.
<img width="1828" height="425" alt="image" src="https://github.com/user-attachments/assets/dc8ee6dd-23c3-40c1-a973-943971e3cb78" />

**Task Adhoc side**: 53028
**Task latam side**: 1356

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

Steps to Reproduce:
1. Go to the website.
2. Create a new menu (e.g., 'Test 1') using the 'Edit Menu' option and add it under another menu (e.g., 'Contact Us'), creating a sub-menu. 
3. Turn on the developer mode.
4. Go to Configuration -> Menus and add two menus (e.g., 'menu 1' and  'menu 2') under the new sub-menu (e.g., 'Test 1').
5. Notice that the two menus ('menu 1' and 'menu 2') are not visible on the website.

Description:
As per functional specifications, creation of multi-level sub-menus should not be allowed.

Key Changes:
raises a `UserError` if a menu exceeds the two-level hierarchy by checking the parent and grandparent levels.
- Implements mega menu restrictions:
    - A mega menu cannot have a parent menu.
    - A mega menu cannot have child menus.
    - Any menu cannot be a child of a mega menu.
- Prevents menus with child menus from being added as submenus to existing menus.

This ensures that the website menu structure adheres to the defined functional specifications, providing a consistent and predictable user experience.

task-3901371

Forward-Port-Of: odoo/odoo#168801

Currently a below occurs or content is not receiving to odoo WhatsApp when the user uploads a large file (tried with > 35 MB).

Stack Trace:
```
MemoryError: null
  File "odoo/http.py", line 2383, in __call__
    response = request._serve_db()
  File "odoo/http.py", line 1913, in _serve_db
    return self._transactioning(
  File "odoo/http.py", line 1976, in _transactioning
    return service_model.retrying(func, env=self.env)
  File "odoo/service/model.py", line 134, in retrying
    result = func()
  File "odoo/http.py", line 1943, in _serve_ir_http
    response = self.dispatcher.dispatch(rule.endpoint, args)
  File "odoo/http.py", line 2187, in dispatch
    result = self.request.registry['ir.http']._dispatch(endpoint)
  File "odoo/addons/base/models/ir_http.py", line 227, in _dispatch
    result = endpoint(**request.params)
  File "odoo/http.py", line 757, in route_wrapper
    result = endpoint(self, *args, **params_ok)
  File "home/odoo/src/enterprise/saas-17.4/whatsapp/controller/main.py", line 42, in webhookpost
    wa_account_id._process_messages(value)
  File "home/odoo/src/enterprise/saas-17.4/whatsapp/models/whatsapp_account.py", line 206, in _process_messages
    datas = wa_api._get_whatsapp_document(messages[message_type]['id'])
  File "home/odoo/src/enterprise/saas-17.4/whatsapp/tools/whatsapp_api.py", line 236, in _get_whatsapp_document
    file_response = self.__api_requests("GET", file_url, auth_type="bearer", endpoint_include=True)
  File "home/odoo/src/enterprise/saas-17.4/whatsapp/tools/whatsapp_api.py", line 46, in __api_requests
    if 'error' in res.json():
  File "requests/models.py", line 971, in json
    return complexjson.loads(self.text, **kwargs)
  File "requests/models.py", line 928, in text
    encoding = self.apparent_encoding
  File "requests/models.py", line 793, in apparent_encoding
    return chardet.detect(self.content)["encoding"]
  File "__init__.py", line 49, in detect
    detector.feed(byte_str)
  File "chardet/universaldetector.py", line 274, in feed
    if prober.feed(byte_str) == ProbingState.FOUND_IT:
  File "chardet/charsetgroupprober.py", line 70, in feed
    state = prober.feed(byte_str)
  File "chardet/hebrewprober.py", line 240, in feed
    byte_str = self.filter_high_byte_only(byte_str)
  File "chardet/charsetprober.py", line 73, in filter_high_byte_only
    buf = re.sub(b"([\x00-\x7F])+", b" ", buf)
  File "__init__.py", line 186, in sub
    return _compile(pattern, flags).sub(repl, string, count)
```

At line [1], the code `'error' in res.json()` is used, which reads all the json content of `res`, but at times users upload large files, it will cause the above error because the `json()` tries to read all bytes from res, which is a very large amount to handle in memory.

This commit will fix the above issue by returning a response if the response
contains content_length more than 10 MB.

[1] - https://github.com/odoo/enterprise/blob/aca7ae2a7cf4aad5427a60d5cad60d08774357d0/whatsapp/tools/whatsapp_api.py#L46

sentry-5810101850

Forward-Port-Of: odoo/enterprise#70001

A non-deterministic error has been occurring across all versions starting from 18.0 when running the
`test_split_line_on_destination_scan`.

problem:
The issue lies in one of the steps of the tour, where the destination location of the remaining quantity is changed from WH/Stock to shelf1 (LOC-01-01-00). Right after this change, the test proceeds to assertLineDestinationLocation. However, the test step was previously waiting for the presence of the .o_validate_page.btn-primary element — an element that is already visible before the destination location update is actually applied. As a result, the tour sometimes skips to the next step prematurely, without ensuring the location change has occurred, leading to test failure.

Fix:
We replaced the trigger .o_validate_page.btn-primary with a more reliable condition: waiting for an element containing the destination text .../Section 1 (.o_line_destination_location:contains(".../Section 1")). This ensures that the step only proceeds once the destination update has been reflected in the UI.

Runbot-145458