arcodangeandClaude Opus 5
613f8b0a8f
sandbox-lifecycle.sh scales deployments to zero, patches the ArgoCD Application and runs DROP OWNED ... CASCADE. Every one of those ran against whatever kube-context happened to be current. This workstation also carries a CLIENT production cluster. On 2026-07-25 a `checkpoint refresh` was issued while the current context was do-nyc3-kissmetrics-prod-k8s-cluster: the script patched the ArgoCD Application, scaled `erp-sandbox` to zero and copied a prod secret — all against the client's cluster. Nothing was damaged only because that cluster has no `application` CRD and no erp/erp-sandbox namespaces, so each call failed silently under `|| true`. That is luck, not a control. - ERP_KUBE_CONTEXT (default: "default") pins the target; every kubectl call now goes through K(), so nothing inherits the ambient context. - assert_arcodange_cluster() proves the target by positive fingerprint — the erp, erp-sandbox and argocd namespaces AND the erp-sandbox ArgoCD Application. A client cluster cannot match all four by accident. Wired into all three entry points, before any mutation. Verified: refuses the client context, refuses an unknown context, passes on the homelab and completes normally. Co-Authored-By: Claude Opus 5 (1M context) <[email protected]> Claude-Session: https://claude.ai/code/session_01VRShc4QhLLU73FLHx9vskh
ERP
CLI — bin/arcodange
Read-only operational CLI for the Arcodange Dolibarr at erp.arcodange.lab. One entry point, subcommands per domain:
bin/arcodange ping # Dolibarr version + liveness
bin/arcodange whoami # confirm auth as ai_agent
bin/arcodange invoice list # KissMetrics invoices with payment state
bin/arcodange invoice audit 12 # JSON facts + PDF mandatory-mention audit
bin/arcodange payments state # per-invoice TTC vs payments reconciliation
bin/arcodange payments timeline --year 2026 # cash receipts with cumulative balance
bin/arcodange tva summary # CA3-ready collectée − déductible per month
bin/arcodange thirdparty audit-all # completeness audit, country-aware
bin/arcodange templates inspect 1 # recurring template health (frequency, next fire, …)
bin/arcodange snapshot --out /tmp/erp.json # full state dump with content_hash
bin/arcodange help # full command tree
Read-only by design. The underlying API key (ai_agent) has no write permissions; corrections go through the Dolibarr UI.
Credentials. Reads .claude/skills/dolibarr/.env (mode 600, gitignored). Setup instructions: .claude/skills/dolibarr/README.md.
Source of behaviour. Each subcommand delegates to a script under .claude/skills/<skill>/scripts/. The skills' SKILL.md files document the business logic and are also discoverable by Claude Code via skill triggers.
Dolibarr
Premiers démarrages
Si l'application log au démarrage l'erreur suivante:
Importing custom SQL from update_table_ownership.sql ...
sed: couldn't open temporary file /var/www/scripts/before-starting.d/sedwHcRlQ: Read-only file system
Il faudra prendre la main du shell du pod et executer:
kubectl exec -n erp `kubectl get pod -n erp -l app.kubernetes.io/name=erp -o=name` -c erp -- sh -c 'PGPASSWORD=${DOLI_DB_PASSWORD} psql -U ${DOLI_DB_USER} -h ${DOLI_DB_HOST} -p ${DOLI_DB_HOST_PORT} ${DOLI_DB_NAME} \
-f /var/www/scripts/before-starting.d/update_table_ownership.sql'
Sous peine de ne plus avoir les droits de consulter la base de données une fois les crédentials mis à jour par vault. Dans ce cas executer la commande mais avec les credentials d'admin postgres.