fix: test_upgrade_to_new_version — use 0.11.5 target, update spec_version assertion

After v0.11.4 release, the hardcoded 0.11.4 target was now the current version
causing 'Already at spec version' instead of 'Upgraded'. Updated target to 0.11.5
and corrected the spec_version assertion from legacy '0.2.0' to '0.11.5'.

Co-Authored-By: Oz <oz-agent@warp.dev>

Author: tbitcs

tests/test_cli.py

@@ -115,14 +115,14 @@ def test_upgrade_to_new_version(self, tmp_path: Path) -> None:
         target = _scaffold_governed(tmp_path)
         runner = CliRunner()
         result = runner.invoke(
-            main, ["upgrade", "--project-dir", str(target), "--spec-version", "0.11.4"]
+            main, ["upgrade", "--project-dir", str(target), "--spec-version", "0.11.5"]
         )
         assert result.exit_code == 0
         assert "Upgraded" in result.output
-        # Verify scaffold.yml was updated
+        # Verify scaffold.yml spec_version was updated to the target version
         with open(target / "scaffold.yml") as fh:
             data = yaml.safe_load(fh)
-        assert data["spec_version"] == "0.2.0"
+        assert data["spec_version"] == "0.11.5"
 
 
 class TestCLICreditsLimits: