chore: tighten scheduling review coverage

docs/thesis/system-design-implementation.md

@@ -1433,7 +1433,9 @@ would still need to preserve the lifecycle's transaction and ownership
 contracts; changing the storage engine alone would not prove those
 properties.
 
-Scheduled deployment execution is not implemented. Nor does exposing a
+Scheduled deployment execution is implemented within the documented first
+slice. It remains bounded by the filesystem-backed, single-process store and
+the explicitly enabled local/static server composition. Nor does exposing a
 provider's callable operations imply that its interactive widgets or entire
 user experience are reproduced through the workflow API.
 
@@ -1501,11 +1503,11 @@ and data-binding model are understandable without implementation knowledge.
 
 ## Scheduling and the Surrounding Application
 
-Scheduled deployment execution is a required product direction, not an
-implemented capability. It introduces trigger identity, overlap policy,
-and recovery decisions in addition to time-expression parsing. It should
-build on the same run lifecycle rather than create a separate execution
-model. Suspending an already-running workflow until a time or event is a
+Scheduled deployment execution is implemented for the current slice. It
+introduces trigger identity, overlap policy, and recovery decisions in
+addition to time-expression parsing, and builds on the same run lifecycle
+rather than creating a separate execution model. Extending it to distributed
+workers or suspending an already-running workflow until a time or event is a
 related but distinct design question; a wait node is not specified here.
 
 The surrounding application is intended to combine assistant-backed chat