prakash888kp

Great catch — this is exactly the right distinction. The default Action / MockLLM path is fixture-bound: a green gate proves the bundled corpus + reference chunker still pass policy, not that your app chunk-size change would fail Retrieve. I shipped that clarification in SentinelRAG 0.2.2: Docs/Action now state fixture vs app binding explicitly evidence.json stamps app_revision + chunker_config sentinelrag-gate app-bound-check runs the unmodified chunker, then a known harmful chunk-size change, remaps relevance by gold text so cases stay the same, and requires Retrieve to regress pip install -U sentinelrag uv run sentinelrag-gate app-bound-check That establishes what the green MockLLM path actually protects before extending claims to prompt/model changes. Thanks for pushing on the real failure mode.