This update strengthens quality checks for the self-ordering point-of-sale experience by adding automated test coverage for key screens, data models, and service behavior. It also reorganizes some internal test setup so future changes can be validated more safely and with fewer naming conflicts.

- Isolated `printer` service into a standalone file to avoid naming conflicts with `point_of_sale` during tests.
- Introduced `setupSelfPosEnv` to mock and bootstrap the self-order testing environment.
- Add Hoot test coverage for core components, models, and service logic

Task-4945633

Forward-Port-Of: odoo/odoo#220537

This update improves the internal test tools used for the website editor so tests wait for the sidebar to finish loading and updating before continuing. This helps reduce flaky test results and gives teams more confidence that website builder changes are validated reliably.

We need a helper to wait enough

The US payroll demo data now includes a Developer USA employee record so demo payroll setup starts with the needed sample information. This helps demos run more reliably by ensuring salary structure defaults are applied after the demo record is available.

Added the Developer USA demo data record in the l10n_us_hr_payroll.xml file instead of leaving it empty for the sake of the demo data being added before triggering the _default_salary_structure function in hy_version.py

Task ID: 5003603

The Hong Kong payroll employee form now places employee name fields under the private contact information section instead of location information. This makes the information easier to find in the most relevant area and improves form organization for HR users.

before: the names were under location information
after: moved the names under private contact information

task-5042649

Pay Run cards now show icons and clearer, capitalized information text, making payroll runs easier to scan. The Pay Runs action also has a cleaner navigation path, improving consistency when users access this area.

- added icons in Pay Run card and capitalized the info texts
- added path to Pay Runs action (as `pay-runs`)

task-5109059

Payslips that have been validated now show the status as "Done" instead of "Validated". This creates consistent wording between individual payslips and payroll runs, reducing confusion for payroll users.

If the payslip status is "validated", the display status for the payslip is "Validated". 
The display has been changed to "Done" to match with the payrun's status.

Forward-Port-Of: odoo/enterprise#95182

Desktop users can now copy the text of AI chat messages directly from the message actions. This makes it easier to reuse AI-generated responses outside the conversation without manual selection.

This commits enables the copy text message action on desktop.

task-3509874

This update changes how accounting-related demo and localization data is loaded, making setup more consistent across modules. It mainly supports smoother testing and onboarding environments without changing day-to-day business workflows.

More information in community PR

An unused field in the Appraisal Skills module was removed because it was no longer serving any purpose. This helps keep the module simpler to maintain without changing expected user behavior.

manager_ids is a computed field defined on hr.appraisal.skill model, but it's never used.

task-5072467

Payslips that were previously shown as “Validated” will now appear as “Done”. This aligns the payslip status wording with the related payrun status, making payroll screens more consistent for users.

If the payslip status is "validated", the display status for the payslip is "Validated". 
The display has been changed to "Done" to match with the payrun's status.

The Stripe payment code was reorganized to keep related checkout and payment form behavior in the same area. This is an internal improvement that should make future payment updates easier to maintain without changing the customer payment experience.

Restaurant point-of-sale demo data now shows selected products with colors that differ from their categories. This helps customers see during onboarding that product colors can be customized independently, making menu setup easier to understand.

In this commit:
------------------
- We’ve added random colors to the below products in onboarding to help customers understand that they can choose different colors for products than the selected pos category.

### Products assigned new colors:
- Water
- Green Tea
- Fanta
- Bacon Burger
- Pasta 4 Formaggi
- Chicken Curry Sandwich
- Club Sandwich
- Sushi Lunch Combo

task: 5103944

The point of sale product editor now shows the name of a color variant when users hover over it. This makes it easier for staff to identify the correct product option quickly and avoid confusion when colors look similar.

In this commit:
---------------
- We will display variant names when hovering over them from edit product popup on UI for color variants.

task: 5095570

The bank configuration card now uses an adjusted background color when dark mode is enabled. This improves visual consistency and readability for users configuring online bank synchronization in dark mode.

This commit will change the background color of the dark mode of the configure bank cart.

no task id

Odoo's core memory cleanup settings were adjusted to match changes in Python 3.13 and 3.14. This helps keep the system aligned with newer Python behavior and supports stable performance as the platform evolves.

The thresholds were changed in 3.13: threshold0 = 2000 instead of 700

There are only 2 collections instead of 3 since 3.14 and the second collection is processed incrementally.
https://github.com/python/cpython/blob/3.14/InternalDocs/garbage_collector.md

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

This update reorganizes how the Accounting app decides when a journal entry needs confirmation before validation. It keeps the same user experience while making future customizations easier and less costly to maintain.

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

This PR refactors the `action_validate_moves_with_confirmation` method to improve its extensibility.

Currently, the conditions that determine whether an `account.move` requires a confirmation dialog before posting (e.g., future-dated moves) are hardcoded within the action method itself. This design limits extensibility, as customizing the confirmation criteria requires overriding the entire action. This approach leads to code duplication and increases the maintenance burden for custom modules.

To address this, the validation logic is decoupled and extracted into a new, protected helper method: `_get_moves_requiring_confirmation`. This change improves the modularity of the `account` module and provides a clean extension point for developers, without altering the existing user-facing behavior.

## Current behavior before PR:

The logic for identifying moves that require confirmation is tightly coupled with the `action_validate_moves_with_confirmation` method. Customizing these conditions necessitates a complete override of the method, which is not ideal for maintainability.


## Desired behavior after PR is merged:

The confirmation logic is isolated in a new, dedicated `_get_moves_requiring_confirmation` method. This provides a clear and standard extension point, allowing developers to modify the confirmation criteria by simply overriding this new method. This promotes cleaner code, reduces duplication in custom modules, and improves overall maintainability.


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