Steps to reproduce:
------------------------
1. Install Planning
2. Create a slot for any resource spanning a full month (e.g., 05/01 08:00 - 05/31 17:00)
3. Enable repeat, set occurrence to "Week"
4. Save and observe generated slots

Issue:
--------
Some recurring weekly slots are created as open shifts (resource_id = False) even though the resource is not actually busy during that period.

Cause:
----------
The overlap check used to detect resource conflicts: https://github.com/odoo/enterprise/blob/a739c6c03c6629bad80f3fe61b1035ce156d59c6/planning/models/planning_recurrency.py#L122-L127

For a full-month slot (05/01 - 05/31), the first weekly recurrence starts on 05/08. Since 05/08 <= 05/31 (the original slot's end_datetime), the overlap condition evaluates to True and incorrectly sets resource_id to False.

This issue does not reproduce for monthly recurrence because the next occurrence (06/01) is always greater than the current month's end_datetime (05/31), so the overlap condition evaluates to False.

Fix:
------
Instead of stripping the resource on any overlap, we now compute total planned hours vs total available hours in the overlap window. The resource is only unassigned if it is truly overbooked (total_hours_planned > total_hours_in_overlap).

NOTE:
---------
This issue has been resolved from version 18 with this 079b0ba.

opw-6144096

Steps to reproduce:
- Install Accounting module
- Accounting > Reporting > Journal Report > Ensure that the last line of the report has an empty balance column, and that the Load More button is displayed immediately after it [image](https://www.awesomescreenshot.com/image/61045422?key=3ee9914f6472026aafa130253a9a32f9)
- Scroll down to the bottom of the Bank journal section and click load more

Traceback:
`TypeError: can only concatenate str (not "float") to str`

When opening a bank journal in the Journal Report and clicking "Load More" to fetch additional entries, the running balance calculation would crash and the report would fail to load further lines.

This was caused by the browser sending an empty string ('') as the current running balance instead of 0.0 when no cumulated balance had been rendered yet. Since the key already exists in the progress dict, the fallback default of 0.0 was never used, causing float arithmetic to fail on an empty string when updating the cumulated balance for each journal entry.

Fixed by sanitizing the progress values before use, converting any empty or missing balance values to 0.0, allowing "Load More" to work correctly on bank journal reports.

opw-6264616

Steps to Reproduce
---
- Create two different working schedules with different public holidays
- Assign employees to specific working schedules
- Set company default working schedule to a different schedule
- Login as employee with specific working schedule
- Navigate to Timesheets app -> My Timesheets
- Observe public holidays and personal time-off displayed in the timesheet grid

Issue
---
- The timesheet grid displays unavailable dates (public holidays, weekends) from the company's default working schedule instead of the employee's assigned working schedule.
- Personal time-off requests are not reflected as unavailable dates in the timesheet grid.

Current Behaviour
---
- Public holidays shown are always from the company's default working schedule, ignoring employee-specific working schedule assignments.
- Employee's approved time-off requests don't appear as unavailable in the timesheet.

Expected Behaviour
---
- Public holidays should display based on the employee's assigned working schedule, with company schedule as fallback only when no specific schedule is assigned.
- Employee's personal time-off requests should appear as unavailable dates.
- This should align with Time Off app behavior.

Fix
---
- Included employee-specific work interval calculation with personal time-off requests.
- Added support for contract-based calendar changes and calendar validity periods.
- Implemented proper fallback when valid intervals are not found.

task-4997080