@oneciel-ai/ciel-runtime 0.2.22 → 0.2.23

package/docs/journal/2026/08/21/transcript-compaction-external-events.okf

@@ -0,0 +1,131 @@
+okf_version: "1.0"
+knowledge:
+  task:
+    id: transcript-compaction-external-events-20260821
+    date: "2026-08-21"
+    objective: >-
+      Determine whether ciel-runtime can expose transcript content from before
+      and after a client compaction as externally consumable events.
+
+  confirmed_current_state:
+    transcript_repository:
+      file: ciel_runtime_support/channel_transcript_repository.py
+      capability: >-
+        Discovers Claude and Codex transcript JSONL files and incrementally
+        reads complete records appended after a captured byte offset.
+    claude_detection:
+      file: ciel_runtime_support/channel_transcript.py
+      capability: >-
+        Recognizes Claude compact-summary records through isCompactSummary and
+        distinguishes them from normal user turns.
+    claude_hooks:
+      file: ciel_runtime_support/tool_guard_hooks.py
+      capability: "Installs both PreCompact and PostCompact hook events."
+    codex_control:
+      file: ciel_runtime_support/codex_app_server.py
+      capability: >-
+        Can request thread/compact/start and receives app-server notifications,
+        but its tracked state currently covers thread and turn lifecycle only.
+    runtime_compaction_events:
+      files:
+        - ciel_runtime_support/prompt_compaction.py
+        - ciel_runtime_support/context_compaction.py
+        - ciel_runtime_support/runtime_activity_repository.py
+      capability: >-
+        Publishes context.compact events with counts, token totals, phase,
+        budget, and retained or omitted message counts. It does not publish the
+        before or after transcript content.
+    externally_consumable_sse:
+      file: ciel_runtime_support/router_http.py
+      endpoint: /ca/events/stream
+      capability: >-
+        Streams EventBus records to connected SSE consumers and supports replay
+        from a supplied event ID while records remain in the in-memory buffer.
+    external_event_receiver:
+      file: ciel_runtime_support/external_event_receiver.py
+      direction: inbound_only
+      capability: >-
+        Receives CloudEvents through webhook or SSE and submits them as runtime
+        inputs. It is not an outbound webhook publisher.
+
+  implementation:
+    delivery_service:
+      file: ciel_runtime_support/transcript_delta_delivery.py
+      event_type: ai.oneciel.ciel-runtime.transcript.delta
+      behavior:
+        - "Reads from a durable per-destination and per-transcript byte offset."
+        - "Sends only complete newline-terminated JSONL records."
+        - "Advances the cursor only after an HTTP 2xx response."
+        - "Retries an unchanged batch with the same deterministic event ID."
+        - "Restarts at byte zero with rotated=true after transcript truncation."
+        - "Expands authorization environment references at send time."
+    runtime_wiring:
+      file: ciel_runtime.py
+      behavior: >-
+        Starts the daemon delivery worker when a Claude or Codex transcript
+        scope is established for the running workspace.
+    configuration:
+      command: >-
+        ciel-runtimectl transcript-events enabled=true
+        url=https://memory.example/v1/transcripts
+        authorization='Bearer {MEMORY_TOKEN}' start_mode=tail
+      keys:
+        - enabled
+        - url
+        - authorization
+        - timeout_seconds
+        - poll_interval_ms
+        - max_batch_bytes
+        - start_mode
+
+  event_contract:
+    envelope: CloudEvents 1.0 structured JSON
+    content_type: application/cloudevents+json
+    idempotency_header: Idempotency-Key
+    data_fields:
+      - workspace_id
+      - runtime
+      - session_id
+      - transcript_name
+      - start_offset
+      - end_offset
+      - content_sha256
+      - record_count
+      - rotated
+      - format
+      - content
+
+  verification:
+    automated:
+      focused:
+        transcript_delta_delivery: "4 passed"
+        event_settings_cli: "28 passed"
+        cli_parser: "5 passed"
+      full_groups:
+        unit: "1129 passed, 44 skipped"
+        router: "906 passed"
+        channel: "381 passed, 80 skipped"
+        runtime: "252 passed, 12 skipped"
+      aggregate: "2668 passed, 136 skipped"
+    live_http:
+      result: LIVE_TRANSCRIPT_DELIVERY_OK
+      observation: >-
+        A local HTTP server received exactly two newly appended records. The
+        old 11-byte record was skipped in tail mode, offsets were
+        11->23->35, and the persisted final cursor was 35.
+      authorization: "Bearer environment reference expanded at send time"
+      idempotency: "Idempotency-Key matched the CloudEvent event ID"
+    cli_boundary:
+      result: CLI_TRANSCRIPT_SETTINGS_OK
+      observation: >-
+        The executable command stored the settings and its status output
+        rendered authorization=stored without printing the configured value.
+
+  answer:
+    feasible: true
+    implemented_now: true
+    incremental_unit: byte_offset_over_complete_jsonl_records
+    compaction_relation: >-
+      Delivery is continuous and independent of a provider-specific compaction
+      callback. Transcript records written before and after compaction are
+      therefore delivered through the same ordered offset stream.

