yonlu/yellowjacket
1
1
Fork 0
Code Issues 49 Pull Requests Actions Packages Projects Releases 12 Wiki Activity

loop: worktree prerequisites, fetch-before-refresh, and corruption halt from P1 #240

New Issue
Closed
opened 2026-09-03 17:56:07 +00:00 by logan · 1 comment
logan commented 2026-09-03 17:56:07 +00:00
Collaborator
Copy Link
Copy Source

Three operational findings from the P1 adoption wave, all of which would break an unattended run:

  1. Loop worktree prerequisites. The pre-push go-test hook refused a push because the loop worktree had no frontend/dist (the Go //go:embed pattern in main.go) and no generated fixture library. A fresh worktree must run make build-frontend and make testdata once before its first push.
  2. Fetch immediately before the refresh merge. The merge leg refreshed docs/220-skill-check-scope against a cached origin/main (a merge had landed in between), CI went green on the wrong base, and the merge came back 405 "behind base" — one full CI cycle wasted. The skill says "fetch, then merge" but the failure mode deserves the emphasis.
  3. Interrupted-fetch corruption signature. The shared object store ended up with three 0-byte object files after a killed fetch; git fetch then fails with error: object file … is empty / unpack-objects failed, and a local ref + the loop worktree HEAD pointed at the dead sha1. The loop must recognize that signature and halt for a human rather than churn. (Repair was done manually: delete the 0-byte objects, re-fetch, re-point the dangling ref.)

All three belong in .pi/skills/yj-loop/ (ON procedure, merge authority, troubleshooting) and the first in plan 020's runtime section.

Three operational findings from the P1 adoption wave, all of which would break an unattended run: 1. **Loop worktree prerequisites.** The pre-push `go-test` hook refused a push because the loop worktree had no `frontend/dist` (the Go `//go:embed` pattern in `main.go`) and no generated fixture library. A fresh worktree must run `make build-frontend` and `make testdata` once before its first push. 2. **Fetch immediately before the refresh merge.** The merge leg refreshed `docs/220-skill-check-scope` against a *cached* `origin/main` (a merge had landed in between), CI went green on the wrong base, and the merge came back 405 "behind base" — one full CI cycle wasted. The skill says "fetch, then merge" but the failure mode deserves the emphasis. 3. **Interrupted-fetch corruption signature.** The shared object store ended up with three 0-byte object files after a killed fetch; `git fetch` then fails with `error: object file … is empty` / `unpack-objects failed`, and a local ref + the loop worktree HEAD pointed at the dead sha1. The loop must recognize that signature and halt for a human rather than churn. (Repair was done manually: delete the 0-byte objects, re-fetch, re-point the dangling ref.) All three belong in `.pi/skills/yj-loop/` (ON procedure, merge authority, troubleshooting) and the first in plan 020's runtime section.
logan added the Kind/Bug
Priority
Low
4
 labels 2026-09-03 17:56:07 +00:00
logan self-assigned this 2026-09-03 17:56:13 +00:00
logan added the
Status
In Progress
 label 2026-09-03 17:56:13 +00:00
logan commented 2026-09-03 17:56:13 +00:00
Author
Collaborator
Copy Link
Copy Source

⟦loop⟧ P1 finding, taking immediately. Branch fix/240-loop-operational-fixes.

Approach: three surgical edits to .pi/skills/yj-loop/SKILL.md (ON prerequisites, the fetch-before-refresh emphasis in merge authority, the interrupted-fetch corruption halt in troubleshooting) plus the worktree prerequisite clause in plan 020. No code.

⟦loop⟧ P1 finding, taking immediately. Branch `fix/240-loop-operational-fixes`. Approach: three surgical edits to `.pi/skills/yj-loop/SKILL.md` (ON prerequisites, the fetch-before-refresh emphasis in merge authority, the interrupted-fetch corruption halt in troubleshooting) plus the worktree prerequisite clause in plan 020. No code.
logan closed this issue 2026-09-03 18:17:03 +00:00
gitea-actions bot removed the
Status
In Progress
 label 2026-09-03 18:17:13 +00:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
Area/Design
Area/Downloads
Area/Explore
Area/Library-UI
Area/Metadata
Area/Packaging
Area/Player
Area/Queue
Area/Settings
Area/Shell-Nav
Compat/Breaking
Breaking change that won't be backward compatible
 Kind/Bug
Something is not working
 Kind/Documentation
Documentation changes
 Kind/Enhancement
Improve existing functionality
 Kind/Feature
New functionality
 Kind/Security
This is security issue
 Kind/Testing
Issue or pull request related to testing
 Platform/Android
Platform/Desktop
Priority
Critical
1
The priority is critical
Priority
High
2
The priority is high
Priority
Medium
3
The priority is medium
Priority
Low
4
The priority is low
Reviewed
Confirmed
1
Issue has been confirmed
Reviewed
Duplicate
2
This issue or pull request already exists
Reviewed
Invalid
3
Invalid issue
Reviewed
Won't Fix
3
This issue won't be fixed
Status
Blocked
1
Something is blocking this issue or pull request
Status
Need More Info
2
Feedback is required to reproduce issue or to continue work
Status
Abandoned
3
Somebody has started to work on this but abandoned work
Status
In Progress
Somebody is actively working on this right now
No labels Kind/Bug
Priority
Low
4
Milestone
No items
No Milestone
Projects
Clear projects
No projects
Assignees
Clear assignees
logan yonlu
No Assignees logan
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: yonlu/yellowjacket#240