[cli-tools-test] example-permissions-warning.md fails compilation despite strict: false

[github-actions]

Discovered during exploratory testing of the compile tool (workflow run #22466261312).

Problem Description

The workflow .github/workflows/example-permissions-warning.md fails to compile with a hard error, even though the file has strict: false and features.dangerous-permissions-write: true in its frontmatter. The workflow's own body text claims "this workflow compiles without warnings", indicating this is a regression.

Steps to Reproduce

Use the compile MCP tool on the workflow:

agenticworkflows-compile workflows: ["example-permissions-warning.md"]
```

## Expected Behavior

The workflow should compile successfully (it has `strict: false` and `features.dangerous-permissions-write: true`), matching the description in the file body: *"All required permissions are properly declared in the frontmatter, so this workflow compiles without warnings."*

## Actual Behavior

Compilation fails with:
```
error: Missing required permissions for GitHub toolsets:
  - contents: write (required by repos)
  - issues: write (required by issues)
  - pull-requests: write (required by pull_requests)

Frontmatter Context

The failing workflow has:

permissions:
  contents: read
  issues: read
  pull-requests: read
tools:
  github:
    toolsets: [repos, issues, pull_requests]
    read-only: false
strict: false
features:
  dangerous-permissions-write: true

Environment

• Repository: github/gh-aw
• Run ID: 22466261312
• Date: 2026-02-26
• File: .github/workflows/example-permissions-warning.md

Impact

• Severity: Medium
• Frequency: Always (reproducible)
• Workaround: None; the example is broken

This is likely a regression introduced when the permissions check was made stricter or when strict: false stopped suppressing the permissions validation error. It also affects make recompile CI runs since it reports 2 compilation failures.

Generated by Daily CLI Tools Exploratory Tester

• expires on Mar 6, 2026, 12:00 AM UTC

[github-actions]

This issue was automatically closed because it expired on 2026-03-06T00:00:01.936Z.

Closed by Workflow