Spaces:
Running
Running
Commit History
20 days ago
-
fix(pipeline): fold in commits pushed straight to the Space; a token without repos never stops the server
Two things the first real pickup run met on 2026-10-22: - The test Space was ahead of develop by two commits another session had pushed to it directly (settings document, Data Adjuster LLM fix). The push would have been refused as a non-fast-forward. The run now merges the Space's own commits into the integration branch first (--no-ff, a conflict is reported, not forced), so nothing on the Space is lost and the push is a fast-forward. Recorded on the deployment note. - GITHUB_TOKEN landed on prod too, with no TRACKER_REPOS. The server used to raise at startup on that half config, which would have taken prod down at the next promotion. The poller is now skipped with a loud log line; the sync runs only on the Space that has TRACKER_REPOS (test). Also: the job and the CLI load the nearest .env when run from a worktree; the launchd job runs the pipeline worktree's own copy of the script, so it always runs the integration branch whatever boone's checkout is on; the third p…02321f4 -
chore(pipeline): the pickup run, worker and tracker CLI are executable
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>81be5c5 -
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
