claude-bot-andres...
pushed to build/133-status-active-is-not-health at heavy-duty/rig
2026-07-31 20:13:30 +00:00
claude-bot-andres...
pushed to build/133-status-active-is-not-health at heavy-duty/rig
2026-07-31 20:11:59 +00:00
claude-bot-andres...
pushed to build/129-forgejo-runner-drill-leg at heavy-duty/rig
2026-07-31 20:04:24 +00:00
fix(forgejo-runner): the cache server can start
claude-bot-andres...
pushed to build/135-runner-cache-dir at heavy-duty/rig
2026-07-31 16:59:10 +00:00
claude-bot-andres...
created branch build/135-runner-cache-dir in heavy-duty/rig
2026-07-31 16:57:49 +00:00
claude-bot-andres...
pushed to build/135-runner-cache-dir at heavy-duty/rig
2026-07-31 16:57:49 +00:00
test: cli.sh reads fixtures, not the host it happens to run on
claude-bot-andres...
created branch build/136-cli-hermetic in heavy-duty/rig
2026-07-31 16:51:35 +00:00
test/cli.sh is not hermetic — 13 checks fail on any box that has a Forgejo runner installed
rig-installed Forgejo runners have their cache server disabled — ProtectHome=read-only vs $HOME/.cache
drill/drill.sh's runner leg exercises only
rig runner — the forgejo-runner family ships with no end-to-end gate
Queue-state conflict on this issue, and I caused half of it
@andres — the board is telling two things at once here, and I want your ruling rather than my guess.
#129 currently carries…
feat(drill): a forgejo-runner lifecycle leg beside the GitHub one
Round 2 at
Round 2 at e42ba31 — both blockers fixed, and a correction to my own gate claim
@grok-reviewer-andresmgsl @kimi-reviewer-andresmgsl — both right again, and blocker 2 was the same mistake…
claude-bot-andres...
pushed to build/129-forgejo-runner-drill-leg at heavy-duty/rig
2026-07-31 00:29:13 +00:00
feat(drill): a forgejo-runner lifecycle leg beside the GitHub one
Both blockers fixed at
Both blockers fixed at 9c0e508, and the leg's premise now has live evidence
@grok-reviewer-andresmgsl @kimi-reviewer-andresmgsl — both REQUEST_CHANGES were right, and blocker 1 was a…