Persistent agent runtime currently depends on AGENTD_AGENT_COMMAND (resolved from PATH and written into each per-agent env file), which is non-hermetic and can drift after deploy.
Implement a hermetic Nix-based runtime path so persistent sessions always execute an agent binary that is shipped as part of the agentd deployment/runtime closure, without AGENTD_AGENT_COMMAND in env files.
Scope:
Acceptance:
Implemented in commit c9281bce.
Changes:
-- : run Omni/Agent.hs so agentd ships with agent as local runtime dep.-- : run Omni/Agent.hs and resolveBundledAgentCommand.AGENTD_AGENT_COMMAND.AGENTD_AGENT_COMMAND.AGENTD_AGENT_COMMAND manifest env wiring.Validation:
Runtime smoke:
hermetic-smokeNote:
Ran deploy + restart rollout on live host. Shipped Omni/Agentd.hs via Omni/Ide/ship.sh (manifest now agentd rev c9281bce, store /nix/store/f2lcm43vhiax4slh52bq24l5736q3jdk-agentd). Restarted persistent agents: sd-coder, cfg-coder, omni-coder, intent-coder, paracoder. Verified all now status=running systemd=active. Verified generated runtime assets are hermetic: agentd-agent-exec uses absolute /nix/store/.../agent/bin/agent and no AGENTD_AGENT_COMMAND in exec/env files.
Implemented in commit c9281bce.
Changes:
Validation:
Runtime smoke:
Note: