Spaces:
Running
Running
Commit History
20 days ago
-
fix(pipeline): read pytest's quiet summary; a token without Checks reads as no checks
Both seen on the first deploy through the pipeline (2026-10-22, test-mcp = 3108c38): - `pytest -q` ends with a bare "3 failed, 2049 passed in 40s" line; the run recorded "pytest exit 1" because the parser wanted the ===== border. - The sync's first pass answered 403 on the pull request list (the token was created without the Pull requests permission: boone's to fix). A token with Pull requests but not Checks would still have failed the whole sync on the check-runs call; that now reads as "none" for that PR. Docs: the exact token permissions in docs/development_process.md; the sprint doc records the first deploy and what is left. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>4637f97 -
feat(pipeline): the pickup run, the agent worker, and the process they implement
Every change on a branch off develop, a PR in, approved on arrival for Mike and Jack and by one of them for everyone else, picked up four times a day and pushed to the test Space. Everything that writes to GitHub or Hugging Face runs on boone's Mac under his own credentials; the server only reads. - scripts/pipeline_run.py: queue -> merges in its own pipeline/ worktree (detached, --no-ff, a conflict skips with a note) -> unit suite with the known-failures allowlist -> push origin -> three-minute idle gate on the Space -> push hf-mcp-test -> ping confirms the sha -> deployments row and "on test-mcp" notes. Never prod, never a red suite, never a non-fast- forward. --dry-run reports against the real tracker. - scripts/launchd/com.demoprep.pipeline.plist: 7:30 / 11:30 / 15:30 / 19:30 local time. scripts/pipeline_known_failures.txt: the pre-existing failures. - scripts/agent_worker.sh + agent_worker_prompt.md + tracker_cli.py: the agent's turn — top task, agent/t<id>-<slug> o…62f3e9a
