[Shubochandrosarker]

Summary

Closes the remaining G2A-CRIT-001 cancel gaps identified against public Memberistic v2.2.0: the dedicated POST .../cancel endpoint and wp-admin cancel already called Stripe_Service::cancel_remote_first(), but two paths still flipped local status first (or skipped Stripe entirely).

Changes

1. Memberships_Controller::update_item (PATCH /memberships/{id})
   When status changes to cancelled, call cancel_remote_first() before change_status(). On Stripe failure return 502 memberistic_stripe_cancel_failed unless force=true (same behaviour/message as the dedicated cancel endpoint). Registers optional force boolean arg.

2. WooCommerce_Bridge::sync_refunded_order
   Before dispatch_order(..., 'refunded'), resolve _memberistic_membership_id and call cancel_remote_first(). Local cancel via the payment-integrity gate always proceeds afterward (Woo refund already happened). Needed because the gate fires memberistic_membership_status_changed with the inbound-event flag set, which skips the post-hoc Stripe listener.

3. CHANGELOG — Unreleased / Fixed entry. No version bump or tag.

Tests

• find . -name '*.php' ... | xargs php -l — exit 0 (PHP 8.4)
• php tests/licensing.php — 8 checks passed
• No dedicated cancel unit suite in this repo (only tests/licensing.php + CI PHP lint)

Risks / notes

• Woo path ignores Stripe WP_Error on purpose (documented); retries still queued by cancel_remote_first.
• PATCH without force will refuse cancel if Stripe fails — callers that previously used PATCH to cancel must handle 502 or use /cancel / force=true.