docs: scope consensus determinism guarantee

Author: vineethsai7

README.md

@@ -197,9 +197,9 @@ Consensus mode keeps a finding only when it appears in more than half of the
 configured runs. When those votes disagree on severity, the highest observed
 severity wins, independent of response order. Failed runs and successful runs
 that omit the finding cast no vote but remain in the denominator. This makes
-aggregation stable for majority-agreed findings; it does not make an individual
-LLM sample deterministic, so single-run output and non-majority findings can
-still vary between scans.
+severity selection stable for majority-agreed findings. It does not make an
+individual LLM sample deterministic, and descriptive fields from equal-severity
+votes, single-run output, and non-majority findings can still vary between scans.
 
 **LLM provider note:** `--llm-provider` currently accepts `anthropic` or `openai`.
 For Bedrock, Vertex, Azure, Gemini, and other LiteLLM backends, set provider-specific model strings and environment variables (see [LLM Analyzer docs](docs/architecture/analyzers/llm-analyzer.md)).

docs/architecture/analyzers/llm-analyzer.md

@@ -215,8 +215,9 @@ remain in the configured-run denominator. Retained findings include agreement,
 severity-vote, successful-run, and failed-run metadata so callers can assess
 the evidence behind the result.
 
-Consensus makes aggregation deterministic once a finding reaches majority. It
-does not make the underlying model deterministic: a single run can still vary,
+Consensus makes severity selection deterministic once a finding reaches
+majority. It does not make the underlying model deterministic: descriptive
+fields from equal-severity votes can still vary, a single run can still vary,
 and a finding near the majority boundary can still appear or disappear between
 separate scans.