pdt-cli 0.1.2__tar.gz → 0.1.4__tar.gz

{pdt_cli-0.1.2 → pdt_cli-0.1.4}/.gitignore

@@ -16,6 +16,7 @@ dist/
 .pytest_cache/
 .uv-cache/
 claude-task-report/
+winget/rendered/
 
 # OS / editor noise
 .DS_Store

pdt_cli-0.1.4/LICENSE

@@ -0,0 +1,9 @@
+MIT License
+
+Copyright (c) 2026 AutoIDM
+
+Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

{pdt_cli-0.1.2 → pdt_cli-0.1.4}/PKG-INFO

@@ -1,8 +1,9 @@
 Metadata-Version: 2.5
 Name: pdt-cli
-Version: 0.1.2
+Version: 0.1.4
 Summary: Easily deploy your process to AWS, Azure, Google Cloud, or Windows.
 License-Expression: MIT
+License-File: LICENSE
 Requires-Python: >=3.12
 Requires-Dist: argcomplete
 Requires-Dist: backoff
@@ -26,7 +27,7 @@ Requires-Dist: gcsfs; extra == 'apps'
 Requires-Dist: google-cloud-secret-manager; extra == 'apps'
 Requires-Dist: google-cloud-storage; extra == 'apps'
 Requires-Dist: pyjwt; extra == 'apps'
-Requires-Dist: s3fs; extra == 'apps'
+Requires-Dist: s3fs>=2024; extra == 'apps'
 Description-Content-Type: text/markdown
 
 # pdt
@@ -41,7 +42,7 @@ uv tool install pdt-cli
 
 That puts a `pdt` command on your PATH. To update it later, run `uv tool upgrade pdt-cli`.
 
-The first interactive `pdt` command turns on tab completion without a prompt. It works in every new terminal: Tab finishes pdt commands, their options, your app names, and example names for `new --from`. It supports bash, zsh, fish, and PowerShell. `pdt completion [SHELL]` sets up a second shell, and `pdt completion --script bash` prints the script instead of writing it, if you keep your own dotfiles.
+On Windows you can run `winget install AutoIDM.pdt` instead, which also installs `uv` if you do not have it and puts the same `pdt` command on your PATH. `winget upgrade AutoIDM.pdt` moves pdt to the latest release, and the first `pdt` command after an install or upgrade finishes setting up that version.
 
 You can also clone this repository and run `./pdt` (or `.\pdt.bat` on Windows) instead. It installs `uv` for you if you do not have it. Both ways give you the same commands.
 
@@ -121,6 +122,7 @@ pdt login my-report
 | `pdt validate` | check the config files and the required env vars |
 | `pdt run APP` | run an app on this machine |
 | `pdt deploy APP` | deploy an app to its configured platform |
+| `pdt deploy --all` | deploy every enabled app, in order; asks whether to skip and disable an app that fails; add `--yes --skip-failures` to run unattended |
 | `pdt destroy APP` | remove everything deploy created |
 | `pdt secrets APP` | show which `.env` values differ from the deployed app |
 | `pdt secrets APP save` | send your `.env` values to the deployed app; the next run uses them |
@@ -128,11 +130,14 @@ pdt login my-report
 | `pdt secrets APP set NAME` | put one value, read from stdin, into the deployed app's secrets |
 | `pdt login APP` | sign in again to the app's cloud provider |
 | `pdt storage APP ls|get|query|destroy` | look at, fetch, query, or delete the app's stored files |
+| `pdt runs APP` | list the deployed app's runs with each run's exit code: the 10 newest, or with `--since 3d` (or `12h`, `2w`, `2026-09-20`, `2026-09-20T14:00`) every run since then, `--span 1d` keeping only the runs within that long after `--since` and `--count N` keeping only the N newest; a run's number is its place among every run pdt can still find, so it stays the same whichever runs print |
+| `pdt logs APP [N]` | read the log of run N as `pdt runs` numbers it; with no N, the newest run, and `--failed` picks the newest failed run instead; `--since`, `--span`, and `--count` limit which runs those two choose from, `--errors` leaves out DEBUG and INFO lines; the last 20 lines print, `--lines N` prints N instead, `--head` prints the first lines instead of the last, and `--full` prints every line |
+| `pdt health [APP] [--all]` | show whether each app's last run succeeded; exits 1 when one failed; inside an app folder it checks only that app, and `--all` checks every app |
 | `pdt az ...` | run the Azure CLI that pdt installs |
 | `pdt gcloud ...` | run the Google Cloud CLI that pdt installs |
 | `pdt completion [SHELL]` | turn on tab completion for a shell |
 
