Differential audit comparing matched code paths that should behave identically. Spawns one auditor per sibling pair (sync/async, bounded/unbounded, view consistency, bulk vs single, generated node variants, read fast vs slow) and requires a concrete witness scenario where the two paths diverge observably.
Heavyweight history-mining bug audit. Walks the caffeine module's git history chronologically (oldest to HEAD), maintains a forward-tracked issue database, and surfaces concerns introduced by past commits that were never resolved. Catches bugs that snapshot mining cannot — half-fixes invisible from current state, latent+trigger pairs across multi-commit interactions, and partial refactors. Slow (~8-14 hours) and rare-run (every several months or before a major release).
Find places where documented API contracts and the implementation diverge
Audit exception safety and failure atomicity across all throw sites
Analyze feature interaction pairs and triples for concurrent defects
Java Memory Model audit of all VarHandle/volatile field access modes
| name | audit-iteration |
| description | Analyze concurrent iteration and view consistency guarantees |
| context | fork |
| agent | auditor |
| disable-model-invocation | true |
Analyze the concurrent iteration and view behavior of the cache.
Assume at least one view operation can observe inconsistent state under concurrent modification. If your analysis yields zero findings, re-examine expired-but-present entries and dead/retired node visibility — explain specifically why no user-observable inconsistency is possible.
View operations to analyze:
For each:
For each issue: construct a concrete interleaving and state whether it violates the documented contract or is expected weakly-consistent behavior.