3 Commits

Include renames

Author	SHA1	Message	Date
mathiasandClaude Opus 5	9d9401ea00	chore(context): adopt canonical context-sync.sh and re-sync adapters ... infra's scripts/context-sync.sh is the estate canonical, and it moved in infra 262369b (a SIGPIPE fix on the placeholder-reporting path: `printf | grep -o | head -1` became `head -1 < <(grep -o ...)`). Every other repo still carried the old line, so ContextSyncScriptDrift and ContextAdapterDrift were both firing. Also picks up the canonical AGENT.md change from local-dev a01ee80 — rule 5's GitOps review lane and the new precedence rule — which every repo's adapters need regenerated for regardless of the script. Refs mathias/infra#470 Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>	2026-09-30 10:37:18 +02:00
mathias	c7c182fb4d	fix(context): sync to the estate canonical context-sync.sh, drop Cursor/Aider ... Same drift as gitea-mcp: this repo's copy of context-sync.sh was two days stale against dma-cli's canonical (Mathias's Cursor/Aider decision, 2026-09-01) and CLAUDE.md itself was stale enough to need 97 lines of correction on regeneration -- this repo's context:sync was apparently never wired into `task check` at all (no drift assertion existed in its Taskfile), so nothing had been catching it. Found while building the estate-wide context-sync drift gate (ADR-0019). - script synced to canonical hash - .cursorrules, .aider.conventions.md, .aider.conf.yml deleted - stale context:sync:cursor Taskfile shortcut removed (would now hit the canonical script's own `exit 1` on an unknown adapter name) - CLAUDE.md, AGENTS.md, .context/system-prompt.txt regenerated against canonical task check -> exit 0.	2026-09-05 08:01:39 +02:00
mathias	d1193a57c6	Initial commit	2026-05-27 21:55:18 +00:00