-Leave `APP` off `run`, `deploy`, `destroy`, `secrets`, or `login`, or mistype it, and pdt lists the apps in the project so you can pick one.
+Inside an app folder, or any folder below it, leave `APP` off any command that takes one and pdt uses that app. For example, `pdt logs 3` in the `hello-world` folder reads run 3 of `hello-world`. Anywhere else, leave `APP` off or mistype it and pdt lists the apps in the project so you can pick one.
 
 `pdt az` and `pdt gcloud` hand your arguments straight to the cloud tool, and install it first if it is missing. For example, `pdt az account list`.
 
@@ -140,7 +145,7 @@ Leave `APP` off `run`, `deploy`, `destroy`, `secrets`, or `login`, or mistype it
 
 Your app runs, writes some files, and stops. Then the computer it ran on is thrown away, and the files go with it. So pdt gives every app a folder in your cloud account that stays. Deploy the app, destroy it, deploy it again: the folder and everything in it is still there.
 
-pdt creates one bucket per cloud account, named `pdt-data-` plus a short code, and gives each app its own folder inside it. When your app runs in the cloud, `PDT_STORAGE_URL` points at that folder. When you run `pdt run APP` on your own computer, it points at `.pdt/storage/APP/` inside your project instead. The app code is the same in both places.
+pdt creates one bucket per cloud account, named `pdt-data-` plus a short code, and gives each app its own folder inside it. When your app runs in the cloud, `PDT_STORAGE_URL` points at that folder. A Windows scheduled task points it at `%ProgramData%\pdt\APP\storage\`. When you run `pdt run APP` on your own computer, it points at `.pdt/storage/APP/` inside your project instead. The app code is the same in every place.
 
 Write and read files with `pdt.utils.storage`:
 
@@ -183,7 +188,7 @@ Every command reads its values from the environment it runs in. A build server s
 
 ## Choosing where jobs run
 
-Set `platform:` in `pdt.yml` for every app, or in an app's own `config.yml` for one app. An app's own file wins.
+Set `platform:` in `pdt.yml` for every app, or in an app's own `config.yml` for one app. An app's own file wins. `timezone` may live under `platform:` as the default for every app, and an app's own `timezone` overrides it.
 
 ### Azure
 
@@ -228,7 +233,7 @@ platform:
 
 ### Bringing your own Dockerfile
 
-Every cloud provider runs a job as a container: AWS on Fargate, Azure on Container Apps Jobs, Google Cloud on Cloud Run Jobs. The deploy builds an image for each app from a generated Dockerfile. It copies the app folder and `pdt.yml` into `/workspace`, installs the script-header dependencies of `run.py` with `uv sync --script`, and runs `run.py` as the entrypoint.
+Every cloud provider runs a job as a container: AWS on Batch (Fargate), Azure on Container Apps Jobs, Google Cloud on Cloud Run Jobs. The deploy builds an image for each app from a generated Dockerfile. It copies the app folder and `pdt.yml` into `/workspace`, installs the script-header dependencies of `run.py` with `uv sync --script`, and runs `run.py` as the entrypoint.
 
 Put a `Dockerfile` in the app folder to build the image your own way, for example to add system packages or to install a heavy tool at build time instead of on every run. The build context is the same as the generated one: the app folder under its own name, next to `pdt.yml`. Start from the generated file:
 
@@ -236,7 +241,7 @@ Put a `Dockerfile` in the app folder to build the image your own way, for exampl
 FROM ghcr.io/astral-sh/uv:python3.12-bookworm-slim
 COPY . /workspace
 WORKDIR /workspace/my-app
-ENV PDT_PROJECT=/workspace
+ENV PDT_PROJECT=/workspace NO_COLOR=1 DBT_USE_COLORS=false
 RUN uv sync --script run.py
 ENTRYPOINT ["uv", "run", "--script", "run.py"]
 ```
