Request to enhance the release-orchestrator.agent.md to support a flexible working directory. Currently, it assumes release work happens in the same repository, leading to tight coupling and limitations in testing agent improvements.
## Problem Current `release-orchestrator.agent.md` assumes release work happens in the same repository where the agent file exists. This creates tight coupling between agent development and release execution. **Current workflow limitations**: - Agent development and release work must share same kserve repo - All paths are relative (`./hack/release/`, `kserve-deps.env`) - Cannot safely test agent improvements during active releases ## Goal Enable separated workflows: - **Agent development**: One kserve repo for improving `.agent.md` - **Release execution**: Different kserve repo for actual release work - **Hot reload**: Agent changes apply on Copilot restart with checkpoint resume ## Required Changes ### 1. Working Directory Setup Add Phase 0 to detect/configure release repository: ```bash if [[ ! -f "kserve-deps.env" ]]; then read -p "Enter KServe repository path: " KSERVE_REPO_PATH cd "$KSERVE_REPO_PATH" fi ``` ### 2. Path Resolution Convert relative paths to work from co