Would Medusa welcome native regression coverage for stock_location.metadata?

[jasonmerx]

Hi Medusa team,

I have a small testing/coverage question rather than a bug report.

While comparing Medusa 2.13.6 -> 2.14.0, I noticed that top-level
stock_location.metadata is now part of the public Admin HTTP type for
AdminStockLocation, apparently related to #15025, which added the
Stock Location metadata form in the Admin dashboard.

From a source comparison:

• StockLocation already had metadata in the module model.
• defaultAdminStockLocationFields already included metadata.
• The public Admin HTTP type now includes AdminStockLocation.metadata.
• The current stock-location integration test appears to cover
  address.metadata, but not top-level stock_location.metadata.

So I am not treating this as a backend bug or a breaking change.

My question is: would Medusa welcome a small native integration test that
locks this Admin response behavior?

The test would probably live in:

integration-tests/http/__tests__/stock-location/admin/stock-location.spec.ts

and cover:

1. create a stock location with top-level metadata
2. assert response.data.stock_location.metadata
3. retrieve the stock location by ID
4. assert the retrieved stock_location.metadata

No external dependency, browser runner, or CI change.

If this is useful, I can open a small PR against develop. If this should
instead be tracked under #14260 or handled differently, I’m happy to
follow that direction.