feat(safety): require read-before-write for adapterConfig.env updates #12
Reference in New Issue
Block a user
Delete Branch "fix/gro-2049-adapter-env-preservation"
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?
Summary
Adds an explicit non-negotiable safety rule covering
adapterConfig.envupdates via the Paperclip API.Root cause of GRO-2049:
PATCH /api/agents/{agentId}with anadapterConfig.envpayload replaces the entire env object — any key omitted from the body is silently dropped. When Shedward's UAT passwords were added this way, all previously configured env vars were erased.Fix: The
safetyskill now mandates a read-merge-write pattern before anyadapterConfig.envwrite, with a code example showing the safejq-based merge approach. Skipping the read step is classified as a destructive operation.Changes
skills/safety/SKILL.md— new bullet under Non-negotiable rules with the safe pattern and examplecc @cpfarhood