[BenCodez]

Summary

Tighten UserDataCache write scheduling and cache ownership without changing its public API.

• close the race where a change queued while a scheduled flush is finishing could remain unscheduled
• automatically schedule another flush when work arrived during the previous flush
• keep scheduled-state transitions synchronized and recover cleanly if the executor rejects scheduling
• drain queued changes into a stable batch before writing user storage
• make cache inspection/update helpers null-safe around dump/cleanup
• defensively copy replacement cache maps instead of retaining caller-owned mutable maps
• route cache comparison failures through AdvancedCore debug logging instead of raw stack traces

Tests

• verifies a change queued during an active scheduled flush causes a follow-up flush to be scheduled
• verifies updateCache(...) does not retain the caller's mutable map

This PR is focused on user cache/storage write correctness; it does not change storage configuration or public user-data keys.

[chatgpt-codex-connector]

You have reached your Codex usage limits for security reviews. Please try again later.

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 3ddabdb67a

ℹ️ About Codex in GitHub

Your team has set up Codex to 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 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[chatgpt-codex-connector]

You have reached your Codex usage limits for security reviews. Please try again later.

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: fe9d4ddad6

ℹ️ About Codex in GitHub

Your team has set up Codex to 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 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[chatgpt-codex-connector]

You have reached your Codex usage limits for security reviews. Please try again later.