Before this commit, clicking "Generate Offer" on an Employee or Applicant redirected the user to the full form view of `hr.contract.salary.offer`. This disrupted the user flow and presented too many fields initially.

This commit improves the UX by introducing a transient wizard (`hr.contract.salary.offer.wizard`) that opens in a popup.

Key changes:
- **Wizard Implementation**: A new popup allows quick data entry for essential fields (Contract Template, Job Title, Dates, Wage).
- **Wage Logic**: Users can toggle between defining "Monthly Gross" or "Yearly Employer Cost", with automatic bidirectional conversion based on the selected contract template.
- **Simulation Preview**: The wizard displays a real-time salary simulation (Gross, Net, Benefits, Company Cost) computed dynamically using the payroll engine without creating persistent records.
- **Action Buttons**: Added "Send by Email", "Copy Link", and "Salary Configurator" actions directly to the wizard footer.
- **Sign Template Logic**: The PDF Sign Template is no longer mandatory. If missing, the signatory logic is skipped to allow pure simulations.
- **Expandability**: Added an "Expand" button to the wizard header to allow users to transition to the full offer form view if needed.
- **Applicant Integration**: The wizard pre-fills data (Salary Expected, Availability) from the Applicant record.

task-5088948

task-4917399

<details><summary>old diagrams</summary>
<p>

```mermaid
sequenceDiagram
    actor EC as External Caller
    participant VC as VoIP Carrier
    participant PX as Proxy Provider
    participant OD as Odoo DB
    participant PS as Push Notification Server
    participant SW as Service Worker of Marc's Android Phone
    actor MD as Marc Demo
    participant PWA

    EC -->> VC: INVITE
    VC -->> PX: INVITE
    PX -->> OD: WebHook /voip/new-call
    OD -->> PS: Push Notification
    OD -->> PX: Dial Marc Demo, if not available play ringback
    PX -->> VC: 183 RINGING EARLY MEDIA
    PS -->> SW: Notif is received
    SW -->> MD: Display Notif
    MD -->> SW: Answer call
    SW -->> PWA: Open PWA window
    PWA -->> PX: REGISTER
    PX -->> PWA: OK
    PWA -->> SW: Ready
    SW -->> PWA: User action is Answer
    PWA -->> OD: Resend INVITE
    OD -->> PX: For current call, dial MD
    PX -->> PWA: INVITE
    PWA -->> PX: ANSWER
```

## Scenario: Client Ready and Not Busy
```mermaid
sequenceDiagram
  actor A as Alice
  participant T as Telnyx
  participant I as Odoo IAP
  participant O as Odoo Server
  participant F as Google FCM
  participant S as Service Worker
  %% participant R as SW Registration
  participant W as WebClient
  %% actor B as Bob

  A -->> T: Call +3281123456
  T -->> O: call.initiated
  O -->> O: create voip.call
  O -->> F: notify
  F -->> S: notify
  O -->> T: OK 200
  S -->> W: post message
  W -->> O: ready to receive call invite
  O -->> I: Transfer to Bob
  I -->> I: inject api key
  I -->> T: Transfer to Bob
  T -->> W: SIP INVITE
```

### Alternative Idea: use bus ws?
(is this doable?)
```mermaid
sequenceDiagram
  actor A as Alice
  participant T as Telnyx
  participant I as Odoo IAP
  participant O as Odoo Server
  %% participant S as Service Worker
  %% participant R as SW Registration
  participant W as WebClient
  %% actor B as Bob

  A -->> T: Call +3281123456
  T -->> O: call.initiated
  O -->> W: bus.message: ready?
  W -->> O: yes
  O -->> I: Transfer to Bob
  O -->> T: OK 200
  I -->> I: inject api key
  I -->> T: Transfer to Bob
  T -->> W: SIP INVITE
```



</p>
</details>

