Fix schema validation for boolean tool configuration values

[Copilot]

Fix TestImportMultipleNeutralTools Schema Validation

• Investigate failing test from CI logs
• Identify root cause: safety-prompt: true (boolean) fails schema validation
• Update main_workflow_schema.json to allow boolean in tools.additionalProperties oneOf
• Rebuild binary (schemas are embedded)
• Run the failing test to verify fix
• Run full test suite before final commit
• Merge base branch copilot/compute-frontmatter-hash
• Recompile all 143 workflows with merged changes

Summary

Fixed TestImportMultipleNeutralTools test failure by adding boolean as a third option in the tools.additionalProperties.oneOf schema definition. The test was failing because safety-prompt: true (boolean value) didn't match the existing schema which only allowed string or object types.

Changes:

1. Updated pkg/parser/schemas/main_workflow_schema.json to include boolean type
2. Merged base branch copilot/compute-frontmatter-hash to get latest changes
3. Recompiled all 143 workflow lock files with updated schema and merged code
4. All tests pass including TestHashConsistencyAcrossLockFiles

Original prompt

Reference: https://github.com/githubnext/gh-aw/actions/runs/21499856490/job/61945026918#step:6:1

Fix test

---

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.

[pelikhan]

@copilot merge base branch, recompile to resolve hash collisions

[Copilot]

@copilot merge base branch, recompile to resolve hash collisions

Merged base branch copilot/compute-frontmatter-hash and recompiled all 143 workflows. Hash collisions resolved. All tests pass including TestHashConsistencyAcrossLockFiles. Commit: dbe4bf2