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: 6139cda76fc6bd4d07a40c8351468364c090e619
• last generated public sync base: 7f514fca918d431635a0ba92a825eb4bd0812cac
• previewed public-tree drift: 2 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@6139cda76fc6bd4d07a40c8351468364c090e619

• Prior destination base: 7f514fc

• Content SHA-256: 0a9c99f245ca6f3b5929664ecdaa6dc22347566ee2a0af6f97bd8ac4c482bc64

• Result: drift_detected; 2 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/telemetry/relay.rs

Drift sample

• copy/update .repository-projection.json
• copy/update packages/local-host-rs/src/telemetry/relay.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@6139cda76fc6bd4d07a40c8351468364c090e619, 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: 95b2c63581

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

Recheck registration before discarding an observation

When an existing relay keeps the hub worker active, a new relay can send Register just after drain_control_messages finishes and then enqueue its first observation before the worker begins or completes the data loop. The worker consumes that observation here while the registration remains queued on the separate control channel, so it silently returns; losing an initial OperationObservation::Admitted or TurnStarted drops the turn ID and experiment assignment and corrupts the resulting telemetry. Handle the pending registration before dropping an unknown relay's message, or serialize registration and observations on one channel.

Useful? React with 👍 / 👎.