### 20251110
```mermaid
---
title: Base Scenario
---

sequenceDiagram
  actor A as Alice
  participant T as Telnyx
  participant O as Odoo Server
  participant S as Service Worker
  participant W as WebClient
  actor B as Bob

  A ->> T: Call +3281123456
  T ->>+ O: call.initiated
  O ->> O: create voip.call
  O ->>- T: OK 200

  par Blind Transfer
    O -->> T: Transfer to Bob (through IAP)
    %% T ->>+ O: Transfer Session Hangup (reason: not found)
    %% O ->>- T: OK 200
  and Notification Push
    O -->> S: notify (through FCM)
    S ->> S: display notification
  end

  opt Receive invite at first transfer
    T ->> W: SIP INVITE (+header X-Odoo-Call-ID)
  end

  opt Decline
    alt From Softphone
      B ->> W: interact with softphone
      W ->> T: SIP DECLINE
      W ->> W: voip.call state = rejected
    else From notification
      B ->> S: interact with notification (decline)
      S ->> O: decline call
      O ->> O: voip.call state = rejected
      O -->> T: Reject
    end
      T ->> A: Reject
  end

  opt Answer
    alt From Softphone
      B ->> W: interact with softphone
    else From notification
    rect rgb(220, 240, 255)
      B ->> S: interact with notification
      S ->> W: wake up WebClient
      W ->> O: ready to receive call invite
      O -->> T: Transfer to Bob (through IAP)
      T ->> W: SIP INVITE (+header X-Odoo-Call-ID)
    end
      alt Manual
        B ->> W: interact with softphone
      else Automatic
        W ->> W: AUTO_ANSWER
      end
    end
    W ->> T: ANSWER
    T ->> W: OK
    A <<->> B: RTP Media
    W ->> W: voip.call state = ongoing
  end

  %% alt Decline From notification
  %% else Open from notification
  %%   B ->> S: interact with notification
  %%   S ->> W: wake up WebClient
  %%   W ->> O: ready to receive call invite
  %%   O -->> T: Transfer to Bob (through IAP)
  %%   T ->> W: SIP INVITE (+header X-Odoo-Call-ID)
  %%   opt Answer
  %%     alt Manual
  %%       B ->> W: ANSWER
  %%     else Automatic
  %%       W ->> W: AUTO_ANSWER
  %%     end
  %%     W ->> T: ANSWER
  %%     T ->> W: OK
  %%     A <<->> B: RTP Media
  %%     W ->> W: voip.call state = ongoing
  %%   end
  %% end
```

Steps to reproduce:
-------------------
1. Install l10n_ch_hr_payroll_elm_transmission.
2. Switch to a Swiss company and create a new employee.
3. Create a new internal user with Payroll Officer/Manager access.
4. Log in as that user, create a contract, and click on "One-time payments".

Issue:
---------
A Traceback with AccessError:
```You are not allowed to access 'Action Window' (ir.actions.act_window) records.```

Cause:
----------
https://github.com/odoo/enterprise/blob/9e39b4b85fcb9f6ed5b21b942796b76b8a6eefdb/l10n_ch_hr_payroll_elm_transmission/models/hr_contract.py#L195
The code attempts to call `.read()` on an `ir.actions.act_window` record.
Standard users typically do not have read access to window action records,
resulting in an **AccessError** even if they have rights to the payroll data.

