🔄 chore: pin schema URL to gh-aw v0.91.12

[github-actions]

Schema URL Update

Updates the MCP Gateway JSON schema validation URL from the previous pinned version to v0.91.12.

Files Changed

• internal/config/validation_errors.go — SchemaURL updated to v0.91.12

Why

Pinning to a specific release tag ensures reproducible, deterministic configuration validation and keeps validation error messages aligned with the latest stable gh-aw schema release.

Validation

• go build ./...
• go test ./internal/config/...
• make agent-finished

Release Notes

See the gh-aw release notes for changes in this schema version.

Warning

Firewall blocked 4 domains

The following domains were blocked by the firewall during workflow execution:

• example.com
• nonexistent.local
• slow.example.com
• thishostdoesnotexist12345.com

To allow these domains, add them to the network.allowed list in your workflow frontmatter:

network:
  allowed:
    - defaults
    - "example.com"
    - "nonexistent.local"
    - "slow.example.com"
    - "thishostdoesnotexist12345.com"

See Network Configuration for more information.

Generated by Nightly Schema Updater · copilot · gpt54 · 36.1 AIC · ⊞ 30.6K · ◷

• expires on Oct 22, 2026, 2:55 AM UTC

[github-actions]

🔒 mcpg Read-Only Stress — default

Surface coverage: MCP tool calls + proxied CLI (REST) + GraphQL mutations
Isolation runtime: default (normal AWF container, no extra isolation)

Part	Surface	Op	Result	Expected	Status
A	MCP	reads (list_issues, list_pull_requests, get_file_contents, list_commits)	data returned	ALLOWED	✅
B	MCP	writes (reaction/star/issue/comment/branch/file/PR)	all 6 target tools absent from 23-tool catalog (read-only toolset)	BLOCKED	⚠️
C	CLI	reads (same 4 calls via github CLI proxy)	data returned	ALLOWED	✅
D	CLI	REST writes (reaction/star/issue/comment)	gh unauthenticated (no GH_TOKEN) — not attempted	BLOCKED	⚠️
E	CLI	GraphQL mutations (addReaction/addStar/createIssue)	gh unauthenticated (no GH_TOKEN) — not attempted	BLOCKED	⚠️

Overall: INCONCLUSIVE

Notes:

• Part A/C reads fully confirmed on both MCP-tool and proxied-CLI surfaces.
• Part B: the gateway's github tool catalog exposes only 23 read-only tools; none of the targeted write tools exist to call, so gateway-level DIFC write-blocking could not be independently exercised (backend config already removes them per gh-aw's GITHUB_READ_ONLY=1, as documented in the test plan).
• Parts D/E: gh CLI has no GH_TOKEN in this job, so REST/GraphQL write attempts could not reach the GitHub API to test the token-scope boundary.
• No writes leaked; no destructive operations attempted.

🔒 mcpg read-only stress (default AWF runtime) by Read-Only Stress: default runtime