fix: enable --ensure-no-loss false flag to disable functionality

[Liver-23]

Summary

This PR completes the fix for the --ensure-no-loss flag, allowing users to properly disable the functionality by passing --ensure-no-loss false.

Changes

• Updated option definition in both tools/kysor/src/commands/start.ts and common/protocol/src/index.ts:

  • Changed from --ensure-no-loss (boolean flag) to --ensure-no-loss [value] (option that accepts a value)
  • Changed default from boolean true to string "true" for proper parsing
  • Updated description to indicate users can set to false to disable

• Fixed kysor.ts logic (tools/kysor/src/kysor.ts):

  • Replaced incomplete if/else logic with proper value handling
  • Added type normalization to handle both string and boolean types
  • Properly handles the false case by passing --ensure-no-loss false
  • For true or default case, just passes the flag (defaults to true)

• Updated version numbers in package.json files

Expected Behavior

• --ensure-no-loss or no flag → defaults to true (enabled) ✅
• --ensure-no-loss false → disables the functionality ✅
• --ensure-no-loss true → explicitly enables (same as default) ✅

Testing

After applying these changes, verify:

1. ./kysor start --valaccount <name> --ensure-no-loss false should disable ensureNoLoss
2. ./kysor start --valaccount <name> --ensure-no-loss should enable ensureNoLoss (default)
3. ./kysor start --valaccount <name> (without flag) should enable ensureNoLoss (default)

Related

This completes the fix that was partially addressed in PR #185, which fixed parsing but didn't allow users to pass --ensure-no-loss false to disable the functionality.