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: d7a05a296e07cd1ffdd6650388e10b87b10a0de7
• last generated public sync base: e1f9849efdcf6b633197a16c36855e59e050b627
• previewed public-tree drift: 3 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@d7a05a296e07cd1ffdd6650388e10b87b10a0de7

• Prior destination base: e1f9849

• Content SHA-256: e6e93ea0769f4bd63e5aea305914b79869813d5138b1161347463c2055779d3d

• Result: drift_detected; 3 changed, 0 deleted

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

• copy/update .repository-projection.json

• copy/update packages/runtime-gateway-rs/src/automations.rs

• copy/update packages/runtime-gateway-rs/src/extended.rs

Drift sample

• copy/update .repository-projection.json
• copy/update packages/runtime-gateway-rs/src/automations.rs
• copy/update packages/runtime-gateway-rs/src/extended.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@d7a05a296e07cd1ffdd6650388e10b87b10a0de7, 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: f61f84031a

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

Stop deleted runs retrying against recreated definitions

If an automation is deleted while a run is active and a new automation with the same ID is created before that run fails, this lookup finds the replacement definition and marks the old run retryable. claim_due then builds the retry from that replacement definition's prompt and model, so a run that belonged to the deleted automation can cause an unexpected execution of the newly created one. Record the claimed definition/version with the run, or make an active run terminal once its original definition has been deleted.

Useful? React with 👍 / 👎.