feat(system): fix(windows-ci): activate venv in Verify step so drone binary is on PATH

PR #330 fixed the pip bootstrap (ensurepip error-swallowing in setup.sh). With that fix working, the Verify step in windows-test.yml now fails at 'drone: command not found' (exit 127). Root cause: each CI step spawns a fresh shell, so the venv activation from setup.sh doesn't carry to Verify. drone lives at .venv/Scripts/drone.exe which isn't on the default PATH.

Fix: prepend 'source .venv/Scripts/activate' to the Verify step so drone is findable.

Stacked on PR #330 conceptually — both fixes needed for windows-test.yml to actually pass.

Co-Authored-By: @devpulse <devpulse@aipass>

.github/workflows/windows-test.yml

@@ -32,6 +32,7 @@ jobs:
       - name: Verify drone CLI
         shell: bash
         run: |
+          source .venv/Scripts/activate
           export PYTHONUTF8=1
           drone --version
           drone systems