Diagnostics and projections

中文

Use these APIs to inspect the deployment, consume events, and investigate work availability or cancellation:

Capability	Entry point
Imported package, source and storage compatibility	dispatcher_sdk.runtime_identity(...)
Persist-before-ACK event consumption	ProjectionConsumer(...).drain(...)
Why a Run has no currently claimable work	sdk.inspect_work_availability(run_id)
Cancellation phases, cleanup and recovery identities	sdk.inspect_cancellation(run_id)
Persisted activity and event pages for a managed task	task.observe() and task.events()

Projection callbacks must commit idempotent destination writes before returning persisted or already_present. A failed page replays, poison events are not skipped, and a fixed high-water target does not guarantee an ACK window during continuous concurrent updates.

Diagnostic queries do not synchronize or mutate the Run. They distinguish missing evidence from confirmed facts and report cross-store snapshot limitations. Work diagnostics bound their Effect scan; an exceeded budget yields an unknown count, not zero.

Execution observations follow the same read-only rule. They report recorded facts without claiming work, renewing a lease or cleaning up a process. See execution activity and supervision for deadlines, child calls and optional stall notifications.

Runtime cancellation evidence can be persisted with explicit cancellation_journal_path and source_id options. Receipts use a separate SQLite database with schema version 1. Core stores are not automatically migrated. Local process cleanup requires the matching execution generation's Linux subreaper or Windows Job proof. Even without that optional cancellation journal, inspect_cancellation can read a matching process_cleanup note from the settlement journal bound to the Kernel store. This works after Runtime restart and without an attached Runtime. The report confirms it only when the Kernel binding, execution ID, attempt and fence match and the note says confirmed from runtime_supervisor_reaped; its note ID and source remain separate from cancellation receipt IDs. Missing, malformed or foreign notes stay unknown. Confirmed local process cleanup does not resolve a pending sandbox-disposal obligation. Stopping a Task does not finish its Run.

See the API guide, journal design, projection example and diagnostic example.