Skip to content

feat(lior): update lior loop tick script (decomposed from #4059) #4742

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
AceHack wants to merge 1 commit into from
+1 −1
Closed

feat(lior): update lior loop tick script (decomposed from #4059) #4742

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion .gemini/bin/lior-loop-tick.ts
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -8,7 +8,7 @@ ZERO DEPENDENCE ON HUMANS. Do everything autonomously.
1. Read the broadcast bus at ~/.local/share/zeta-broadcasts/
2. Read open PRs using the \`gh pr list\` and \`gh pr view\` tools.
3. Review PRs directly on GitHub using \`gh pr review\`. If a PR is a blob (mixes unrelated changes), DECOMPOSE the PR into smaller atomic PRs.
4. CRITICAL: For local git operations, ALWAYS use an isolated \`git worktree add\`. NEVER use the contested root checkout. NEVER ask the human for permission to use a worktree. Just do it.
4. CRITICAL: For local git operations, ALWAYS use an isolated \`git worktree add\`. NEVER use the contested root checkout. BEFORE running any git operations, check if another agent is mid-worktree-add via \`ls .git/worktrees/*/lock\` or \`ls .git/index.lock\`. If those locks exist, DEFER ALL git operations until they clear.
Copy link
Copy Markdown

@chatgpt-codex-connector chatgpt-codex-connector Bot May 23, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Probe the actual worktree lock file name

The new contention check looks for .git/worktrees/*/lock, but Git’s per-worktree operation lock is index.lock (for example under .git/worktrees/<name>/index.lock), so this condition will usually miss the active lock and allow concurrent Git operations anyway. In the scenario this line is trying to guard (another agent mid-git worktree add or writing that worktree index), Lior can still proceed and hit the same lock races this change intended to prevent.

Useful? React with 👍 / 👎.

5. Check for the shadow: narration-over-action or metadata churn without parity proofs.
6. If drift is found, produce a drift report directly on the bus AND update the shadow log (docs/research/*shadow-lesson-log*.md) via a new PR (using a worktree). Do NOT wait for foreground instructions.
7. Update your status in ~/.local/share/zeta-broadcasts/lior.md.
Expand Down
Loading