[Bug]: Error downloading aldoc because it is not included in the artifact

AL-Go version

8.3

Describe the issue

When I use the “Create Reference Documentation” feature in CI/CD in AL-Go, it cannot find aldoc for country-specific on-premises artifacts.

In the https://github.com/microsoft/AL-Go/blob/main/Actions/BuildReferenceDocumentation/BuildReferenceDocumentation.HelperFunctions.ps1, the artifact-url is changed to a non-existent URL.
Would it be possible to define a separate artifactUrl for aldoc in the settings? Or to modify the configuration so that it points to an existing URL?

Expected behavior

AL-Go finds aldoc and can build the documentation.

Steps to reproduce

Use

"country": "de",
"artifact": "/OnPrem/27.4//latest",

in .AL-Go/settings.xml

Additional context (logs, screenshots, etc.)

https://github.com/microsoft/AL-Go/blob/main/Actions/BuildReferenceDocumentation/BuildReferenceDocumentation.HelperFunctions.ps1

function DownloadAlDoc {
    Param(
        [string] $artifactUrl = ''
    )
    if ("$ENV:aldocPath" -eq "") {
        $ENV:aldocCommand = ''
        Write-Host "Locating aldoc"
        if ($artifactUrl -notlike "https://*") {
            Write-Host "ArtifactUrl ($artifactUrl) provided, but not in the format of a URL, ignoring it and using latest non-insider sandbox artifact instead."
            $artifactUrl = Get-BCArtifactUrl -type sandbox -country core -select Latest -accept_insiderEula
        } elseif ($artifactUrl -notlike "*/core") {
            # Change country to core as aldoc is not shipped in country specific artifacts
            $artifactUrlCountry = $artifactUrl.Split('/')[-1]
            $artifactUrl = $artifactUrl.Replace("/$artifactUrlCountry",'/core')
        }
        Write-Host "Found artifactUrl: $artifactUrl"
        Write-Host "Downloading aldoc"

Error

2026-05-10T16:57:04.3302096Z Locating aldoc
2026-05-10T16:57:04.3321004Z Found artifactUrl: https://bcartifacts-exdbf9fwegejdqak.b02.azurefd.net/onprem/27.4.45366.45458/core
2026-05-10T16:57:04.3327902Z Downloading aldoc
2026-05-10T16:57:04.4680372Z Downloading artifact /onprem/27.4.45366.45458/core
2026-05-10T16:57:04.4930932Z Downloading C:\Users\runneradmin\AppData\Local\Temp\699138f2-a40b-4a7f-bc17-2ec29fd558d1.zip
2026-05-10T16:57:06.0940440Z Download-Artifacts Telemetry Correlation Id: e5f773b9-f9b6-4a11-be9b-5dcb7f0172ec
2026-05-10T16:57:06.7398275Z Enabling Microsoft telemetry...
2026-05-10T16:57:07.1451460Z ##[error]Unexpected error when running action. Error Message: Exception calling "GetResult" with "0" argument(s): "Response status code does not indicate success: 404 (The specified blob does not exist.)." Response status code does not indicate success: 404 (The specified blob does not exist.)., StackTrace: at Download-File, C:\ProgramData\BcContainerHelper\6.1.14\BcContainerHelper\Common\Download-File.ps1: line 83 <- at DownloadPackage, C:\ProgramData\BcContainerHelper\6.1.14\BcContainerHelper\Artifacts\Download-Artifacts.ps1: line 50 <- at Download-Artifacts, C:\ProgramData\BcContainerHelper\6.1.14\BcContainerHelper\Artifacts\Download-Artifacts.ps1: line 171 <- at DownloadAlDoc, D:\a\_actions\microsoft\AL-Go-Actions\v8.3\BuildReferenceDocumentation\BuildReferenceDocumentation.HelperFunctions.ps1: line 18 <- at GenerateDocsSite, D:\a\_actions\microsoft\AL-Go-Actions\v8.3\BuildReferenceDocumentation\BuildReferenceDocumentation.HelperFunctions.ps1: line 192 <- at <ScriptBlock>, D:\a\_actions\microsoft\AL-Go-Actions\v8.3\BuildReferenceDocumentation\BuildReferenceDocumentation.ps1: line 71 <- at <ScriptBlock>, D:\a\_temp\24f30bd5-a71f-4999-a303-7c38521602e5.ps1: line 3 <- at <ScriptBlock>, D:\a\_actions\microsoft\AL-Go-Actions\v8.3\Invoke-AlGoAction.ps1: line 21 <- at <ScriptBlock>, D:\a\_temp\24f30bd5-a71f-4999-a303-7c38521602e5.ps1: line 2 <- at <ScriptBlock>, <No file>: line 1

Start with Actions/BuildReferenceDocumentation/BuildReferenceDocumentation.HelperFunctions.ps1, especially DownloadAlDoc and its call from GenerateDocsSite. Reproduce the issue using country de and the on-premises artifact in .AL-Go/settings.xml, then verify that the reference-documentation workflow locates aldoc and completes the documentation build without the 404 error.