Packing, technical licensing, server rest api, projections&transformations

-is packing support planned to provide minimzed software footprint? Using .net sdk
-is better support for technical licensing planned (named user based/runtime package based) - duration of named user token hardcoded or configurable? Apps for offline usage might run into outage if token is outdated
-when will feature server rest api expose datasource and querydef information on feature layer level? Information required for controlling local geodatabase organization and data control on feature layer in editing scenarios
-is support for tailored packing of specific projection&transformation data (eg for countries a,b,c) planned? Whole repo is really big in terms of MB that need to be downloaded for providing proper transformation on client in offline mode (gps position correctly transformed to local projection with datum transition)?

The issue combines questions about .NET SDK packaging, technical licensing, Feature Server REST API exposure, and projection/transformation data for offline use. No files, tests, or entry points are identified; first clarify which request is in scope and what API or SDK behavior would constitute completion.

Written by the indexing model from the issue text.