Promote multi-harness flag to prod

[liliwilson]

Summary

Enable agent_harness by default for stable clients, for orchestration launch.

Co-Authored-By: Oz oz-agent@warp.dev

Conversation: https://staging.warp.dev/conversation/8a0111a3-0ada-4e49-aa47-928c5fff2f3e
Run: https://oz.staging.warp.dev/runs/019e2c9c-6df1-75dc-b32e-794e3ab11b69
This PR was generated with Oz.

[oz-for-oss]

@liliwilson

I'm starting a first review of this pull request.

You can view the conversation on Warp.

I completed the review and no human review was requested for this pull request.

Comment /oz-review on this pull request to retrigger a review (up to 3 times on the same pull request).

Powered by Oz

[oz-for-oss]

Overview

Promotes agent_harness to the default Cargo feature set and removes FeatureFlag::AgentHarness from the dogfood-only runtime flags. The existing enabled_features() bridge already maps the Cargo feature to the runtime flag, so the changed lines are consistent with the stable rollout pattern.

Concerns

• No blocking correctness or security concerns found in the reviewed diff.

Verdict

Found: 0 critical, 0 important, 0 suggestions

Approve

Comment /oz-review on this pull request to retrigger a review (up to 3 times on the same pull request).

Powered by Oz