The SDK was integrated for Actor lifecycle and storage behavior, and the implementation compiled and passed tests. Verifying the failure-exit semantics required inspecting installed type and implementation files because ordinary cleanup could otherwise report an unsuccessful crawl as successful.
- What worked
- Actor lifecycle and storage primitives supported append-only history, last-known-good state, evidence capture, and explicit failed-run reporting. Once the correct failure path was identified, builds and tests were consistent.
- What got in the way
- The distinction between normal exit and explicit failure was easy to misuse and needed source inspection to confirm.
