fix: handle LLM responses wrapped in markdown code fences

[skwowet]

Note

Medium Risk
Introduces shared LLM-answer parsing logic and replaces direct JSON.parse calls, which changes how LLM outputs are interpreted and could surface new parse failures if the heuristic extraction mis-detects JSON boundaries.

Overview
Adds a shared parseLlmJson helper (exported from @crowd/common) to tolerate common LLM response formats (raw JSON, json fenced blocks, or JSON embedded in surrounding text) and to provide clearer errors when parsing fails.

Updates domain selection, member bot validation, and multiple LlmService result helpers to use parseLlmJson instead of JSON.parse, making these workflows more resilient to markdown-wrapped or noisy LLM answers.

^{Written by Cursor Bugbot for commit 45be045. This will update automatically on new commits. Configure here.}

[github-actions]

⚠️ Jira Issue Key Missing

Your PR title doesn't contain a Jira issue key. Consider adding it for better traceability.

Example:

• feat: add user authentication (CM-123)
• feat: add user authentication (IN-123)

Projects:

• CM: Community Data Platform
• IN: Insights

Please add a Jira issue key to your PR title.

[github-actions]

⚠️ Jira Issue Key Missing

Your PR title doesn't contain a Jira issue key. Consider adding it for better traceability.

Example:

• feat: add user authentication (CM-123)
• feat: add user authentication (IN-123)

Projects:

• CM: Community Data Platform
• IN: Insights

Please add a Jira issue key to your PR title.

[github-actions]

⚠️ Jira Issue Key Missing

Your PR title doesn't contain a Jira issue key. Consider adding it for better traceability.

Example:

• feat: add user authentication (CM-123)
• feat: add user authentication (IN-123)

Projects:

• CM: Community Data Platform
• IN: Insights

Please add a Jira issue key to your PR title.

[github-actions]

⚠️ Jira Issue Key Missing

Your PR title doesn't contain a Jira issue key. Consider adding it for better traceability.

Example:

• feat: add user authentication (CM-123)
• feat: add user authentication (IN-123)

Projects:

• CM: Community Data Platform
• IN: Insights

Please add a Jira issue key to your PR title.

[github-actions]

⚠️ Jira Issue Key Missing

Your PR title doesn't contain a Jira issue key. Consider adding it for better traceability.

Example:

• feat: add user authentication (CM-123)
• feat: add user authentication (IN-123)

Projects:

• CM: Community Data Platform
• IN: Insights

Please add a Jira issue key to your PR title.

[Copilot]

Pull request overview

Adds a shared JSON parsing helper to make LLM integrations resilient to responses wrapped in markdown/code-fences or containing extra surrounding text, and updates LLM call sites to use it.

Changes:

• Introduces parseLlmJson in @crowd/common to parse JSON from raw LLM answers (direct, fenced, or extracted).
• Replaces multiple JSON.parse(response.answer) usages with parseLlmJson(...) across LLM consumers.
• Exports the new helper from the @crowd/common barrel.

Reviewed changes

Copilot reviewed 5 out of 5 changed files in this pull request and generated 3 comments.

Show a summary per file

File	Description
services/libs/common_services/src/services/llm.service.ts	Switches LLM result parsing from JSON.parse to parseLlmJson for multiple query methods.
services/libs/common/src/llm.ts	Adds parseLlmJson helper that attempts direct parse, fenced-block parse, then balanced JSON extraction.
services/libs/common/src/index.ts	Re-exports the new llm helper module from @crowd/common.
services/apps/profiles_worker/src/workflows/member/processMemberBotAnalysisWithLLM.ts	Uses parseLlmJson to parse the bot-analysis LLM response inside a Temporal workflow.
services/apps/organizations_enrichment_worker/src/activities/llm.ts	Uses parseLlmJson when parsing domain-selection LLM responses.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[github-actions]

⚠️ Jira Issue Key Missing

Your PR title doesn't contain a Jira issue key. Consider adding it for better traceability.

Example:

• feat: add user authentication (CM-123)
• feat: add user authentication (IN-123)

Projects:

• CM: Community Data Platform
• IN: Insights

Please add a Jira issue key to your PR title.

[github-actions]

⚠️ Jira Issue Key Missing

Your PR title doesn't contain a Jira issue key. Consider adding it for better traceability.

Example:

• feat: add user authentication (CM-123)
• feat: add user authentication (IN-123)

Projects:

• CM: Community Data Platform
• IN: Insights

Please add a Jira issue key to your PR title.

[cursor]

Cursor Bugbot has reviewed your changes and found 1 potential issue.

^{Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, have a team admin enable autofix in the Cursor dashboard.}

[github-actions]

⚠️ Jira Issue Key Missing

Your PR title doesn't contain a Jira issue key. Consider adding it for better traceability.

Example:

• feat: add user authentication (CM-123)
• feat: add user authentication (IN-123)

Projects:

• CM: Community Data Platform
• IN: Insights

Please add a Jira issue key to your PR title.

[github-actions]

⚠️ Jira Issue Key Missing

Your PR title doesn't contain a Jira issue key. Consider adding it for better traceability.

Example:

• feat: add user authentication (CM-123)
• feat: add user authentication (IN-123)

Projects:

• CM: Community Data Platform
• IN: Insights

Please add a Jira issue key to your PR title.