Workers: scripts not fully synced to unstable #7

New issue

Closed

opened 2026-05-24 01:31:58 +00:00 by Mark · 0 comments

Mark commented

2026-05-24 01:31:58 +00:00

Owner

The workers directory on unstable has symlinks to ~/Projects/hermes-scripts/scripts/, but several scripts are missing or not executable:

gsd-gate referenced by gsd-issue-fixer.py but not found
feature-triage.py needed chmod fix (symlink target was executable but dispatch failed until explicit chmod)
quickfix-runner existed in hermes-scripts but had no symlink in workers/
forgejo-event-logger.sh and pr-review-prep.sh referenced in old YAML never existed (now cleaned up)

Root cause: The worker dir on unstable uses symlinks to ~/Projects/hermes-scripts/scripts/, but there is no sync mechanism keeping them in sync with the repo or ensuring new scripts get symlinked.

Fix: Set up a deployment mechanism (git pull + symlink sync or a deploy script) so that workers/ on unstable matches the repo state.

Labels: blocked:needs-decision

The workers directory on unstable has symlinks to `~/Projects/hermes-scripts/scripts/`, but several scripts are missing or not executable: - `gsd-gate` referenced by gsd-issue-fixer.py but not found - `feature-triage.py` needed chmod fix (symlink target was executable but dispatch failed until explicit chmod) - `quickfix-runner` existed in hermes-scripts but had no symlink in workers/ - `forgejo-event-logger.sh` and `pr-review-prep.sh` referenced in old YAML never existed (now cleaned up) **Root cause:** The worker dir on unstable uses symlinks to `~/Projects/hermes-scripts/scripts/`, but there is no sync mechanism keeping them in sync with the repo or ensuring new scripts get symlinked. **Fix:** Set up a deployment mechanism (git pull + symlink sync or a deploy script) so that workers/ on unstable matches the repo state. Labels: blocked:needs-decision