同步request_user_input选项流程

runtime/agents/art-director.toml

@@ -58,17 +58,16 @@ plain text. Follow the **Explain -> Capture** pattern:
 1. **Explain first** -- Write full analysis in conversation: pros/cons, theory,
    examples, pillar alignment.
 2. **Capture the decision** -- Use Codex `request_user_input` with concise labels and
-   short descriptions. User picks an option or uses the free-form Other path.
+   short descriptions. User picks an option or uses a free-form/custom option.
 
 **Codex `request_user_input` requirements:**
 - Ask 1-3 short questions per call.
 - Each question must include `header` (12 or fewer characters), `id` (snake_case),
-  `question` (one sentence), and 2-3 mutually exclusive options.
+  `question` (one sentence), and 2-5 mutually exclusive options.
 - Each option must include `label` (1-5 words) and `description` (one short sentence).
 - Add "(Recommended)" to your preferred option's label when you make a recommendation.
-- Do not add an explicit Other option in Codex app runs; the client supplies the
-  free-form Other path. For app-server integrations, the equivalent free-form
-  option is represented by `isOther`.
+- Use the full meaningful choice set when it fits within five options.
+- Use a free-form/custom option when the decision benefits from custom input.
 - For open-ended questions or file-write confirmations, use conversation instead.
 - If running as a Codex custom-agent subagent, structure text so the orchestrator can
   present the decision through `request_user_input`.

runtime/agents/creative-director.toml

@@ -158,13 +158,12 @@ Follow the **Explain → Capture** pattern:
 **Codex `request_user_input` requirements:**
 - Ask 1-3 short questions per call.
 - Each question must include `header` (12 or fewer characters), `id` (snake_case),
-  `question` (one sentence), and 2-3 mutually exclusive options.
+  `question` (one sentence), and 2-5 mutually exclusive options.
 - Each option must include `label` (1-5 words) and `description` (one short sentence
   with the key trade-off).
 - Add "(Recommended)" to your preferred option's label when you make a recommendation.
-- Do not add an explicit Other option in Codex app runs; the client supplies the
-  free-form Other path. For app-server integrations, the equivalent free-form
-  option is represented by `isOther`.
+- Use the full meaningful choice set when it fits within five options.
+- Use a free-form/custom option when the decision benefits from custom input.
 - For open-ended context gathering, use conversation instead.
 - If running as a Codex custom-agent subagent, structure text so the orchestrator can
   present the decision through `request_user_input`.

runtime/agents/producer.toml

@@ -63,13 +63,12 @@ Follow the **Explain → Capture** pattern:
 **Codex `request_user_input` requirements:**
 - Ask 1-3 short questions per call.
 - Each question must include `header` (12 or fewer characters), `id` (snake_case),
-  `question` (one sentence), and 2-3 mutually exclusive options.
+  `question` (one sentence), and 2-5 mutually exclusive options.
 - Each option must include `label` (1-5 words) and `description` (one short sentence
   with the key trade-off).
 - Add "(Recommended)" to your preferred option's label when you make a recommendation.
-- Do not add an explicit Other option in Codex app runs; the client supplies the
-  free-form Other path. For app-server integrations, the equivalent free-form
-  option is represented by `isOther`.
+- Use the full meaningful choice set when it fits within five options.
+- Use a free-form/custom option when the decision benefits from custom input.
 - For open-ended context gathering, use conversation instead.
 - If running as a Codex custom-agent subagent, structure text so the orchestrator can
   present the decision through `request_user_input`.

runtime/agents/technical-director.toml

@@ -63,13 +63,12 @@ Follow the **Explain → Capture** pattern:
 **Codex `request_user_input` requirements:**
 - Ask 1-3 short questions per call.
 - Each question must include `header` (12 or fewer characters), `id` (snake_case),
-  `question` (one sentence), and 2-3 mutually exclusive options.
+  `question` (one sentence), and 2-5 mutually exclusive options.
 - Each option must include `label` (1-5 words) and `description` (one short sentence
   with the key trade-off).
 - Add "(Recommended)" to your preferred option's label when you make a recommendation.
-- Do not add an explicit Other option in Codex app runs; the client supplies the
-  free-form Other path. For app-server integrations, the equivalent free-form
-  option is represented by `isOther`.
+- Use the full meaningful choice set when it fits within five options.
+- Use a free-form/custom option when the decision benefits from custom input.
 - For open-ended context gathering, use conversation instead.
 - If running as a Codex custom-agent subagent, structure text so the orchestrator can
   present the decision through `request_user_input`.