Repository navigation
0.1.8 Beta6: Define the real Codex-to-Chat runtime-field and V2 item contract #253
Description
This was generated by AI during triage and updated by the approved Beta6 scope decision.
Parent
What to build
Define and verify the exact Codex runtime-field and item adaptation contract consumed by the three Beta6 Ollama Chat tracer bullets #285, #286, and #396 and the generic Chat Collaboration V2 implementation #394.
Every observed value/item is preserved, consumed locally, mapped through an approved reversible equivalent, or rejected before upstream I/O; wholesale key deletion is not accepted.
Acceptance criteria
- 0.1.8 Beta6: Complete the GLM-5.2 Ollama Chat and V2 CLI path #285, 0.1.8 Beta6: Complete the K2.7 Code Ollama Chat and V2 CLI path #286, and 0.1.8 Beta6: Complete the DeepSeek V4 Flash 0731 Chat CLI path #396 satisfy the field/item contract on real CLI Ollama Chat paths.
-
client_metadataandprompt_cache_keyare consumed locally with no semantic claim to the upstream. -
store=falseis accepted only on a non-storing route;store=truefails unless equivalent behavior is proven. - Plain-text configuration is mapped; unsupported structured text fails visibly.
- Requested
includevalues are classified independently. - The complete V2 direct-tool, call/result, task identity, message/
agent_message, history, and replay fields follow 0.1.8 Beta6: Generate the runtime-derived Chat and Collaboration V2 conversion matrix #66/0.1.8 Beta6: Implement generic Collaboration V2 over Chat Completions #394 without V1 downgrade. - Unknown future values/items fail before upstream I/O.
- Chat Code Mode/custom/freeform, client
tool_search, arbitrary namespaces, search, and hosted semantics remain unavailable unless separately proven reversible.
Activity
5 remaining items
[-]0.1.8 Beta4: Define the real Codex-to-Chat runtime-field contract[/-][+]0.1.8 Beta5: Define the real Codex-to-Chat runtime-field contract[/+][-]0.1.8 Beta5: Define the real Codex-to-Chat runtime-field contract[/-][+]0.1.8 Beta6: Define the real Codex-to-Chat runtime-field contract[/+][-]0.1.8 Beta6: Define the real Codex-to-Chat runtime-field contract[/-][+]0.1.8 Beta6: Define the real Codex-to-Chat runtime-field and V2 item contract[/+]NOirBRight commentedon Aug 19, 2026
Campaign rewrite from #441: this contract ticket is now blocked only by #66. #285 / #286 / #396 consume the contract; they do not block it.
NOirBRight commentedon Aug 19, 2026
Contract source is now the #66 matrix (ac1a27e, docs/evidence/issue-66/chat-conversion-matrix.json). Field/value dispositions live there. Remaining #253 work is Provider verification after #442/#394, not a second classification table.
NOirBRight commentedon Aug 19, 2026
Completed by the generic #66/#394 contract plus final authenticated Provider proof.
Contract evidence:
docs/evidence/issue-66/chat-conversion-matrix.jsonclassifies transport fields, values, items, V2, custom adapters, unavailable semantics, unknowns, and no-fallback invariants.prepare_exchangetests cover consumedclient_metadata/prompt_cache_key, non-storingstore=false, rejection ofstore=true, text/include value classification, and unknown-value fail-closed behavior.docs/evidence/authenticated-provider/chat/summary.json(evidence commitc82baad, source73e4ed3) proves all three exact Ollama Chat cells consume that contract through realcodex-cli 0.147.0, with exact standard/custom identity, phased six-tool V2, fallback=0, and V1=false.The custom/freeform ceiling is explicit: exact text-format custom tools are reversible only with
accepts_custom_adapter; absent capability or malformed envelopes fail closed. No model/Provider-specific conversion branch was added.