[workflow-health] Daily Rendering Scripts Verifier: prompt placeholder validator false positive on literal __GH_AW_TRUE__ test s [Content truncated due to length]

[github-actions]

Failure Summary

The Daily Rendering Scripts Verifier workflow is consistently failing at the Validate prompt placeholders activation step with a false positive error.

Run: §24281115984 — Apr 11, 2026
Failed step: Validate prompt placeholders (activation job, step 12)

Error Message

🔍 Validating prompt placeholders...
❌ Error: Found unreplaced placeholders in prompt file:

373:    input: "\{\\{\#if __GH_AW_TRUE__ }}\nHello\n\{\{/if}}",
378:    input: "\{\\{\#if __GH_AW_FALSE__ }}\nHidden\n\{\{/if}}",
383:    input: "Start \{\\{\#if __GH_AW_TRUE__ }}middle\{\{/if}} end",
388:    input: "Start \{\\{\#if __GH_AW_FALSE__ }}gone\{\{/if}} end",
393:    input: "Before\n\{\\{\#if __GH_AW_FALSE__ }}\nRemoved\n\{\{/if}}\nAfter",

These placeholders should have been replaced with their actual values.
This indicates a problem with the placeholder substitution step.

Root Cause

The daily-rendering-scripts-verifier.md workflow tests the render_template.cjs rendering logic. As part of its prompt, it includes literal JavaScript test input strings that contain \{\\{\#if __GH_AW_TRUE__}} and \{\\{\#if __GH_AW_FALSE__}} patterns — these are test cases for the rendering system, not actual template variables.

The validate_prompt_placeholders.sh script scans the rendered prompt file for any remaining __GH_AW_TRUE__ or __GH_AW_FALSE__ occurrences and flags them as unsubstituted placeholders. But in this workflow, they appear inside code/JSON literals that are part of the workflow's test suite description.

Impact

• Daily Rendering Scripts Verifier cannot run at all
• Rendering scripts (render_template.cjs, etc.) go unvalidated daily
• The verification workflow was created precisely to catch bugs in the rendering pipeline, so this blocker undermines an important quality gate

Suggested Fixes

Option A (Preferred): Escape literals in the workflow markdown

Escape the test input strings in daily-rendering-scripts-verifier.md so they don't contain literal __GH_AW_TRUE__ tokens. For example, split the string or use an alternative representation:

// Instead of:
input: "\{\\{\#if __GH_AW_TRUE__ }}\nHello\n\{\{/if}}"
// Use a variable or escaped form the validator won't match
const TRUE_TOKEN = "__GH_AW_TRUE__";
input: `\{\\{\#if \$\{TRUE_TOKEN} }}\nHello\n\{\{/if}}`

Option B: Make the validator smarter

Update validate_prompt_placeholders.sh to exclude matches that appear inside code blocks (triple-backtick) or JSON/JavaScript string literals.

Option C: Add a skip-placeholder-validation option

Add a workflow frontmatter option to opt specific workflows out of placeholder validation.

Files to Modify

• .github/workflows/daily-rendering-scripts-verifier.md — for Option A
• actions/setup/sh/validate_prompt_placeholders.sh — for Option B

Priority

P2 — The workflow fails every run, blocking daily rendering script validation.

---

Detected by Workflow Health Manager · §24281978807

Generated by Workflow Health Manager - Meta-Orchestrator · ● 3.7M · ◷

• expires on Apr 12, 2026, 12:09 PM UTC

[pelikhan]

@copilot make validation smarter, convert to JavaScript script file instead of .sh