@@ -253,10 +258,11 @@ platform:
 
 apps:
   - name: my-report
-    timezone: local
     schedule: daily
 ```
 
+The Windows provider runs each job on the PC's local time, so `timezone` defaults to `local` there, the only value it accepts.
+
 The job runs as the SYSTEM account. Windows accepts these schedules:
 
 - `hourly`, `daily`, `weekly`, `monthly`, and `yearly`
@@ -267,6 +273,8 @@ The job runs as the SYSTEM account. Windows accepts these schedules:
 
 Other cron forms are rejected, because they do not translate to Windows Task Scheduler.
 
+Each app keeps its run data in `%ProgramData%\pdt\<app>\`. The task writes one log file per run to the `logs\` folder in it, named by the run's UTC start time, and `pdt runs <app>` and `pdt logs <app>` read those files. The app's own files (see [Keeping files between runs](#keeping-files-between-runs)) live in the `storage\` folder next to it. Deploy creates the folder and gives the SYSTEM account full control and you modify rights, so `pdt storage <app> destroy` works without an administrator. `pdt destroy <app>` removes the task and the `logs\` folder and keeps `storage\`. A run is stopped after 30 minutes, the same limit as the cloud providers, and a run that is still going when the next one is due is left alone; the new start is skipped.
+
 ## The bundled examples
 
 Run `pdt examples` to list them, then `pdt new <name> --from <example>` to copy one.
@@ -290,9 +298,11 @@ Reports active Monday users whose email address does not match the `userPrincipa
 | Item | Where |
 | --- | --- |
 | the `pdt` command and its code | the tool's own environment, from `uv tool install` |
+| the `pdt` launcher from winget | `%LOCALAPPDATA%\Microsoft\WinGet\Packages`, linked from `%LOCALAPPDATA%\Microsoft\WinGet\Links` |
 | the example apps | inside the pdt package, copied out by `pdt new` |
 | your apps, `pdt.yml`, `.env` | your project folder, under version control |
 | the Google Cloud CLI pdt downloads | `~/.local/share/pdt/gcloud`, or `%LOCALAPPDATA%\pdt\gcloud` |
+| a Windows scheduled task's run logs and files | `%ProgramData%\pdt\<app>\logs` and `%ProgramData%\pdt\<app>\storage` |
 | cloud sign-in state | `~/.azure` and `~/.config/gcloud`, as usual |
 
 Set `PDT_PROJECT` to name the project folder directly, instead of letting pdt search upward. Deployed jobs get it set for them.
