Edits carry the version read; lifecycle actions are guarded by state

Context

The present lifecycle exception is an observed mismatch with the standard, not approval of that exception.

Decision

Require the read version for configuration edits and reject stale replacements. Existing integration lifecycle actions instead lock and check current standing without receiving a client-held version.

Alternatives Considered

Add client-held versions to every lifecycle action. This would align with the record-write standard but requires changes to current routes and callers.

Allow edits without version checks. An administrator could overwrite intervening configuration changes without learning about them.

Consequences

A stale edit requires reloading the current record.

State guards serialize lifecycle mutations but do not tell the second administrator about every intervening change.

Workflow replacement operations carry a complete document and its read version.