[BUG] Windshift Tree View: Missing Work Items When Pagination Is Triggered #400

Description

When a workspace contains a sufficient number of Work Items to trigger backend pagination, the Tree View does not display all items. Some parent Work Items appear without their children, and items visible when filtering (e.g. Hide Completed) are absent from the All Items view.

The issue does not appear to be related to custom fields. It also reproduces on a workspace where all items were manually entered, confirming it is a structural issue tied to pagination.

Steps to Reproduce

1. Create or use a workspace containing enough Work Items to exceed the pagination threshold (≥ ~50 items).
2. Open the Tree view in All Items mode.
3. Observe that some parents do not display an expander arrow even though they have children.
4. Apply a filter (e.g. Hide Completed) to reduce the dataset below the pagination threshold.
5. Observe that the previously missing Work Items reappear.

Expected Behavior

The Tree View displays the full hierarchy (parents + children) regardless of the total number of Work Items in the workspace.

Actual Behavior

• Some parents are rendered as flat nodes (no expander arrow) because their children have not yet been loaded.
• Infinite scroll loads subsequent pages but does not retroactively inject children into already-rendered parent rows.
• Items are invisible in All Items but visible when a filter reduces the dataset below the pagination threshold.

Root Cause (Hypothesis)

⚠️ This hypothesis comes from an exploratory analysis (AI). To be confirmed with the Windshift development team.

Desynchronization between the API pagination logic and the tree construction in the UI component:

1. The API returns items by page (e.g. 50 per page), ordered by creation/modification date.
2. A parent may land on Page 1 while its children are on Page 2 or 3.
3. The Tree component parses Page 1, finds no children in the payload, and hides the expander arrow.
4. The reactive state engine does not update the state of already-rendered parents when subsequent pages are loaded.

Workarounds (pending a fix)