fix(ci): read the caller's perf config from the calling commit

.github/workflows/run.yaml

@@ -62,9 +62,12 @@ jobs:
     outputs:
       run-id: ${{ steps.run.outputs.run-id }}
     steps:
+      # The caller's perf config comes from the commit that called this workflow, not from the
+      # commit under test: a release tag can predate the config. --commit still reports the
+      # commit under test.
       - uses: actions/checkout@v4
         with:
-          ref: ${{ inputs.commit }}
+          ref: ${{ github.sha }}
       - uses: actions/setup-node@v4
         with:
           node-version: 22

docs/github-workflow.md

@@ -31,7 +31,7 @@ adds that machine's IP to the run's firewall before it logs in, with `PERFKIT_SS
 | `perfkit-ref` | required | The perfkit tag the workflow is called at, like `v0.1.0`; the jobs run that perfkit (`npx -y github:fonoster/perfkit#<perfkit-ref>`). A reusable workflow can't see its own ref, so pass the same tag as in `uses:`. |
 | `config` | `perf/perfkit.yaml` | The project's perfkit.yaml. |
 | `target-version` | required | The image tag under test, like `2.31.5`. |
-| `commit` | required | The commit under test; `start` checks it out. |
+| `commit` | required | The commit under test, written to report.json. The `perf/` config is read from the commit that called the workflow (`github.sha`), because a release tag under test can predate the config. |
 | `benchmarks` | empty | Comma-separated benchmark ids; empty runs them all. |
 
 | Secret | Meaning |

package.json

@@ -1,6 +1,6 @@
 {
   "name": "perfkit",
-  "version": "0.1.0",
+  "version": "0.1.1",
   "description": "Benchmark harness for Fonoster projects: DigitalOcean runs, one report.json schema, one branded report page",
   "license": "MIT",
   "author": "Pedro Sanders <psanders@fonoster.com>",