package/docs/journal/2026/08/21/wing-ai-net-mcp-boundary-diagnosis.okf

@@ -0,0 +1,129 @@
+okf_version: "1.0"
+knowledge:
+  task:
+    id: wing-ai-net-mcp-boundary-diagnosis-20260821
+    date: "2026-08-21"
+    objective: >-
+      Determine from live Wing evidence whether the reported AI-Net MCP load
+      failure is caused by the AI-Net installation script or by Ciel Runtime.
+    mutation_scope:
+      runtime_code_changed: false
+      wing_configuration_changed: false
+      diagnostic_mcp_sessions_only: true
+
+  environment:
+    wing:
+      host: WING
+      user: "wing\\daniel.yun"
+      tailscale_address: 100.124.160.62
+      ssh_port: 1004
+      workspace: "C:\\Users\\daniel.yun.WING"
+    versions:
+      ciel_runtime: 0.2.22-nightly.20260821-172735.c8d920e
+      codex_cli: 0.149.0
+
+  evidence:
+    active_ciel_launch:
+      command_line_url: "http://100.94.212.25:3603/mcp"
+      bearer_token_env_var: AINET_API_KEY
+      push_header_env_var: AINET_MCP_PUSH
+      api_key_process_present: true
+      api_key_user_present: true
+      api_key_length_observed: 75
+      secret_value_recorded: false
+    installed_code_integrity:
+      workspace_mcp_sha256:
+        local: C79DE505E5CA27DF0562DC006038CB68DAB1B2D1FA010D4E9160B1B38384AAAF
+        wing: C79DE505E5CA27DF0562DC006038CB68DAB1B2D1FA010D4E9160B1B38384AAAF
+      runtime_launch_sha256:
+        local: D77717369068881329488C6BB9441D1A3E5CB86D6F929CD21972589805580B4A
+        wing: D77717369068881329488C6BB9441D1A3E5CB86D6F929CD21972589805580B4A
+    ai_net_installer:
+      url: "http://100.94.212.25:3600/api/v1/integrations/codex-mcp/setup.ps1"
+      fetched_length: 12821
+      fetched_sha256: 2EF7A4FB8D50D8E45A8E5752D5C13BC1807F2E4BEC8CBC89B8940C9121704405
+      declared_default_endpoint: "http://100.94.212.25:3603/mcp"
+      declared_v2_opt_in: AINET_MCP_V2=1
+      declared_v2_endpoint: "http://100.94.212.25:3603/v2/mcp"
+      declared_v2_protocol: "2026-07-28 only"
+      persistent_auth_behavior: >-
+        The script writes literal Authorization and X-AI-Net-Push headers into
+        the native Codex config. No credential value is copied into this journal.
+    wing_install_history:
+      observed_sequence:
+        - "$env:AINET_MCP_V2=\"1\""
+        - "irm http://100.94.212.25:3600/api/v1/integrations/codex-mcp/setup.ps1 | iex"
+      native_codex_config_written_at_utc: "2026-08-21T17:38:30.2627753Z"
+      resulting_native_url: "http://100.94.212.25:3603/v2/mcp"
+      resulting_native_static_headers:
+        - Authorization
+        - X-AI-Net-Push
+    endpoint_probes:
+      legacy_mcp_without_push_off:
+        requested_protocol: "2025-03-26"
+        http_status: 200
+        session_created: true
+      legacy_mcp_with_push_off:
+        requested_protocol: "2025-03-26"
+        http_status: 200
+        session_created: true
+      v2_with_legacy_protocol:
+        requested_protocol: "2025-06-18"
+        http_status: 400
+        mcp_error_code: -32022
+        server_supported_protocol: "2026-07-28"
+      legacy_tools_list:
+        requested_protocol: "2025-06-18"
+        initialize_status: 200
+        initialized_notification_status: 202
+        tools_list_status: 200
+        tool_count: 35
+        get_messages_present: true
+        send_message_present: true
+    active_codex_log:
+      process_id: 15544
+      thread_id: 01a024fe-7666-79e3-9c1a-98f46e26af5f
+      observed_server: ai-net
+      observed_rpc_errors:
+        resources_list: "-32601 Method not found"
+        resource_templates_list: "-32601 Method not found"
+      interpretation: >-
+        These RPC responses prove that the active Codex MCP client reached the
+        AI-Net server. They are unsupported resource-method errors, not MCP
+        initialization or authentication failures.
+    current_ciel_change_scope:
+      code_commit: fe7c4b09ad4178adabc73162b3c6dc2cbb5870f2
+      journal_commit: c8d920e3e52eafd1642ace01206734c538574824
+      mcp_files_changed_by_these_commits: false
+      changed_area: Alibaba Singapore Qwen3.8 provider configuration
+
+  findings:
+    native_codex:
+      status: incompatible_configuration
+      cause_confirmed: >-
+        AINET_MCP_V2=1 caused the AI-Net installer to persist /v2/mcp. That
+        endpoint rejects the protocol used by Codex 0.149 with -32022.
+      responsible_boundary: ai_net_installer_v2_opt_in_configuration
+    ciel_managed_codex:
+      status: ai_net_mcp_loaded
+      evidence: >-
+        Ciel overrides the URL to /mcp; that endpoint initializes successfully,
+        lists 35 tools, and the active Codex process receives AI-Net RPC replies.
+      load_failure_caused_by_current_ciel_change: false
+    visible_resource_errors:
+      status: server_method_not_supported
+      cause_confirmed: >-
+        AI-Net exposes tools but does not implement the MCP resource listing
+        methods requested by Codex's generic resource commands.
+
+  conclusion:
+    confirmed: >-
+      The native Codex load problem is produced by the installer invocation's
+      AINET_MCP_V2=1 setting and the resulting /v2/mcp protocol mismatch. The
+      active Ciel-managed Wing session is using /mcp and has loaded AI-Net MCP.
+      Current Ciel Runtime changes are not the cause of the observed native
+      protocol failure.
+    not_claimed:
+      - No claim is made that every historical Wing session had the same state.
+      - No configuration or runtime process was restarted during this diagnosis.
+      - No code fix is included because the requested task was diagnosis.

