Findings
1. gh-aw-duplicate-issue-detector.md is the only workflow_call source missing the standard runtime setup trio
Which workflow deviates
.github/workflows/gh-aw-duplicate-issue-detector.md
Majority pattern
Across workflow_call source workflows (.github/workflows/gh-aw-*.md), the standard structure includes all three of:
Import gh-aw-fragments/runtime-setup.md
Define workflow_call.inputs.setup-commands
Add step - name: Repo-specific setup
Repository-wide counts from current tree:
workflow_call sources: 52
with runtime-setup.md import: 51/52
with setup-commands input: 51/52
with Repo-specific setup step: 51/52
Only outlier in each case: .github/workflows/gh-aw-duplicate-issue-detector.md.
Evidence
Outlier file lacks all three entries in frontmatter/steps:
.github/workflows/gh-aw-duplicate-issue-detector.md lines 4-10 (imports), 19-44 (inputs), 68-91 (steps)
Examples that follow the majority pattern:
.github/workflows/gh-aw-issue-triage.md: line 7 (runtime-setup.md), line 35 (setup-commands), line 75 (Repo-specific setup)
.github/workflows/gh-aw-mention-in-issue.md: line 7, line 37, line 85
.github/workflows/gh-aw-bug-hunter.md: line 7, line 35, line 86
What is missing/different
duplicate-issue-detector omits the shared repo setup hook that nearly all peer workflows expose and execute.
Suggested fix
Update .github/workflows/gh-aw-duplicate-issue-detector.md to align with peers:
Add gh-aw-fragments/runtime-setup.md to imports
Add setup-commands under on.workflow_call.inputs
Add the standard Repo-specific setup step guarded by if: $\{\{ inputs.setup-commands != '' }}
Suggested Actions
Note
🔒 Integrity filter blocked 1 item
The following item were blocked because they don't meet the GitHub integrity level.
#704 search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
To allow these resources, lower min-integrity in your GitHub frontmatter:
tools :
github :
min-integrity : approved # merged | approved | unapproved | none
Generated by Internal: Workflow Patrol · ◷
Findings
1.
gh-aw-duplicate-issue-detector.mdis the onlyworkflow_callsource missing the standard runtime setup trioWhich workflow deviates
.github/workflows/gh-aw-duplicate-issue-detector.mdMajority pattern
Across
workflow_callsource workflows (.github/workflows/gh-aw-*.md), the standard structure includes all three of:gh-aw-fragments/runtime-setup.mdworkflow_call.inputs.setup-commands- name: Repo-specific setupRepository-wide counts from current tree:
workflow_callsources: 52runtime-setup.mdimport: 51/52setup-commandsinput: 51/52Repo-specific setupstep: 51/52Only outlier in each case:
.github/workflows/gh-aw-duplicate-issue-detector.md.Evidence
.github/workflows/gh-aw-duplicate-issue-detector.mdlines 4-10 (imports), 19-44 (inputs), 68-91 (steps).github/workflows/gh-aw-issue-triage.md: line 7 (runtime-setup.md), line 35 (setup-commands), line 75 (Repo-specific setup).github/workflows/gh-aw-mention-in-issue.md: line 7, line 37, line 85.github/workflows/gh-aw-bug-hunter.md: line 7, line 35, line 86What is missing/different
duplicate-issue-detectoromits the shared repo setup hook that nearly all peer workflows expose and execute.Suggested fix
Update
.github/workflows/gh-aw-duplicate-issue-detector.mdto align with peers:gh-aw-fragments/runtime-setup.mdtoimportssetup-commandsunderon.workflow_call.inputsRepo-specific setupstep guarded byif: $\{\{ inputs.setup-commands != '' }}Suggested Actions
.github/workflows/gh-aw-duplicate-issue-detector.mdto match the establishedworkflow_callpattern.Note
🔒 Integrity filter blocked 1 item
The following item were blocked because they don't meet the GitHub integrity level.
search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".To allow these resources, lower
min-integrityin your GitHub frontmatter: