Development record
The pinned PATH symlink written by ahoy install targets pluginBinaryPath(pluginRoot) — a commit-stamped plugin cache directory. Every plugin update orphans that directory and the harness garbage-collects it ~14 days after .orphaned_at, so for a marketplace user the ~/.local/bin/abcd symlink silently dangles within two weeks of every update. The heal path (symlink.dangling gap + re-running ahoy install) exists but nothing triggers it automatically. Fix follows the persistent-data-dir relocation: point the pinned symlink at the data-dir binary, whose path is stable across updates.
The pinned PATH symlink written by ahoy install targets pluginBinaryPath(pluginRoot) — a commit-stamped plugin cache directory. Every plugin update orphans that directory and the harness garbage-collects it ~14 days after .orphaned_at, so for a marketplace user the ~/.local/bin/abcd symlink silently dangles within two weeks of every update. The heal path (symlink.dangling gap + re-running ahoy install) exists but nothing triggers it automatically. Fix follows the persistent-data-dir relocation: point the pinned symlink at the data-dir binary, whose path is stable across updates.
Frontmatter
| id | iss-2608210934566222 |
|---|---|
| type | issue |
| lifecycle | resolved |
| severity | major |
.abcd/work/issues/resolved/iss-2608210934566222-pinned-symlink-targets-gcd-cache-dir.md
open on GitHub ↗ · commit history ↗
References1
- itd-132The hook binary survives plugin updatesrelated
mentions1
- durable-state-lives-where-the-platform-says-it-survivesDurable state lives where the platform says it survives