Fix strict mode isolation between workflows and add script to priority fields

[Copilot]

Problem

When compiling multiple workflows, the strict: true flag in one workflow's frontmatter would affect all subsequent workflow compilations. This happened because the compiler instance is reused across multiple workflows, and setting c.strictMode = true for one workflow would persist for all following workflows.

Additionally, the script field was missing from the step field priority ordering.

Example of the Issue

# workflow1.md - has strict: true
---
on: push
strict: true
permissions:
  contents: read
engine: claude
network:
  allowed:
    - "api.example.com"
---
# This workflow enables strict mode

# workflow2.md - no strict flag
---
on: push
permissions:
  contents: write
engine: claude
---
# This workflow should NOT be in strict mode
# But it was incorrectly validated with strict rules!

When compiling both workflows sequentially using gh aw compile, workflow2 would fail strict mode validation even though it didn't have strict: true, because the strict mode state leaked from workflow1.

Solution

1. Strict Mode Isolation

Modified ParseWorkflowFile in pkg/workflow/compiler.go to:

• Save the initial strictMode state before processing each workflow
• Apply workflow-specific strict mode from frontmatter if present
• Restore the initial state immediately after validation
• Handle error cases by restoring state before returning

This ensures strict mode is isolated per-workflow and doesn't affect other compilations.

2. Script Field Priority

Added "script" as the first field in PriorityStepFields in pkg/constants/constants.go, ensuring proper field ordering in generated workflow steps.

Testing

Added TestStrictModeIsolation that validates:

• A strict workflow with missing required fields fails validation
• A subsequent non-strict workflow compiles successfully without being affected
• Multiple workflows can be compiled in any order without strict mode leaking

All existing tests continue to pass, and all 59 workflows in the repository recompile successfully.

Original prompt

when a workflow has the "strict: true" flag enabled, it should not affect the compilation "strictness" of other workflows (+ add script in field priority list as first field)

---

💬 Share your feedback on Copilot coding agent for the chance to win a $200 gift card! Click here to start the survey.