Skip to content

Remove legacy task runners and enforce UniversalRunner#11

Open
google-labs-jules[bot] wants to merge 1 commit intomainfrom
cleanup-legacy-code-15390281059723496134
Open

Remove legacy task runners and enforce UniversalRunner#11
google-labs-jules[bot] wants to merge 1 commit intomainfrom
cleanup-legacy-code-15390281059723496134

Conversation

@google-labs-jules
Copy link
Copy Markdown

This change removes the legacy "Classic" task execution path (GatherRunner, LinearPlanRunner) and enforces the "Universal" runner architecture across the backend. It simplifies the TaskExecutor, cleans up unused interfaces (LLMTaskActor, SemanticActionResolver), and updates the application entry point and tests to reflect these changes. This aligns the codebase with the latest architectural direction (Phase 3+).


PR created automatically by Jules for task 15390281059723496134 started by @HCID274

…itecture

1. Removed `ClassicRunnerFactory`, `GatherRunner`, and `LinearPlanRunner`.
2. Removed legacy actor/resolver components: `LLMTaskActor`, `SemanticActionResolver`, and related interfaces.
3. Updated `TaskExecutor` to remove legacy `runner_registry` fallback logic and rely solely on `RunnerFactory`.
4. Updated `backend/main.py` to initialize only the Universal architecture components.
5. Cleaned up `backend/task/runner_factory.py` to always return `UniversalRunnerFactory`.
6. Updated `backend/task/interfaces.py` and `backend/task/kb_resolver.py` to remove legacy imports and unused methods.
7. Fixed tests in `backend/tests/test_task_executor.py` to align with the new interface and removed obsolete tests.
@google-labs-jules
Copy link
Copy Markdown
Author

👋 Jules, reporting for duty! I'm here to lend a hand with this pull request.

When you start a review, I'll add a 👀 emoji to each comment to let you know I've read it. I'll focus on feedback directed at me and will do my best to stay out of conversations between you and other bots or reviewers to keep the noise down.

I'll push a commit with your requested changes shortly after. Please note there might be a delay between these steps, but rest assured I'm on the job!

For more direct control, you can switch me to Reactive Mode. When this mode is on, I will only act on comments where you specifically mention me with @jules. You can find this option in the Pull Request section of your global Jules UI settings. You can always switch back!

New to Jules? Learn more at jules.google/docs.


For security, I will only act on instructions from the user who triggered this task.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants