Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
config/
Implementation and setup artifacts land here when a decision in ../decisions/DECISIONS.md moves from "adopt" to actually being done — install scripts, compose snippets, wiring notes, env templates for the tool being set up (e.g. jcode/OpenCode install + Claude integration, a local model gateway, a LifeOS port).
Convention
- One subdirectory per thing being set up (e.g.
config/opencode/,config/local-model-gateway/). - Keep a short
NOTES.mdin each explaining what it wires and how to verify it works.
Important — live config is edited in place, not stored here
The running Claude Code config is authoritative at its real locations and must be edited there,
because ~/.claude/settings.json references hooks/skills by absolute path:
/home/administrator/.claude/settings.json— global settings, hook + plugin registration./opt/appdata/docker/.claude/hooks/— hooks./opt/appdata/docker/.claude/skills/— homelab-skills plugin.
Back up before modifying (cp hook.sh hook.sh.bak.YYYYMMDD) and validate Python
(python3 -c "import ast; ast.parse(open('file').read())") before saving. This directory holds
the setup artifacts and reasoning, not a relocated copy of the live config.
Secrets
No secrets in this directory. Follow the homelab rule: secrets via the secrets-proxy / Vault references, never written into files or the terminal.