More smashing bugs and Markdown Stances support

[xangcastle]

This pull request makes significant changes to the configuration and initialization of "stances" (AI assistant personas) in the project, streamlining how stance data is managed and loaded, simplifying the settings UI, and improving the chat tool's command execution handling. The most important changes are grouped below.

Stance Configuration and Loading Improvements:

• Refactored stance loading to dynamically parse all markdown files in the /stances resource directory, supporting both file and JAR resource loading. This replaces the previous approach of loading from a single JSON profile, allowing for easier extension and modular configuration of stances.
• Simplified the Stance data model by removing the scope, executionCommand, and allowedTools fields, centralizing all stance-specific instructions and configuration into the systemPrompt and frontmatter in the markdown files.

Settings UI Simplification:

• Removed all UI fields and logic related to scope, executionCommand, allowedTools, and coreWorkflow from RoninSettingsConfigurable, making the stance configuration interface cleaner and less error-prone. [1] [2] [3] [4] [5] [6] [7] [8]

System Prompt Handling:

• Updated the LLM service to use the stance's systemPrompt directly (as defined in the markdown), removing the hardcoded, monolithic prompt template and allowing each stance to fully define its own behavior and instructions.

Chat Tool Command Execution:

• Added a currentCommandFuture field to ChatToolWindow to track the currently running command, and improved cancellation handling to prevent follow-up actions if generation is cancelled. This makes command execution safer and more responsive to user actions. [1] [2] [3]

Minor Cleanups:

• Removed obsolete comments and code related to history pruning and custom endpoint handling in the LLM service.

[github-actions]

Qodana Community for JVM

3 new problems were found

Inspection name	Severity	Problems
Unused import directive	🔶 Warning	1
Unstable API Usage	🔶 Warning	1
Unused symbol	🔶 Warning	1

💡 Qodana analysis was run in the pull request mode: only the changed files were checked

View the detailed Qodana report

To be able to view the detailed Qodana report, you can either:

• Register at Qodana Cloud and configure the action
• Use GitHub Code Scanning with Qodana
• Host Qodana report at GitHub Pages
• Inspect and use qodana.sarif.json (see the Qodana SARIF format for details)

To get *.log files or any other Qodana artifacts, run the action with upload-result option set to true,
so that the action will upload the files as the job artifacts:

      - name: 'Qodana Scan'
        uses: JetBrains/qodana-action@v2025.1.1
        with:
          upload-result: true

Contact Qodana team

Contact us at qodana-support@jetbrains.com

• Or via our issue tracker: https://jb.gg/qodana-issue
• Or share your feedback: https://jb.gg/qodana-discussions