Problem

The card cannot show when the configured Schedule & Timing window opens and closes, because the integration never publishes those clock times. The start/end sensors are sun azimuth sensors, not the schedule window. Today the only schedule signal the card can read is the in_time_window boolean on the decision-trace attributes.

This came out of card issue jrhubott/adaptive-cover-pro-card#128: a user's cover moved at 18:00:30 with an 18:00:00 schedule end, and no card surface could explain it. The card side is shipping a boolean "Outside schedule" indicator (driven by in_time_window) now — but the richer asks (inline window times on the tile, a schedule-window section, a grayed-out off-schedule zone / vertical bars on the sun chart, sky-compass schedule-start/end tooltips) all need the actual clock times.

Ask

Expose the configured (resolved) schedule window start/end times as data the card can read — ideally as attributes on an existing diagnostic sensor (e.g. control_status or the decision-trace sensor), so no new entity discovery is required:

• schedule_start / schedule_end — the resolved window bounds for today, as ISO timestamps or HH:MM[:SS].
• These should reflect whatever TimeWindowManager actually used (static config value or entity-driven value), so the card displays the same window the integration enforced.

If attributes on an existing sensor aren't a good fit, dedicated schedule_start_time / schedule_end_time timestamp sensors (with stable translation_keys) work too — the card would add the roles to its TRANSLATION_KEY_ROLES map.

Card-side follow-up (once this ships)

The card will render: chart off-schedule gray zone + window bars (the sun chart already has a time→x mapping and now-line), sky-compass hover tooltips, a main-card schedule section, and inline window times on the tile.

Refs jrhubott/adaptive-cover-pro-card#128