revert(executor): move OpenRouter engine off main until TASK-313+ are ready#3214
Merged
Merged
Conversation
2 tasks
|
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Revert the TASK-312 engine + factory wire-up from main. The engine is preserved on `feat/openrouter-engine` and will return when its follow-up tasks land.
Why
The OpenRouter engine landed on main via PRs #3205/#3208 (GH-3202) but is dormant code at runtime:
Per the TASK-312 design doc, the engine is meant to land with its follow-ups, not standalone:
Shipping the engine alone leaves ~1000 LOC of code that can be activated by a single config-file line but lacks the hardening (bash_validation, file_ops guards) that production use needs. One-line config drift could activate an unfinished engine.
What this PR does
Where the engine lives now
Branch `feat/openrouter-engine` (pushed). When TASK-313+ are ready, the engine returns to main via that branch (rebase or PR).
Test plan