Feature request: Support generic ACP elicitation/create for structured user input

We are integrating @zed-industries/codex-acp in an ACP client and would like to support the ACP RFD Elicitation: Structured User Input.

Current observation

• codex-acp appears to handle MCP tool approval elicitation specially by converting it into ACP session/request_permission.
• For generic MCP/ACP elicitation form/url requests, the current implementation seems to auto-decline unsupported MCP elicitation instead of forwarding it to the ACP client as elicitation/create.

Expected behavior

When the ACP client declares:

{
  "clientCapabilities": {
    "elicitation": {
      "form": {},
      "url": {}
    }
  }
}

codex-acp should forward supported structured input requests to the client via:

• elicitation/create for form/url requests
• elicitation/complete for URL-mode completion notifications, if applicable

Questions

1. Is generic ACP elicitation/create support planned for codex-acp?
2. If yes, is there an estimated version or milestone?
3. Should clients rely on the current MCP tool approval -> request_permission mapping only, or should we prepare for generic elicitation/create support soon?
4. Would a contribution adding generic form-mode forwarding be acceptable?

Context

We want to support structured user input in an ACP client, including schema-driven forms for decisions, text input, and follow-up questions. Tool approval is already covered by session/request_permission, but generic elicitation requires structured content responses rather than an option ID.