@@ -304,7 +314,7 @@ An app is a folder with a `run.py` that has a `main()` function. It declares its
 ```python
 # /// script
 # requires-python = ">=3.12"
-# dependencies = ["pdt-cli[apps]==0.1.2"]
+# dependencies = ["pdt-cli[apps]==0.1.4"]
 # ///
 from pathlib import Path
 
@@ -320,6 +330,14 @@ def main() -> int:
 
 The pinned version matters. A deployed job keeps using the version in its header, so upgrading pdt on your machine does not change a job already running in the cloud.
 
+### PowerShell apps
+
+A folder of `.ps1` files with no `run.py` is a PowerShell app: pdt reads the scripts to find the modules to install, then runs the entry scripts in name order through pwsh. A `run.ps1` file is the only entry script. Otherwise, use `run_scripts` in `config.yml` to choose entries and set their order. Do not use `run.ps1` and `run_scripts` together. By default, pdt stops after the first failed script. Set `continue_on_error: true` to run every entry script. The run still fails with the first script's exit code. To change either step, run `pdt new <app> --from-scripts`. It writes `requirements.psd1`, which lists the modules with pinned versions, and `run.py`, which runs the scripts. Once they exist, pdt installs exactly the modules in `requirements.psd1` (`pdt validate` warns about a module the scripts need that it leaves out), and `pdt run` and deploy run your `run.py`.
+
+```
+pdt new my-report --from-scripts
+```
+
 # Utilities
 
 `pdt.utils` provides built-in support for common functionality:

{pdt_cli-0.1.2 → pdt_cli-0.1.4}/README.md

@@ -10,7 +10,7 @@ uv tool install pdt-cli
 
 That puts a `pdt` command on your PATH. To update it later, run `uv tool upgrade pdt-cli`.
 
-The first interactive `pdt` command turns on tab completion without a prompt. It works in every new terminal: Tab finishes pdt commands, their options, your app names, and example names for `new --from`. It supports bash, zsh, fish, and PowerShell. `pdt completion [SHELL]` sets up a second shell, and `pdt completion --script bash` prints the script instead of writing it, if you keep your own dotfiles.
+On Windows you can run `winget install AutoIDM.pdt` instead, which also installs `uv` if you do not have it and puts the same `pdt` command on your PATH. `winget upgrade AutoIDM.pdt` moves pdt to the latest release, and the first `pdt` command after an install or upgrade finishes setting up that version.
 
 You can also clone this repository and run `./pdt` (or `.\pdt.bat` on Windows) instead. It installs `uv` for you if you do not have it. Both ways give you the same commands.
 
@@ -90,6 +90,7 @@ pdt login my-report
 | `pdt validate` | check the config files and the required env vars |
 | `pdt run APP` | run an app on this machine |
 | `pdt deploy APP` | deploy an app to its configured platform |
+| `pdt deploy --all` | deploy every enabled app, in order; asks whether to skip and disable an app that fails; add `--yes --skip-failures` to run unattended |
 | `pdt destroy APP` | remove everything deploy created |
 | `pdt secrets APP` | show which `.env` values differ from the deployed app |
 | `pdt secrets APP save` | send your `.env` values to the deployed app; the next run uses them |
@@ -97,11 +98,14 @@ pdt login my-report
 | `pdt secrets APP set NAME` | put one value, read from stdin, into the deployed app's secrets |
 | `pdt login APP` | sign in again to the app's cloud provider |
 | `pdt storage APP ls|get|query|destroy` | look at, fetch, query, or delete the app's stored files |
+| `pdt runs APP` | list the deployed app's runs with each run's exit code: the 10 newest, or with `--since 3d` (or `12h`, `2w`, `2026-09-20`, `2026-09-20T14:00`) every run since then, `--span 1d` keeping only the runs within that long after `--since` and `--count N` keeping only the N newest; a run's number is its place among every run pdt can still find, so it stays the same whichever runs print |
+| `pdt logs APP [N]` | read the log of run N as `pdt runs` numbers it; with no N, the newest run, and `--failed` picks the newest failed run instead; `--since`, `--span`, and `--count` limit which runs those two choose from, `--errors` leaves out DEBUG and INFO lines; the last 20 lines print, `--lines N` prints N instead, `--head` prints the first lines instead of the last, and `--full` prints every line |
+| `pdt health [APP] [--all]` | show whether each app's last run succeeded; exits 1 when one failed; inside an app folder it checks only that app, and `--all` checks every app |
 | `pdt az ...` | run the Azure CLI that pdt installs |
 | `pdt gcloud ...` | run the Google Cloud CLI that pdt installs |
 | `pdt completion [SHELL]` | turn on tab completion for a shell |
 
-Leave `APP` off `run`, `deploy`, `destroy`, `secrets`, or `login`, or mistype it, and pdt lists the apps in the project so you can pick one.
+Inside an app folder, or any folder below it, leave `APP` off any command that takes one and pdt uses that app. For example, `pdt logs 3` in the `hello-world` folder reads run 3 of `hello-world`. Anywhere else, leave `APP` off or mistype it and pdt lists the apps in the project so you can pick one.
 
 `pdt az` and `pdt gcloud` hand your arguments straight to the cloud tool, and install it first if it is missing. For example, `pdt az account list`.
 
@@ -109,7 +113,7 @@ Leave `APP` off `run`, `deploy`, `destroy`, `secrets`, or `login`, or mistype it
 
 Your app runs, writes some files, and stops. Then the computer it ran on is thrown away, and the files go with it. So pdt gives every app a folder in your cloud account that stays. Deploy the app, destroy it, deploy it again: the folder and everything in it is still there.
 
-pdt creates one bucket per cloud account, named `pdt-data-` plus a short code, and gives each app its own folder inside it. When your app runs in the cloud, `PDT_STORAGE_URL` points at that folder. When you run `pdt run APP` on your own computer, it points at `.pdt/storage/APP/` inside your project instead. The app code is the same in both places.
+pdt creates one bucket per cloud account, named `pdt-data-` plus a short code, and gives each app its own folder inside it. When your app runs in the cloud, `PDT_STORAGE_URL` points at that folder. A Windows scheduled task points it at `%ProgramData%\pdt\APP\storage\`. When you run `pdt run APP` on your own computer, it points at `.pdt/storage/APP/` inside your project instead. The app code is the same in every place.
 
 Write and read files with `pdt.utils.storage`:
 
@@ -152,7 +156,7 @@ Every command reads its values from the environment it runs in. A build server s
 
 ## Choosing where jobs run
 
-Set `platform:` in `pdt.yml` for every app, or in an app's own `config.yml` for one app. An app's own file wins.
+Set `platform:` in `pdt.yml` for every app, or in an app's own `config.yml` for one app. An app's own file wins. `timezone` may live under `platform:` as the default for every app, and an app's own `timezone` overrides it.
 
 ### Azure
 
@@ -197,7 +201,7 @@ platform:
 
 ### Bringing your own Dockerfile
 
-Every cloud provider runs a job as a container: AWS on Fargate, Azure on Container Apps Jobs, Google Cloud on Cloud Run Jobs. The deploy builds an image for each app from a generated Dockerfile. It copies the app folder and `pdt.yml` into `/workspace`, installs the script-header dependencies of `run.py` with `uv sync --script`, and runs `run.py` as the entrypoint.
+Every cloud provider runs a job as a container: AWS on Batch (Fargate), Azure on Container Apps Jobs, Google Cloud on Cloud Run Jobs. The deploy builds an image for each app from a generated Dockerfile. It copies the app folder and `pdt.yml` into `/workspace`, installs the script-header dependencies of `run.py` with `uv sync --script`, and runs `run.py` as the entrypoint.
 
 Put a `Dockerfile` in the app folder to build the image your own way, for example to add system packages or to install a heavy tool at build time instead of on every run. The build context is the same as the generated one: the app folder under its own name, next to `pdt.yml`. Start from the generated file:
 
@@ -205,7 +209,7 @@ Put a `Dockerfile` in the app folder to build the image your own way, for exampl
 FROM ghcr.io/astral-sh/uv:python3.12-bookworm-slim
 COPY . /workspace
 WORKDIR /workspace/my-app
-ENV PDT_PROJECT=/workspace
+ENV PDT_PROJECT=/workspace NO_COLOR=1 DBT_USE_COLORS=false
 RUN uv sync --script run.py
 ENTRYPOINT ["uv", "run", "--script", "run.py"]
 ```
