Upgrade workflows to gh-aw v0.92.0

[lpcox]

Summary

Upgrades the gh-aw extension from v0.91.12 to the latest prerelease, v0.92.0, and recompiles all agentic workflows.

Changes

• Ran gh aw upgrade --pre-releases
• Updated github/gh-aw-actions/setup and setup-cli to v0.92.0
• Updated actions/setup-java from v6.0.1 to v6.1.0
• Refreshed firewall and MCP gateway container digest pins
• Regenerated the maintenance workflow and all 34 workflow lock files with compiler v0.92.0
• Ran a separate gh aw compile pass after the upgrade

Validation

• gh aw compile: 34/34 workflows compiled successfully
• make agent-finished: passed
  • build and lint passed
  • all Go tests passed
  • all 682 Rust guard tests passed

The compiler continues to report eight existing advisory warnings for /tmp/ prompt references, dispatch concurrency, and a secret expression; there were no compilation errors.

[github-actions]

🔒 mcpg Read-Only Stress — default

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

Part	Surface	Op	Result	Expected	Status
A	MCP	reads	data	ALLOWED	✅
B	MCP	writes (reaction/star/issue/comment/branch/file/PR)	refused	BLOCKED	⚠️
C	CLI	reads	data	ALLOWED	✅
D	CLI	REST writes (reaction/star/issue/comment)	refused	BLOCKED	⚠️
E	CLI	GraphQL mutations (addReaction/addStar/createIssue)	refused	BLOCKED	⚠️

Overall: INCONCLUSIVE

⚠️ Part B: all 6 targeted write tools (add_issue_comment, star_repository, issue_write, create_branch, create_or_update_file, create_pull_request) were absent from the gateway's 23-tool catalog (github --help lists only read tools). This confirms gh-aw's backend-level GITHUB_READ_ONLY=1 wrapper, but cannot independently confirm mcpg's own gateway-layer DIFC/guard write-blocking, since no write-capable tool was ever reachable to refuse.

⚠️ Parts D/E: gh CLI is unauthenticated in this environment (gh auth status → not logged into any GitHub hosts; GH_TOKEN unset), so REST/GraphQL write attempts could not be executed at all — the token-scope boundary was not exercised this run.

No writes leaked. No destructive operations attempted. Parts A and C (reads) fully passed on both MCP and CLI surfaces.

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

[Copilot]

🔵 Needs a closer look

The prerelease changes security-sensitive workflow runtimes whose end-to-end compatibility still needs live smoke validation.

0 open findings

What changed in this PR

Upgrades the repository’s agentic workflow automation to gh-aw v0.92.0.

Changes:

• Updates setup actions, the Java action lock entry, and firewall/gateway pins.
• Regenerates workflow and maintenance YAML.
• Adds runtime metadata handling, telemetry isolation, and GitHub rate-limit logging.

File	Description
.github/​workflows/​test-improver.lock.yml	Refreshes runtime pins and metadata handling.
.github/​workflows/​smoke-copilot.lock.yml	Updates smoke-test automation and firewall pins.
.github/​workflows/​nightly-schema-updater.lock.yml	Updates gateway pins and adds rate-limit logging.
.github/​workflows/​ghcr-download-tracker.lock.yml	Refreshes runtimes and adds rate-limit logging.
.github/​workflows/​gateway-issue-dispatcher.lock.yml	Updates runtimes and cross-repository rate-limit logging.
.github/​workflows/​agentics-maintenance.yml	Updates maintenance setup actions and CLI version.
.github/​aw/​actions-lock.json	Records updated action and container pins.

🧠 Review effort: Max

---

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.