Enforce register transitions and immutable history in the database

Context

Other modules and background work can write delivery records whose histories must remain dependable.

Decision

Enforce obligation lifecycle transitions in the database and restrict application history writers to append operations.

Alternatives Considered

Validate obligation moves only in services. Service-only validation cannot prevent other database writers from making invalid obligation moves.

Add database transition guards to every warehouse lifecycle. Equivalent warehouse transition triggers have not been implemented.

Consequences

Warehouse state checks remain weaker than obligation guards. Database ownership and administrative access remain distinct from application-role grants.