fix(mcp): require duplicate checks before application creation

[vitorhugo-dotnet]

Summary

• requires MCP clients to search active and archived applications before Create-Application
• uses URL, vacancy title, organization, and recruiter instead of relying only on an optional link
• distinguishes confirmed duplicates from possible duplicates that require user confirmation
• repeats the guardrails in the creation resource, intake prompt, and tool description
• adds focused tests for the mandatory wording

Scope

Instruction and metadata changes only. No database constraint, URL normalization, new MCP tool, or backend duplicate-enforcement logic.

TDD verification

• RED: CI failed with the new expectations against the old URL-only wording
• GREEN: repository CI completed mvn -B -ntp clean verify successfully on the final head

Tests

• Backend CI/CD: Test and Build ✅
• Full Maven verification: mvn -B -ntp clean verify ✅

[github-actions]

Qodana for JVM

3 new problems were found

Inspection name	Severity	Problems
Nullability and data flow problems	🔶 Warning	1
Mismatched query and update of 'StringBuilder'	🔶 Warning	1
Simplifiable conditional expression	🔶 Warning	1

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.3.2
        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