[uk ai resilience] UK AI Governance: Recent-Changes Risk & Resilience Review (2026-09-03) #58260

Executive summary

This 7-day recent-changes review (2026-08-27 → 2026-09-03, 220 commits, 55 security-signal commits) found the repository's open-code risk posture largely stable and well-tracked: of 11 open CodeQL/workflow-security alerts, 10 already have active UK-AI-resilience tracking issues with correct tier assignments. One genuinely new, untracked finding was identified — CodeQL go/allocation-size-overflow (#672) in pkg/workflow/mcp_setup_generator.go, introduced by recent MCP gateway setup changes. A secondary hygiene gap was confirmed: alert #667 (go/bad-redirect-check in pkg/cli/add_package_manifest_includes.go) is the same false-positive pattern already tracked by issue #54037, but that issue still references the pre-refactor filename add_package_manifest.go — a symptom of the alert-dismissal/tracking hygiene gap already flagged in issue #57982. No open secret-scanning alerts exist. No CODEOWNERS file exists repo-wide, which continues to weaken ownership-confidence scoring across all findings. Per governance guidance, this report favors resilience and remediation velocity over repository concealment; no hiding recommendations are made.

Asset graph summary (recent-change scoped)

Tier classification table

Control verification gaps

• Ownership controls — Gap. No .github/CODEOWNERS file exists anywhere in the repository. All ownership-confidence scores below are inferred from commit authorship, not enforced review routing.
• SDLC controls — Present. CodeQL scanning runs on every push (11 alerts actively surfaced); recent commits (Bump Agentic Workflow Firewall to v0.28.13 #58103, Harden Windows Defender release scans #58115) show test/verification steps in their PR trail.
• Dependency controls — Present. The firewall v0.28.13 bump went through a changeset process with lockfile regeneration/verification steps recorded in commit history, and images are SHA-pinned in pkg/actionpins/data/action_pins.json.
• Secret exposure controls — Present. Zero open secret-scanning alerts; scripts/ensure-docs-slide-pdf.js (alert [Custom Engine Test] Test Pull Request - Custom Engine Safe Output #663) fetches remote content to a file without an obvious secret-handling role, per [uk-ai-resilience] UK AI Governance: untrusted network data written to file in scripts/ensure-docs-slide-pdf.js (Tier C) #53737 investigation.
• Runtime observability — Partial. pkg/parser/import_error.go uses the pkg/logger namespace convention (parser:import_error); pkg/workflow/mcp_setup_generator.go and pkg/cli/add_package_manifest_includes.go were not confirmed to use structured debug logging at the flagged lines.
• Recovery controls — Present but degraded by hygiene gap. 10 of 11 alerts have an existing tracking issue (fast MTTR proxy), but stale metadata (alert [Custom Engine Test] Test Pull Request - Custom Engine Safe Output #667 referencing a renamed file) delays remediation-queue accuracy, consistent with [uk-ai-resilience] Alert-dismissal hygiene gap: 3 CodeQL alerts remain open despite closed/remediated tracking issues (Tier C) #57982.

Risk-scoring table and rationale

Remediation queue with SLAs

Exception register

None required this cycle — no repository-hiding or long-lived exception requests are recommended.

Operational metrics baseline

• MTTR proxy: 10/11 open alerts (91%) have an active tracking issue within one review cycle of creation.
• Ownership coverage: 0% — no CODEOWNERS file exists; all ownership signals are inferred, not enforced.
• Unsupported dependency ratio: 0 flagged in this window; firewall images are current (v0.28.13) and SHA-pinned.
• Exception aging: No open exceptions this cycle.
• Exposure without recovery capability: 1 finding (Hello from Claude #672) currently has detectability but no assigned remediation owner or SLA — now queued above.

Generated by UK AI Operational Resilience · copilot · auto · 46.9 AIC · ⌖ 18.5 AIC · ⊞ 8.1K · ◷

• expires on Sep 6, 2026, 7:40 AM UTC-08:00