fix: forward delegated context to Codex app-server threads

[09473ZH]

Delegated tasks put their context in ephemeral_system_prompt, but the Codex app-server runtime only forwarded the goal. A real three-rule evaluation returned an empty judgment list despite receiving a nonempty context argument.

Pass the scoped ephemeral instructions through developerInstructions on thread start/resume. Omit the field when unset so server configuration remains authoritative, and initialize it once per session.

Validation: nine focused lifecycle/start/resume and runtime wiring tests passed; Ruff and diff checks passed. With the changed modules loaded only inside an isolated process, the original delegate_task(context=...) request on the account's gpt-5.6-sol / openai-codex / codex_app_server returned hit, no_hit and unknown correctly, with no tool calls. The broader session suite stalled after 26 cases and was stopped; no full-suite success is claimed. No running gateway modules were replaced. The CI Python slices now pass after correcting the runtime stub and adding the existing contributor email mapping; desktop E2E failed in two existing mock-backend background-dot checks (sidebar-states / tile-unread-bug). These tests configure provider=mock; their relationship to this Codex-only change is not established. CI is not fully green and no deployment is claimed.

The instructions become part of the Codex thread rather than only Hermes' transient prompt; callers should treat delegated input as retained thread content. Harness rollout requires a separate pin update.

Related: CorgiCortex/Qortex-Trading-Harness#175, CorgiCortex/Qortex-Trading-Harness#164.

[09473ZH]

关闭此方案，不合并 Hermes 源码补丁。已由 CorgiCortex/Qortex-Trading-Harness#196 替代并合并：自然语言规则使用自包含 delegate_task(goal=...) 传递冻结规则和事实，现有 Hermes 锁定版本上的真实模型及隔离 Runtime 验证已通过。无需新增 Hermes 私有补丁。