fix(wdk): prevent resetting cron job lastRun timestamps to 0 in storage

[Ysh204]

Description

This PR resolves a critical bug in the WDK Cron scheduler utility (packages/wallet/wdk/src/sequence/cron.ts) that caused persisted cron job lastRun timestamps to be overwritten with 0 in localStorage when WDK reloaded or initialized.

The Bug

1. When WDK is instantiated, registered jobs are initialized with lastRun = 0.
2. The background checking loop runJobs() loads the persisted last run timestamps from localStorage asynchronously.
3. If the elapsed time since the persisted lastRun is less than the job's interval, the job's handler is not executed.
4. Because the handler did not execute, the in-memory job.lastRun remained at 0.
5. At the end of runJobs(), syncWithStorage() serialized the in-memory this.jobs (where the job's lastRun was 0) and wrote it back to localStorage, erasing the actual last run timestamp.
6. Consequently, on the very next tick, the scheduler loaded lastRun: 0 and triggered the job prematurely.

In practice, this meant every background cron job (such as checking queued recovery payloads) would run on every single app restart/tab refresh plus exactly 1 tick later, completely ignoring the configured execution interval.

The Fix

Update runJobs() in cron.ts to sync the in-memory job.lastRun state with the loaded lastRun value from storage before evaluating the elapsed time. This ensures that non-triggered jobs preserve their actual persisted timestamps when writing back to storage.

Testing & Verification

• Added a comprehensive unit test suite in packages/wallet/wdk/test/cron.test.ts to verify last run persistence, check skip behavior, and ensure correct interval triggers.
• Verified the tests pass successfully (4ms execution time).
• Verified the tests fail on the original buggy implementation.

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: eee01b0f4c

ℹ️ About Codex in GitHub

Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".

[chatgpt-codex-connector]

Preserve legacy Latin-1 payloads that are valid UTF-8

When a redirect response was produced by the previous Latin-1 btoa(JSON.stringify(...)) path, this line now treats it as UTF-8 whenever the raw bytes are well-formed UTF-8. For example, a legacy payload containing the literal text é decodes to é, so getRedirectResponse() silently returns different data instead of honoring the legacy fallback. This affects existing wallet redirects with those byte patterns; add an explicit encoding/version signal or otherwise disambiguate before preferring UTF-8.

Useful? React with 👍 / 👎.