4.4.0

Spec revision 20, on the developer's ok of 2026-10-13. No record shape changes; earlier logs still read, and a request that fits is built as before, so earlier measurements and calibration are unchanged.

• A Consequential decision on a large commitment can be measured (issue #69). The measurement state carries the text of every requirement in the commitment, so a commitment with many requirements filled the request by itself: every sudus measure on it was unavailable oversize, the agent could cut nothing, and every Consequential decision went to the developer. A request over a size limit is now built once more with the text of only the requirements the draft's concerns name; the others keep their identifier and text digest. When that request fits, it is sent, and the measurement's reason ends with "sent with requirement text for REQ only (the full request: ...)", so sudus decide --consequential can follow. When it still does not fit, the draft is unavailable oversize, the reason ends with "with requirement text for REQ only", and sudus escalate --consequential takes it to the developer as before.