chore(repo): prune stale remote branches already merged via squash PRs

[ZhuchkaTriplesix]

Context

Audit 2026-07-26: 56 remote topic branches besides main/dev.

Class	Count	Action
Tip already ancestor of main and dev	~26	Safe to delete
Merged into dev, waiting on 0.4.11 (issue/323…339, etc.)	~9	Delete after 0.4.11 lands on main
Tip not ancestor (squash-merged leftovers: feature/208…, issue/241…, …)	~19	Delete after confirming PR merged
release/0.4.10, fix/release-yml-secrets-if	2	Keep until policy says otherwise / delete after 0.4.11 if unused

Task

• List merged PR heads with gh pr list --state merged
• Delete remote branches whose work is on main (and optionally dev)
• Document retention: keep main, dev, active issue/* with open PR only

Caution

Do not delete issue/323–issue/339 until 0.4.11 is on main (or confirm squash tips are disposable and history is only on dev).

Related: release epic #341 · Obsidian audit 06 — Планирование/Аудит готовности 0.4.11

[ZhuchkaTriplesix]

Done (2026-07-26): deleted 47 stale remotes (fully merged / squash leftovers / release/0.4.10 / issue/225).

Kept until 0.4.11 ships to main:

• issue/323 … issue/339 (9 branches, tips on dev only)
• main, dev

[ZhuchkaTriplesix]

Closed: pruned 48 stale remotes. Remaining 9 issue/323…339 intentionally kept until 0.4.11 is on main.