cqs-auditor

Use when functions both mutate state and return values, when calling a "getter" has hidden side effects, when it's unclear whether a call is safe to retry or cache, or when tests must verify both a return value and a state change. Trigger on "is it safe to call this twice?", "why does reading this value change the system?", or when designing read/write boundaries. NOT for stack/queue pop(), iterator next(), or…