A log rotation policy is correct (Resource Exhaustion)

The rotated files are gone from the directory and still present on disk. The functional path still exists, but one hidden dependency still assumes the old boundary between shared and isolated resources. A hidden dependency still assumes the old shared-service boundary even though the visible workflow stayed intact. The visible workflow still functions, but one dependency continues to assume the previous shared ownership contract. The happy path still looks intact, but one dependency kept assuming the softer boundary model that existed before the hardening work. The visible path still looks normal, but one supporting dependency kept relying on the softer isolation model from before the reset.