Merge patches

[qmuntal]

DO NOT SUBMIT

[github-actions]

Patch Consistency Review

I've reviewed this PR which merges patches 0012 and 0013 into a single patch file. Here are my findings:

Summary of Changes

• Patch 0012 (TLS settings) now includes content from the deleted Patch 0013 (version information)
• The merge reduces the patch count from 13 to 12

Observations

Shared files merged correctly:

• doc/godebug.md: Both patches added GODEBUG documentation - now combined ✅
• src/internal/godebugs/table.go: Both patches registered GODEBUG entries - now combined ✅

Potential consistency concern:

The merged patch combines two logically distinct features:

1. TLS/crypto policy settings (ms_tlsx25519, ms_tlsprofile) - modifies src/crypto/tls/*
2. Build version branding (ms_version) - modifies src/cmd/dist/, src/cmd/go/, src/runtime/

Recommendation:

Consider whether these features should remain separate because:

• They serve different purposes (crypto policy vs. build identification)
• The patch title "Align TLS settings with Microsoft policies" no longer accurately describes all content
• Future maintenance might be clearer with separate patches

However, if there's a strategic reason to merge them (e.g., they were always intended to be released together, or this simplifies the patch management), that's reasonable.

Could you clarify the reasoning for merging these patches? If the merge is intentional, consider updating the patch title/description to reflect both features, e.g., "Align TLS settings and add version information".

AI generated by Patch Consistency Review Agent

[gdams]

@qmuntal guessing we can close this now?