A code review needs tests that distinguish correct implementations from plausible mistakes. Build the validator named in each request and keep its successful candidate passing while adding the missing boundary. The fresh examples include empty inputs, exact comparisons and responses with a correct body but a wrong status. You have already learned every operation used here. A test that rejects everything is as unhelpful as one that accepts everything. For properties, compare the relationship the contract names instead of one convenient sample. These local validators teach test bodies; a normal Go repository would place them inside Test or Fuzz functions and run the corresponding go test command outside this browser workspace.