v0.1.14

What's Changed

KV Store Support (duroxide 0.1.24)

• OrchestrationContext: set_value, get_value, clear_value, clear_all_values, get_value_from_instance
• Client: get_value, wait_for_value
• Constants: MAX_KV_KEYS = 10, MAX_KV_VALUE_BYTES = 16384
• 2 KV e2e tests (request/response, cross-orchestration read)
• Updated README, user-guide, architecture docs, CHANGELOG
• Bumped duroxide to 0.1.24, duroxide-pg to 0.1.25

v0.1.13

Changes

• Bumped duroxide core to 0.1.23 (activity tag ack validation)
• Bumped duroxide-pg to 0.1.24 (tag routing + migration fixes)
• Added MAX_WORKER_TAGS and MAX_TAG_NAME_BYTES constants
• Added 5 new e2e tests for advanced tag patterns and error handling

v0.1.12

Changes

• Add Windows x86_64 wheel build
• Bump duroxide to 0.1.21 + duroxide-pg to 0.1.23

v0.1.11

Changes

• Bump duroxide to 0.1.21 and duroxide-pg to 0.1.23
• Picks up orphan queue message drop fix from duroxide 0.1.21

v0.1.10

Full Changelog: v0.1.9...v0.1.10

v0.1.9

What's New

• get_custom_status() — new method on OrchestrationContext to read the current custom status (returns Optional[str])
• Continue-as-new status inheritance — custom status is automatically preserved across CAN boundaries via initial_custom_status
• Bumped to duroxide 0.1.20 and duroxide-pg 0.1.22

Breaking Changes

• Custom status is now stored via CustomStatusUpdated history events instead of ExecutionMetadata
• This is transparent to SDK users — no code changes needed