Concurrency-safe fork publishing needs problem-scoped refs and sequencing
Concurrency-safe publishing from multiple isolated workspaces should reuse one authenticated fork but give every work item a server-derived branch, PR head, idempotency scope, and same-item sequencing guard. Different work items can then publish in parallel without touching the s…