history

Explicit application autosave

id: LK-20260716-explicit-autosave
date: 2026-07-16
sequence: 68
type: feat
compatibility: compatible
component: `labkit.ui` | `6.0.2 -> 6.0.3`
component: `labkit_VideoMarker_app` | `1.3.0 -> 1.4.0`
scope: Runtime V2 project recovery
scope: Video Marker session workflow

Context

Runtime V2 already wrote debounced recovery generations after durable edits, but an app could only expose the named-project save operation. Video Marker users who wanted to force the current recovery point had no direct control and using Save State introduced a destination prompt for an unnamed project.

Decision and rationale

Expose the existing framework-owned recovery writer as an injected action service. The service accepts the current action state, writes the same bounded recovery generations as the timer, and deliberately leaves the named project path and dirty status unchanged. Video Marker exposes that operation as Save autosave in its Session panel.

Changes

• Factored the atomic recovery-generation writer out of the timer scheduler.
• Added services.project.saveAutosave(state) for an immediate, pathless recovery write.
• Added the Video Marker Save autosave button and visible workflow log acknowledgement.
• Kept ordinary Save State as the separate operation for choosing or updating a named project file.

User and data impact

Clicking Save autosave does not open a native file dialog. It updates the current app/document recovery file and retains one previous generation. It does not make the recovery file the active named project and does not suppress later unsaved-close protection.

Compatibility and migration

Existing projects, recovery files, and automatic autosave behavior remain compatible. Apps that do not expose the new service behave exactly as before.

Validation

The focused Video Marker GUI workflow verifies that the button immediately creates a recovery file while the runtime document path remains empty. The existing Runtime V2 project test continues to cover debouncing, bounded generations, and recovery loading.

Evidence

• Runtime and lifecycle documents the injected recovery operation and its distinction from named saves.
• Video Marker documents the Session button and no-dialog behavior.

Known limitations and follow-up

An autosave is a recovery aid, not a user-named archival project. Users still use Save State when they need a deliberate project filename or location.