What's missing: The manifest entry for gh-aw-mcpg:v0.3.17 lacks the digest and pinned_image fields that were present in the previous version (v0.3.16). This weakens supply-chain security guarantees.

Before (v0.3.16) — ✅ Correctly pinned:

{
  "image": "ghcr.io/github/gh-aw-mcpg:v0.3.16",
  "digest": "sha256:8001e4bfa52d45abd05c45a8f855ce62bc893eb66e4807bb487bf2ff07fc1473",
  "pinned_image": "ghcr.io/github/gh-aw-mcpg:v0.3.16@sha256:8001e4bfa52d45abd05c45a8f855ce62bc893eb66e4807bb487bf2ff07fc1473"
}

After (v0.3.17) — ❌ Missing digest:

{
  "image": "ghcr.io/github/gh-aw-mcpg:v0.3.17"
}

Why this matters: Container tags are mutable. Without digest pinning, workflows lose bit-for-bit reproducibility and supply-chain integrity verification.

How to fix:

1. Verify ghcr.io/github/gh-aw-mcpg:v0.3.17 is published and accessible
2. Run make recompile to regenerate lockfiles with proper digest resolution
3. Confirm all lockfiles now include digest and pinned_image fields for MCP Gateway

Verification:

grep -r "gh-aw-mcpg:v0.3.17" .github/workflows/*.lock.yml | grep -c "digest"
# Should return a count matching the number of workflows using MCP Gateway

Change Classification

This PR is a dependency version bump — updating two pinned infrastructure versions (gh-aw-firewall v0.25.50 → v0.25.51 and gh-aw-mcpg v0.3.16 → v0.3.17) and mechanically regenerating 245 lock files to reflect the new versions.

Key Findings

✅ Correct regeneration process followed — The PR description and commit history confirm the documented two-pass rebuild (make build && make recompile && make recompile) was executed, which is critical for refreshing container SHA pins.

✅ Consistency across artifacts — All 245 lock files show uniform version updates (AWF: v0.25.50 → v0.25.51, schema URLs updated, container image tags bumped).

✅ Changeset properly configured — The .changeset/patch-bump-awf-v0-25-51-mcpg-v0-3-17.md file correctly declares this as a patch release.

/zoom-out Observations

From an architectural perspective, this change:

• Maintains the existing versioning contract — The version constants act as the single source of truth, and all derived artifacts (lock files, schemas, container tags) are generated from them
• Follows the documented process — The warnings in version_constants.go explicitly document the two-recompile requirement, which was followed
• Preserves backward compatibility — This is a patch-level bump on existing infrastructure, not a breaking change

/tdd Observations

The codebase has existing test coverage for version propagation (aw_info_versions_test.go, awf_config_test.go, mcp_gateway_config_test.go), which validates that version constants flow correctly through the compilation pipeline. However:

• No regression tests for the specific versions — Tests use constants.DefaultFirewallVersion symbolically rather than asserting specific version strings
• No validation that recompilation was complete — There's no automated check that all 245 files were regenerated (though this is apparent from the diff size)

These aren't blockers for this PR but represent opportunities for future hardening.