[Bug] Solution export fails again on 9.2.26091.144 — code app package container missing (404 in GetBlobBytes) for every publish since 2026-09-24 ~08:00 UTC (regression of #464)

No repository file or test is named. Begin by reproducing the failure with pac solution export and compare a working and broken code app using the listed container and package-blob checks; use the support case and captured ActivityIds to determine whether an actionable repository change exists. Done means code app versions consistently retain their package containers and export successfully through pac, the maker portal, and the Web API.

Follow-up to #464 / #454, which were closed as fixed on 2026-09-22. We see the problem again, with a slightly different signature.

Environment

• Region: Germany (crm16), Dataverse 9.2.26091.144 (DEV and target env)
• Publish client: pac 1.52.1 (pac code push), @microsoft/power-apps ^1.2.5, Vite 7

Symptom

pac solution export / maker portal / Web API export (managed and unmanaged) fails with "An unexpected error occurred". Async operation message:

HttpRequestException: 404 (The specified resource does not exist.)
  at StorageBlobDataProvider.GetBlobBytes
  at CanvasAppHandlerInternal.MarkBlobForExportAndUpdateXmlNode
  at CanvasAppHandlerInternal.AddBlobFileXmlNodes
  at CanvasAppHandler.ExportItem

(#464 had 401 NoAuthenticationInformation in ListBlobNamesAndUrisInContainer — the listing seems fixed, but the package blob itself is not there.)

Observations

Using the same check as in #464 (anonymous ?restype=container&comp=list on properties.appUris.codeAppPackageUri), plus container properties and a direct index.html GET:

• App B's version history: all 28 versions up to 2026-09-09 have a readable container, all 18 versions since 2026-09-24 08:26 UTC have none. 5 consecutive republishes on 2026-09-25 06:15–06:16 UTC: all 404.
• App A had two broken versions on 2026-09-21 and good ones again from 2026-09-23 — so it is intermittent/server-side, not app-specific.
• A solution import into the target env on 2026-09-24 05:24 UTC also produced a version without container.
• Same storage account and container naming pattern for good and bad versions; no difference in app metadata (almMode, status, client versions).
• The apps themselves still run in the player; only the export path is broken.

Impact

All ALM routes for code apps are blocked again (export, pipelines, solution checker). The only practical advice until a fix: don't republish a code app that still exports.

A Microsoft support case has been opened; ActivityIds / async operation IDs / timestamps can be shared privately.