fix: handle empty dict resume

[radu-mocanu]

• handle empty dict resume

[Copilot]

Pull request overview

This PR fixes a bug in the resumable runtime where passing an empty dictionary ({}) for the input parameter during resume was incorrectly treated as valid input instead of triggering data restoration from storage. The fix adds a truthiness check (bool(input)) to distinguish between explicitly provided input and empty dictionaries that should be ignored.

Key Changes:

• Updated _restore_resume_input() logic to check both input is not None and bool(input) to properly handle empty dict scenarios
• Added comprehensive test coverage with three new test cases validating the fix for both execute() and stream() methods
• Version bumped from 0.2.0 to 0.2.1

Reviewed changes

Copilot reviewed 3 out of 4 changed files in this pull request and generated 1 comment.

File	Description
src/uipath/runtime/resumable/runtime.py	Fixed the condition in _restore_resume_input() to treat empty dicts as missing input, triggering fetch from storage
tests/test_resumable_runtime.py	Added three test cases with mock implementations to verify empty dict fetches from storage and non-empty dict uses provided input
pyproject.toml	Version bump from 0.2.0 to 0.2.1
uv.lock	Version bump from 0.2.0 to 0.2.1 in lock file

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[Copilot]

Missing test case for stream() with non-empty dict input when resuming. While test coverage exists for execute() with non-empty dict (line 94-109), there's no corresponding test for stream() to ensure it behaves consistently. Consider adding a test like test_stream_restore_resume_input_with_non_empty_dict_uses_provided_input() to verify that stream mode also uses the provided input directly instead of fetching from storage when a non-empty dict is provided.