fix(agents): allow orchestrator.py to run as a direct script

[cvsz]

Motivation

• Running python agents/orchestrator.py from the repository root caused ModuleNotFoundError: No module named 'agents' because absolute imports failed when sys.path[0] pointed at the agents/ package.

Description

• When __package__ is empty, prepend the repository root to sys.path by inserting str(Path(__file__).resolve().parent.parent), ensuring from agents.* imports resolve when the orchestrator is executed directly.

Testing

• Ran python agents/orchestrator.py and the orchestrator executed end-to-end without the import error (script completed successfully).

---

Codex Task

[gemini-code-assist]

Code Review

This pull request modifies agents/orchestrator.py to include a manual sys.path adjustment for handling imports when the script is run directly. The review feedback correctly identifies this as a maintenance anti-pattern that can lead to module shadowing and suggests using the standard python -m execution method instead.

[gemini-code-assist]

Manually manipulating sys.path is generally considered a maintenance anti-pattern in Python. It can lead to unexpected side effects such as module shadowing (where a local file unintentionally overrides a standard library or third-party module) and makes the code fragile if the directory structure changes. The standard and recommended way to execute a script within a package is to use the -m flag from the project root: python -m agents.orchestrator. This approach correctly sets up the module search path and handles absolute imports without requiring manual overrides in the source code.