11cdc19e39
* test(#3737): use_worktrees=false opt-out must win in the dispatch-isolation sentinel * fix(#3737): fold the workflow.use_worktrees opt-out into the dispatch-isolation record * test(#3737): guard allows sequential dispatch under the opt-out sentinel * chore(#3737): changeset fragment (pr number backfilled after PR creation) * chore(#3737): backfill changeset PR number (3938) --------- Co-authored-by: sim <sim@local>
399 B
399 B
type, pr
| type | pr |
|---|---|
| Fixed | 3938 |
workflow.use_worktrees=false now actually wins for executor dispatch — query dispatch-isolation folds the project opt-out into the isolation sentinel it records, so a plain re-query can no longer re-persist the host's worktree capability over the mandated none record and have the isolation guard deny the sequential dispatch the project configured. (#3737)