Solution:
-------------
Use [_for_xml_id](https://github.com/odoo/odoo/blob/93bd4d018d815b5f98d1eaaac3ae613aefbdba56/odoo/addons/base/models/ir_actions.py#L187) to return action content for the provided xml id
in a safe way by doing [sudo](https://github.com/odoo/odoo/blob/93bd4d018d815b5f98d1eaaac3ae613aefbdba56/odoo/addons/base/models/ir_actions.py#L205) internally to bypass the access restriction.

opw-5491467

Forward-Port-Of: odoo/enterprise#107628
Forward-Port-Of: odoo/enterprise#106598

This recent commit:
odoo/enterprise@d223f826eaafa3189846b555af16b240f91936ba

changed the formula for `account_financial_report_line_ch_290_a_balance` from:
```py
[('account_id.code', '>=', '290'), ('account_id.code', '<', '2991'), ('account_id.account_type', '!=', 'equity_unaffected')]
```
to:
```py
[('account_id.code', '>=', '290'), ('account_id.code', '<', '2970')]
```
The main goal of the commit was to remove the unaffected earnings account from the CH reports. While doing so, the formula was also modified by replacing `account_id.code = 2991` with `account_id.code = 2970`.

However, since the condition uses the `<` operator, the account with `code = 2970` is not taken into account. Account `2970` is the last account that should be considered before `Annual profit or annual loss`. see:
https://github.com/odoo/odoo/blob/19.0/addons/l10n_ch/data/template/account.account-ch.csv#L106

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

Forward-Port-Of: odoo/enterprise#102247

The grouped tax reports are broken if an invoice is created with 2 lines on 2 different income accounts.

[A previous commit](https://github.com/odoo/odoo/commit/48d60151254045768d5aac1b29c5acf84b70cef2) modified the query responsible for the construction of the grouped reports. It only keeps the baselines of type 'entry' which have a balance of the same sign as the tax line.

But in our case, the CABA move is of type 'entry'. It has only one tax line with a positive amount because the taxes amounts on each line are added. But the balance of the negative line is negative. So the query will only consider the positive line hence the error.

So now, the logic of the only considering lines with the same sign is to avoid entries where the invoice lines and the refund lines are both there. This is why it only checks for moves of type 'entry'.

We also ignore the check for CABA moves, i.e. moves where `tax_cash_basis_origin_move_id` is defined.

Steps to reproduce:
- Activate Cash Basis in the Settings
- Create a tax based on payment
- Create an invoice with two lines:
	- One with a negative amount, an income account and the created tax
	- One with a positive amount big enough to compensate the previous line, a different income account and the same tax
- Confirm
- Click "Pay", validate the payment
- In the Dashboard > Bank journal > Create a reconciliation of the amount of the invoice
- Reconcile it with the invoice
- Accounting > Reporting > Tax Return
- Select "Group By: Account tax"

Community PR: odoo/odoo#239081

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

Forward-Port-Of: odoo/enterprise#107707
Forward-Port-Of: odoo/enterprise#101601

Bug reproduction: When version >= 19.0, install Kenya payroll and accounting, create payslip for one of the Kenyan employee -> validate the payslip -> Reporting: P9 Report in payroll app -> Create new tax deduction card -> populate employees -> in the inside of the card: select employees and click to generate pdf -> it will not be generated 

Bug cause:
    1 - In cron parameters, context passed wrongly, it should take place in the clickable parameters
    2 - After saas-18.4 in the migration, employee.l10n_ke_pin field is removed but this field still takes place in l10n_ke_tax_reduction_card_templates.xml and it gets error when the user clicks to generate PDF.

Bug solution:
    1 - Fixing cron parameter passing
    2 - Removing PIN of employee field from P9 report since it is not available anymore.

Testing: Unit test is written to check PDF's are generated for sure.
    1 - Creating Kenya company, employees
    2 - Creating payslip for employees and validate them
    3 - Creating tax deduction card and generate declarations
    4 - Checking PDF's are created

task - 5395267

Forward-Port-Of: odoo/enterprise#107744
Forward-Port-Of: odoo/enterprise#104816

Reinstalling the appointment module fails during mail template validation.

### Reproduction Steps

1. Install the `appointment_hr_recruitment` module.
2. Uninstall `appointment`.
3. Reinstall `appointment`.

→ A template parsing error appears.

### Cause

The global `request.env` is bound to the registry active at the start of the request. When reinstalling a module, this registry becomes stale and does not include the models being re-added.

During installation, the `mail.template` model performs a test render to validate its XML data. One of the templates calls `_get_interview_invite_url`, which invokes a controller that looks up the `appointment.type` model using `request.env`.

Because the registry is stale and does not contain this model, the lookup raises a KeyError and the installation fails.

### Fix Rationale

Skip invite URL generation when `install_mode` is set to avoid using the stale `request.env`.

opw-5898780

Forward-Port-Of: odoo/enterprise#107650

Bug : allocate a number of holidays that is not an integer (ex : 20.5), then check the holiday attest (shows 20 allocation).
      The same problem happens if the number of leaves taken is not an integer

Steps : - in the belgian company, create a new employee with a valid contract give an employee 19.5 days of Time Off type leaves.
	- on the form view of the employee , click on the action button -> Departure: Notice period and payslip -> and fire the employee.
	- now click on action button -> Departure: Holiday Attests, you'll see that the employee has 19 allocated instead of 19.5

Reason :  The number of leave_allocation_count and leave_count are defined as integers in HrPayslipEmployeeDepatureHolidayAttestsTimeOffLine, when they are populated, they end up casting the assigned value to an int.

Fix : Create two new float fields leave_count_float and leave_allocation_count_float to replace their corresponding integer fields.

task - https://github.com/odoo/enterprise/commit/5461268c9411d36feac90cd45dcff42aab59599b

Forward-Port-Of: odoo/enterprise#103258

The goal of this task is to completely review the field service flow since the users need a better integration with planning features to plan their intervention, the field service features will now be integrated inside planning instead of being an extension of project app. 

By doing that, 
- the flow to plan an intervention is simplify thanks to the existing features in planning.
- the field service settings inside the project have been moved into global configuration of planning app once field service feature is installed.
- the intervention will now be a shift instead of a task
- `task_id` field is added to `planning.slot` to be able to use the task as a maintenance contract (a way to centralize all the interventions made for a specific customer for instance).
- the timesheets will now just be generated once the intervention is mark as done. The number of hours for each resource set on the intervention will be the allocated hours set on the intervention.
- worksheet feature has also been moved in `planning.slot`.
- `Extra Quotation` feature can now be enabled in planning configuration instead of having the settings in each project.
- `Add Materials on tasks` feature can now be enabled globally in planning configuration.
- 2 new status on `planning.slot`, `in progress` to mark the intervention has on going and `completed` to mark the intervention as completed.

task-5258989