Merge master to official for 2026.5 release

[ravirk91]

Description

Type of Change

• Bug fix - [ ] New feature - [ ] Breaking change - [ ] Plugin update

Checklist

• PR description clearly describes the changes
• Target branch is correct (master for features, Releases/* for fixes)
• Latest code from target branch merged
• No commented/junk code included
• No new build warnings or errors
• All existing unit tests pass
• New unit tests added for new functionality
• Cross-platform compatibility verified (Windows/Linux/macOS)
• CI/CD pipeline passes
• Code follows project conventions (Act{Platform}{Type}, {Platform}Driver)
• Repository objects use [IsSerializedForLocalRepository] where needed
• Error handling uses Reporter.ToLog() pattern
• Documentation updated for user-facing changes
• Self-review completed and code review comments addressed

Summary by CodeRabbit

• New Features

  • Added URL column to the apps list grid view for easier reference.

• Bug Fixes

  • Increased folder path validation limit from 100 to 255 characters in HTML report configuration.
  • Enhanced MySQL database connection handling with improved SSL mode configuration.

• Improvements

  • Improved WireMock API request payload serialization and handling.
  • Added HTML encoding to GenAI service request fields for enhanced security.

• Chores

  • Updated ImageMagick library to version 14.13.0 across all projects.

[coderabbitai]

Walkthrough

This PR consolidates five independent updates: stricter folder path validation with new messaging, external API payload serialization enhancements, MySQL SSL mode configuration parsing, UI layout spacing adjustments, and a Magick.NET library version bump across project files.

Changes

Folder Path Validation Enhancement

Layer / File(s)	Summary
Message Pool Definition Ginger/GingerCoreCommon/ReporterLib/UserMsgsPool.cs	Adds FolderPathsAreTooLong enum value and registers a 255-character path-length warning message in the user message pool.
Validation Threshold Update Ginger/Ginger/Reports/HTMLReportAttachmentConfigurationPage.xaml.cs	Changes alternative HTML report folder length validation from > 100 to > 255 characters and updates the error message key reference.

External API Payload Handling

Layer / File(s)	Summary
Namespace Imports Ginger/GingerCoreNET/External/WireMock/WireMockAPI.cs, Ginger/GingerCoreNET/GenAIServices/GenAIServiceHelper.cs	Adds System.Net and System.Text.Json using directives to support JSON serialization and HTML encoding.
WireMock Request Serialization Ginger/GingerCoreNET/External/WireMock/WireMockAPI.cs	StartRecordingAsync uses JsonSerializer.Serialize() instead of string interpolation; CreateStubAsync and UpdateStubAsync now parse JSON and send canonical raw JSON text, with HTML encoding applied in stub creation.
GenAI Service HTML Encoding Ginger/GingerCoreNET/GenAIServices/GenAIServiceHelper.cs	Wraps credential-derived form fields (account, domainType, temperatureVal, maxTokensVal, dataPath) with WebUtility.HtmlEncode() and null-to-empty conversion; simplifies exception logging.

MySQL SSL Mode Configuration

Layer / File(s)	Summary
Connection String SSL Parsing Ginger/GingerCoreNET/Database/DatabaseOperations.cs	Connect() now parses ConnectionStringCalculated for SslMode settings, applies them to the connection builder, and conditionally assigns the final connection string only when calculated string is empty.

UI Layout Adjustments

Layer / File(s)	Summary
Appium Driver Layout Ginger/Ginger/Drivers/DriversConfigsEditPages/AppiumDriverEditPage.xaml	Increases xNativeHybRdBtn radio button margin from 8,0,0,0 to 36,0,0,0.
Applications Grid Column Ginger/Ginger/Environments/AppsListPage.xaml.cs	Adds EnvApplication.Url column (labeled URL) to grid definition; removes SetAllColumnsDefaultView() and InitViewItems() calls from SetGridView() method.

Dependency Updates

Layer / File(s)	Summary
Magick.NET Version Bump Ginger/Ginger/Ginger.csproj, Ginger/GingerCoreNET/GingerCoreNET.csproj, Ginger/GingerTest/GingerTest.csproj	Updates Magick.NET-Q16-AnyCPU PackageReference from version 14.11.1 to 14.13.0 across all three project files.

Estimated code review effort

🎯 3 (Moderate) | ⏱️ ~25 minutes

Possibly related PRs

• Ginger-Automation/Ginger#4488: Shares the same MySQL SSL mode connection-string parsing logic in DatabaseOperations.cs.
• Ginger-Automation/Ginger#4486: Implements the same folder path validation threshold increase and FolderPathsAreTooLong message key.
• Ginger-Automation/Ginger#4487: Updates Magick.NET-Q16-AnyCPU to the same 14.13.0 version across the same three csproj files.

Suggested reviewers

• Maheshkale447

Poem

🐰 A patchwork of tweaks, both great and small,
From folder paths stretching (255 chars, that's all!)
To JSON that's parsed with methodical care,
SSL modes secured, and margins to spare—
A rabbit's delight, these fixes so rare! 🌟

🚥 Pre-merge checks | ✅ 3 | ❌ 2

❌ Failed checks (2 warnings)

Check name	Status	Explanation	Resolution
Description check	⚠️ Warning	The PR description is largely empty with only the template structure present; the Description section contains no content and all checklist items are unchecked, providing no meaningful information about the changes.	Fill in the Description section with a summary of the key changes being merged, and ensure relevant checklist items are verified and marked before merging.
Docstring Coverage	⚠️ Warning	Docstring coverage is 37.50% which is insufficient. The required threshold is 80.00%.	Write docstrings for the functions missing them to satisfy the coverage threshold.

✅ Passed checks (3 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly summarizes the PR's main purpose: merging master into the official release branch for the 2026.5 release, which aligns with the changeset.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

📝 Generate docstrings

• Create stacked PR
• Commit on current branch

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch Merge-master-to-official-for-2026.5-release

Tip

💬 Introducing Slack Agent: The best way for teams to turn conversations into code.

Slack Agent is built on CodeRabbit's deep understanding of your code, so your team can collaborate across the entire SDLC without losing context.

• Generate code and open pull requests
• Plan features and break down work
• Investigate incidents and troubleshoot customer tickets together
• Automate recurring tasks and respond to alerts with triggers
• Summarize progress and report instantly

Built for teams:

• Shared memory across your entire org—no repeating context
• Per-thread sandboxes to safely plan and execute work
• Governance built-in—scoped access, auditability, and budget controls

One agent for your entire SDLC. Right inside Slack.

👉 Get started

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[codacy-production]

Not up to standards ⛔

_{NEW Get contextual insights on your PRs based on Codacy's metrics, along with PR and Jira context, without leaving GitHub. Enable AI reviewer
TIP This summary will be updated as you push new changes.}

[coderabbitai]

Actionable comments posted: 4

🤖 Prompt for all review comments with AI agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@Ginger/GingerCoreCommon/ReporterLib/UserMsgsPool.cs`:
- Line 619: The user-facing message for eUserMsgKey.FolderPathsAreTooLong in
UserMsgsPool.cs contradicts the validation (which allows length == 255 and flags
> 255); update the message string in the UserMsg constructor (the entry keyed by
eUserMsgKey.FolderPathsAreTooLong) to say something like "Provided folder paths
are too long. Please change them to be 255 characters or less" (or "no more than
255 characters") so it matches the > 255 guard.

In `@Ginger/GingerCoreNET/External/WireMock/WireMockAPI.cs`:
- Around line 160-171: The stub payload construction is not null-safe and
incorrectly HTML-encodes JSON; change the logic around stubMapping/body so you
never pass null into new StringContent (use empty string or "{}" as appropriate)
and remove WebUtility.HtmlEncode so the JSON is sent raw; update the block that
parses stubMapping (the JsonDocument.Parse branch and the fallback) and the
StringContent creation (the call to new StringContent(..., Encoding.UTF8,
contentType)) to use the non-null raw JSON string instead of HtmlEncoded data.

In `@Ginger/GingerCoreNET/GenAIServices/GenAIServiceHelper.cs`:
- Around line 107-109: In GenAIServiceHelper.cs update the catch block that
currently sets var error = "Failed to get access token" and calls
Reporter.ToLog(eLogLevel.ERROR, error, ex): replace the three-argument call with
the repository-required message-only overload Reporter.ToLog(eLogLevel.ERROR,
error) (leave the error string and exception handling intact but remove passing
ex to Reporter.ToLog) so the code uses the standard logging signature used
across this codebase.
- Around line 248-252: The multipart form field values are being HTML-encoded
before being wrapped in StringContent in GenAIServiceHelper.cs; remove the
WebUtility.HtmlEncode(...) calls so the raw results of
CredentialsCalculation(WorkSpace.Instance.Solution.AskLisaConfiguration....) are
passed directly into the StringContent for the fields "account", "domainType",
"temperatureVal", "maxTokensVal" and "dataPath"; keep using
CredentialsCalculation and StringContent but do not mutate the values with
HtmlEncode when building the MultipartFormDataContent.

🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

• Push a commit to this branch (recommended)
• Create a new PR with the fixes

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Repository UI

Review profile: ASSERTIVE

Plan: Pro

Run ID: 2211d00a-2d09-49ff-95f7-0cc93fd1c45f

📥 Commits

Reviewing files that changed from the base of the PR and between 5ec586e and c626a3b.

📒 Files selected for processing (10)

• Ginger/Ginger/Drivers/DriversConfigsEditPages/AppiumDriverEditPage.xaml
• Ginger/Ginger/Environments/AppsListPage.xaml.cs
• Ginger/Ginger/Ginger.csproj
• Ginger/Ginger/Reports/HTMLReportAttachmentConfigurationPage.xaml.cs
• Ginger/GingerCoreCommon/ReporterLib/UserMsgsPool.cs
• Ginger/GingerCoreNET/Database/DatabaseOperations.cs
• Ginger/GingerCoreNET/External/WireMock/WireMockAPI.cs
• Ginger/GingerCoreNET/GenAIServices/GenAIServiceHelper.cs
• Ginger/GingerCoreNET/GingerCoreNET.csproj
• Ginger/GingerTest/GingerTest.csproj

💤 Files with no reviewable changes (1)

• Ginger/Ginger/Environments/AppsListPage.xaml.cs

[coderabbitai]

⚠️ Potential issue | 🟡 Minor | ⚡ Quick win

User-facing message text is inaccurate — "less than 255" conflicts with the > 255 guard.

The validation in HTMLReportAttachmentConfigurationPage.xaml.cs fires when Length > 255, meaning a path of exactly 255 characters is valid. The current message text tells users to keep paths "less than 255 characters", which incorrectly implies 254 is the maximum.

✏️ Suggested fix

-{ eUserMsgKey.FolderPathsAreTooLong, new UserMsg(eUserMsgType.WARN, "Folder Paths Are Too Long", "Provided folder paths are too long. Please change them to be less than 255 characters", eUserMsgOption.OK, eUserMsgSelection.None) },
+{ eUserMsgKey.FolderPathsAreTooLong, new UserMsg(eUserMsgType.WARN, "Folder Paths Are Too Long", "Provided folder paths are too long. Please change them to be no more than 255 characters", eUserMsgOption.OK, eUserMsgSelection.None) },

📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change

	{ eUserMsgKey.FolderPathsAreTooLong, new UserMsg(eUserMsgType.WARN, "Folder Paths Are Too Long", "Provided folder paths are too long. Please change them to be less than 255 characters", eUserMsgOption.OK, eUserMsgSelection.None) },
	{ eUserMsgKey.FolderPathsAreTooLong, new UserMsg(eUserMsgType.WARN, "Folder Paths Are Too Long", "Provided folder paths are too long. Please change them to be no more than 255 characters", eUserMsgOption.OK, eUserMsgSelection.None) },

🤖 Prompt for AI Agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@Ginger/GingerCoreCommon/ReporterLib/UserMsgsPool.cs` at line 619, The
user-facing message for eUserMsgKey.FolderPathsAreTooLong in UserMsgsPool.cs
contradicts the validation (which allows length == 255 and flags > 255); update
the message string in the UserMsg constructor (the entry keyed by
eUserMsgKey.FolderPathsAreTooLong) to say something like "Provided folder paths
are too long. Please change them to be 255 characters or less" (or "no more than
255 characters") so it matches the > 255 guard.

[coderabbitai]

⚠️ Potential issue | 🔴 Critical | ⚡ Quick win

🧩 Analysis chain

🌐 Web query:

In .NET, what does new StringContent((string)null, Encoding.UTF8, "application/json")do, and shouldWebUtility.HtmlEncodebe used on JSON bodies sent asapplication/json?

💡 Result:

The expression new StringContent((string)null, Encoding.UTF8, "application/json") creates a StringContent instance intended to represent a null string value in the HTTP request body, with UTF-8 encoding and Content-Type header set to "application/json" [1][2][3]. In modern.NET versions (e.g.,.NET 8+ as of 2026), the constructor explicitly throws ArgumentNullException if the content string is null, as shown in the source code: ArgumentNullException.ThrowIfNull(content); before encoding [1]. This distinguishes null from empty string (which is allowed and sends an empty body). Earlier versions may have allowed it, treating null differently [4]. WebUtility.HtmlEncode should not be used on JSON bodies sent as application/json [5][6]. WebUtility.HtmlEncode converts special characters like < > " to HTML entities for safe insertion into HTML contexts [5]. JSON is a distinct format parsed directly by servers/clients based on Content-Type; HTML encoding corrupts valid JSON (e.g., "{"key": ""}" becomes invalid after encoding), causing parse errors [7][8]. JSON serializers handle escaping (e.g., \u003c for < in strings) as needed. Use it only for HTML output, not JSON payloads [6].

Citations:

• 1: https://github.com/dotnet/runtime/blob/main/src/libraries/System.Net.Http/src/System/Net/Http/StringContent.cs
• 2: https://learn.microsoft.com/en-us/dotnet/api/system.net.http.stringcontent?view=net-10.0
• 3: https://learn.microsoft.com/en-us/dotnet/api/system.net.http.stringcontent.-ctor?view=net-10.0
• 4: [release/7.0] Default media type used when 'null' is passed to StringContent #81506 dotnet/runtime#83425
• 5: https://technet.microsoft.com/library/system.net.webutility.htmlencode
• 6: https://security.stackexchange.com/questions/202196/encoding-output-in-json-http-api
• 7: https://stackoverflow.com/questions/37026480/httppost-request-not-working-when-json-string-has-html-in
• 8: https://www.stevejgordon.co.uk/asp-net-mvc-core-html-encoding-json-body

---

🏁 Script executed:

cat -n Ginger/GingerCoreNET/External/WireMock/WireMockAPI.cs | sed -n '150,180p'

Repository: Ginger-Automation/Ginger

Length of output: 1628

---

🏁 Script executed:

cat -n Ginger/GingerCoreNET/External/WireMock/WireMockAPI.cs | sed -n '215,240p'

Repository: Ginger-Automation/Ginger

Length of output: 1338

---

🏁 Script executed:

head -30 Ginger/GingerCoreNET/External/WireMock/WireMockAPI.cs | cat -n

Repository: Ginger-Automation/Ginger

Length of output: 1181

---

Fix stub payload construction: null-safe content and no HTML encoding for JSON.

There are two correctness issues:

1. Lines 161-164 and 223-226 assign body = stubMapping when stubMapping is null/empty, causing new StringContent(null, ...) to throw ArgumentNullException at runtime.
2. Line 171 HTML-encodes the JSON body before sending as application/json, which corrupts valid JSON (e.g., " becomes ").

Suggested fix

-                    string body;
-                    if (string.IsNullOrEmpty(stubMapping))
-                    {
-                        body = stubMapping;
-                    }
-                    else
-                    {
-                        using JsonDocument doc = JsonDocument.Parse(stubMapping);
-                        body = doc.RootElement.GetRawText();
-                    }
-
-                    var content = new StringContent(WebUtility.HtmlEncode(body), Encoding.UTF8, contentType);
+                    string body = string.IsNullOrWhiteSpace(stubMapping)
+                        ? string.Empty
+                        : JsonDocument.Parse(stubMapping).RootElement.GetRawText();
+
+                    var content = new StringContent(body, Encoding.UTF8, contentType);
@@
-                    string body;
-                    if (string.IsNullOrEmpty(stubMapping))
-                    {
-                        body = stubMapping;
-                    }
-                    else
-                    {
-                        using JsonDocument doc = JsonDocument.Parse(stubMapping);
-                        body = doc.RootElement.GetRawText();
-                    }
+                    string body = string.IsNullOrWhiteSpace(stubMapping)
+                        ? string.Empty
+                        : JsonDocument.Parse(stubMapping).RootElement.GetRawText();

Also applies to: 222-233

🤖 Prompt for AI Agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@Ginger/GingerCoreNET/External/WireMock/WireMockAPI.cs` around lines 160 -
171, The stub payload construction is not null-safe and incorrectly HTML-encodes
JSON; change the logic around stubMapping/body so you never pass null into new
StringContent (use empty string or "{}" as appropriate) and remove
WebUtility.HtmlEncode so the JSON is sent raw; update the block that parses
stubMapping (the JsonDocument.Parse branch and the fallback) and the
StringContent creation (the call to new StringContent(..., Encoding.UTF8,
contentType)) to use the non-null raw JSON string instead of HtmlEncoded data.

[coderabbitai]

⚠️ Potential issue | 🟡 Minor | ⚡ Quick win

Use the standard error-logging signature in this catch block.

Line 108 uses Reporter.ToLog(eLogLevel.ERROR, error, ex), but this repository requires the message-only overload for error logs.

Suggested fix

-                var error = "Failed to get access token";
-                Reporter.ToLog(eLogLevel.ERROR, error, ex);
+                var error = $"Failed to get access token. {ex.Message}";
+                Reporter.ToLog(eLogLevel.ERROR, error);

As per coding guidelines **/*.cs: Use Reporter.ToLog(eLogLevel.ERROR, message) for logging errors.

📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change

	var error = "Failed to get access token";
	Reporter.ToLog(eLogLevel.ERROR, $"{error}, Error :{ex.Message}");
	Reporter.ToLog(eLogLevel.ERROR, $"{error}, Error :{ex.Message}, InnerException:{ex.InnerException},StackTrace:{ex.StackTrace}");
	Reporter.ToLog(eLogLevel.ERROR, error, ex);
	return false;
	var error = $"Failed to get access token. {ex.Message}";
	Reporter.ToLog(eLogLevel.ERROR, error);
	return false;

🤖 Prompt for AI Agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@Ginger/GingerCoreNET/GenAIServices/GenAIServiceHelper.cs` around lines 107 -
109, In GenAIServiceHelper.cs update the catch block that currently sets var
error = "Failed to get access token" and calls Reporter.ToLog(eLogLevel.ERROR,
error, ex): replace the three-argument call with the repository-required
message-only overload Reporter.ToLog(eLogLevel.ERROR, error) (leave the error
string and exception handling intact but remove passing ex to Reporter.ToLog) so
the code uses the standard logging signature used across this codebase.

[coderabbitai]

⚠️ Potential issue | 🟠 Major | ⚡ Quick win

🧩 Analysis chain

🌐 Web query:

In .NET, is System.Net.WebUtility.HtmlEncodeappropriate for values sent throughMultipartFormDataContent/StringContent, or is it intended only for HTML output encoding?

💡 Result:

Answer: No—System.Net.WebUtility.HtmlEncode is not the appropriate encoding step for values you put into MultipartFormDataContent/StringContent as general “HTTP/form data escaping”. It’s intended for HTML entity encoding (and its docs even describe HTML encoding behavior), not for making arbitrary multipart/form-data fields safe to transmit. For multipart form values, you should generally send the raw string (letting StringContent handle HTTP body bytes/charset) and only apply encoding appropriate to the receiving context (e.g., HTML-escape only when inserting into HTML, URL-encode only for URL/query-string components). Why: 1) WebUtility.HtmlEncode is defined as converting a string into an HTML-encoded string (HTML entities), including a remark that encoding converts characters into “character-entity equivalents” and gives < and > as examples for HTTP transmission when embedded in text/HTML blocks. That describes HTML entity encoding, not multipart/form-data field escaping rules [1]. 2) MultipartFormDataContent is a container for content encoded using the multipart/form-data MIME type. It “adds required Content-Disposition headers to [the] content object added to the collection” and serializes the multipart stream. It does not state that callers should pre–HTML-encode field values [2]. 3) If you HTML-encode form fields, you can change the payload semantics: e.g., a value containing & becomes &, and the server will receive & unless it explicitly HTML-decodes it. Multipart/form-data processing is governed by MIME/form encoding rules (e.g., how parts are structured and how headers like Content-Disposition are represented), not by HTML entity encoding. Practical guidance: - For MultipartFormDataContent fields, typically do: form.Add(new StringContent(value, Encoding.UTF8), "name"); and avoid HTML-encoding unless the server expects HTML entities. - Apply encoding at the “output to HTML” step: if (and only if) the server later renders the submitted value into an HTML page, then HTML encoding should happen right before HTML rendering. So: WebUtility.HtmlEncode is primarily an HTML entity encoder, not a general-purpose “safe for HTTP form data/multipart” encoder.

Citations:

• 1: https://learn.microsoft.com/en-us/dotnet/api/system.net.webutility.htmlencode?view=net-10.0
• 2: https://learn.microsoft.com/en-us/dotnet/api/system.net.http.multipartformdatacontent?view=net-10.0

---

Remove WebUtility.HtmlEncode() from multipart form field values.

Lines 248-252 apply WebUtility.HtmlEncode(...) before StringContent. HtmlEncode is intended for HTML entity encoding only and is inappropriate for form-data payloads. It mutates field values (e.g., & becomes &), which can break backend parsing and value matching. For MultipartFormDataContent, send raw string values directly.

Suggested fix

-                { new StringContent(WebUtility.HtmlEncode(CredentialsCalculation(WorkSpace.Instance.Solution.AskLisaConfiguration.Account) ?? string.Empty)), "account" },
-                { new StringContent(WebUtility.HtmlEncode(CredentialsCalculation(WorkSpace.Instance.Solution.AskLisaConfiguration.DomainType) ?? string.Empty)), "domainType" },
-                { new StringContent(WebUtility.HtmlEncode(CredentialsCalculation(WorkSpace.Instance.Solution.AskLisaConfiguration.TemperatureLevel) ?? string.Empty)), "temperatureVal" },
-                { new StringContent(WebUtility.HtmlEncode(CredentialsCalculation(WorkSpace.Instance.Solution.AskLisaConfiguration.MaxTokenValue) ?? string.Empty)), "maxTokensVal" },
-                { new StringContent(WebUtility.HtmlEncode(CredentialsCalculation(WorkSpace.Instance.Solution.AskLisaConfiguration.DataPath) ?? string.Empty)), "dataPath" }
+                { new StringContent(CredentialsCalculation(WorkSpace.Instance.Solution.AskLisaConfiguration.Account) ?? string.Empty), "account" },
+                { new StringContent(CredentialsCalculation(WorkSpace.Instance.Solution.AskLisaConfiguration.DomainType) ?? string.Empty), "domainType" },
+                { new StringContent(CredentialsCalculation(WorkSpace.Instance.Solution.AskLisaConfiguration.TemperatureLevel) ?? string.Empty), "temperatureVal" },
+                { new StringContent(CredentialsCalculation(WorkSpace.Instance.Solution.AskLisaConfiguration.MaxTokenValue) ?? string.Empty), "maxTokensVal" },
+                { new StringContent(CredentialsCalculation(WorkSpace.Instance.Solution.AskLisaConfiguration.DataPath) ?? string.Empty), "dataPath" }

📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change

	{ new StringContent(WebUtility.HtmlEncode(CredentialsCalculation(WorkSpace.Instance.Solution.AskLisaConfiguration.Account) ?? string.Empty)), "account" },
	{ new StringContent(WebUtility.HtmlEncode(CredentialsCalculation(WorkSpace.Instance.Solution.AskLisaConfiguration.DomainType) ?? string.Empty)), "domainType" },
	{ new StringContent(WebUtility.HtmlEncode(CredentialsCalculation(WorkSpace.Instance.Solution.AskLisaConfiguration.TemperatureLevel) ?? string.Empty)), "temperatureVal" },
	{ new StringContent(WebUtility.HtmlEncode(CredentialsCalculation(WorkSpace.Instance.Solution.AskLisaConfiguration.MaxTokenValue) ?? string.Empty)), "maxTokensVal" },
	{ new StringContent(WebUtility.HtmlEncode(CredentialsCalculation(WorkSpace.Instance.Solution.AskLisaConfiguration.DataPath) ?? string.Empty)), "dataPath" }
	{ new StringContent(CredentialsCalculation(WorkSpace.Instance.Solution.AskLisaConfiguration.Account) ?? string.Empty), "account" },
	{ new StringContent(CredentialsCalculation(WorkSpace.Instance.Solution.AskLisaConfiguration.DomainType) ?? string.Empty), "domainType" },
	{ new StringContent(CredentialsCalculation(WorkSpace.Instance.Solution.AskLisaConfiguration.TemperatureLevel) ?? string.Empty), "temperatureVal" },
	{ new StringContent(CredentialsCalculation(WorkSpace.Instance.Solution.AskLisaConfiguration.MaxTokenValue) ?? string.Empty), "maxTokensVal" },
	{ new StringContent(CredentialsCalculation(WorkSpace.Instance.Solution.AskLisaConfiguration.DataPath) ?? string.Empty), "dataPath" }

🤖 Prompt for AI Agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@Ginger/GingerCoreNET/GenAIServices/GenAIServiceHelper.cs` around lines 248 -
252, The multipart form field values are being HTML-encoded before being wrapped
in StringContent in GenAIServiceHelper.cs; remove the WebUtility.HtmlEncode(...)
calls so the raw results of
CredentialsCalculation(WorkSpace.Instance.Solution.AskLisaConfiguration....) are
passed directly into the StringContent for the fields "account", "domainType",
"temperatureVal", "maxTokensVal" and "dataPath"; keep using
CredentialsCalculation and StringContent but do not mutate the values with
HtmlEncode when building the MultipartFormDataContent.