humainflow-web/src/app/shared/bias-compare-dialog
Lucio Lelii 984af08f36 Show every LLM assessment as a history, and drop one that arrives too late
The report carried a single `judge`, so asking a second model overwrote the
first - there was no way to compare two opinions, and reopening a report
after a re-evaluation only ever showed the newest one. The viewer now renders
`judgements`, newest first, each collapsible: the current one open and
labelled so, the earlier ones a click away with their own verdicts, narrative
and errors. A report saved with the old single field still reads, as a
history of one.

Also: closing the dialog while an assessment was running left `judging` stuck
true forever, so reopening any report showed a disabled button stuck on
"Evaluating...". And opening a different report while one was still running
let the late answer land on it, silently replacing the report on screen with
someone else's assessment. Both dialogs now carry a token that advances
whenever what they're showing changes; a response that arrives after its
token is stale gets discarded instead of applied. The job itself is
unaffected - it keeps running server-side and its verdicts land on the report
regardless, which is what makes reopening it later still show them.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
2026-09-08 11:42:06 +02:00
..
bias-compare-dialog.css fix: correct real bugs and remove dead code found in a full-project quality review 2026-07-21 14:27:34 +02:00
bias-compare-dialog.html Say which subject a bias intervention moved, and let an LLM assess it 2026-09-08 10:50:54 +02:00
bias-compare-dialog.spec.ts feat(bias-impact): complete side-effect policy, compare, report list and canvas highlighting 2026-07-21 11:20:57 +02:00
bias-compare-dialog.ts Show every LLM assessment as a history, and drop one that arrives too late 2026-09-08 11:42:06 +02:00