Skip to content

fix(integration): restore codex and memory pipeline contracts - #4474

Merged
diegosouzapw merged 6 commits into
diegosouzapw:release/v3.8.32from
KooshaPari:fix/integration-codex-memory-4436
Jun 21, 2026
Merged

diegosouzapw merged 6 commits into
diegosouzapw:release/v3.8.32from
KooshaPari:fix/integration-codex-memory-4436

Conversation

@KooshaPari

Copy link
Copy Markdown
Contributor

Summary

  • restore the Codex CLI Responses body order so prompt_cache_key is serialized before include
  • make explicit MCP memory search run with a positive retrieval budget even when chat memory injection is disabled by default

Root Cause

Integration Tests (2/2) was failing on upstream main for two unrelated contracts:

  • Codex CLI fingerprinting uses open-sse/config/cliFingerprints.ts as the final serialization order. That order still placed include before prompt_cache_key, so the Codex OAuth Responses integration test observed the wrong key order.
  • omniroute_memory_search reused toMemoryRetrievalConfig() directly. With default settings, memory injection is disabled and the config becomes enabled: false / maxTokens: 0, so an explicit search returned no memories before relevance ranking could run.

Validation

  • node --import tsx/esm --test --test-force-exit --test-concurrency=1 --test-name-pattern "Codex CLI fingerprint" tests/integration/chat-pipeline.test.ts
  • node --import tsx/esm --test --test-force-exit --test-concurrency=1 --test-name-pattern "memory search ranks query-relevant" tests/integration/memory-pipeline.test.ts
  • npx eslint open-sse/config/cliFingerprints.ts open-sse/executors/codex.ts open-sse/mcp-server/tools/memoryTools.ts --quiet
  • npm run typecheck:core -- --pretty false
  • commit/pre-push hooks: docs sync, check:any-budget:t11, tracked artifacts

@gemini-code-assist

Copy link
Copy Markdown
Contributor

Warning

You have reached your daily quota limit. Please wait up to 24 hours and I will start processing your requests again!

@diegosouzapw
diegosouzapw force-pushed the fix/integration-codex-memory-4436 branch from 8af611c to a079455 Compare June 21, 2026 11:58
@diegosouzapw
diegosouzapw marked this pull request as ready for review June 21, 2026 11:58
@diegosouzapw
diegosouzapw self-requested a review as a code owner June 21, 2026 11:58
@diegosouzapw
diegosouzapw changed the base branch from main to release/v3.8.32 June 21, 2026 11:58
@chatgpt-codex-connector

Copy link
Copy Markdown

You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard.

@diegosouzapw
diegosouzapw merged commit 21d61c6 into diegosouzapw:release/v3.8.32 Jun 21, 2026
3 checks passed
diegosouzapw pushed a commit that referenced this pull request Jun 21, 2026
…4464)

Thanks @KooshaPari! Merged the core of this PR (provider-asset shrink + budget gate + usage-rollup same-day cutoff fix + test), rebuilt scoped on release/v3.8.32. On review we dropped the codeqlAlerts 0->1 baseline loosening and the off-topic changes (the codex/memory contract fixes already landed via #4474; getProviderNames removal + cognitive baseline left out). Asset gate passes, rollup 22/22.
@diegosouzapw diegosouzapw mentioned this pull request Jun 21, 2026
diegosouzapw pushed a commit to Witroch4/OmniRoute that referenced this pull request Jun 21, 2026
…ouzapw#4474)

Thanks @KooshaPari! Rebased onto release/v3.8.32 (clean cherry-pick — coexists with diegosouzapw#4467's specialty changes, 118/118 unit + 12/12 memory-pipeline integration). Codex fingerprint ordering + memory-search contract fixes land.

(cherry picked from commit 21d61c6)
diegosouzapw pushed a commit to Witroch4/OmniRoute that referenced this pull request Jun 21, 2026
…iegosouzapw#4464)

Thanks @KooshaPari! Merged the core of this PR (provider-asset shrink + budget gate + usage-rollup same-day cutoff fix + test), rebuilt scoped on release/v3.8.32. On review we dropped the codeqlAlerts 0->1 baseline loosening and the off-topic changes (the codex/memory contract fixes already landed via diegosouzapw#4474; getProviderNames removal + cognitive baseline left out). Asset gate passes, rollup 22/22.

(cherry picked from commit 911e1fb)
@diegosouzapw diegosouzapw mentioned this pull request Jun 22, 2026
5 tasks
tkgo11 pushed a commit to tkgo11/OmniRoute that referenced this pull request Sep 23, 2026
…ouzapw#4474)

Thanks @KooshaPari! Rebased onto release/v3.8.32 (clean cherry-pick — coexists with diegosouzapw#4467's specialty changes, 118/118 unit + 12/12 memory-pipeline integration). Codex fingerprint ordering + memory-search contract fixes land.

(cherry picked from commit bd0344f)
tkgo11 pushed a commit to tkgo11/OmniRoute that referenced this pull request Sep 23, 2026
…iegosouzapw#4464)

Thanks @KooshaPari! Merged the core of this PR (provider-asset shrink + budget gate + usage-rollup same-day cutoff fix + test), rebuilt scoped on release/v3.8.32. On review we dropped the codeqlAlerts 0->1 baseline loosening and the off-topic changes (the codex/memory contract fixes already landed via diegosouzapw#4474; getProviderNames removal + cognitive baseline left out). Asset gate passes, rollup 22/22.

(cherry picked from commit e9bde79)
tkgo11 pushed a commit to tkgo11/OmniRoute that referenced this pull request Sep 23, 2026
…ouzapw#4474)

Thanks @KooshaPari! Rebased onto release/v3.8.32 (clean cherry-pick — coexists with diegosouzapw#4467's specialty changes, 118/118 unit + 12/12 memory-pipeline integration). Codex fingerprint ordering + memory-search contract fixes land.
tkgo11 pushed a commit to tkgo11/OmniRoute that referenced this pull request Sep 23, 2026
…iegosouzapw#4464)

Thanks @KooshaPari! Merged the core of this PR (provider-asset shrink + budget gate + usage-rollup same-day cutoff fix + test), rebuilt scoped on release/v3.8.32. On review we dropped the codeqlAlerts 0->1 baseline loosening and the off-topic changes (the codex/memory contract fixes already landed via diegosouzapw#4474; getProviderNames removal + cognitive baseline left out). Asset gate passes, rollup 22/22.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants