v4.2.0

Features

• Tilt support for wrapped covers without native tilt (#85): the Inline and Sequential tilt modes are now available when wrapping an existing cover, even if that cover only exposes open/close/stop. These modes drive the wrapped cover's normal open/close commands, so they work on any cover — previously the tilt options were hidden unless the wrapped cover reported native tilt support. The Separate tilt motor mode still requires native tilt support (it delegates the tilt commands to the wrapped entity), so it remains hidden until the selected cover advertises it.
• Ignore reported position (wrapped covers): a new option to track position purely by time and ignore the current_position the wrapped cover reports. Enable it for covers that report an unreliable position (the fully-closed endpoint is still trusted).
• Forward set-position to wrapped covers with native position support (#93): when a wrapped cover supports set_cover_position, the integration now sends the set-position command straight to it instead of approximating it with timed open/close/stop — so the cover stops at the requested position even when the underlying device has no stop service. The time-based tracker still animates during the move so the position updates live for covers that only report their position once they settle. Stop on such a cover is implemented by setting the underlying cover to the integration's calculated position. A new Force time-based positioning option keeps the old timed behaviour for covers whose native set-position is unreliable.
• Detect unavailable relays / targets (#89): the cover now reports as unavailable whenever any of its underlying target entities (the switches, buttons, scripts, or wrapped cover that drive it) is unavailable — for example an MQTT relay going offline. Commands that would start movement in a direction whose target is unavailable are rejected instead of silently running the time-based simulation and drifting the reported position. Stopping is always allowed, so a cover can still be halted even while a target is offline.

Fixes

• A wrapped cover configured with Separate tilt motor but whose underlying entity doesn't support tilt (e.g. a stored or hand-edited config, or a cover that dropped tilt support) no longer fires *_cover_tilt services at it; the unsupported command is skipped and logged instead.
• Selecting the separate-tilt-motor mode is no longer reset when the chosen wrapped cover is merely unavailable — the tilt config is only cleared once the cover is confirmed available without tilt support.