Written by an AI agent working in this repository.
Today's red-team run drew platform/counter/usage-data.mjs at random. It is the small tool sessions use to read the portfolio's daily visit counts. A scheduled workflow commits those counts to a usage-data branch, since main only takes changes through pull requests. The tool fetches that branch and then prints a summary (status), prints one file (show), or copies the files into portfolio/usage/ (sync).
Eight of eight mutants survived
The run changed the file in eight small ways, one at a time: it flipped a comparison, changed a return value, or turned a + into a -. The test suite caught none of them. The four existing tests covered the merge logic (which copy of a file wins) and the one-line summaries. Nothing ran the command itself. A build that made status write files, wrote NaN into the usage JSON, or ignored the command a person typed would have passed CI.
The bug the new tests found
The new tests run the real script. Each one copies it into a temporary git repository whose origin is another local repository holding a usage-data branch. One test commits to that branch, runs status, commits again and runs status a second time. The second run failed:
! [rejected] usage-data -> origin/usage-data (non-fast-forward)
Could not fetch origin/usage-data
The script fetched usage-data:refs/remotes/origin/usage-data with --depth=1. A depth-1 fetch keeps only the tip commit. On the next fetch git cannot see that the new tip descends from the stored one, so it treats the update as a force-push. With no + on the refspec, git refuses it. The branch gets a new commit every day, so in any clone that had run the tool once, every later run exited 1. In a fresh cloud clone the first run works, which is probably why nobody noticed.
The fix is +usage-data:refs/remotes/origin/usage-data. The six new tests cover the default command, sync (the written file must be valid JSON that keeps the days main already had), show, a remote with no branch, a second run after the branch has moved, and importing the module without starting the command. With them in place, all eight mutants are caught.
The guard
platform/ci/check_shallow_refspec.py reads every tracked script outside .github/ and fails on any line that fetches with --depth into a refs/... destination when the source has no leading +. On main before this fix it flagged exactly this line, and nothing else. You don't need to wire it into a workflow: unwired_checks.py already runs every check_*.py that no workflow names.
The second campaign of the run seeded eight faults in platform/ci/check_page_lists.py, and its tests caught all eight.