chore(merge): reconcile master into main (session 2026-05-11)

[ahmetabdullahgultekin]

Summary

master and main had diverged since the 2026-03-28 merge base. master was the active integration branch where the 2026-04-19 audit remediation, SEO PRs (#42-#47), and the 2026-05-11 session work (ROADMAP refresh + submodule pointer bumps + CHANGELOG entry, PR #50) all landed. main accumulated parallel work: the spoof-detector standalone restructure, the 2026-05-04 through 2026-05-09 investigation/audit doc waves, and PR #48 (branch protection across 5 repos with CICD_AUDIT_2026-05-04.md appended).

This PR brings master's content into main so both branches can converge.

Reconciliation rules applied

File / scope	Winner	Reason
ROADMAP.md (root)	master	Master has the 2026-05-11 refresh; main had archived it
CHANGELOG.md	master	Has the 2026-05-11 session entry
.gitmodules	master	Includes spoof-detector entry; main's was already converging
Submodule pointers	master	Latest HEADs: api 606f1f4, bio 750492c, docs 78a9b4a, spoof-detector cc73cf0, web-app 096ed05, client-apps 5ab3abb
CICD_AUDIT_2026-05-04.md	main	PR #48 added 91 lines of branch-protection evidence; master never had this file
archive/2026-04-pre-roadmap-2028/* (most)	master (delete)	Rename-to-archive on main vs delete-on-master => take delete
All INVESTIGATION_*_2026-05-07.md, SENIOR_*_2026-05-04.md, etc.	main (preserved)	Forward historical record from main's lineage
.env.example, CLAUDE.md, .github/workflows/deploy-landing.yml, .gitignore	main	Carries newer content (BE-H1 RS256, MTCNN/Facenet512 docs, ubuntu-latest runner, archive/ tracked)

Verification

• No unresolved merge conflicts
• git diff --cached origin/master -- ROADMAP.md CHANGELOG.md .gitmodules is empty
• All 6 submodule index entries match master's HEADs
• CICD_AUDIT_2026-05-04.md preserved unmodified from main HEAD
• Spoof-detector entry present in .gitmodules

Follow-up

A second PR (chore(sync): main -> master post-reconciliation) will fast-forward master to this merge commit so the two branches are byte-identical. Branch-protection requires PR even for that sync.

Test plan

• Reviewer confirms no critical file accidentally reverted
• gh pr merge --squash --admin --delete-branch (admin bypass per CICD T3.1.d policy)
• Open follow-up sync PR from main -> master
• After both merges: git log origin/main..origin/master empty AND git log origin/master..origin/main empty

Generated with Claude Code.

[gitguardian]

⚠️ GitGuardian has uncovered 2 secrets following the scan of your pull request.

Please consider investigating the findings and remediating the incidents. Failure to do so may lead to compromising the associated services or software components.

🔎 Detected hardcoded secrets in your pull request

GitGuardian id	GitGuardian status	Secret	Commit	Filename
29834700	Triggered	Generic Password	f48bddf	scripts/test-rbac.sh	View secret
32722355	Triggered	Generic Password	6d4cc73	scripts/test-rbac.sh	View secret

🛠 Guidelines to remediate hardcoded secrets

1. Understand the implications of revoking this secret by investigating where it is used in your code.
2. Replace and store your secrets safely. Learn here the best practices.
3. Revoke and rotate these secrets.
4. If possible, rewrite git history. Rewriting git history is not a trivial act. You might completely break other contributing developers' workflow and you risk accidentally deleting legitimate data.

To avoid such incidents in the future consider

• following these best practices for managing and storing secrets including API keys and other credentials
• install secret detection on pre-commit to catch secret before it leaves your machine and ease remediation.

---

^{🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request.}