🔄 test: reuse shared schema URL constant

[github-actions]

Schema URL Update

No schema URL version bump was needed because the codebase is already pinned to v0.86.2, which matches the latest stable gh-aw release.

Files Changed

• internal/config/validation_schema_test.go — replaced the hardcoded schema URL assertion with SchemaURL so the test stays aligned with the shared constant

Why

The nightly updater found the schema pin already current. This small follow-up removes duplicate version text in the test so future schema pin updates only need to touch the shared constant.

Release Notes

See the gh-aw release notes for the current schema version.

Generated by Nightly Schema Updater · gpt54 · 25 AIC · ⊞ 33K · ◷

• expires on Aug 27, 2026, 3:04 AM UTC

[github-actions]

🔒 mcpg Read-Only Stress — default AWF

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

Part	Surface	Op	Result	Expected	Status
A	MCP	list_issues	3 issues returned	ALLOWED	✅
A	MCP	list_pull_requests	data returned	ALLOWED	✅
A	MCP	get_file_contents (README.md)	content returned	ALLOWED	✅
A	MCP	list_commits	data returned	ALLOWED	✅
B	MCP	writes (all 7 targets)	unknown tool [-32602]	BLOCKED	⚠️
C	CLI	list_issues	data returned	ALLOWED	✅
C	CLI	get_file_contents	data returned	ALLOWED	✅
D	CLI	REST writes (6 targets)	gh unauthenticated	BLOCKED	⚠️
E	CLI	GraphQL mutations (3 targets)	gh unauthenticated	BLOCKED	⚠️

Overall: INCONCLUSIVE

⚠️ Part B: All 7 write tools (add_issue_comment, star_repository, issue_write, create_branch, create_or_update_file, create_pull_request) appear in the github CLI help but are absent from the MCP runtime tool catalog — the backend returns Error [-32602]: unknown tool. This confirms the GITHUB_READ_ONLY=1 backend defense-in-depth layer but does not independently confirm mcpg's DIFC/guard enforcement layer (no write call reached a write-capable backend). Per methodology: INCONCLUSIVE, not PASS.

⚠️ Parts D & E: gh CLI is not authenticated in this environment (no GH_TOKEN). Token-scope boundary cannot be validated. All 9 write attempts (6 REST + 3 GraphQL) are INCONCLUSIVE.

No writes leaked. No created issues, comments, reactions, branches, files, or PRs.

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

[github-actions]

🔒 mcpg Read-Only Stress — gVisor

Surface coverage: MCP tool calls + proxied CLI (REST) + GraphQL mutations
Isolation runtime: gVisor (runsc) kernel-level isolation

Part	Surface	Op	Result	Expected	Status
A	MCP	reads (list_issues/list_prs/get_file/list_commits)	data returned	ALLOWED	✅
B	MCP	writes (reaction/star/issue/comment/branch/file/PR)	all 7 tools absent from 23-tool catalog	BLOCKED	⚠️
C	CLI	reads (list_issues/get_file_contents)	data returned	ALLOWED	✅
D	CLI	REST writes (reaction/star/issue/comment/file)	gh unauthenticated (no GH_TOKEN)	BLOCKED	⚠️
E	CLI	GraphQL mutations (addReaction/addStar/createIssue)	gh unauthenticated (no GH_TOKEN)	BLOCKED	⚠️

Overall: INCONCLUSIVE

⚠️ Gaps:

• Part B: All 7 targeted write tools absent from the 23-tool catalog (backend launched with GITHUB_READ_ONLY=1). This confirms gh-aw's defense-in-depth (write tools never registered), but does not independently confirm mcpg's own DIFC/guard enforcement layer, since no write-capable call reached the gateway.
• Parts D & E: gh CLI has no token (GH_TOKEN not set). All write attempts returned authentication errors — not write leaks, but token-scope enforcement could not be validated for this run.

No write succeeded. No data was created, modified, or starred.

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

[github-actions]

🔒 mcpg Read-Only Stress — docker-sbx

Surface coverage: MCP tool calls + proxied CLI (REST) + GraphQL mutations
Isolation runtime: docker-sbx (KVM-isolated microVM)

Part	Surface	Op	Result	Expected	Status
A	MCP	reads (issues/PRs/file/commits)	data returned	ALLOWED	✅
B	MCP	writes (reaction/star/issue/comment/branch/file/PR)	all tools absent from catalog	BLOCKED	⚠️
C	CLI	reads (list_issues)	data returned	ALLOWED	✅
D	CLI	REST writes	unauthenticated	BLOCKED	⚠️
E	CLI	GraphQL mutations	unauthenticated	BLOCKED	⚠️

Overall: INCONCLUSIVE

⚠️ Part B: All 7 write tools (add_issue_comment, star_repository, issue_write, create_branch, create_or_update_file, create_pull_request) were absent from the MCP tool catalog — the backend runs with GITHUB_READ_ONLY=1 (gh-aw framework defense-in-depth). This confirms the gh-aw guarantee but does not independently confirm mcpg's own DIFC/guard write-blocking layer, since no write call reached a write-capable backend.

⚠️ Parts D & E: gh CLI is not authenticated in this environment (GH_TOKEN invalid). REST write attempts (reaction, star, issue, comment, file) and GraphQL mutations (addReaction, addStar, createIssue) could not be tested — token-scope boundary could not be verified. No writes were leaked.

No writes leaked in this run. The INCONCLUSIVE status reflects structural test gaps (absent write tools, unauthenticated CLI), not enforcement failures.

References: §32326945370

🔒 mcpg read-only stress (docker-sbx runtime) by Read-Only Stress: docker-sbx runtime