rayhpeng 376c272f52 refactor(schedule): drop the UNSET sentinel for plain None defaults ...

Every top-level update field is non-nullable as a business value, so
None can safely double as "not supplied" -- the one field whose None is
meaningful, thread_id, already travels inside ContextChange where it is
unambiguous. The UnsetType singleton solved a three-state problem this
command does not currently have; plain `| None = None` reads better.

The constraint is documented on UpdateScheduledTask: a future field
whose None is meaningful must ride inside a small change object the way
thread_id does, rather than reintroducing a second convention.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

2026-07-31 17:16:42 +08:00

..

harness

refactor(schedule): drop the UNSET sentinel for plain None defaults

2026-07-31 17:16:42 +08:00