Prefer staging for a conflict test. Take an encrypted backup, record the active package pair and disable only one suspected extension at a time. Keep Free active while testing Pro, preserve the Aurelia child theme, and do not remove payment, language or iCal data to simplify the result. Reproduce with synthetic rooms, guests and dates, then restore the original state before moving to the next test.
Use a small matrix: Free alone, Free plus Pro with the entitlement available, Aurelia with and without Pro, and the suspected third-party extension isolated. Run a read-only page check first, then Search, Room Detail, Book Now, the Payment or Pay at hotel step, Confirmation, Admin Booking and (when configured) iCal health. Compare status, totals, inventory, language route and logs. A theme conflict must not change server availability, tax, payment ledger or external blocks.
Escalate when the failure is deterministic on a supported clean pair or when data integrity is uncertain. Include versions, PHP/WordPress, schema, route, locale, viewport, exact steps, expected/actual result, timestamps and a redacted evidence bundle. Replace booking codes, emails, signatures, API keys, license values, signed URLs, calendar tokens and raw feed bodies with stable placeholders. Never attach a production database dump or ask support to bypass nonce, TLS, capability or digest checks.