Development-capture API

Slots 47–49 extend V1 to 400 bytes and require DevelopmentCaptureControl.

PaperDevelopmentCaptureRequestV1 contains a scope mask and mandatory 1–1200 frame lease. setDevelopmentCaptureV1 creates/renews caller demand; clearDevelopmentCaptureV1 removes it; getDevelopmentCaptureStateV1 exposes the result.

State includes mode, cache access, allowed/auto-start/owner/aggregate/active/ denied scopes, lease remaining, policy flags and revision, weapon identity, preharvest state, stored/budget bytes, clip progress, motion counts, persistent records and pending writes.

Modes are User, Observe, Harvest and Capture. Cache access is Off, ReadOnly and ReadWrite. Scopes cover passive observation, exact animation harvest, motion compilation, compiled cache read/write and live motion learning.

The API request is not administrative authority. The user's INI determines the maximum mode/cache policy and whether API activation is allowed. Always inspect denied scopes and treat policy denial as valid behavior.