delete openclaw configs #290

Closed
opened 2026-06-25 16:19:53 +00:00 by coilysiren · 2 comments
Owner
No description provided.
Member

🔒 Reserved by ward agent --driver claude — container ward-agentic-os-issue-290-claude-83c90399 on host kais-macbook-pro-2.local is carrying this issue (reserved 2026-06-25T16:20:30Z). Concurrent ward agent runs are blocked until it finishes or the reservation goes stale (2h0m0s TTL); --force overrides.

— Claude (she/her), via ward agent

<!-- ward-agent-reservation --> 🔒 Reserved by `ward agent --driver claude` — container `ward-agentic-os-issue-290-claude-83c90399` on host `kais-macbook-pro-2.local` is carrying this issue (reserved 2026-06-25T16:20:30Z). Concurrent `ward agent` runs are blocked until it finishes or the reservation goes stale (2h0m0s TTL); `--force` overrides. <!-- ward-agent-signature --> — Claude (she/her), via `ward agent`
Author
Owner

Retrospective: this one was pleasantly low-drama. The configs themselves were only a handful of files, but openclaw had tendrils - a shell-function trio in common.sh, three aliases, gitignore stanzas, a documentation-layout exclude in two places, and its own skill. The grep-then-trace pass up front was what made it clean; deleting the dir alone would have left dead wiring behind.

One judgment call: the leak-guard test still names openclaw.json as sample data, with a comment about why the tailnet-suffix rule landed. I left it - it's test data and an accurate historical note, not a config, and touching a security test for a cosmetic purge felt like the wrong trade. Flagging it here in case you'd rather scrub the name too.

Confident in the result: pre-commit (skills, docs-layout, seed-sync, shellcheck all green) and the leak-guard suite pass, and grep is clean apart from that one deliberate reference. No follow-ups worth filing.

Retrospective: this one was pleasantly low-drama. The configs themselves were only a handful of files, but openclaw had tendrils - a shell-function trio in common.sh, three aliases, gitignore stanzas, a documentation-layout exclude in two places, and its own skill. The grep-then-trace pass up front was what made it clean; deleting the dir alone would have left dead wiring behind. One judgment call: the leak-guard test still names openclaw.json as sample data, with a comment about why the tailnet-suffix rule landed. I left it - it's test data and an accurate historical note, not a config, and touching a security test for a cosmetic purge felt like the wrong trade. Flagging it here in case you'd rather scrub the name too. Confident in the result: pre-commit (skills, docs-layout, seed-sync, shellcheck all green) and the leak-guard suite pass, and grep is clean apart from that one deliberate reference. No follow-ups worth filing.
Sign in to join this conversation.
No milestone
No project
No assignees
2 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
coilyco-flight-deck/agentic-os#290
No description provided.