chore: back-merge main into development

[reeshika-h]

What

Back-merges main into development via an intermediate branch, bringing across the two CODEOWNERS commits (5a42146, b7eca21). CODEOWNERS is the only file changed, and its contents now match main exactly.

Why not merge main into development directly

main and development had diverged in both directions:

• main was ahead by 2 commits (CODEOWNERS)
• development was ahead by 5 commits (the 1.5.3 dependency bumps and changelog)

With "require branches to be up to date before merging" enabled, that deadlocks:

• DX | 24-09-2026 | Release #260 (development → main) reports BEHIND, wanting main's commits
• back merge #261 (main → development) reports BEHIND, wanting development's commits

#261 cannot be brought up to date the usual way, because GitHub would need development merged into main — but main is that PR's head branch and is protected, so it cannot be pushed to.

This branch breaks the cycle: it is cut from the current tip of development (so it is up to date with the base by construction) and has main merged into it (so it carries main's commits). Both verified — origin/main and origin/development are each ancestors of this branch.

Merge order

1. Merge this PR into development
2. Close back merge #261 — it is superseded and cannot merge on its own
3. DX | 24-09-2026 | Release #260 (development → main) then becomes up to date and can proceed with the release

Note on the automation

back-merge-pr.yml opens main → development PRs automatically on every push to main. Under the current branch protection those PRs will deadlock whenever development has also moved on, which is the normal case. Worth tracking separately — the workflow likely wants to open the PR from an intermediate branch like this one rather than from main directly.

🤖 Generated with Claude Code

[snyk-io]

✅ Snyk checks have passed. No issues have been found so far.

Status	Scan Engine	Critical	High	Medium	Low	Total (0)
✅	Open Source Security	0	0	0	0	0 issues
✅	Licenses	0	0	0	0	0 issues
✅	Code Security	0	0	0	0	0 issues

💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse.

[github-actions]

🔒 Security Scan Results

ℹ️ Note: Only vulnerabilities with available fixes (upgrades or patches) are counted toward thresholds.

Check Type	Count (with fixes)	Without fixes	Threshold	Result
🔴 Critical Severity	0	0	10	✅ Passed
🟠 High Severity	0	0	25	✅ Passed
🟡 Medium Severity	0	0	500	✅ Passed
🔵 Low Severity	0	0	1000	✅ Passed

⏱️ SLA Breach Summary

✅ No SLA breaches detected. All vulnerabilities are within acceptable time thresholds.

Severity	Breaches (with fixes)	Breaches (no fixes)	SLA Threshold (with/no fixes)	Status
🔴 Critical	0	0	15 / 30 days	✅ Passed
🟠 High	0	0	30 / 120 days	✅ Passed
🟡 Medium	0	0	90 / 365 days	✅ Passed
🔵 Low	0	0	180 / 365 days	✅ Passed

✅ BUILD PASSED - All security checks passed

[Copilot]

Copilot review overview

🟢 Approval recommended

No unresolved review issues were identified.

Review effort: Lite
Findings: None

What changed in this PR

Back-merges main into development by synchronizing CODEOWNERS.

Changes:

• Updates default code ownership.
• Consolidates workflow, Snyk, and CODEOWNERS ownership rules.

File	Description
CODEOWNERS	Synchronizes repository ownership rules with main.

---

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.