From d2550c6426844b5627e760b062758e7499b4447b Mon Sep 17 00:00:00 2001
From: Claude <noreply@anthropic.com>
Date: Sat, 7 Feb 2026 20:39:10 +0000
Subject: [PATCH 1/2] Use map_response instead of match_correct in text entry
 exemplar

The match operator is always case-sensitive for strings, so match_correct
would reject correct answers with different capitalization. QTI 3.0 mappings
are case-insensitive by default, making map_response the better choice for
text entry interactions.

https://claude.ai/code/session_01K1EbPpn6oCv4q2ipHGGvX1
---
 .../src/example-items/standard-text-entry.ts  | 25 +++++++++++++------
 1 file changed, 18 insertions(+), 7 deletions(-)

diff --git a/packages/cutie-example/src/example-items/standard-text-entry.ts b/packages/cutie-example/src/example-items/standard-text-entry.ts
index b7143a8..8abd8eb 100644
--- a/packages/cutie-example/src/example-items/standard-text-entry.ts
+++ b/packages/cutie-example/src/example-items/standard-text-entry.ts
@@ -10,10 +10,20 @@ https://purl.imsglobal.org/spec/qti/v3p0/schema/xsd/imsqti_asiv3p0p1_v1p0.xsd"
 identifier="text-entry-feedback" title="Text Entry - With Feedback"
 adaptive="false" time-dependent="false" xml:lang="en">
 
+  <!--
+    For text entry interactions, prefer using qti-mapping with qti-map-response over
+    match_correct. The match operator is always case-sensitive for strings, so a learner
+    typing "Correct" instead of "correct" would be marked wrong. Mappings in QTI 3.0 are
+    case-insensitive by default, which is more forgiving and appropriate for text responses.
+    Individual map entries can opt into case-sensitive matching with case-sensitive="true".
+  -->
   <qti-response-declaration identifier="RESPONSE" cardinality="single" base-type="string">
     <qti-correct-response>
       <qti-value>correct</qti-value>
     </qti-correct-response>
+    <qti-mapping default-value="0">
+      <qti-map-entry map-key="correct" mapped-value="1"/>
+    </qti-mapping>
   </qti-response-declaration>
 
   <qti-outcome-declaration identifier="SCORE" cardinality="single" base-type="float">
@@ -42,15 +52,16 @@ adaptive="false" time-dependent="false" xml:lang="en">
   </qti-item-body>
 
   <qti-response-processing>
+    <qti-set-outcome-value identifier="SCORE">
+      <qti-map-response identifier="RESPONSE"/>
+    </qti-set-outcome-value>
+
     <qti-response-condition>
       <qti-response-if>
-        <qti-match>
-          <qti-variable identifier="RESPONSE"/>
-          <qti-correct identifier="RESPONSE"/>
-        </qti-match>
-        <qti-set-outcome-value identifier="SCORE">
-          <qti-base-value base-type="float">1</qti-base-value>
-        </qti-set-outcome-value>
+        <qti-gte>
+          <qti-variable identifier="SCORE"/>
+          <qti-variable identifier="MAXSCORE"/>
+        </qti-gte>
         <qti-set-outcome-value identifier="FEEDBACK">
           <qti-multiple>
             <qti-variable identifier="FEEDBACK"/>

From 515302e1c21b3cc69be759c2bcc392640aabf19f Mon Sep 17 00:00:00 2001
From: Claude <noreply@anthropic.com>
Date: Sat, 7 Feb 2026 20:44:38 +0000
Subject: [PATCH 2/2] Fix response processing to match editor-generated pattern

Use qti-sum wrapping qti-map-response for scoring (editor's sumScores
pattern) and qti-match/qti-correct for feedback conditions instead of
qti-gte with MAXSCORE.

https://claude.ai/code/session_01K1EbPpn6oCv4q2ipHGGvX1
---
 .../src/example-items/standard-text-entry.ts         | 12 +++++++-----
 1 file changed, 7 insertions(+), 5 deletions(-)

diff --git a/packages/cutie-example/src/example-items/standard-text-entry.ts b/packages/cutie-example/src/example-items/standard-text-entry.ts
index 8abd8eb..5f106a8 100644
--- a/packages/cutie-example/src/example-items/standard-text-entry.ts
+++ b/packages/cutie-example/src/example-items/standard-text-entry.ts
@@ -53,15 +53,17 @@ adaptive="false" time-dependent="false" xml:lang="en">
 
   <qti-response-processing>
     <qti-set-outcome-value identifier="SCORE">
-      <qti-map-response identifier="RESPONSE"/>
+      <qti-sum>
+        <qti-map-response identifier="RESPONSE"/>
+      </qti-sum>
     </qti-set-outcome-value>
 
     <qti-response-condition>
       <qti-response-if>
-        <qti-gte>
-          <qti-variable identifier="SCORE"/>
-          <qti-variable identifier="MAXSCORE"/>
-        </qti-gte>
+        <qti-match>
+          <qti-variable identifier="RESPONSE"/>
+          <qti-correct identifier="RESPONSE"/>
+        </qti-match>
         <qti-set-outcome-value identifier="FEEDBACK">
           <qti-multiple>
             <qti-variable identifier="FEEDBACK"/>