These tasks mix the object rules from the unit on fresh data. You will decide which values identify a record, derive readiness from current state, preserve originals while creating revisions, and apply exact external status mappings. Several tasks look short because the difficult part is stating the contract before choosing a data structure.
Read each boundary carefully. A capacity of zero can be valid even when a ready shipment needs positive counts. A return names both a book and a patron. Two equal labels can represent repeated events or one value, depending on the task. The checks distinguish those cases rather than rewarding a particular class layout. You can use classes where they clarify the model or small functions where no persistent state is needed.