Update docs changelog (for PR #60858) (#61273)

Co-authored-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
Co-authored-by: Joe Clark <31087804+jc-clark@users.noreply.github.com>

Author: 3 people

CHANGELOG.md

@@ -6,6 +6,16 @@ We published the first iteration of a [journey landing page](https://docs.github
 
 <hr>
 
+**16 May 2026**
+
+To help admins understand security configuration statuses, we documented the relationship between organization and enterprise configurations and repositories, including how and why that relationship changes.
+
+- [Security configuration statuses](https://docs.github.com/en/code-security/reference/security-at-scale/security-configuration-statuses) covers all 8 statuses a security configuration can have, with descriptions, causes, and recommended actions
+- [Diagnosing security configuration issues](https://docs.github.com/en/code-security/reference/security-at-scale/troubleshoot-security-configurations/diagnosing-security-configuration-issues) now covers `removed` and `removed_by_enterprise` statuses in addition to `failed`
+- [About enabling security features at scale](https://docs.github.com/en/code-security/concepts/security-at-scale/about-enabling-security-features-at-scale) explains how configurations relate to repositories over time
+
+<hr>
+
 **15 May 2026**
 
 We've published a new [GitHub Secret Protection adoption journey landing page](https://docs.github.com/en/code-security/tutorials/secret-protection-adoption-path) for AppSec administrators. Our content audit found that while individual GHSP articles existed, there was no clear end-to-end path from evaluation to organization-wide rollout.