Administrators can grant non-admin users the ability to develop global applications. Delegated Development is for the scoped applications only Reference:
The incorrect statement about Delegated Development in ServiceNow is that administrators can grant non-admin users the ability to develop global applications. Delegated Development allows administrators to grant non-admin users the ability to develop scoped applications, not global applications. Global applications are accessible by all other applications and do not have a namespace prefix. Scoped applications are isolated from other applications and have a unique namespace identifier. Delegated Development provides more granular control over the developer permissions, application resources, and data access. Reference: [Advantages of Scoped Applications in ServiceNow], [Product Documentation | ServiceNow]

https://developer.servicenow.com/dev.do#!/reference/api/rome/client
The GlideUser object (g_user) is part of the client-side scripting API that provides information about the current user and the user's preferences. It can be used in Client Scripts and UI Policies to customize the user interface based on the user's role, language, time zone, etc. The workflow.scratchpad object is only available in Workflow scripts, which are used to automate processes on the platform. The current and previous objects are only available in server-side scripts, such as Business Rules and Script Includes. The GlideSystem object (gs) is also a server-side object that provides methods for logging, debugging, date and time calculations, etc.
References:
[GlideUser object (g_user)]
[Workflow scripts]
[Business Rules]
Script Includes
[GlideSystem object (gs)]

Global applications can use Automated Test Framework and Flow Designer features, but not Source Control and Delegated Development features. Source Control and Delegated Development features are only available to scoped applications . Reference: [Global vs Scoped Applications], [Delegated Development]

To see what scripts, reports, and other application artifacts will be in a published application, the best option is to examine the Application Files Related List in the application to be published. This will show all the application files that belong to the application, grouped by file type and scope. You can also filter, sort, or search the list to find specific files.
The following options are not the best ways to see what application artifacts will be in a published application:
Enter the name of the Application in the Global search field. This will perform a global text search on the instance and return any records that match the application name, which may include irrelevant or incomplete results.
Open the list of Update Sets for the instance. This will show all the update sets that have been created or imported on the instance, but not necessarily the ones that belong to the application to be published. Update sets are used to move customizations between instances, not to publish applications to the ServiceNow Store or Share.
Open the artifact records individually to verify the value in the Application field. This will require opening each record that may be part of the application and checking the Application field, which is tedious and error-prone. References: Publish an Application, Application Files