Release v4.140.0

Added

• propose-property plans a rename or removal of explicitly selected command, current-event and read-model properties in one reviewable proposal. It updates proven references, preserves AutoMap relationships, and refuses removal while readers remain. Removing an example value that a then step inherits is disclosed with weakensAssertion: true; when those steps cannot be determined, the removal is refused instead. Review the retained proposal before applying it (part of #389)
• Event-property edits require newGeneration or eventNeverPersisted. The proposal reports every selected event's revision pair and mode in an ordered generations array, preserves historical generations, and discloses in-place edits. New generations require transformations before deployment to Chronicle (part of #389)