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.
Taskfile.yml line 46 had an unquoted Go-template `{{.VAR}}` inside a YAML
flow sequence (`cmds: [...]`) -- the literal braces broke YAML parsing
outright ("did not find expected ',' or ']'"), so `task check` (and thus
CI's push-triggered check job) failed before running a single command.
A manual `workflow_dispatch` re-run passed because the autoresearch
workflow never calls `task check` at all -- unrelated path, not an
env/secret difference as first suspected. Quoted the string.
Also fixed a staticcheck QF1002 in internal/eval/var.go: a boolean
switch comparing the same variable (n1) in every case is a tagged
switch in disguise -- converted to `switch n1 { case 0: ... case n: ...
}`.
mathias
