Code Apps - ALM Strategy

[tom-tmltd]

When a Code App is exported as part of a managed solution and imported into a target environment, the solution import completes successfully and the Code App component appears correctly within the solution. However, the app is not visible in the Apps list (under My Apps, Shared with Me, or All) and navigating to the app's direct URL returns an HTTP 404 / Not Found error.
The app metadata transfers correctly via the managed solution, but the compiled React app bundle does not appear to be deployed to the target environment's hosting infrastructure.

Steps to Reproduce:

Create a Code App in a development environment using pac code init and develop it locally
Deploy the Code App to the development environment using pac code push; app works correctly in dev
Add the Code App to an unmanaged solution in the development environment
Export the solution as managed
Import the managed solution into a target environment (e.g. UAT or Production)
Solution import reports success with no errors or warnings

Expected Behaviour:

The Code App should appear in the target environment's Apps list
Users with appropriate security roles should be able to launch and use the app
The app should be fully functional, consistent with other managed solution components (Model-Driven Apps, Canvas Apps, Cloud Flows, etc.)

Actual Behaviour:

The managed solution imports successfully; green tick, no errors
The Code App component is visible inside the solution with the correct display name, unique name, and type ("Code App")
The Code App does not appear in the Apps list under any filter (My Apps, Shared with Me, or All)
Navigating directly to the app URL (e.g. https://[org].crm11.dynamics.com/apps/code/[app_unique_name]) returns HTTP Error 404 / Not Found
The solution metadata is present but the compiled app bundle is not being served

Impact:

This effectively blocks any proper ALM process for Code Apps. Without managed solution support, organisations cannot:

Promote Code Apps through dev > test > production using standard solution pipelines
Maintain version control and rollback capability across environments
Comply with enterprise change management requirements
Use Code Apps in any scenario where managed solution deployment is mandated

The only current workaround is to authenticate the PAC CLI against each target environment and run pac code push directly, which completely undermines the managed solution ALM model and introduces significant risks around environment consistency, auditability, and controlled deployments.

Environment Details:

PAC CLI Version: 1.46+
Target Environment: Dataverse with Dynamics 365
Region: UK (crm11)
Solution Type: Managed
Code App Framework: React/TypeScript (standard pac code init scaffold)

Request:

Code Apps need to be first-class citizens in the managed solution ALM pipeline. Specifically:

The compiled app bundle should be included in the solution export and deployed to the target environment's hosting on import
Code Apps imported via managed solutions should appear in the Apps list alongside Canvas and Model-Driven apps
Standard sharing and security role assignment should work from the Apps list or solution context
The deployment behaviour should be consistent with how Canvas Apps and Model-Driven Apps work in managed solutions today

This is a critical gap for any organisation looking to adopt Code Apps in an enterprise context with proper governance and ALM practices.