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: 36bd59e4bac6e289aaf493f38e26f42fc382c4b3
• last generated public sync base: dccebe04146633d0841585f1d511aceda5ea746d
• previewed public-tree drift: 4 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@36bd59e4bac6e289aaf493f38e26f42fc382c4b3

• Prior destination base: dccebe0

• Content SHA-256: 78b16e2e7b3b23f64ba5345cbae3d36206cdf4d1df28f1756e5ecf53cfb2d4ea

• Result: drift_detected; 4 changed, 0 deleted

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

• copy/update .repository-projection.json

• copy/update packages/local-host-rs/src/model_catalog_data.json

• copy/update packages/local-host-rs/src/model_facts_generated.rs

• copy/update packages/local-host-rs/src/model_facts_resolution.generated.json

Drift sample

• copy/update .repository-projection.json
• copy/update packages/local-host-rs/src/model_catalog_data.json
• copy/update packages/local-host-rs/src/model_facts_generated.rs
• copy/update packages/local-host-rs/src/model_facts_resolution.generated.json

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@36bd59e4bac6e289aaf493f38e26f42fc382c4b3, 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

Here are some automated review suggestions for this pull request.

Reviewed commit: 669c7f248d

ℹ️ 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]

Drop the synthetic 90% output limit

235,929 is 90% (rounded down) of this row’s 262,144-token context window—the OpenRouter fallback that distinctOutputTokens documents as not being a vendor output limit—yet its exact Math.round(context * 0.9) check only rejects 235,930. This refresh therefore replaces the previous 32K cap with 235,929 (and does the same for qwen/qwen3-next-80b-a3b-instruct); default_max_output_tokens and ModelLimits::for_model propagate that value, so prompts/tool schemas exceeding the fixed 8,192-token reserve can be sent with an output budget larger than the remaining context and receive provider 400s. Treat the rounded-down 90% value as absent and regenerate the snapshot.

Useful? React with 👍 / 👎.