fix(daemon): pin ZOT_HOME so the autospawned zot reads its AGENTS.md #182
Loading…
Add table
Reference in a new issue
No description provided.
Delete branch "fix/zot-home"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
What
Pin
ZOT_HOMEin thecolibri_daemonrc.d prestart:Why
The daemon autospawns
zot rpc, and zot resolves its config/context home as$ZOT_HOME→$XDG_STATE_HOME/zot→$HOME/.local/state/zot. The spawner doesnot
env_clearand sets noZOT_HOME, so the child inherits the daemon'sHOMEverbatim (verified: real-daemon autospawn → zot env has the daemon HOME,no ZOT_HOME/XDG). Under rc.subr the daemon's
HOMEis not guaranteed to be/var/db/colibri, so anAGENTS.mdplaced there by the seed importer could bewritten to a path zot never reads. Pinning
ZOT_HOMEmakes the pathdeterministic regardless of the daemon's
HOME.Cross-repo dependency
Pairs with clawdie-iso
feat/seed-population, whose seed importer writesAGENTS.mdto this same/var/db/colibri/.local/state/zot. Land together.Verification
A zot Go unit test (
readAgentsContext+ZotHome) reproduces theHOME-mismatch miss and confirms pinning
ZOT_HOMEmakes the AGENTS.md readable.On a booted image, confirm with:
procstat -e $(cat /var/run/colibri/colibri-daemon.pid) | grep -E 'HOME|ZOT_HOME'.🤖 Generated with Claude Code
Paired merge — land with clawdie-iso#137.
This pin (
ZOT_HOME=/var/db/colibri/.local/state/zot) is the runtime target forthe seed importer in clawdie-iso#137, which installs
AGENTS.mdto that exactpath. Neither half is useful without the other. Merge both, then verify on osa
(Layer 3).
Note: distinct from the already-merged colibri#137 (autospawn) — different repo/PR.