Resume and Observe Progress

Practical guide: resume from a specific Objective through scene handoff

Configure the source Chapter with Restore Checkpoint, assign the target scene, choose Next Chapter, and choose Checkpoint Objective. On completion, the Manager writes and flushes a versioned one-use handoff before loading. The destination Manager validates and consumes it before considering Editor testing or Default Chapter.

Earlier Completed and Skipped records remain terminal. The requested row is a starting request within hydrated progress, not permission to replay earlier lifecycle events or overwrite a completed row.

Practical guide: expose current progress to UI

1. 1
   After OnManagerReady, read CurrentChapterId, CurrentChapterState, CurrentObjectiveId, and CurrentObjectiveState.
2. 2
   Render an empty Objective as a valid terminal/no-selection state rather than a null error.
3. 3
   Refresh after project commands and the lifecycle notifications relevant to the UI.
4. 4
   For exact accepted Objective indices, subscribe to the current Chapter's ObjectiveCompleted event and rebind after Chapter selection.
5. 5
   Unsubscribe before scene unload or receiver disable.

Practical guide: record transitions without changing them

A telemetry observer should read public state and listen to notifications, never call selection or completion from its logging callbacks. Record the Chapter/Objective ID before and after accepted project commands if both sides are needed. OnBeforeSceneLoad can record destination intent only if the project already knows it; the parameterless event itself does not expose scene or handoff IDs.

Do not infer historical event counts from hydrated state. Persistence restores a snapshot without replay. If analytics needs lifetime history, store that history in the project's telemetry backend.