HYPERFLEET-909: normalize capitalization in "standard unavailable" messages

Use Title Case for standard names consistently across all group files.

Author: rafabene

hyperfleet-code-review/.claude-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "hyperfleet-code-review",
-  "version": "0.4.0",
+  "version": "0.4.1",
   "description": "Standardized PR review workflow with JIRA validation, HyperFleet architecture checks, impact analysis, and interactive recommendations",
   "author": {
     "name": "Rafael Benevides",

hyperfleet-code-review/skills/review-pr/group-08-security.md

@@ -4,13 +4,13 @@ This group is **language-agnostic** and runs for every PR regardless of file typ
 
 ## Pass 8a — Injection vulnerabilities
 
-Apply the injection prevention requirements from the HyperFleet error model standard fetched in step 4b. If the standard was not fetched, emit a mandatory finding stating "required error model standard unavailable" with details and skip this pass.
+Apply the injection prevention requirements from the HyperFleet error model standard fetched in step 4b. If the standard was not fetched, emit a mandatory finding stating "required Error Model standard unavailable" with details and skip this pass.
 
 List every place in the diff where external input (HTTP parameters, environment variables, user-provided strings, file content) is incorporated into SQL queries, shell commands, template rendering, or any other injection vector identified in the standard. For each, check against the sanitization and validation requirements defined in the standard.
 
 ## Pass 8b — Secrets exposure
 
-Apply the data redaction requirements from the HyperFleet logging specification and error model standard fetched in step 4b. These standards define the specific list of items that MUST be redacted and the rules for what can appear in logs, error responses, and metric labels. If the standards were not fetched, emit a mandatory finding stating "required logging/error model standards unavailable" with details and skip this pass.
+Apply the data redaction requirements from the HyperFleet logging specification and error model standard fetched in step 4b. These standards define the specific list of items that MUST be redacted and the rules for what can appear in logs, error responses, and metric labels. If the standards were not fetched, emit a mandatory finding stating "required Logging/Error Model standards unavailable" with details and skip this pass.
 
 List every log statement, error message, HTTP response body, and metric label in the diff. For each, check against the redaction and exposure requirements defined in the standards.
 

hyperfleet-code-review/skills/review-pr/group-09-code-hygiene.md

@@ -4,7 +4,7 @@ This group is **language-agnostic** and runs for every PR regardless of file typ
 
 ## Pass 9a — TODOs/FIXMEs without ticket
 
-Apply the commit message and code comment requirements from the HyperFleet **Commit Message Standard** fetched in step 4b. The standard defines the expected ticket reference format and TODO conventions. If the standard was not fetched, emit a mandatory finding stating "required Commit Message Standard unavailable" with details and skip this pass.
+Apply the commit message and code comment requirements from the HyperFleet **Commit Message Standard** fetched in step 4b. The standard defines the expected ticket reference format and TODO conventions. If the standard was not fetched, emit a mandatory finding stating "required Commit Message standard unavailable" with details and skip this pass.
 
 List every `TODO`, `FIXME`, `HACK`, and `XXX` comment added or modified in the diff. For each, check whether it references a ticket ID per the format defined in the standards. Flag TODOs that have no ticket reference.