Chore: Enhance spreadsheet state management with debouncing and schema validation

[vprashrex]

Issue: #178

• Persist full Univer workbook snapshot (cells + styles) to localStorage on every mutation, keyed by runId, so user edits in the assessment results spreadsheet survive reload, modal close, and tab close.
• Previously only UI/styling state was persisted; cell value edits were in-memory only and lost on close.

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on base/target branches other than the default branch.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: eaaa2a7d-47d2-4fa2-ae25-acef5b3a4109

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch chore/spreadsheet-state-management

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[Ayush8923]

Some small comments and question

[Ayush8923]

when the command 0 and 1 used?

[vprashrex]

0 = COMMAND (user intent), 1 = OPERATION (UI/view change, no data mutation), 2 = MUTATION (atomic state write only safe persistence point).