docs: add Lua script preloading documentation for kvrocks

[github-actions]

Documentation Update

This PR adds comprehensive documentation for the Lua script preloading feature introduced in PR #510 (fix/kvrocks-noscript-and-install-bundle).

Changes

1. docs/07-storage-kvrocks.md - Added "Lua scripts" section

• Explains the two critical Lua scripts: claimMoveScript and tokenBucketScript
• Documents script preloading via PreloadScripts() at startup
• Explains kvrocks compatibility: different NOSCRIPT error format
• Describes automatic EVAL fallback for transparent error recovery

2. docs/10-operations.md - Added "Startup" section

• Documents the 4-step API initialization process
• Emphasizes Lua script preloading as a critical startup step
• Explains why preloading is necessary for kvrocks
• Clarifies the fallback mechanism and error recovery

3. docs/28-troubleshooting.md - Added 2 new troubleshooting sections

• Section 1: "API fails to start with 'preload repository scripts' error"
  • Symptoms, causes, and resolution steps
  • Guidance on KVRocks memory and configuration
• Section 2: "Tasks fail with 'NOSCRIPT' errors"
  • Explains automatic fallback behavior
  • Recovery steps if issues persist
  • Memory management best practices

All subsequent troubleshooting sections have been renumbered accordingly (now 3-12).

Rationale

The Lua script preloading feature is critical for kvrocks compatibility. codeQ uses Lua scripts for atomic operations in hot paths (task claiming, rate limiting). kvrocks returns NOSCRIPT errors in a different format than standard Redis, so preloading ensures scripts are cached at startup. The automatic fallback to EVAL provides transparent error recovery if scripts are evicted from memory.

This documentation:

• Helps operators understand startup errors
• Guides troubleshooting of NOSCRIPT issues
• Explains the kvrocks compatibility layer
• Provides best practices for memory management

Quality Assurance

• ✅ Documentation follows Diátaxis (Explanation + Reference)
• ✅ Consistent with existing documentation style
• ✅ Progressive disclosure: high-level first, details second
• ✅ All cross-references verified (e.g., file names, function names)
• ✅ Troubleshooting sections include causes, symptoms, and resolution steps

AI generated by Update Docs