chore: sync public mirror from internal

[evalops-mirror]

Summary

• sync the sanitized public tree from dx-corp/mono
• keep dx-corp/code as a generated public mirror of the private source of truth
• preserve public-owned CI and trusted-publishing workflows from the public checkout
• internal source SHA: f0184c6753b3ec240c0e7da694a16886cbecfae7
• last generated public sync base: 1761784b70fe4375102cfe54aa6029e946699ffc
• previewed public-tree drift: 6 file(s) to copy/update and 0 stale file(s) to delete
• public-only commits since last generated sync: 0
• to pause generated syncs while hand-editing this branch, apply the sync-hold label to this PR; the sync workflow skips every push while it is set

Source-of-truth status

Projection: deixic-code

• Source: dx-corp/mono@f0184c6753b3ec240c0e7da694a16886cbecfae7

• Prior destination base: 1761784

• Content SHA-256: cc056cd6ac865d7b0d8e7eae1032e70006f3788e20adc2871696aa27010e94e0

• Result: drift_detected; 6 changed, 0 deleted

• Destination-owned content is preserved. Destination CI is a separate health signal.

• copy/update .repository-projection.json

• copy/update vendor/dex-loop/src/compaction.rs

• copy/update vendor/dex-loop/src/engine.rs

• copy/update vendor/dex-loop/src/event.rs

• copy/update vendor/dex-loop/src/summary.rs

• copy/update vendor/dex-loop/tests/scenarios.rs

Drift sample

• copy/update .repository-projection.json
• copy/update vendor/dex-loop/src/compaction.rs
• copy/update vendor/dex-loop/src/engine.rs
• copy/update vendor/dex-loop/src/event.rs
• copy/update vendor/dex-loop/src/summary.rs
• copy/update vendor/dex-loop/tests/scenarios.rs

Public-only commits since last generated sync

• none detected since last generated sync

Validation

• generated by the sync-public-release-mirror workflow in public-tree mode

Test Plan

• generated by the maestro-sync-public-release-mirror workflow in public-tree mode
• public-source-provenance require-internal-pr confirms internal source PR lineage
• generated mirror PRs use the slim public CI path (fmt/clippy/smoke + provenance); full cargo test/evals already ran on internal main for this SHA
• bot review threads on generated mirror PRs are advisory and do not block the next sync update

Staged Rollout

• Staging is unnecessary for this generated mirror PR: it does not independently promote user-visible behavior. It mirrors already-reviewed internal source from dx-corp/mono@f0184c6753b3ec240c0e7da694a16886cbecfae7, including existing hidden/evaluation surfaces, and keeps public package parity behind the established public-source-provenance gate.

[evalops-mirror]

Resolved 0 review-bot thread(s) on this generated public mirror PR.
Left 0 human-started thread(s) unresolved.

Review of mirrored code belongs on the mono source PR.
See https://github.com/dx-corp/mono/issues/9100 for the triage pattern.

[chatgpt-codex-connector]

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review	Status	Commit	Review trigger
📝 Code Review	✅ Completed 2026-10-07T16:22:23.440854Z	f0fd055	PR opened

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: f0fd055ab8

ℹ️ About Codex in GitHub

Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".

[chatgpt-codex-connector]

Propagate context-capacity errors from the production adapter

This recovery branch is unreachable for actual context-window failures from the production AiRsModel: packages/ai-rs/src/openai.rs reports both HTTP and streamed context-overflow failures as ProviderStreamErrorKind::ProviderDeclaredFailure, while packages/dex-host-rs/src/model.rs converts that kind to ErrorClass::Unknown. The newly extended ErrorClass::of_gateway_code has no production callers (repo-wide search finds only its unit tests), so only the synthetic FakeModel scenarios supply ContextCapacity; real oversized requests still skip compaction and fail immediately. Propagate a typed context-capacity kind/code through the adapter before relying on this equality check.

Useful? React with 👍 / 👎.