Fixes for PR check failures

Author: data-douser

actions/ql/integration-tests/query-suite/not_included_in_qls.expected

@@ -10,6 +10,8 @@ ql/actions/ql/src/experimental/Security/CWE-078/CommandInjectionCritical.ql
 ql/actions/ql/src/experimental/Security/CWE-078/CommandInjectionMedium.ql
 ql/actions/ql/src/experimental/Security/CWE-088/ArgumentInjectionCritical.ql
 ql/actions/ql/src/experimental/Security/CWE-088/ArgumentInjectionMedium.ql
+ql/actions/ql/src/experimental/Security/CWE-1427/PromptInjectionCritical.ql
+ql/actions/ql/src/experimental/Security/CWE-1427/PromptInjectionMedium.ql
 ql/actions/ql/src/experimental/Security/CWE-200/SecretExfiltration.ql
 ql/actions/ql/src/experimental/Security/CWE-284/CodeExecutionOnSelfHostedRunner.ql
 ql/actions/ql/src/experimental/Security/CWE-829/ArtifactPoisoningPathTraversal.ql

actions/ql/lib/codeql/actions/security/PromptInjectionQuery.qll

@@ -85,7 +85,7 @@ predicate criticalSeverityPromptInjection(
  * and any other externally triggerable context that Critical excludes.
  *
  * Only actor/association control checks suppress Medium findings because
- * repository checks do not prevent prompt injection — any user who can
+ * repository checks do not prevent prompt injection -- any user who can
  * open an issue/PR on the target repo can inject into the prompt content.
  */
 Event getRelevantEventForMediumSeverity(DataFlow::Node sink) {