[ops] import gemini loop and timmy orchestrator into sidecar truth (#152)
This commit was merged in pull request #152.
This commit is contained in:
@@ -179,6 +179,7 @@ They can still persist because they were started with `nohup` or by other parent
|
||||
|
||||
#### 8. gemini-loop.sh
|
||||
- Live process: `~/.hermes/bin/gemini-loop.sh`
|
||||
- Source of truth: `timmy-config/bin/gemini-loop.sh`
|
||||
- State files:
|
||||
- `~/.hermes/logs/gemini-loop.log`
|
||||
- `~/.hermes/logs/gemini-skip-list.json`
|
||||
@@ -187,6 +188,9 @@ They can still persist because they were started with `nohup` or by other parent
|
||||
- `~/.hermes/logs/gemini-pids/`
|
||||
- worktrees under `~/worktrees/gemini-w*`
|
||||
- per-issue logs `~/.hermes/logs/gemini-*.log`
|
||||
- Default-safe behavior:
|
||||
- only picks issues explicitly assigned to `gemini`
|
||||
- self-assignment is opt-in via `ALLOW_SELF_ASSIGN=1`
|
||||
- Old-state risk:
|
||||
- skip list suppresses issues for hours
|
||||
- lock directories can make issues look "already busy"
|
||||
@@ -203,20 +207,21 @@ printf '{}\n' > ~/.hermes/logs/gemini-active.json
|
||||
|
||||
#### 9. timmy-orchestrator.sh
|
||||
- Live process: `~/.hermes/bin/timmy-orchestrator.sh`
|
||||
- Source of truth: `timmy-config/bin/timmy-orchestrator.sh`
|
||||
- State files:
|
||||
- `~/.hermes/logs/timmy-orchestrator.log`
|
||||
- `~/.hermes/logs/timmy-orchestrator.pid`
|
||||
- `~/.hermes/logs/timmy-reviews.log`
|
||||
- `~/.hermes/logs/workforce-manager.log`
|
||||
- transient state dir: `/tmp/timmy-state-$$/`
|
||||
- Working behavior:
|
||||
- bulk-assigns unassigned issues to claude
|
||||
- Default-safe behavior:
|
||||
- reports unassigned issues by default
|
||||
- bulk auto-assignment is opt-in via `AUTO_ASSIGN_UNASSIGNED=1`
|
||||
- reviews PRs via `hermes chat`
|
||||
- runs `workforce-manager.py`
|
||||
- Old-state risk:
|
||||
- writes agent assignments back into Gitea
|
||||
- can repopulate agent queues even after you thought they were cleared
|
||||
- not represented in timmy-config/bin yet as of this audit
|
||||
- if `AUTO_ASSIGN_UNASSIGNED=1`, it will mutate Gitea assignments and can repopulate queues
|
||||
- still uses live process/log state as an input surface
|
||||
|
||||
### D. Hermes cron automations
|
||||
|
||||
@@ -344,7 +349,7 @@ cp ~/.hermes/sessions/sessions.json ~/.hermes/sessions/sessions.json.bak.$(date
|
||||
|
||||
1. README and DEPRECATED were corrected on 2026-04-04, but older local clones may still have stale prose.
|
||||
2. The quarantined launch agents now live under `~/Library/LaunchAgents.quarantine/timmy-legacy-20260404/`; if someone moves them back, the old state can return.
|
||||
3. `gemini-loop.sh` and `timmy-orchestrator.sh` are live but not yet mirrored into timmy-config/bin/.
|
||||
4. The open docs PR must be kept clean: do not mix operational script recovery and documentation history on the same branch.
|
||||
3. `gemini-loop.sh` and `timmy-orchestrator.sh` now have source-controlled homes in `timmy-config/bin/`, but any local forks or older runtime copies should be treated as suspect until redeployed.
|
||||
4. Keep docs-only PRs and script-import PRs on clean branches from `origin/main`; do not mix them with unrelated local history.
|
||||
|
||||
Until those are reconciled, trust this inventory over older prose.
|
||||
|
||||
Reference in New Issue
Block a user