task check reports false context drift in any clone outside ~/dev #70

Open
opened 2026-10-05 14:16:32 +00:00 by mathias · 0 comments
Owner

Found 2026-10-05 during the estate CI hygiene sweep. In a clone outside ~/dev (for example ~/.cache/…), task check fails with a context-drift error even though the adapters are current. The script looks for canonical AGENT.md relative to ~/dev.

Workaround: run it with ROOT_CONTEXT=$HOME/dev/.context/AGENT.md task check.

Fix: when ROOT_CONTEXT is unset and ../.context/AGENT.md doesn't exist, either fall back to $HOME/dev/.context/AGENT.md or skip the drift step with a loud notice. A gate that fails in every agent scratch clone trains agents to bypass it.


Created via git-mcp on behalf of @mathias

Found 2026-10-05 during the estate CI hygiene sweep. In a clone outside `~/dev` (for example `~/.cache/…`), `task check` fails with a context-drift error even though the adapters are current. The script looks for canonical AGENT.md relative to `~/dev`. **Workaround:** run it with `ROOT_CONTEXT=$HOME/dev/.context/AGENT.md task check`. **Fix:** when ROOT_CONTEXT is unset and `../.context/AGENT.md` doesn't exist, either fall back to `$HOME/dev/.context/AGENT.md` or skip the drift step with a loud notice. A gate that fails in every agent scratch clone trains agents to bypass it. --- _Created via git-mcp on behalf of @mathias_
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: mathias/gitea-mcp#70