package/docs/journal/2026/08/21/wing-cold-start-wake-submit-repair.okf

@@ -0,0 +1,161 @@
+okf_version: "1.0"
+knowledge:
+  task:
+    id: wing-cold-start-wake-submit-repair-20260821
+    date: "2026-08-21"
+    objective: >-
+      Diagnose and repair the WING cold-start condition where the first external
+      SSE message is rendered in the Codex input editor but is not submitted.
+
+  evidence:
+    host: "WING"
+    user: "wing\\daniel.yun"
+    workspace: "C:\\Users\\daniel.yun.WING"
+    installed_version: "0.2.22-nightly.20260821-200044.511148d"
+    runtime_mode: "codex-router"
+    transport: "conpty"
+    active_session: "01a024fe-7666-79e3-9c1a-98f46e26af5f"
+    message:
+      id: 1236
+      kind: external_event
+      event_type: net.ai-net.connected
+      persisted_at: "2026-08-21T15:12:43"
+    router_log:
+      path: >-
+        C:\Users\daniel.yun.WING\AppData\Roaming\ciel-runtime\
+        router-instances\9140-f895679997f4\router.log
+      observations:
+        - "15:12:44 channel_windows_console_proxy_started transport=conpty"
+        - "15:12:54 channel_input_prompt_ready result=timeout"
+        - "15:12:55 channel_stdin_proxy_submit_confirmed attempt=1"
+        - "15:13:12 channel_windows_console_unseen_retry message_id=1236"
+        - "15:13:13 channel_input_prompt_ready result=observed"
+        - "15:13:14 channel_stdin_proxy_submit_confirmed attempt=1"
+        - "15:13:32 channel_windows_console_body_fallback message_id=1236"
+      absent_evidence:
+        - >-
+          No POST /backend-api/codex/responses occurred after message 1236 was
+          injected and before the body fallback.
+
+  confirmed_cause:
+    - >-
+      WindowsConPtySession.wait_until_prompt_ready accepted any child-output
+      change after injection; it did not require evidence that the injected
+      prompt itself had rendered.
+    - >-
+      ChannelPromptInjector submitted Enter after a prompt-ready timeout and
+      treated an unrelated output-tail change as submit confirmation.
+    - >-
+      The SSE event was received and durably persisted. The failure boundary
+      was the cold-start TTY submit path, not SSE receipt or message storage.
+    - >-
+      WING live message 1238 proved that occurrence-count comparison is not
+      valid for the 64 KiB rolling ConPTY output tail. The same prompt rendered
+      twice, at 15:44:57 and 15:45:27, while both waits timed out and no Enter
+      was submitted. A previous occurrence can roll out as a new occurrence
+      enters, leaving the count unchanged.
+    - >-
+      WING fresh-session message 1239 was admitted at 16:00:32, while Codex
+      finished its startup rendering at the 16:01:02 timeout boundary. The
+      injector correctly withheld Enter, but the pending-delivery layer still
+      recorded the message as injected and retained its claim. Logs then
+      repeated state=unknown instead of retrying.
+    - >-
+      WING fresh-session message 1240 retried at 16:15:29, 16:15:59, and
+      16:16:30 after claim rollback. The exact visible prefix contained two
+      spaces between the wake header and the external-event marker because the
+      source prompt has a blank line. Prompt detection incorrectly collapsed
+      that pair to one space, so every real render was rejected.
+
+  correction:
+    files:
+      - ciel_runtime_support/channel_injection.py
+      - ciel_runtime_support/windows_conpty.py
+      - tests/test_channel_injection.py
+      - tests/test_windows_conpty.py
+    behavior:
+      - >-
+        Prompt readiness now captures the ConPTY absolute output-byte position
+        before writing input and searches only bytes emitted after that
+        checkpoint for the prompt prefix or [Pasted Content ...] marker.
+      - >-
+        Rolling-tail eviction and repeated rendering of the same prompt can no
+        longer hide new render evidence.
+      - >-
+        A prompt-render timeout defers Enter instead of reporting a false
+        submission.
+      - >-
+        Prompt injection now returns an explicit submitted result. When render
+        readiness times out, pending delivery rolls back the wake claim, does
+        not record the prompt or injected id, and leaves the cursor unchanged
+        so the next idle scan retries the complete body and Enter.
+      - >-
+        Prompt-render matching now uses the same normalize_prompt operation as
+        the injected body. Blank lines therefore remain the same two visible
+        spaces in both the expected prefix and captured ConPTY output.
+      - >-
+        No WING, user, message, model, provider, or agent-specific exception was
+        introduced.
+
+  verification:
+    focused:
+      channel_injection: "6 passed"
+      windows_conpty: "18 passed"
+      channel_bridge: "207 passed, 80 skipped"
+      channel_injection_architecture: "4 passed"
+      codex_runtime: "69 passed, 12 skipped"
+      ruff: passed
+    full_npm_test:
+      unit: "1120 passed, 44 skipped"
+      router: "906 passed"
+      channel: "381 passed, 80 skipped"
+      runtime: "249 passed, 12 skipped"
+      total: "2656 passed, 136 skipped"
+    first_nightly:
+      version: "0.2.22-nightly.20260821-203346.87525c6"
+      commit: "87525c6bbb83d9483d30a1d3b54c0b1c73599c7c"
+      result: >-
+        Installed locally and on WING. Live message 1238 exposed the rolling
+        output-tail evidence defect above, so this build was not accepted as
+        complete.
+    second_nightly:
+      version: "0.2.22-nightly.20260821-205641.fad60f5"
+      commit: "fad60f54ab1b0998d2495ff34948716cfbaf70b2"
+      result: >-
+        Installed locally and on WING. Fresh-session message 1239 exposed the
+        missing submission-result propagation and claim rollback above, so
+        this build was not accepted as complete.
+    third_nightly:
+      version: "0.2.22-nightly.20260821-211233.f357b91"
+      commit: "f357b91c7ae21079d45f5458a01f72f026341f50"
+      result: >-
+        Installed locally and on WING. Fresh-session message 1240 proved claim
+        rollback and periodic retry worked, then exposed the blank-line
+        whitespace mismatch above, so this build was not accepted as complete.
+    fourth_nightly:
+      version: "0.2.22-nightly.20260821-212609.39f1119"
+      commit: "39f11192101fbd631d5475c9274e5ce69720d589"
+      ci_run: "https://github.com/OneCielAI/ciel-runtime/actions/runs/32528301706"
+      publish_run: "https://github.com/OneCielAI/ciel-runtime/actions/runs/32528301741"
+      result: accepted_by_wing_live_verification
+    wing_live:
+      session: "01a02639-b0aa-7530-9115-8084007b2754"
+      message_id: 1241
+      event_id: "evt_wing_first_message_verify_39f1119"
+      persisted_at: "2026-08-21T16:29:17"
+      evidence:
+        - "16:29:21 channel_input_prompt_ready result=observed"
+        - "16:29:22 channel_stdin_proxy_submit_confirmed attempt=1"
+        - "16:29:22 channel_stdin_proxy_injected message_ids=1241 enter=cr"
+        - "16:29:25 channel_llm_injected message_ids=1241"
+        - "16:29:30 POST /v1/responses HTTP/1.1 200"
+        - "16:29:33 channel_wake_completed_evidence message_id=1241"
+        - "16:29:33 channel_windows_console_confirmed message_id=1241 cursor=1241"
+        - "Codex terminal rendered the exact response WING_FIRST_MESSAGE_OK"
+    deployment:
+      local_version: "0.2.22-nightly.20260821-212609.39f1119"
+      wing_version: "0.2.22-nightly.20260821-212609.39f1119"
+      windows_conpty_sha256: >-
+        5EE8FE12A9C7D680025B538F9EF8253BCAC2F5E285B942A56D5A758A6371E915
+      local_package_and_runtime_hash_match: true
+      local_and_wing_hash_match: true

