Each of the disabled app hidden after initial enrollment can be added back simply by sending the script command

   enable_system_app   Your_App_Bundle_ID

Thanks Raymond I've discovered this does work even if the device details screen was not showing it as installed under the applications menu.

Have you seen this scenario with android enterprise before?  Where using the stage programmer app does not remove all the system apps where afw#mobicontrol method does?

Edit: also discovered application run control removes visibility of an app too.  So probably the best way forward is to use stage to easily enroll and apply an ARC profile to remove what I need leaving the required OEM apps alone.

Some OEM brands/models have glitches in their implementation of hiding  bundled apps.  In the worst case, I've tested a model that does not hide any, possibly intentionally. As there are hundreds of brands and models to choose from, it's not a big deal to kick that model out of the choice for corporate owned device solutions that require the app-hiding feature.

Recently, I also found some inconsistent hiding behaviour  even for devices of the same model shipped in the same carton/batch.  The relative rare (much less frequent than 1 in every 50 on average) inconsistencies are seen in all enrollment methods (afw@mobicontrol hash tag,  QR code and NFC bump, etc.) and we are still looking for any possible pattern that cause this minor problem.   Any problem detected is simply handle by factory-resetting the device and retry the enrollment again.