Change Details

**Steps to replicate the issue** (include links if applicable): * Create a list of articles and add the `<page-collection />` marker to it * Notice that it gets picked up by the recommendation api and displayed on the CX unified dashboard * Remove the `<page-collection />` marker from the article list **What happens?**: * It remains displayed as an available collection but contains no pages and give no recommendations when selected **What should have happened instead?**: * It should be removed from the list of page collections after the next update cycle **Software version** (on `Special:Version` page; skip for WMF-hosted wikis like Wikipedia): **Other information** (browser name/version, screenshots, etc.):

**Steps to replicate the issue** (include links if applicable): * Create a list of articles and add the `<page-collection />` marker to it * Notice that it gets picked up by the recommendation api and displayed on the CX unified dashboard * Remove the `<page-collection />` marker from the article list **What happens?**: * It remains displayed as an available collection but contains no pages and give no recommendations when selected **What should have happened instead?**: * It should be removed from the list of page collections after the next update cycle **Software version** (on `Special:Version` page; skip for WMF-hosted wikis like Wikipedia): **Other information** (browser name/version, screenshots, etc.): --- **Derived Requirement** Ensure that when the `<page-collection />` marker is removed from an article list, the **Recommendation API** automatically removes the corresponding page collection from the **CX unified dashboard** during the next update cycle, preventing display of empty or invalid collections. **Test Case 1: Verify page collection removal after marker deletion** 1. On the test wiki, create a new list of articles (e.g., “User:Test/PageCollection”). 2. Add the `<page-collection />` marker to the list and save. 3. Open the **CX unified dashboard** and confirm the new page collection appears in the available collections list. 4. Edit the same article list and remove the `<page-collection />` marker. 5. Wait for or trigger the next **Recommendation API update cycle** (if manual trigger available). 6. Refresh the CX unified dashboard. 7. ✅❌❓⬜ **AC1:** Confirm that the page collection is **no longer displayed** on the dashboard after the update cycle.

**Steps to replicate the issue** (include links if applicable): * Create a list of articles and add the `<page-collection />` marker to it * Notice that it gets picked up by the recommendation api and displayed on the CX unified dashboard * Remove the `<page-collection />` marker from the article list **What happens?**: * It remains displayed as an available collection but contains no pages and give no recommendations when selected **What should have happened instead?**: * It should be removed from the list of page collections after the next update cycle **Software version** (on `Special:Version` page; skip for WMF-hosted wikis like Wikipedia): **Other information** (browser name/version, screenshots, etc.): --- **Derived Requirement** Ensure that when the `<page-collection />` marker is removed from an article list, the **Recommendation API** automatically removes the corresponding page collection from the **CX unified dashboard** during the next update cycle, preventing display of empty or invalid collections. **Test Case 1: Verify page collection removal after marker deletion** 1. On the test wiki, create a new list of articles (e.g., “User:Test/PageCollection”). 2. Add the `<page-collection />` marker to the list and save. 3. Open the **CX unified dashboard** and confirm the new page collection appears in the available collections list. 4. Edit the same article list and remove the `<page-collection />` marker. 5. Wait for or trigger the next **Recommendation API update cycle** (if manual trigger available). 6. Refresh the CX unified dashboard. 7. ✅❌❓⬜ **AC1:** Confirm that the page collection is **no longer displayed** on the dashboard after the update cycle.