docs: Backfill the features ledger from all merged PRs

[vpacher]

Fixes #1250

What and why

#1267 added docs/features.md and the rule that a PR with a user-visible change adds its line. This PR fills in everything that merged before: the features that were announced once in a PR and then disappeared (discussion #1078).

How the list was made:

1. Collect. All 698 PRs merged up to 2026-10-17 (docs: Rust port testing policy #2 to obs-qsv11: Host code behind qsv-host.h (#860) #1263), with title, body, linked issues and changed paths, through the GraphQL API. Also the 141 commits that went to master without a PR since 2026-09-01: 90 are upstream OBS commits from the syncs, and the 51 fork commits are all build, CI, test or README work.
2. Filter. A script left out 309 PRs by title prefix (ci:, test:, docs:, ...), by work type (unity groups, precompiled headers, ratchets, oracles, rust: Port ...) or because they change only CI, test or docs paths. 389 candidates were left.
3. Sort. Each candidate was read and sorted as a feature, a fixed upstream bug (a user can notice it: crash, hang, data loss, wrong output, a leak that grows), a fix of the fork's own code (it goes on the line of the feature it fixes), or internal (no symptom a user can notice, for example a sanitizer-only finding). 115 more PRs were internal.
4. Write. One line per feature or per fix, by area, in merge order. The 44 Rust port PRs are one line, "Rust libobs (opt-in)", because the packages still ship the C libobs.
5. Check. Upstream references come from the "(upstream ...)" note in the linked issues' titles, with their repository: 12 lines point to obsproject/obs-websocket, not obs-studio. Every linked issue and PR was checked to exist, and every linked PR to be merged (512 links).

Result: 20 feature lines and 189 lines of fixed upstream bugs, with links to 274 PRs and 238 issues.

Area	Features	Fixed upstream bugs
Headless and automation	5	–
obs-websocket	–	10
GPU status	2	–
Video capture	2	26
Audio	1	20
Encoding, streaming and recording	1	41
Sources and filters	1	35
Scenes and UI	1	32
Scripting	–	5
Performance	1	–
Stability	1	18
Security hardening	–	2
Platforms and packages	5	–

Borderline cases went to "internal" when the PR showed no symptom a user saw: for example the obs_shutdown crash after a failed startup (#1060, seen only as a test flake), the shift UB in DecodeTEA (#208) and the dstr overrun (#53). Each line can move in a later PR; the rule from #1267 keeps the list current from now on.

RED → GREEN

• Not applicable: documentation only.
• Real app: not applicable.

Checklist

• Base is master (or the description starts with a Stacked: note)
• I claimed the issue, or no one else has an open PR for it
• Characterization test (if the unit had none), then RED, then GREEN commits (not applicable: docs only)
• User-visible change: its line in docs/features.md is added or updated
• (Optional) Local gate passed and the pushed head is stamped; otherwise PR CI runs the full suite
• Warning or flag changes (-W..., ratchets): built with scripting ON (a flag change under cmake/ or build-aux/ runs the full builds) and cross-checked with clang and MSVC (not applicable: no flag changes)
• Intentional differences from C listed in the parity test header and rust/README.md (ports) (not applicable: no port)

🤖 Generated with Claude Code