A service review mixes record methods, small interfaces and failures that callers must handle. Read each requested result before deciding whether the function should mutate its input. The first examples use unfamiliar values from the same contracts, including zero quantities and a cleanup path after an error. You do not need a new language feature to solve them. Keep normal errors as returned values, and keep a resource open until the action using it finishes. The hidden checks revisit ordinary data so a special case for one displayed example will not pass. When you finish, describe which function owns each mutation and which caller is responsible for examining an error.