State Persistence After Reuse

Shared runtime or framework state gets reused across executions (processes, JVM runs, or test boundaries), so queued or cached work appears “flushed/cleared” while pending items or declarations still leak across runs, causing missing updates and misleading success signals.