Do we do this hardcoding every time?

I'd love for that not to be the case but we haven't made the work to fix it. Main issue is that PackageVersion can't be used as that is a variable that changes depending on the project you are building, so when you are emitting a reference (like in this case or in the Directory.Packages.Helix.props) to a different package getting built, you don't want to use PackageVersion (as that is the package version of the project getting built) and instead you want to have a way to call a target into that reference to know whether or not that specific reference should be stable or not.

This is not super trivial and we haven't been able to prioritize it, so for now, we have to hard code each time we stabilize, but I'd love to not have to do this in the future :)

Same q here

[nitpick] The version literal 9.3.0 is duplicated across many lines. Extract this into a shared MSBuild property to reduce repetition and simplify future updates.

[nitpick] Hardcoding the SDK version can lead to more churn each release. Consider referencing a centralized version property (e.g., $(AspireSdkVersion)) to DRY up the files.

Why no update here?

Because this package is not going to get stable yet so no need to stabilize the reference: