Cursor and Aider are not supported harnesses. The context generator emitted five adapters (claude, agents, cursor, aider, system-prompt) and task check policed all five for drift — pure maintenance tax for two harnesses we don't use. This removes the dead two.
Changes
scripts/context-sync.sh — drop generate_cursor / generate_aider, their no-arg calls, and their case arms. Active adapters: claude, agents, system-prompt.
Taskfile.yml — drop the context:sync:cursor task; remove .cursorrules + .aider.conventions.md from the drift-guard file list in check.
Deleted .cursorrules and .aider.conventions.md (generated artifacts).
Why a PR (not direct-to-main)
I edited the generator and its drift-guard in tandem but couldn't run task check locally (egress-blocked from the build env). CI running task check is the real validation here — if the guard logic is wrong, this is where it shows. Merge when green.
Known follow-up — NOT in this PR (out of repo reach)
The canonical root context ~/dev/.context/AGENT.md (on flamingo, outside any repo) still:
says "Cursor uses .cursorrules; Aider uses .aider.conventions.md" in the workflow steps
lists Cursor/Aider under "Harness-agnostic principles"
Until that root file is hand-edited, task context:sync in other repos under ~/dev/ will keep emitting cursor/aider adapters there. This PR makes hyperguild clean; the workspace-wide cleanup needs that one manual edit on flamingo. Recommend doing it next time you're on flamingo.
Cursor and Aider are not supported harnesses. The context generator emitted five adapters (claude, agents, cursor, aider, system-prompt) and `task check` policed all five for drift — pure maintenance tax for two harnesses we don't use. This removes the dead two.
## Changes
- `scripts/context-sync.sh` — drop `generate_cursor` / `generate_aider`, their no-arg calls, and their `case` arms. Active adapters: claude, agents, system-prompt.
- `Taskfile.yml` — drop the `context:sync:cursor` task; remove `.cursorrules` + `.aider.conventions.md` from the drift-guard file list in `check`.
- Deleted `.cursorrules` and `.aider.conventions.md` (generated artifacts).
## Why a PR (not direct-to-main)
I edited the generator and its drift-guard in tandem but couldn't run `task check` locally (egress-blocked from the build env). CI running `task check` is the real validation here — if the guard logic is wrong, this is where it shows. **Merge when green.**
## Known follow-up — NOT in this PR (out of repo reach)
The canonical root context `~/dev/.context/AGENT.md` (on flamingo, outside any repo) still:
- lists `.cursorrules` + `.aider.conventions.md` under "How context propagates → Derived files"
- says "Cursor uses `.cursorrules`; Aider uses `.aider.conventions.md`" in the workflow steps
- lists Cursor/Aider under "Harness-agnostic principles"
Until that root file is hand-edited, `task context:sync` in *other* repos under `~/dev/` will keep emitting cursor/aider adapters there. This PR makes **hyperguild** clean; the workspace-wide cleanup needs that one manual edit on flamingo. Recommend doing it next time you're on flamingo.
Cursor and Aider are not supported harnesses. Remove generate_cursor
and generate_aider, their no-arg calls, and their case arms. The active
adapters are claude (CLAUDE.md), agents (AGENTS.md), and system-prompt
(.context/system-prompt.txt).
Drop the context:sync:cursor task and remove .cursorrules +
.aider.conventions.md from the drift-guard file list in `check`, now
that the generator no longer emits them.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Cursor and Aider are not supported harnesses. The context generator emitted five adapters (claude, agents, cursor, aider, system-prompt) and
task checkpoliced all five for drift — pure maintenance tax for two harnesses we don't use. This removes the dead two.Changes
scripts/context-sync.sh— dropgenerate_cursor/generate_aider, their no-arg calls, and theircasearms. Active adapters: claude, agents, system-prompt.Taskfile.yml— drop thecontext:sync:cursortask; remove.cursorrules+.aider.conventions.mdfrom the drift-guard file list incheck..cursorrulesand.aider.conventions.md(generated artifacts).Why a PR (not direct-to-main)
I edited the generator and its drift-guard in tandem but couldn't run
task checklocally (egress-blocked from the build env). CI runningtask checkis the real validation here — if the guard logic is wrong, this is where it shows. Merge when green.Known follow-up — NOT in this PR (out of repo reach)
The canonical root context
~/dev/.context/AGENT.md(on flamingo, outside any repo) still:.cursorrules+.aider.conventions.mdunder "How context propagates → Derived files".cursorrules; Aider uses.aider.conventions.md" in the workflow stepsUntil that root file is hand-edited,
task context:syncin other repos under~/dev/will keep emitting cursor/aider adapters there. This PR makes hyperguild clean; the workspace-wide cleanup needs that one manual edit on flamingo. Recommend doing it next time you're on flamingo.