Fine‑tuning automatic retry thresholds for DOM elements that require state changes beyond visibility

The goal is to understand how Cypress determines when a DOM element is truly actionable and whether the default four‑second retry window adequately covers cases where the element becomes clickable only after asynchronous UI updates such as class modifications or attribute changes.

Constraints include preserving the built‑in automatic waiting behavior while allowing per‑command adjustment of retry count or timeout, and uncertainty remains about whether Cypress provides a supported mechanism to extend waiting criteria beyond basic visibility without disabling global waiting.

Specific questions: How can the retry count or timeout be overridden for an individual command while retaining automatic waiting? Is there a supported way to extend waiting to include waiting for particular attribute or class changes? Can the default four‑second timeout be calibrated per command type without affecting other commands?