Description of the Change

Previously, the block guard feature had inconsistent behavior in query loop blocks. When enabled on a block within a query loop, it would only protect the first instance while leaving repeated instances across other posts unprotected. Additionally, all blocks of the same type would share the same guard state globally, causing unintended cross-contamination between different block contexts.

Fixes

• ✅ Block guard now applies consistently across all repeated instances within the same query loop
• ✅ Individual blocks outside query loops maintain independent guard states
• ✅ Different block positions within the same query loop are independent (e.g., 1st RSVP vs 2nd RSVP)
• ✅ No cross-contamination between blocks in different query loops or individual blocks

Testing

1. Query Loop Test: Add a GatherPress block with block guard to a query loop template, toggle the guard on/off, verify it affects all repeated instances across posts
2. Independence Test: Add multiple blocks of the same type in different contexts (individual blocks, different query loops, different positions), verify each has independent guard state
3. Mixed Context Test: Have the same block type both inside and outside query loops, verify they don't affect each other

How to test the Change

Changelog Entry

Fixed - Bug fix

Credits

Props @mauteri

Checklist:

• I agree to follow this project's Code of Conduct.
• I have updated the documentation accordingly.
• I have added tests to cover my change.
• All new and existing tests pass.