Fix idempotency key default value handling in LedgerClient

[jfrench9]

Summary

Fixes a bug where the idempotency key in LedgerClient could be left unset (e.g., None) instead of being assigned a proper default value. This ensures that all ledger requests consistently carry a valid idempotency key, preventing potential issues with duplicate request processing or API errors due to missing keys.

Key Accomplishments

• Fixed default value assignment: Updated the idempotency key handling logic in LedgerClient to ensure a proper default value is always set when one is not explicitly provided by the caller.
• Updated tests: Adjusted the corresponding test in test_ledger_client.py to validate the corrected default behavior, ensuring the fix is properly covered.

Breaking Changes

None. This is a backward-compatible bugfix. Callers that were already providing an explicit idempotency key will see no change in behavior. Callers relying on the default will now get the correct, expected default value instead of an unset/None value.

Testing Notes

• Existing unit tests have been updated to reflect and verify the corrected default idempotency key behavior.
• Verify that ledger operations without an explicitly provided idempotency key now produce a valid default key in outgoing requests.
• Recommended to test end-to-end against the ledger service to confirm that requests with default idempotency keys are accepted and deduplicated as expected.

Infrastructure Considerations

• No infrastructure or deployment changes required.
• This fix may resolve intermittent failures or unexpected behavior in downstream services that depend on a valid idempotency key being present in ledger requests.

---

🤖 Generated with Claude Code

Branch Info:

• Source: bugfix/idempotency-key-unset
• Target: main
• Type: bugfix

Co-Authored-By: Claude noreply@anthropic.com