A hard Go interview asks you to justify the boundary around concurrent work and the test that would expose a defect. This round combines shared-state and verification contracts you have already used. Read each request carefully before writing a function. A count of scheduled work is different from a count of completed work, and a validator that rejects every implementation is not a useful test. The six problems use original local fixtures. No network, server deployment or external module is needed. Explain the invariant behind each mutex or atomic operation, then name the empty, zero or canceled input that would disprove an incomplete answer. The checks compare behavior across both successful and failing candidates.