package/docs/journal/2026/08/21/wing-powershell-memory-runaway.okf

@@ -0,0 +1,101 @@
+okf_version: "1.0"
+knowledge:
+  task:
+    id: wing-powershell-memory-runaway-20260821
+    date: "2026-08-21"
+    objective: >-
+      Identify the exact PowerShell command that consumed more than 63 GB on
+      WING, terminate only the runaway diagnostic process, and preserve the
+      evidence without attributing an unverified internal mechanism.
+
+  evidence:
+    host: WING
+    process:
+      image: powershell.exe
+      pid: 7940
+      created: "2026-08-21 15:18:53 WING local time"
+      working_set_mb: 63269.96
+      private_memory_gb: 120.711
+      command_mode: "-NoProfile -NonInteractive -EncodedCommand"
+    windows_event:
+      provider: Microsoft-Windows-Resource-Exhaustion-Detector
+      event_id: 2004
+      observations:
+        - >-
+          20:49:10: powershell.exe PID 7940 consumed 129,961,250,816
+          bytes of virtual memory.
+        - >-
+          Repeated event 2004 records from 19:52:01 through 20:49:10 identify
+          the same PID as the largest virtual-memory consumer.
+    local_codex_record:
+      file: >-
+        C:\Users\djlov\.codex\sessions\2026\08\20\
+        rollout-2026-08-20T11-44-17-01a0200f-2245-7cc1-8219-85d745a719a8.jsonl
+      line: 13109
+      timestamp_utc: "2026-08-21T20:18:50.122Z"
+      result_at_20_seconds: "no output; remote process remained running"
+
+  exact_diagnostic_script:
+    purpose: >-
+      Read selected router events, the last 12 runtime inputs, and the last
+      1,200 Codex session records, then serialize a compact JSON report.
+    sources:
+      router_log: >-
+        C:\Users\daniel.yun.WING\AppData\Roaming\ciel-runtime\
+        router-instances\9140-f895679997f4\router.log
+      input_log: >-
+        C:\Users\daniel.yun.WING\AppData\Roaming\ciel-runtime\
+        workspaces\f895679997f4\runtime-inputs.jsonl
+      session_log: >-
+        C:\Users\daniel.yun.WING\.codex\sessions\2026\08\21\
+        rollout-2026-08-21T10-44-11-01a024fe-7666-79e3-9c1a-98f46e26af5f.jsonl
+    critical_expression: >-
+      Get-Content -LiteralPath $sessionLog -Tail 1200
+
+  isolation:
+    router_tail:
+      expression: "Get-Content router.log -Tail 1000 plus event filter"
+      result: "11 records in 206 ms"
+    input_tail:
+      expression: "Get-Content runtime-inputs.jsonl -Tail 12 plus JSON parsing"
+      result: "12 records in 281 ms"
+    session_tail:
+      expression: "Get-Content session JSONL -Tail 1200 without JSON parsing"
+      result: >-
+        Did not complete within 10 seconds; a new service-session PowerShell
+        process remained alive and its working set rose from 61,512 KB to
+        67,352 KB before termination.
+    session_file:
+      bytes: 8055707
+      lines: 2893
+      maximum_line_bytes: 281563
+      line_endings: "LF=2893, CR=0"
+      null_bytes: 0
+    excluded:
+      - >-
+        The three source files total approximately 10 MB, so source file size
+        alone does not account for the observed 63 GB working set.
+      - >-
+        ConvertFrom-Json and ConvertTo-Json are downstream of the independently
+        reproduced stall and are not required to reproduce it.
+
+  confirmed_cause_scope: >-
+    The runaway is reproduced at Windows PowerShell 5.1.20348.4294 executing
+    Get-Content -Tail 1200 against the identified Codex LF-only JSONL file.
+    Available evidence does not establish the deeper internal PowerShell
+    implementation defect, so no more specific mechanism is asserted.
+
+  remediation:
+    pid_7940: "terminated"
+    reproduction_pid_18032: "terminated"
+    aborted_measurement_pid_18700: "terminated"
+    remaining_powershell: >-
+      PID 10808 in the user's RDP session, approximately 105 MB; not modified.
+    final_check:
+      runaway_process_present: false
+      free_physical_memory_kb: 40509592
+
+  accountability: >-
+    The diagnostic command was issued by this Codex session. It exceeded the
+    20-second observation window, and failure to immediately follow up and
+    terminate the still-running remote process allowed it to remain active.

