Tool or config surface
Windsurf — agent rules / system prompts
File paths
.windsurfrules (legacy single file).windsurf/rules/*.md (newer per-rule format, if Windsurf has moved this direction)
Risky drift examples
Same shape as the Cursor rules issue — these are natural-language prompts, not structural config:
- Rules file removed → lost team-wide guardrail.
- Rules file substantially rewritten → policy event worth surfacing.
- Specific phrase additions (skip tests, ignore lint, "yes to everything") → higher-signal but requires a maintained phrase list.
- Rules file added → low-severity advisory.
Affected scope
Multiple repositories.
Review surface
Pull request check.
Notes
Same scope question as the Cursor rules issue: do we want ScopeTrail to expand from structural config drift into prompt-content analysis, and if so, at what precision/maintenance level? Cross-reference the Cursor issue's options 1/2/3 before deciding.
Filing per the inspection guidance — this is a request, not an implementation proposal. If you decide to support either Cursor or Windsurf rules, the other should probably ship at the same time since they have identical detection shape.
Tool or config surface
Windsurf — agent rules / system prompts
File paths
.windsurfrules(legacy single file).windsurf/rules/*.md(newer per-rule format, if Windsurf has moved this direction)Risky drift examples
Same shape as the Cursor rules issue — these are natural-language prompts, not structural config:
Affected scope
Multiple repositories.
Review surface
Pull request check.
Notes
Same scope question as the Cursor rules issue: do we want ScopeTrail to expand from structural config drift into prompt-content analysis, and if so, at what precision/maintenance level? Cross-reference the Cursor issue's options 1/2/3 before deciding.
Filing per the inspection guidance — this is a request, not an implementation proposal. If you decide to support either Cursor or Windsurf rules, the other should probably ship at the same time since they have identical detection shape.