[QTI] Repeated Text entry answers show an inline error but don't make the question incomplete #6257

❌ This issue is not open for contribution. Visit Contributing guidelines to learn about the contributing process and how to find suitable issues.

Target branch: unstable

Observed behavior

• A Text entry question with the accepted answers Paris and Paris, or Paris and Paris, shows Duplicate answers are not allowed inline. The exercise doesn't count it as incomplete.
• Paris and paris, neither case-sensitive, count as incomplete as expected.
• _extractAnswers collects the saved answers in a Set, so validateQtiItem sees an exact repeat as one answer:

  studio/contentcuration/contentcuration/frontend/shared/views/QTIEditor/interactions/textEntry/parse.js

  Lines 109 to 114 in f65cb93

  	const values = new Set([
  	...(correctResponse ?? []).map(value => declaration.formatValue(value)),
  	...mapEntries
  	.filter(entry => entry.mappedValue >= 1)
  	.map(entry => declaration.formatValue(entry.mapKey)),
  	]);

• The incomplete count comes from validateQtiItem:

  studio/contentcuration/contentcuration/frontend/shared/utils/validation.js

  Line 466 in f65cb93

  const errors = validateQtiItem(assessmentItem.raw_data, { allowFreeResponse });

• [QTI] Numeric answer validation doesn't match xsd:double and differs between inline and headless validation #6150 fixes the same split for Numeric answers.

User-facing consequences

The exercise reports no incomplete questions while the editor shows an error on one.

Steps to reproduce

1. On unstable at f65cb93, open an exercise in the QTI editor.
2. Add a Text entry question with a prompt and the accepted answers Paris and Paris.
3. Close the editor and read the exercise's incomplete question count.

Acceptance Criteria

• For Paris + Paris, Paris + Paris and Paris + paris, validateQtiItem reports DUPLICATE_ANSWER_CONTENT on the same answers as the editor.
• The exercise's incomplete question count agrees with the inline errors for each pair above.
• Tests run each pair through both the editor's validation and validateQtiItem.

AI usage

Claude Code found this while reviewing #6150, reproduced it on unstable and on the #6150 branch with a scratch Jest harness, and drafted this issue.