P1 adoption-wave findings (#240), fixed in the loop's own protocol.
.pi/skills/yj-loop/SKILL.md — ON procedure: provision the worktree (make build-frontend + make testdata) before the first push; merge authority: git fetch origin in the same breath as the refresh merge (a cached origin/main cost one full CI cycle on a behind-base 405); troubleshooting: the interrupted-fetch corruption signature halts the loop for a human, with the repair recipe.
.planning/plans/active/020-autonomous-backlog-loop.md — same provisioning clause under Runtime.
Verification run
make skill-check — 48 documented targets, all present (the hook's run)
scripts/commit-check.sh — well-formed subject
Docs-only: no Go/frontend change; CI still runs the full gate on this PR
## What this is
P1 adoption-wave findings (#240), fixed in the loop's own protocol.
- `.pi/skills/yj-loop/SKILL.md` — ON procedure: provision the worktree (`make build-frontend` + `make testdata`) before the first push; merge authority: `git fetch origin` in the same breath as the refresh merge (a cached `origin/main` cost one full CI cycle on a behind-base 405); troubleshooting: the interrupted-fetch corruption signature halts the loop for a human, with the repair recipe.
- `.planning/plans/active/020-autonomous-backlog-loop.md` — same provisioning clause under Runtime.
## Verification run
- `make skill-check` — 48 documented targets, all present (the hook's run)
- `scripts/commit-check.sh` — well-formed subject
- Docs-only: no Go/frontend change; CI still runs the full gate on this PR
Closes #240
Three P1 adoption-wave findings, all of which break an unattended run.
The worktree needs make build-frontend and make testdata once before its
first push — the pre-push go-test hook embeds frontend/dist and the
fixture library and refused the push without them. The merge leg now
says to fetch origin/main in the same breath as the refresh merge: a
cached origin/main merged against the wrong base, CI went green on it,
and the merge came back 405 "behind base" — a full cycle wasted. And a
killed fetch leaves 0-byte objects in the shared store whose signature
(error: object file … is empty / unpack-objects failed) must halt the
loop for a human instead of churning, with the repair recipe written
down.
Closes#240
logan
merged commit 18f10e966b into main2026-09-03 18:17:02 +00:00
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
What this is
P1 adoption-wave findings (#240), fixed in the loop's own protocol.
.pi/skills/yj-loop/SKILL.md— ON procedure: provision the worktree (make build-frontend+make testdata) before the first push; merge authority:git fetch originin the same breath as the refresh merge (a cachedorigin/maincost one full CI cycle on a behind-base 405); troubleshooting: the interrupted-fetch corruption signature halts the loop for a human, with the repair recipe..planning/plans/active/020-autonomous-backlog-loop.md— same provisioning clause under Runtime.Verification run
make skill-check— 48 documented targets, all present (the hook's run)scripts/commit-check.sh— well-formed subjectCloses #240