🐛 Bug - Saving rule order fails with category index update error

[ssw-yakshaver]

Requested by: @PennyWalker via YakShaver.ai 🦬
cc: @kulesy, @0xharkirat, @PennyWalker, @Marxoz, @PothieuG, @Freego1783

Hi Team!

  🟥  Watch the video (1 min 58 sec)

  Url from screen share: https://ssw.com.au/rules/admin/index.html#/collections/edit/category/marketing-and-video/rules-to-better-event-management

Pain

When reordering rules in the Rules (Content) management screen and attempting to save, the save operation intermittently fails with a "category index update failure" error. The error message indicates that a related GitHub branch cannot be found, even though the branch does exist. This prevents users from changing and saving the order of rules.

Acceptance Criteria

1. Users can reorder rules in Rules (Content) management without encountering a save error.
2. Saving reordered rules completes successfully without a "category index update failure" message.
3. The system correctly references the existing GitHub branch when saving rule order changes.
4. If a save failure does occur, the error message is accurate, actionable, and clearly explains the root cause.
5. No regression occurs when switching between branches (e.g., feature branch and main branch).

Reproduce Steps

1. Navigate to Rules (Content) management.
2. Create a new rule or use existing rules in a category.
3. Change the order of a rule by moving it within the list.
4. Click Save.
5. Observe that after a short delay, an error appears stating a category index update failure and that a GitHub branch cannot be found, despite the branch existing.

Screenshot

Figure: Reordering rules causes a category index update failure on save