Steps to reproduce:

1. Create a maintenance request with these values:

   * Maintenance Type: Preventive
   * Recurrent: enabled
   * Repeat Every: 1 day, forever
   * Scheduled Date: today
2. Confirm that an activity is created for the responsible user.
3. Mark the activity as done.
4. Move the request to `Repaired`, or another done stage.
5. Check the newly generated request in the recurring series.

When a recurrent maintenance request is moved to a done stage, Odoo creates the next request in the series.

The existing activity on the completed request is marked as done and automatically unlinked by `activity_feedback()`.

Previously, `activity_update()` was then called on all requests whose stage changed. Since the completed request no longer had a pending activity, this created a new one on that request.

The newly generated recurring request also received its own activity, resulting in one activity on the completed request and another on the new request.

Only call `activity_update()` for requests that remain in a non-done stage. This prevents a new activity from being created on a completed request while preserving the reminder on the next recurring request.

opw-6409396


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

Forward-Port-Of: odoo/odoo#279470

When a relational property has a domain the server cannot evaluate, opening its definition editor crashes. The editor calls search_count on that domain to show how many records match, both when it opens and on every later render. The server raises a ValueError and the call has no error handling, so the whole editor goes down. The bad domain stays saved on the property, so reopening the editor fails the same way and the property can no longer be edited or deleted.

Wrap the search_count call in _updateMatchingRecordsCount (property_definition.js) in a try/catch and show no count when it fails. This is the only place the editor counts matching records, so guarding it here handles a bad domain from any source, the field selector or the code editor. The field selector still shows its warning on the invalid path, so the user can fix or delete the property.

Steps to reproduce:
1. On a model that has a Properties field, add a Many2one property and set its Model to a model that itself has a Properties field.
2. Open the property Domain and click New Rule.
3. In the field selector pick the Properties entry, then close the selector.

=> An error dialog appears and the property can no longer be edited or deleted.

Ticket [link](https://www.odoo.com/odoo/project.task/6101311)
opw-6101311

Forward-Port-Of: odoo/odoo#281221
Forward-Port-Of: odoo/odoo#259886

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

When using the POS in dark mode, certain form control elements display
black text on a dark background, making them illegible.

This occurred because the POS application lacked the `color-scheme` CSS
property. While the backend web client correctly applied this property,
its absence in the POS meant the browser still assumed a light theme, 
forcing default User Agent styles (black text) onto native form controls 
that escaped standard view helpers.

This commit resolves the issue by applying the `$o-webclient-color-scheme`
variable to the POS application. This signals the browser to render form
controls and UI elements based on the current web client color scheme,
ensuring text remains legible within the POS app.

**Steps to reproduce:**

- POS > Open Restaurant Register
  - Hamburger icon (top right) > Switch to Dark Mode
  - Register > vertical ellipses icon (bottom left) > Quotation/Order > type in the search bar > observe black text on dark grey background


**Current behavior before PR:**

<img width="1911" height="588" alt="Before 1" src="https://github.com/user-attachments/assets/99581745-23eb-45e1-96f7-bca78853369c" />
<img width="1919" height="550" alt="Before 2" src="https://github.com/user-attachments/assets/b7eb9726-e2d2-492b-ad2b-6c0cc6613bb8" />

**Desired behavior after PR is merged:**

<img width="1910" height="433" alt="After 1" src="https://github.com/user-attachments/assets/419b7a2a-234e-47c8-854e-22adf6a7c5c1" />
<img width="1915" height="513" alt="After 2" src="https://github.com/user-attachments/assets/8f1cf5c9-5ad1-4aac-9879-840d6d9d537e" />

opw-6508945

Forward-Port-Of: odoo/odoo#284831