@@ -222,10 +226,11 @@ platform:
 
 apps:
   - name: my-report
-    timezone: local
     schedule: daily
 ```
 
+The Windows provider runs each job on the PC's local time, so `timezone` defaults to `local` there, the only value it accepts.
+
 The job runs as the SYSTEM account. Windows accepts these schedules:
 
 - `hourly`, `daily`, `weekly`, `monthly`, and `yearly`
@@ -236,6 +241,8 @@ The job runs as the SYSTEM account. Windows accepts these schedules:
 
 Other cron forms are rejected, because they do not translate to Windows Task Scheduler.
 
+Each app keeps its run data in `%ProgramData%\pdt\<app>\`. The task writes one log file per run to the `logs\` folder in it, named by the run's UTC start time, and `pdt runs <app>` and `pdt logs <app>` read those files. The app's own files (see [Keeping files between runs](#keeping-files-between-runs)) live in the `storage\` folder next to it. Deploy creates the folder and gives the SYSTEM account full control and you modify rights, so `pdt storage <app> destroy` works without an administrator. `pdt destroy <app>` removes the task and the `logs\` folder and keeps `storage\`. A run is stopped after 30 minutes, the same limit as the cloud providers, and a run that is still going when the next one is due is left alone; the new start is skipped.
+
 ## The bundled examples
 
 Run `pdt examples` to list them, then `pdt new <name> --from <example>` to copy one.
@@ -259,9 +266,11 @@ Reports active Monday users whose email address does not match the `userPrincipa
 | Item | Where |
 | --- | --- |
 | the `pdt` command and its code | the tool's own environment, from `uv tool install` |
