Schedule editing
A runnable bounded event-edit recipe using the same revision and idempotency contract.
Local memory example
Edit one supplied event
Schedule status
Extend the supplied event, then review the exact change.
The fixture uses UTC so the displayed civil time maps to one unambiguous offset. This example checks the revision and event bounds in memory; calendar ownership, provider authorization, recurrence, and synchronization remain host responsibilities.
What this example proves
It exercises the kit’s local transition and validation contract with supplied fixture data. The manifest lists the production services and authorization checks that stay outside this browser example.
- Initial state
- editing
- Terminal state
- confirmed
- Kit version
- 0.1.0