Why is `Microsoft.AspNetCore.ClientAssets` still experimental and not released as stable?

The `Microsoft.AspNetCore.ClientAssets` package has been listed as experimental for several years and still appears under [https://github.com/aspnet/AspLabs](AspLabs) and NuGet pre-release status. The package solves a real problem for Razor Class Libraries that need integrated client-side build pipelines, and the manual MSBuild alternative is significantly more complex.

Given that:

* The package has existed for 2 years
* The functionality is stable and widely applicable
* The RCL ecosystem still needs an official, supported workflow for frontend asset building

Why has `Microsoft.AspNetCore.ClientAssets` not progressed beyond experimental? Is the package abandoned?

This will help teams like mine decide whether to adopt the package or do manual work using MSBuild. Is there a better alternative?

Start by reviewing the Microsoft.AspNetCore.ClientAssets package in AspLabs and its NuGet pre-release status. Compare its current Razor Class Library client-asset workflow with the manual MSBuild approach described in the issue. Done means a maintainer clarifies whether the package is supported, abandoned, or has a recommended alternative.

Written by the indexing model from the issue text.