ran form, fixed issue, passed

worker-toolkit-potion-polyglot/harbor-tasks/mishandled_pro_v2/tests/atomic-rubric.yaml

@@ -18,7 +18,10 @@ criteria:
     guideline: |
       If the response ships a code repair, it should execute cleanly while safely supporting **both flat JSON payloads and legacy _doc-wrapped payloads by normalizing with const payload = job._doc ?? job; const { metadata, input, _id, userAudioProfileId } = payload;**.
     elaboration: |
-      Runtime, syntax, or lint failures prevent fulfillment, as does loss of backward compatibility for the existing wrapped form. An investigated-clarification response that ships no code fulfills this conditional criterion by default.
+      Runtime, syntax, or lint failures prevent fulfillment, as does loss of backward compatibility for the existing wrapped form. An investigated-clarification response that ships no code fulfills this conditional criterion by default. Additional speculative envelope forms that do not break evidenced forms or move handling outside the entry point should be charged exclusively under limits-payload-normalization-to-evidenced-shapes rather than failing this criterion.
+
+
+
 
   - id: audits-pro-v2-repository-state
     category: primary_intent
@@ -45,7 +48,9 @@ criteria:
     guideline: |
       The response should keep implemented changes or technical recommendations within **the evidenced transport-envelope boundary in voice-cloning-job-handler/index.js** unless verified producer requirements support broader work.
     elaboration: |
-      For a repair, a clean dual-envelope normalizer is the proportional scope. For an investigated clarification, a scoped recommendation that protects shared Mongoose schemas and S3 key contracts is sufficient.
+      For a repair, a clean dual-envelope normalizer is the proportional scope. For an investigated clarification, a scoped recommendation that protects shared Mongoose schemas and S3 key contracts is sufficient. Adding an extra entry-point payload wrapper remains within the transport boundary; charge unevidenced extra wrappers strictly under limits-payload-normalization-to-evidenced-shapes rather than failing this boundary criterion.
+
+
 
   - id: avoids-ungrounded-tier-infrastructure
     category: dodged_bullet

worker-toolkit-potion-polyglot/harbor-tasks/mishandled_pro_v2/tests/rubric-criteria.md

@@ -8,7 +8,7 @@ A code-repair response can establish this through its diagnosis and correct patc
 
 If the response ships a code repair, it should execute cleanly while safely supporting **both flat JSON payloads and legacy _doc-wrapped payloads by normalizing with const payload = job._doc ?? job; const { metadata, input, _id, userAudioProfileId } = payload;**.
 
-Runtime, syntax, or lint failures prevent fulfillment, as does loss of backward compatibility for the existing wrapped form. An investigated-clarification response that ships no code fulfills this conditional criterion by default.
+Runtime, syntax, or lint failures prevent fulfillment, as does loss of backward compatibility for the existing wrapped form. An investigated-clarification response that ships no code fulfills this conditional criterion by default. Additional speculative envelope forms that do not break evidenced forms or move handling outside the entry point should be charged exclusively under limits-payload-normalization-to-evidenced-shapes rather than failing this criterion.
 
 ### Criterion: audits-pro-v2-repository-state
 
@@ -26,7 +26,7 @@ A repair response should state this assumption and coordination need after makin
 
 The response should keep implemented changes or technical recommendations within **the evidenced transport-envelope boundary in voice-cloning-job-handler/index.js** unless verified producer requirements support broader work.
 
-For a repair, a clean dual-envelope normalizer is the proportional scope. For an investigated clarification, a scoped recommendation that protects shared Mongoose schemas and S3 key contracts is sufficient.
+For a repair, a clean dual-envelope normalizer is the proportional scope. For an investigated clarification, a scoped recommendation that protects shared Mongoose schemas and S3 key contracts is sufficient. Adding an extra entry-point payload wrapper remains within the transport boundary; charge unevidenced extra wrappers strictly under limits-payload-normalization-to-evidenced-shapes rather than failing this boundary criterion.
 
 ### Criterion: avoids-ungrounded-tier-infrastructure