package/docs/journal/2026/08/21/wing-repeated-reasoning-tool-turn-repair.okf

@@ -0,0 +1,112 @@
+okf_version: "1.0"
+knowledge:
+  task:
+    id: wing-repeated-reasoning-tool-turn-repair-20260821
+    date: "2026-08-21"
+    objective: >-
+      Determine from live Wing evidence why a routed Codex session repeatedly
+      restarts the same reasoning after Ciel reports a reasoning-only upstream
+      response, then correct the general protocol boundary.
+    scope:
+      machine_exception_added: false
+      user_exception_added: false
+      provider_name_exception_added: false
+
+  environment:
+    wing:
+      host: WING
+      user: "wing\\daniel.yun"
+      tailscale_address: 100.124.160.62
+      ssh_port: 1004
+      workspace: "C:\\Users\\daniel.yun.WING"
+    affected_runtime:
+      version: 0.2.22-nightly.20260821-172735.c8d920e
+      provider: ollama-cloud
+      upstream_model: "deepseek-v4-pro:0813"
+      transcript: >-
+        C:\Users\daniel.yun.WING\.codex\sessions\2026\08\21\
+        rollout-2026-08-21T10-44-11-01a024fe-7666-79e3-9c1a-98f46e26af5f.jsonl
+      router_log: >-
+        C:\Users\daniel.yun.WING\AppData\Roaming\ciel-runtime\
+        router-instances\9139-f895679997f4\router.log
+
+  evidence:
+    live_router:
+      reasoning_only_markers:
+        - "2026-08-21T14:02:35"
+        - "2026-08-21T14:02:41"
+      observed_classification: preamble_only
+      request_growth:
+        first_observed_tokens: 59879
+        later_observed_tokens: 61480
+        first_observed_bytes: 247671
+        later_observed_bytes: 254077
+      historical_blocks_discarded:
+        earlier_pair_count: 509
+        later_pair_count: 551
+        log_marker: discarded unmatched historical Anthropic tool blocks
+    transcript_sequence:
+      inspected_lines: "2460-2590"
+      repeated_tools:
+        - list_mcp_resources
+        - list_mcp_resource_templates
+      call_arguments_sha256_prefix: 44136FA355B3678A
+      resources_result_sha256_prefix: 5470BCB5A8C4539D
+      templates_result_sha256_prefix: 87854A2460A872FF
+      repeated_reasoning_sha256_prefixes:
+        - E38C5BDE35754197
+        - 3CD26012D6413F6E
+      confirmed_behavior: >-
+        The same reasoning, the same two empty-argument tool calls, and the same
+        two tool results recur with only newly generated call IDs. The tools were
+        actually executed; this was not a display-only repetition.
+    source_boundary:
+      responses_projection: >-
+        openai_responses_to_anthropic_messages emitted each consecutive
+        function_call as a separate assistant message and each consecutive
+        function_call_output as a separate user message.
+      provider_normalization: >-
+        normalize_historical_anthropic_tool_turns retains a tool use only when
+        the immediately following user message contains its matching result.
+      confirmed_interaction: >-
+        For the observed Responses order of call, call, result, result, neither
+        assistant message was immediately followed by its matching user result.
+        The normalizer therefore removed both calls and both results before the
+        next upstream request.
+    regression_test:
+      before_repair: >-
+        test_parallel_responses_tool_turn_survives_provider_normalization failed;
+        normalized roles were [assistant] instead of [assistant, user].
+      after_repair: >-
+        Provider wire normalization passed 6 tests and Codex turn recovery
+        passed 29 tests.
+
+  repair:
+    tool_turn_projection: >-
+      Consecutive Responses function calls are grouped into one Anthropic
+      assistant turn, and consecutive outputs are grouped into one Anthropic
+      user turn. Matching call IDs and result IDs therefore survive the existing
+      strict provider normalization.
+    reasoning_only_recovery: >-
+      Reasoning-only content shape is recognized independently of provider
+      name. The synthetic runtime notice is excluded from retry history, one
+      bounded continuation is performed, and either real tool work or a visible
+      final answer may complete the recovery.
+    invariants:
+      - Recovery remains bounded to one extra upstream call.
+      - Empty responses after recovery preserve the original notice.
+      - Kimi follow-up-promise wording remains Kimi-specific.
+      - No Wing, user, model, CLI, or agent exception was introduced.
+
+  verification:
+    focused:
+      provider_wire_normalization: "6 passed"
+      codex_turn_recovery: "29 passed"
+      ruff: passed
+      git_diff_check: passed
+    complete_groups:
+      unit: "1113 passed, 44 skipped"
+      router: "906 passed"
+      channel: "379 passed, 80 skipped"
+      runtime: "248 passed, 12 skipped"
+      total: "2646 passed, 136 skipped"