Manufacturing users get redesigned Bill of Materials structure and cost reports that can be expanded dynamically and printed for multiple products. The change also adds richer demo manufacturing data and cost-per-hour tracking for work centers, making production cost analysis easier and more accurate.

Description of the issue/feature this PR addresses:

Current behavior before PR:

Desired behavior after PR is merged:




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

This update modernizes online bank synchronization by adding a new Plaid connection flow and support for many more financial institutions. It also improves the setup experience for both Plaid and Yodlee connections and adds tests to help ensure reliability.

New api for plaid (now support 9000+ institutions)
Use of plaid link for authentication
Use of yodlee fast link for authentication
New institution selection widget
Better usability when starting/ending synchronization process
Add tests for plaid/yodlee

Adds project reporting that compares forecasted work with actual timesheet hours, helping teams see planning accuracy by project, task, or user. It also streamlines project overview views and removes a redundant sales forecast module whose functionality already exists elsewhere.

Description of the issue/feature this PR addresses:
https://www.odoo.com/web#id=34702&view_type=form&model=project.task&action=333&active_id=965&menu_id=4720

Users can now view PDF and image attachments from the chatter alongside a form on large displays. This makes it easier to review related documents without leaving or scrolling away from the main record.

Task: https://www.odoo.com/web?#id=40663&view_type=form&model=project.task&action=333&active_id=131&menu_id=4720
PAD: https://pad.odoo.com/p/r.87a7ead0f01433057eaae2b3f0735dc5

The server now provides a standard signal for custom code to know when the system registry has finished loading. This helps multiprocessing deployments and external customizations coordinate startup more reliably without changing user-facing workflows.

**Description of the issue/feature this PR addresses:**
During multiprocessing we should have an event to patch into to wait for the registry to be loaded. This adds an event that's easy to inherit and implement in external customizations.

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

This update strengthens project profitability reporting by adding clearer analysis of project costs, revenues, managers, products, and time spent. It also separates projects from analytic accounts and improves timesheet cost tracking, making it easier to manage multiple projects from sales orders and understand project performance.

Description of the issue/feature this PR addresses:
https://www.odoo.com/web#id=34702&view_type=form&model=project.task&action=333&active_id=965&menu_id=4720


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

The Sales app’s report layout category list has been improved to make report sections easier to view and manage. This helps users organize sales document layouts more clearly with a small usability enhancement.

Project kanban cards now show their action links in more consistent positions, making the dashboard easier to scan and use. The update adjusts how project, timesheet, and sales-timesheet links are laid out so card content no longer shifts unpredictably.

Description of the issue/feature this PR addresses:

Current behavior before PR:

Desired behavior after PR is merged:




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

Vendor bill and employee expense forms now include a dedicated space where attachment previews can be shown. This prepares the interface for a follow-up enhancement that will let users preview related documents directly from the side panel.

Task: https://www.odoo.com/web?#id=40663&view_type=form&model=project.task&action=333&active_id=131&menu_id=4720
PAD: https://pad.odoo.com/p/r.87a7ead0f01433057eaae2b3f0735dc5


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

Financial reports can now be filtered and grouped using configurable accounting move line criteria. This makes reports easier to analyze by presenting grouped results in clearer column hierarchies, including exported spreadsheets.

This implements filtering and grouping on HTML financial
reports. account.move.line filters can be configured per report in
applicable_filters_ids.

When selecting a filter the report will be filtered based on the
domain of the filter. Additionally the report will be grouped on the
first specified group in the filter.

Task: https://www.odoo.com/web#id=31198&view_type=form&model=project.task&action=333&active_id=967&menu_id=4720
Pad: https://pad.odoo.com/p/r.7a80338665fd49246f52d3e041dfc804

This fixes an issue where combining multiple search filters could produce incorrect results when some filters used shorthand logic. The change makes Odoo normalize filters before combining them, helping developers avoid subtle errors and ensuring users see the intended records.

Before this rev:

* Take 2 domains that contain at least two leaves, and at least one of
them must use the implicit `&` operator

e.g.:
```python
    d1 = [('so_line', 'in', [91]), ('amount', '<=', 0.0)]
    d2 = ['&', ('so_line', 'in', []), ('project_id', '!=', False)]
```

* Perform osv.expression.OR() between both domains

Expected result:
```python
    d3 = ['|', d1, d2]
```

Actual result (after normalization):
```
    d3 = ['&', '|', d1, d2]
```

This is because, since the `&` is implicit for the first domain, when we
OR it, we give it an explicit `|` operator, so when we pass this domain
through the normalize_domain function, d1 no longer contains an implicit
`&` operator but instead the implicit operator is the one between d1 and
d2, therefore giving us a completely wrong domain.

The `combine` function states that it only accepts normalized domains,
however neither the OR nor AND functions do, this leads to a lot of
developers putting non-normalized domains into these functions, and
there's no error checking or anything that obviously indicates that the
domain is incorrect, so we might as well normalize all domains being
passed since it's already pretty optimized.

Task-ID: 1833909