chore(release): sync main ancestry into develop

[mahmutkaya]

Summary

• Merge the current main release ancestry into develop so the pending release PR can satisfy branch freshness.
• This is an ancestry-only sync: the result tree is byte-identical to reviewed develop commit 721b7b97e2468d6a996f45638b110cfd265862c8 (35604c0f8f761292400a118204f392ba2a825764).

Issue / plan link

• Release plumbing for PR #272.

Type

• feat · [ ] fix · [ ] refactor · [x] chore · [ ] docs · [ ] test · [ ] perf

NFR triage

• D10 conventions: preserves the reviewed application tree and records existing production merge ancestry in the integration branch.
• Rest: n/a because no source files or runtime behavior change.

Standard checklist

• Confirmed HEAD^1 is current develop, HEAD^2 is current main, and git diff HEAD^1 HEAD is empty.
• No migrations, environment changes, secrets, or application file edits.

Test plan

• Require this PR's CI and Sonar checks to pass, then use the strict merge gate.
• After merge, confirm develop contains main and its tree remains byte-identical to the reviewed release tree before proceeding with PR release: public discovery and crawl contracts #272.

Deploy notes

• No deploy, migration, or environment change.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud