fix: show md rules and prompts in respective sections

[uinstinct]

Description

Previously the markdown prompts were showing under the rules sections. This was happening because rules extractor was picking up prompts from the prompts folder also. This PR fixes it.

resolves CON-4160

AI Code Review

• Team members only: AI review runs automatically when PR is opened or marked ready for review
• Team members can also trigger a review by commenting @continue-review

Checklist

• [] I've read the contributing guide
• [] The relevant docs, if any, have been updated or created
• [] The relevant tests, if any, have been updated or created

Screen recording or screenshot

Before	After

Tests

[ What tests were added or updated to ensure the changes work as expected? ]

---

Summary by cubic

Fixes misclassification so markdown prompts and rules appear in the correct sections. Rules load only from .continue/rules; prompts load from prompts folders (including .md). Resolves CON-4160.

• Bug Fixes
  • Removed .continue/prompts from rules loader.
  • Included .md in prompt file discovery.
  • Stopped scanning rules dir when collecting prompts.

[cubic-dev-ai]

1 issue found across 2 files

Prompt for AI agents (all 1 issues)

Understand the root cause of the following 1 issues and fix them.


<file name="core/config/markdown/loadMarkdownRules.ts">

<violation number="1" location="core/config/markdown/loadMarkdownRules.ts:57">
This comment still claims we load from multiple directories even though we now only scan .continue/rules. Please update the wording to reflect the single directory.</violation>
</file>

_{React with 👍 or 👎 to teach cubic. Mention @cubic-dev-ai to give feedback, ask questions, or re-run the review.}

[RomneyDa]

@uinstinct the invokable property means prompts and rules are the same underlying markdown and rules that are not invokable in the prompts directory will be stranded. I believe this is the original reason they were both read. You should be able to categorize based on invokable rather than changing the directory reading.

@tomasz I remember you had done some thinking on this, does that sound right?