+| the `pdt` launcher from winget | `%LOCALAPPDATA%\Microsoft\WinGet\Packages`, linked from `%LOCALAPPDATA%\Microsoft\WinGet\Links` |
 | the example apps | inside the pdt package, copied out by `pdt new` |
 | your apps, `pdt.yml`, `.env` | your project folder, under version control |
 | the Google Cloud CLI pdt downloads | `~/.local/share/pdt/gcloud`, or `%LOCALAPPDATA%\pdt\gcloud` |
+| a Windows scheduled task's run logs and files | `%ProgramData%\pdt\<app>\logs` and `%ProgramData%\pdt\<app>\storage` |
 | cloud sign-in state | `~/.azure` and `~/.config/gcloud`, as usual |
 
 Set `PDT_PROJECT` to name the project folder directly, instead of letting pdt search upward. Deployed jobs get it set for them.
@@ -273,7 +282,7 @@ An app is a folder with a `run.py` that has a `main()` function. It declares its
 ```python
 # /// script
 # requires-python = ">=3.12"
-# dependencies = ["pdt-cli[apps]==0.1.2"]
+# dependencies = ["pdt-cli[apps]==0.1.4"]
 # ///
 from pathlib import Path
 
@@ -289,6 +298,14 @@ def main() -> int:
 
 The pinned version matters. A deployed job keeps using the version in its header, so upgrading pdt on your machine does not change a job already running in the cloud.
 
+### PowerShell apps
+
+A folder of `.ps1` files with no `run.py` is a PowerShell app: pdt reads the scripts to find the modules to install, then runs the entry scripts in name order through pwsh. A `run.ps1` file is the only entry script. Otherwise, use `run_scripts` in `config.yml` to choose entries and set their order. Do not use `run.ps1` and `run_scripts` together. By default, pdt stops after the first failed script. Set `continue_on_error: true` to run every entry script. The run still fails with the first script's exit code. To change either step, run `pdt new <app> --from-scripts`. It writes `requirements.psd1`, which lists the modules with pinned versions, and `run.py`, which runs the scripts. Once they exist, pdt installs exactly the modules in `requirements.psd1` (`pdt validate` warns about a module the scripts need that it leaves out), and `pdt run` and deploy run your `run.py`.
+
+```
+pdt new my-report --from-scripts
+```
+
 # Utilities
 
 `pdt.utils` provides built-in support for common functionality:

{pdt_cli-0.1.2 → pdt_cli-0.1.4}/ci/tests/test_claude_task.py

@@ -91,18 +91,6 @@ def test_missing_task_or_prompt(tmp_path):
         runner.load_task("bare", tmp_path)
 
 
-def test_shipped_rebase_task_loads():
-    task = runner.load_task("rebase-mrs")
-    assert task.model == "opus"
-    assert task.select.name == "select_mrs.py"
-    assert task.check.name == "check_mrs.py"
-    assert "Bash(git push --force-with-lease*)" in task.allowed_tools
-    assert not any("git push -f" in tool for tool in task.allowed_tools)
-    assert runner.render_prompt(task.prompt, {
-        "source_branch": "b", "target_branch": "master", "iid": 1, "title": "t",
-        "before_sha": "abc", "ahead": 2})
-
-
 def test_render_prompt_fills_and_names_missing_fields():
     assert runner.render_prompt("Rebase {branch} for !{iid}", {"branch": "x", "iid": 7}) == \
         "Rebase x for !7"
@@ -126,7 +114,7 @@ def test_missing_token_message_names_the_variable():
     assert runner.missing_token_problem({"CLAUDE_CODE_OAUTH_TOKEN": "tok"}) == ""
 
 
-def test_claude_env_maps_the_gitlab_name_to_the_name_claude_reads():
+def test_claude_env_maps_the_secret_name_to_the_name_claude_reads():
     env = runner.claude_env({"CLAUDE_TOKEN": "tok", "PATH": "/bin"})
     assert env["CLAUDE_CODE_OAUTH_TOKEN"] == "tok"
     assert env["PATH"] == "/bin"
@@ -193,6 +181,28 @@ def test_exit_codes():
     assert runner.exit_code(["needs_human", "error"]) == 1
 
 
+def test_run_url_links_the_workflow_run():
+    env = {"GITHUB_SERVER_URL": "https://github.com", "GITHUB_REPOSITORY": "AutoIDM/pdt",
+           "GITHUB_RUN_ID": "77"}
+    assert runner.run_url(env) == "https://github.com/AutoIDM/pdt/actions/runs/77"
+    assert runner.run_url({}) == ""
+
+
+def test_an_item_that_needs_a_person_prints_a_warning_annotation(tmp_path, monkeypatch, capsys):
+    make_task(tmp_path)
+    load = runner.load_task
+    monkeypatch.setattr(runner, "load_task", lambda name: load(name, tmp_path))
+    monkeypatch.setattr(runner, "verify_token", lambda task, env, report_dir: "")
+    monkeypatch.setattr(runner, "REPORT_DIR", tmp_path / "report")
+    monkeypatch.setattr(runner, "run_items", lambda *a: [
+        {"id": "7", "status": "needs_human", "message": "needs discussion:\ncli.py"},
+        {"id": "8", "status": "ok", "message": "tier::simple"}])
+    assert runner.main(["demo"]) == runner.EXIT_NEEDS_HUMAN
+    warnings = [line for line in capsys.readouterr().out.splitlines()
+                if line.startswith("::warning")]
+    assert warnings == ["::warning title=demo 7 needs a person::needs discussion: cli.py"]
+
+
 def test_claude_command_shape(tmp_path):
     task = runner.load_task("demo", make_task(
         tmp_path, "allowed_tools: [Read, 'Bash(git *)']\ndisallowed_tools: ['Bash(git push -f*)']\n"))
@@ -223,13 +233,6 @@ def test_parallel_parses_and_defaults_to_one(tmp_path):
         runner.load_task("demo", make_task(tmp_path / "zero", "parallel: 0\n"))
 
 
-def test_claude_env_makes_a_relative_uv_cache_absolute(tmp_path):
-    env = runner.claude_env({"UV_CACHE_DIR": ".uv-cache"}, cwd=tmp_path)
-    assert env["UV_CACHE_DIR"] == str(tmp_path.resolve() / ".uv-cache")
-    assert runner.claude_env({"UV_CACHE_DIR": "/abs/cache"})["UV_CACHE_DIR"] == "/abs/cache"
-    assert "UV_CACHE_DIR" not in runner.claude_env({})
-
-
 def test_items_run_side_by_side_and_outcomes_keep_order(tmp_path, monkeypatch):
     task = runner.load_task("demo", make_task(tmp_path, "parallel: 3\n"))
     started = threading.Barrier(3, timeout=5)

pdt_cli-0.1.4/ci/tests/test_close_stale_drafts.py

@@ -0,0 +1,105 @@
+"""close_stale_drafts.py: what counts as a person touching a Draft PR."""
+
+import importlib.util
+import sys
+from datetime import date
+from pathlib import Path
+
+import yaml
+
+SCRIPT = Path(__file__).resolve().parent.parent / "close_stale_drafts.py"
+REPO = SCRIPT.parent.parent
+
+spec = importlib.util.spec_from_file_location("close_stale_drafts", SCRIPT)
+stale = importlib.util.module_from_spec(spec)
+sys.modules["close_stale_drafts"] = stale
+spec.loader.exec_module(stale)
+
+BOT = "pdt-bot"
+PERSON = "alice"
+TODAY = date(2026, 9, 15)  # a Tuesday
+
+
+def pr(**overrides):
+    base = {"number": 5, "title": "thing", "draft": True,
+            "created_at": "2026-08-03T09:00:00Z"}
+    return {**base, **overrides}
+
+
+def commit(authored):
+    return {"commit": {"author": {"date": authored}}}
+
+
+def comment(login, when):
+    return {"user": {"login": login}, "updated_at": when}
+
+
+def review(login, when):
+    return {"user": {"login": login}, "submitted_at": when}
+
+
+def test_business_days_skip_weekends():
+    friday, monday = date(2026, 9, 11), date(2026, 9, 14)
+    assert stale.business_days_since(friday, monday) == 1
+    assert stale.business_days_since(friday, TODAY) == 2
+    assert stale.business_days_since(TODAY, TODAY) == 0
+
+
+def test_opening_the_pr_counts():
+    assert stale.last_person_activity(pr(), [], [], [], BOT) == date(2026, 8, 3)
+
+
+def test_the_token_user_and_bots_do_not_count():
+    """A label or comment from score-prs, or any bot, leaves no trace."""
+    commits = [commit("2026-08-04T10:00:00Z")]
+    comments = [comment(BOT, "2026-09-14T10:00:05Z"),
+                comment("github-actions[bot]", "2026-09-14T10:00:06Z"),
+                comment("dependabot[bot]", "2026-09-14T10:00:07Z")]
+    reviews = [review("copilot-pull-request-reviewer[bot]", "2026-09-14T11:00:00Z")]
+    assert stale.last_person_activity(pr(), commits, comments, reviews, BOT) == date(2026, 8, 4)
+
+
+def test_a_person_committing_commenting_or_reviewing_counts():
+    commits = [commit("2026-08-04T10:00:00Z")]
+    comments = [comment(BOT, "2026-09-14T10:00:00Z"), comment(PERSON, "2026-09-09T15:00:00Z")]
+    reviews = [review(PERSON, "2026-09-10T15:00:00Z"), {"user": {"login": PERSON},
+                                                        "submitted_at": None}]
+    assert stale.last_person_activity(pr(), commits, comments, reviews, BOT) == date(2026, 9, 10)
+    commits.append(commit("2026-09-12T08:00:00Z"))
+    assert stale.last_person_activity(pr(), commits, comments, reviews, BOT) == date(2026, 9, 12)
+
+
+def test_timestamps_are_read_in_utc():
+    comments = [comment(PERSON, "2026-09-10T22:00:00-05:00")]
+    assert stale.last_person_activity(pr(), [], comments, [], BOT) == date(2026, 9, 11)
+
+
+def test_stale_needs_more_than_the_limit_and_a_draft():
+    limit = stale.STALE_BUSINESS_DAYS
+    assert stale.business_days_since(date(2026, 9, 8), TODAY) == limit
+    assert not stale.is_stale(pr(), date(2026, 9, 8), TODAY)
+    assert stale.is_stale(pr(), date(2026, 9, 7), TODAY)
+    assert not stale.is_stale(pr(draft=False), date(2026, 8, 1), TODAY)
+
+
+def test_dry_run_is_the_default():
+    assert stale.dry_run_wanted({})
+    assert stale.dry_run_wanted({"DRY_RUN": "False "}) is False
+    assert stale.dry_run_wanted({"DRY_RUN": "no"})
+
+
+def test_slack_text_lists_each_closed_pr():
+    text = stale.slack_text("AutoIDM/pdt", [pr(html_url="https://github.com/AutoIDM/pdt/pull/5")])
+    assert text.splitlines() == [
+        "Closed 1 stale Draft PR(s) in AutoIDM/pdt (nobody touched them for more than "
+        "5 business days):",
+        "• #5 thing https://github.com/AutoIDM/pdt/pull/5"]
+
+
+def test_workflow_runs_armed_on_its_schedule_and_dry_by_hand():
+    flow = yaml.safe_load((REPO / ".github" / "workflows" / "close-stale-drafts.yml").read_text())
+    on = flow[True]  # YAML 1.1 reads the bare key on as true
+    assert on["schedule"] and on["workflow_dispatch"]["inputs"]["dry_run"]["default"] is True
+    env = flow["jobs"]["close-stale-drafts"]["env"]
+    assert "inputs.dry_run" in env["DRY_RUN"]
+    assert "secrets.SLACK_WEBHOOK_URL" in env["SLACK_WEBHOOK_URL"]