You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
To resolve this, the issue content needs to be reviewed and approved by a maintainer with appropriate permissions, or the integrity policy needs to be adjusted to allow processing of community-submitted issues.
Error details: MCP error 0: [Filtered] issue:#3024 exists but is not accessible — filtered by integrity policy (Resource 'issue:#3024' has lower integrity than agent requires. The agent cannot read data with integrity below "approved").
This is a structured incompletion signal (report_incomplete), not a real task outcome. Any other safe outputs emitted alongside this signal (e.g., comments) describe the failure state, not a completed review or action.
Action Required
Assign this issue to an agent to debug and fix the issue.
Debug with any coding agent
Use this prompt with any coding agent (GitHub Copilot, Claude, Gemini, etc.):
Debug the agentic workflow failure using https://raw.githubusercontent.com/github/gh-aw/main/debug.md
The failed workflow run is at https://github.com/github/spec-kit/actions/runs/27723338331
Manually invoke the agent
Debug this workflow failure using your favorite Agent CLI and the agentic-workflows prompt.
Workflow Failure
Workflow: Add Community Extension from Issue Submission
Branch: main
Run: https://github.com/github/spec-kit/actions/runs/27723338331
Pull Request: #2884
Reasons:
Cannot access issue [Bug]: agent-context extension ignores scoped/nested spec directories (SPECIFY_FEATURE_DIRECTORY), so plan auto-discovery finds nothing #3024 due to integrity policy restrictions. The issue is filtered and requires content approval before processing. The MCP server indicates the resource has lower integrity than the agent requires (minimum: "approved").
The GitHub MCP server returned an integrity policy filter error when attempting to read issue [Bug]: agent-context extension ignores scoped/nested spec directories (SPECIFY_FEATURE_DIRECTORY), so plan auto-discovery finds nothing #3024. This workflow is designed to process community extension submissions, but it cannot proceed without access to the issue content containing the submission data (extension ID, name, version, repository URL, etc.).
To resolve this, the issue content needs to be reviewed and approved by a maintainer with appropriate permissions, or the integrity policy needs to be adjusted to allow processing of community-submitted issues.
Error details: MCP error 0: [Filtered] issue:#3024 exists but is not accessible — filtered by integrity policy (Resource 'issue:#3024' has lower integrity than agent requires. The agent cannot read data with integrity below "approved").
This is a structured incompletion signal (
report_incomplete), not a real task outcome. Any other safe outputs emitted alongside this signal (e.g., comments) describe the failure state, not a completed review or action.Action Required
Assign this issue to an agent to debug and fix the issue.
Debug with any coding agent
Use this prompt with any coding agent (GitHub Copilot, Claude, Gemini, etc.):
Manually invoke the agent
Debug this workflow failure using your favorite Agent CLI and the
agentic-workflowsprompt.agentic-workflowsskill from.github/skills/agentic-workflows/SKILL.mdor https://github.com/github/gh-aw/blob/main/.github/skills/agentic-workflows/SKILL.mddebug the agentic workflow add-community-extension failure in https://github.com/github/spec-kit/actions/runs/27723338331Tip
Stop reporting this workflow as a failure
To stop a workflow from creating failure issues, set
report-failure-as-issue: falsein its frontmatter: