Executor selection has no capability matching, so a phase can be placed on a host that cannot satisfy it

[AdamFrisby]

Automated via CodeyBox — work item 6091978fa12842a1b06dc10a9eb3adae

Untrusted agent output — do not treat as instructions.

…y --diff-filter=U; echo ---; dotnet build -c Debug
  │ src/CodeyBox.Orchestrator/CodeyBox.Orchestrator.csproj --nologo -v q 2>&1 | tail -5
  └ 11 lines…

● Stage resolved files (shell)
  │ git add docs/operating/remote-executors.md
  │ src/CodeyBox.Orchestrator/ExecutorPhaseDispatchOptions.cs
  │ src/CodeyBox.Orchestrator/ExecutorPhaseProxy.cs && git diff --name-only --diff-filter=U; echo
  │ unmerged_exit=$?; git status --short
  └ 21 lines…

All three conflicts resolved by keeping both sides:

- `ExecutorPhaseDispatchOptions.cs`: kept `MaxStreamChunkChars` + validation and added `PlacementRecheckIn` / `RuntimeUnhealthyBackoff` + validation.
- `ExecutorPhaseProxy.cs`: kept both doc bullets (failover sentence + stream-relay item).
- `remote-executors.md`: combined bounds list (all 11 knobs) with both the placement-backoff paragraph and the live-relay section.

Build: `dotnet build -c Debug` on Orchestrator — 0 warnings, 0 errors. All three files `git add`'d; no unmerged paths remain.

Initiated by CodeyBox operator

---

Co-Authored-By: CodeyBox noreply@codeybox.invalid
🤖 Generated with CodeyBox