Closes two bugs from the tracker, both verified locally on macOS.

Fixes #3589
Fixes #3851

#3589 — clear-cache button mislabeled

The button under the Clear Cache card read scan. It starts the clear flow, so it now reads clear.

before:  [ Clear Cache ]                 ( scan )
after:   [ Clear Cache ]                 ( clear )

#3851 — scheduled pipes fired in UTC, not local time

Raw cron (0 7 * * *) was evaluated against Utc::now(), so it fired at 07:00 UTC. The "every day at Nam" UI path worked around this by pre-shifting the hour to UTC at parse time (local_hour_to_utc), which was fragile (DST, parse-time offset).

Now both paths interpret schedules in local time: parse_human_schedule encodes the local hour directly, and should_run evaluates via a new generic cron_should_fire(.., Local::now()) that preserves the catch-up / grace window.

Tests (new, deterministic)

test pipes::tests::human_schedule_encodes_local_hour_not_utc ... ok
test pipes::tests::cron_fires_relative_to_scheduled_time ... ok
test pipes::tests::human_schedule_pm_hour_is_local ... ok
test result: ok. 3 passed; 0 failed

Follow-up (NOT in this PR)

While testing I found a separate, pre-existing bug: the cron crate v0.13 treats dow=1 as Sunday, but parse_human_schedule maps monday→1, so "every monday …" schedules currently fire on Sundays. Easy to fix with tests if wanted.

🤖 Generated with Claude Code