Set min-integrity: none on /review workflow

[jonathanpeppers]

Description

The /review agentic workflow currently uses the default min-integrity: approved, which blocks the agent from reading PR descriptions authored by external or first-time contributors. This means the reviewer can analyze the code diff but cannot read the PR body or linked context -- resulting in an incomplete review.

This adds min-integrity: none to the tools.github section so the reviewer agent can read PR content from any contributor. The /review slash command is already gated to maintainers (owners, members, collaborators), so only trusted users can trigger a review.

Context: #11151 (review)

[Copilot]

Pull request overview

Updates the /review agentic workflow configuration so the reviewer agent can read PR content even when the PR is authored by external or first-time contributors, improving review completeness for maintainer-triggered reviews.

Changes:

• Set tools.github.min-integrity: none in the workflow source (android-reviewer.md).
• Regenerated the compiled workflow lock file (android-reviewer.lock.yml) to apply the new guard policy configuration.

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 3 comments.

File	Description
.github/workflows/android-reviewer.md	Lowers GitHub tool min-integrity to allow reading PR descriptions from any contributor.
.github/workflows/android-reviewer.lock.yml	Regenerated compiled workflow; updates MCP guard policy configuration and related steps/log uploads.

[Copilot]

MCP_GATEWAY_DOCKER_COMMAND still includes -e GITHUB_MCP_GUARD_MIN_INTEGRITY -e GITHUB_MCP_GUARD_REPOS, but the workflow no longer sets these environment variables (the previous determine-automatic-lockdown step was removed and start-mcp-gateway no longer exports them). This leaves the container with empty/stale env vars and makes the gateway setup harder to reason about. Remove these -e ... entries from the docker command (or reintroduce setting the variables) so the config is self-consistent.

Suggested change

export MCP_GATEWAY_DOCKER_COMMAND='docker run -i --rm --network host -v /var/run/docker.sock:/var/run/docker.sock -e MCP_GATEWAY_PORT -e MCP_GATEWAY_DOMAIN -e MCP_GATEWAY_API_KEY -e MCP_GATEWAY_PAYLOAD_DIR -e MCP_GATEWAY_PAYLOAD_SIZE_THRESHOLD -e DEBUG -e MCP_GATEWAY_LOG_DIR -e GH_AW_MCP_LOG_DIR -e GH_AW_SAFE_OUTPUTS -e GH_AW_SAFE_OUTPUTS_CONFIG_PATH -e GH_AW_SAFE_OUTPUTS_TOOLS_PATH -e GH_AW_ASSETS_BRANCH -e GH_AW_ASSETS_MAX_SIZE_KB -e GH_AW_ASSETS_ALLOWED_EXTS -e DEFAULT_BRANCH -e GITHUB_MCP_SERVER_TOKEN -e GITHUB_MCP_GUARD_MIN_INTEGRITY -e GITHUB_MCP_GUARD_REPOS -e GITHUB_REPOSITORY -e GITHUB_SERVER_URL -e GITHUB_SHA -e GITHUB_WORKSPACE -e GITHUB_TOKEN -e GITHUB_RUN_ID -e GITHUB_RUN_NUMBER -e GITHUB_RUN_ATTEMPT -e GITHUB_JOB -e GITHUB_ACTION -e GITHUB_EVENT_NAME -e GITHUB_EVENT_PATH -e GITHUB_ACTOR -e GITHUB_ACTOR_ID -e GITHUB_TRIGGERING_ACTOR -e GITHUB_WORKFLOW -e GITHUB_WORKFLOW_REF -e GITHUB_WORKFLOW_SHA -e GITHUB_REF -e GITHUB_REF_NAME -e GITHUB_REF_TYPE -e GITHUB_HEAD_REF -e GITHUB_BASE_REF -e GH_AW_SAFE_OUTPUTS_PORT -e GH_AW_SAFE_OUTPUTS_API_KEY -v /tmp/gh-aw/mcp-payloads:/tmp/gh-aw/mcp-payloads:rw -v /opt:/opt:ro -v /tmp:/tmp:rw -v '"${GITHUB_WORKSPACE}"':'"${GITHUB_WORKSPACE}"':rw ghcr.io/github/gh-aw-mcpg:v0.2.19'

export MCP_GATEWAY_DOCKER_COMMAND='docker run -i --rm --network host -v /var/run/docker.sock:/var/run/docker.sock -e MCP_GATEWAY_PORT -e MCP_GATEWAY_DOMAIN -e MCP_GATEWAY_API_KEY -e MCP_GATEWAY_PAYLOAD_DIR -e MCP_GATEWAY_PAYLOAD_SIZE_THRESHOLD -e DEBUG -e MCP_GATEWAY_LOG_DIR -e GH_AW_MCP_LOG_DIR -e GH_AW_SAFE_OUTPUTS -e GH_AW_SAFE_OUTPUTS_CONFIG_PATH -e GH_AW_SAFE_OUTPUTS_TOOLS_PATH -e GH_AW_ASSETS_BRANCH -e GH_AW_ASSETS_MAX_SIZE_KB -e GH_AW_ASSETS_ALLOWED_EXTS -e DEFAULT_BRANCH -e GITHUB_MCP_SERVER_TOKEN -e GITHUB_REPOSITORY -e GITHUB_SERVER_URL -e GITHUB_SHA -e GITHUB_WORKSPACE -e GITHUB_TOKEN -e GITHUB_RUN_ID -e GITHUB_RUN_NUMBER -e GITHUB_RUN_ATTEMPT -e GITHUB_JOB -e GITHUB_ACTION -e GITHUB_EVENT_NAME -e GITHUB_EVENT_PATH -e GITHUB_ACTOR -e GITHUB_ACTOR_ID -e GITHUB_TRIGGERING_ACTOR -e GITHUB_WORKFLOW -e GITHUB_WORKFLOW_REF -e GITHUB_WORKFLOW_SHA -e GITHUB_REF -e GITHUB_REF_NAME -e GITHUB_REF_TYPE -e GITHUB_HEAD_REF -e GITHUB_BASE_REF -e GH_AW_SAFE_OUTPUTS_PORT -e GH_AW_SAFE_OUTPUTS_API_KEY -v /tmp/gh-aw/mcp-payloads:/tmp/gh-aw/mcp-payloads:rw -v /opt:/opt:ro -v /tmp:/tmp:rw -v '"${GITHUB_WORKSPACE}"':'"${GITHUB_WORKSPACE}"':rw ghcr.io/github/gh-aw-mcpg:v0.2.19'

[Copilot]

The GitHub MCP allow-only guard policy is now hard-coded to "repos": "all". This broadens the reviewer agent’s read scope beyond the current repository (to anything the token can access), which is a meaningful security/safety change beyond just lowering min-integrity. Consider restricting this to the current repository (or an explicit allowlist) unless there’s a demonstrated need for cross-repo reads.

Suggested change

	"repos": "all",
	"repos": [
	"${{ github.repository }}"
	],

[Copilot]

The artifact upload list adds /tmp/gh-aw/proxy-logs/ (excluding proxy-tls), but this workflow appears to write proxy logs to /tmp/gh-aw/sandbox/firewall/logs via --proxy-logs-dir, and there’s no step creating /tmp/gh-aw/proxy-logs. If this path isn’t actually used, it’s dead/duplicative config and should be removed (or update --proxy-logs-dir to match) to keep artifacts and troubleshooting paths consistent.

Suggested change

	/tmp/gh-aw/proxy-logs/
	!/tmp/gh-aw/proxy-logs/proxy-tls/