Route API docs to the website branch matching the compiler major
Why
Following the website default branch lets v13 compiler prereleases update stable v12 API docs. The target must follow the compiler package version through website promotions and maintenance branch cuts.
Select v<major> for API checks and publication, push to that branch explicitly, and cover maintenance branches in CI. Test release promotion and branch cuts without changing the API documentation destination.