chore(release): v4.5.1

[kirtesh-cstk]

Release commit for v4.5.1, cut from stage_v4. No source changes.

• npm version 4.5.1: package.json, package-lock.json, and CHANGELOG.md regenerated by auto-changelog
• README CDN snippet pinned to 4.5.1 (regenerated from main.mustache by the commit-msg hook)
• main merged in, which brings back the CODEOWNERS edit that landed there directly. Without it stage_v4 stays behind main and the release PR cannot be merged.

What v4.5.1 ships, all of it unreleased since v4.5.0:

• dompurify bump for the XSS advisory, plus the npm audit fix that went with it (fix(security): bump dompurify to patch XSS vulnerability #638)
• edit button now sends the page the editor was on to the CMS, and live preview's own query params moved to one list (fix(edit-button): send the page the editor was on to the CMS #635, Develop v4 #640)
• api key placeholder cleanup in the specs (chore(tests): standardize api key placeholder values in specs #639)
• develop_v4 / stage_v4 back-merge (chore: sync develop_v4 with stage_v4 #645)

The stage_v4 to main release PR follows once this lands.

Branch is named release-v4.5.1 rather than release/v4.5.1: the remote still has an old branch called release, so git rejects any release/* ref alongside it.

---

🤖 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

[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

[github-actions]

Coverage Report

Status	Category	Percentage	Covered / Total
🔵	Lines	67.43%	2530 / 3752
🔵	Statements	66.28%	2570 / 3877
🔵	Functions	64.71%	453 / 700
🔵	Branches	61.98%	1531 / 2470

File Coverage

No changed files found.

Generated in workflow #904 for commit 3d2e823 by the Vitest Coverage Report Action

[karancs06]

LGTM!!