@@ -33,7 +33,7 @@ This feature is opt-in. If you don't configure a snapshot repository, {% data va
 
 Configure the following settings using `ghe-config` over SSH. For more information, see [AUTOTITLE](/admin/administering-your-instance/administering-your-instance-from-the-command-line/accessing-the-administrative-shell-ssh).
 
-You'll apply the configuration to register the snapshot repository with Elasticsearch. The repository is named `search_index_snapshots-VERSION`, where `VERSION` is the current {% data variables.product.prodname_ghe_server %} release version.
+You'll apply the configuration to register the snapshot repository with Elasticsearch. The repository is named `search_index_snapshots-vVERSION`, where `VERSION` is the current {% data variables.product.prodname_ghe_server %} release version.
 
 ### Azure Blob storage
 
@@ -106,7 +106,7 @@ You'll apply the configuration to register the snapshot repository with Elastics
 After configuration apply completes, confirm the snapshot repository was registered.
 
 ```shell
-curl -k "http://127.0.0.1:9200/_snapshot/search_index_snapshots-$(ghe-version -v)/_status"
+curl -k "http://127.0.0.1:9200/_snapshot/search_index_snapshots-v$(ghe-version -v)/_status"
 ```
 
 If a required secret is missing, configuration apply fails while registering the repository. Update the secrets and rerun `ghe-config-apply` to retry.
@@ -137,9 +137,9 @@ You can manage Elasticsearch snapshots directly using the following commands. Ru
 
 | Command | Description |
 | --- | --- |
-| `ghe-es-create-snapshot` | Creates a new snapshot in the configured repository. |
-| `ghe-es-list-snapshots` | Lists snapshot repositories, or snapshots within a repository. |
-| `ghe-es-restore-snapshot` | Restores search indices from a snapshot. |
+| `/usr/local/share/enterprise/ghe-es-create-snapshot` | Creates a new snapshot in the configured repository. |
+| `/usr/local/share/enterprise/ghe-es-list-snapshots` | Lists snapshot repositories, or snapshots within a repository. |
+| `/usr/local/share/enterprise/ghe-es-restore-snapshot` | Restores search indices from a snapshot. |
 
 > [!TIP]
 > For routine backups and restores, use {% data variables.product.prodname_enterprise_backup_utilities %} or {% data variables.product.prodname_enterprise_backup_service %} instead of these commands directly. The backup tooling coordinates Elasticsearch snapshots with the rest of your instance's data to ensure a consistent backup or restore. Use the manual commands only when you need to manage search index snapshots independently of a full instance backup or restore.
@@ -151,13 +151,13 @@ You can restore a snapshot created by an earlier {% data variables.product.prodn
 1. List available snapshots for the earlier version.
 
    ```shell
-   ghe-es-list-snapshots -v 3.14.0
+   /usr/local/share/enterprise/ghe-es-list-snapshots -v 3.14.0
    ```
 
 1. Restore the snapshot you want.
 
    ```shell
-   ghe-es-restore-snapshot -v 3.14.0 -s SNAPSHOT-NAME
+   /usr/local/share/enterprise/ghe-es-restore-snapshot -v 3.14.0 -s SNAPSHOT-NAME
    ```
 
 Elasticsearch automatically upgrades the restored indices to the current version's format.
 
@@ -23,7 +23,6 @@ The following features are currently unavailable on {% data variables.enterprise
 | Feature | Details | More information |
 | :- | :- | :- |
 | Dependency insights | Organization-level and enterprise-level dependency insights are unavailable and display no data. | [AUTOTITLE](/organizations/collaborating-with-groups-in-organizations/viewing-insights-for-dependencies-in-your-organization) |
-| License and package metadata in the dependency graph | License and package details are not currently populated in the dependency graph. This can result in empty license fields in software bill of materials (SBOM) exports and missing license information from the {% data variables.dependency-review.action_name %}. | [AUTOTITLE](/code-security/how-tos/secure-your-supply-chain/establish-provenance-and-integrity/export-dependencies-as-sbom)<br>[AUTOTITLE](/code-security/how-tos/secure-your-supply-chain/manage-your-dependency-security/configure-dependency-review-action) |
 | macOS runners for {% data variables.product.prodname_actions %} | Currently unavailable. | [AUTOTITLE](/actions/concepts/runners/github-hosted-runners) |
 | Maven and Gradle support for {% data variables.product.prodname_registry %} | Currently unavailable. | [AUTOTITLE](/packages/working-with-a-github-packages-registry/working-with-the-apache-maven-registry) |
 | {% data variables.product.prodname_marketplace %} | {% data variables.product.prodname_marketplace %}, as a means of searching for, purchasing, and directly installing apps and actions, is unavailable. Ecosystem apps and actions can still be discovered and installed from their source, but they may require modification to work on {% data variables.enterprise.data_residency_site %}. | [{% data variables.product.prodname_actions %} workflows from {% data variables.product.prodname_marketplace %}](#github-actions-workflows-from-github-marketplace) |
 
@@ -109,21 +109,6 @@ Across all of your enterprise's organizations, you can allow or disallow people
 
 {% endif %}
 
-{% ifversion secret-scanning-actions-logs %}
-
-## Enforcing a policy for secret scanning in {% data variables.product.prodname_actions %} workflow logs
-
-As an enterprise owner, you can choose whether {% data variables.product.github %} scans {% data variables.product.prodname_actions %} workflow logs for secrets. This policy is disabled by default.
-
-When you enable the policy, {% data variables.product.github %} scans the logs of new workflow runs in all repositories in your enterprise where {% data variables.product.prodname_secret_scanning %} is enabled.
-
-{% data reusables.enterprise-accounts.access-enterprise %}
-{% data reusables.enterprise-accounts.policies-tab %}
-{% data reusables.enterprise-accounts.code-security-and-analysis-policies %}
-1. Under "Secret scanning for Actions workflow logs", select the **All repositories** dropdown menu, then click **Enabled** or **Disabled**.
-
-{% endif %}
-
 {% ifversion code-scanning-autofix %}
 
 ## Enforcing a policy to manage the use of {% data variables.copilot.copilot_autofix_short %} in your enterprise's repositories
 
@@ -30,6 +30,7 @@ category:
 | Enterprise owner | Can manage all enterprise settings, members, and policies. |
 | {% ifversion ghec %} |
 | Billing manager | Can manage enterprise billing settings. |
+| Enterprise open-source license manager | Can edit license compliance policy. Receives notifications for license alert closure requests. |
 | {% endif %} |
 | {% ifversion enterprise-app-manager %} |
 | App manager | Can manage {% data variables.product.prodname_github_app %} registrations that are owned by the enterprise. |
 
@@ -43,7 +43,7 @@ Before you install or authorize a {% data variables.product.prodname_github_app
 
 {% data reusables.copilot.agent-apps-intro %} Powered by {% data variables.copilot.copilot_cloud_agent %}, you can trigger these agents from issues, pull requests, and the Agents UI.
 
-When you install an {% data variables.copilot.agent_app %}, you will be asked if you want to enable agent features. For more information, see [AUTOTITLE](/copilot/concepts/agents/agent-apps).
+When you install an {% data variables.copilot.agent_app %}, you will be asked if you want to enable agent features. For more information, see [AUTOTITLE](/copilot/concepts/agent-capabilities/about-agents/agent-apps).
 
 If the app is installed in an organization owned by an enterprise, an administrator must also enable the "{% data variables.copilot.agent_apps %}" {% data variables.product.prodname_copilot_short %} policy before the agent features become available.
 
 
@@ -19,6 +19,18 @@ For most license-based products such as {% data variables.product.prodname_copil
 
 For metered products such as {% data variables.product.prodname_actions %}, {% data variables.product.prodname_copilot_short %} {% data variables.product.prodname_ai_credits_short %}, or cloud sandboxes, you can set budgets to prevent usage once the budget threshold is reached.
 
+{% ifversion fpt or ghec %}
+
+The bundled {% data variables.product.prodname_ai_credits_short %} budget controls metered spending across all AI-credit SKUs. You can also create a SKU-level budget for **Code Security AI Credits** to control spending on AI Scan and agentic autofix.
+
+When no Code Security AI Credits quota remains because of a hard budget, AI Scan cannot produce findings and agentic autofix cannot start a session. Usage resumes when the limiting budget is increased or a new billing cycle begins.
+
+Hard budgets for Code Security AI Credits limit AI feature usage, not enablement. Reaching a budget limit does not prevent administrators from enabling AI Scan or agentic autofix.
+
+By contrast, a hard budget for active-committer licenses prevents enabling {% data variables.product.prodname_code_security %} or {% data variables.product.prodname_secret_protection %} on additional repositories. It does not disable these products in repositories where they are already enabled.
+
+{% endif %}
+
 ## Types and scopes
 
 Each budget has a type and a scope that define which paid use contributes to spending against the budget.
 
@@ -1,6 +1,6 @@
 ---
 title: '{% data variables.product.prodname_GHAS %} license billing'
-intro: 'Learn how usage of {% data variables.product.prodname_AS %} features is measured and how to pay for additional licenses.'
+intro: 'Understand how {% data variables.product.prodname_AS %} licenses{% ifversion fpt or ghec %} and AI-credit usage{% endif %} are billed.'
 product: '{% data reusables.gated-features.ghas-billing %}'
 redirect_from:
 # Article on migrating to two separate SKUs
@@ -60,6 +60,28 @@ For full details of available features, see [AUTOTITLE](/get-started/learning-ab
 
 You need to **pay** to use {% data variables.product.prodname_AS %} features in **private repositories** on {% data variables.product.prodname_dotcom_the_website %}, and in all repositories hosted by {% data variables.enterprise.data_residency_site %} and {% data variables.product.prodname_ghe_server %}.
 
+{% ifversion fpt or ghec %}
+
+## How AI feature usage is billed
+
+Some {% data variables.product.prodname_AS %} features consume {% data variables.product.prodname_ai_credits_short %} in addition to the active-committer licenses described in this article. AI Scan and agentic autofix consume the **Code Security AI Credits** SKU.
+
+These features consume Code Security AI Credits even when the repository is public and does not require active-committer licenses.
+
+If the account being billed has included {% data variables.product.prodname_ai_credits_short %} from a {% data variables.product.prodname_copilot %} entitlement, eligible usage draws from that allowance first. After the included allowance is exhausted, further usage is metered. If the account doesn't have included {% data variables.product.prodname_ai_credits_short %}, all usage is metered.
+
+For an organization-owned repository, usage is attributed to the account that pays for the organization's usage. This is the standalone organization account or its enterprise account. The included {% data variables.product.prodname_ai_credits_short %} and budgets for that account apply, including for public repositories.
+
+Repositories in the personal namespace of a {% data variables.enterprise.prodname_managed_user %} are not treated as ordinary personal-account repositories for Code Security AI Credits. AI Scan and agentic autofix are not currently available for these repositories and do not consume Code Security AI Credits there. Purchasing {% data variables.product.prodname_code_security %}, having included {% data variables.product.prodname_ai_credits_short %}, or configuring a Code Security AI Credits budget does not make these features available.
+
+This limitation does not affect classic {% data variables.copilot.copilot_autofix_short %}, which is distinct from agentic autofix and does not consume {% data variables.product.prodname_ai_credits_short %}.
+
+Before security administrators enable AI Scan or agentic autofix broadly, billing administrators should review the account's included {% data variables.product.prodname_ai_credits_short %} and set budgets for metered usage. After the included allowance is exhausted, a hard budget can prevent further metered usage. For more information, see [AUTOTITLE](/billing/concepts/budgets-and-alerts).
+
+For information about features that consume Code Security AI Credits, see [AUTOTITLE](/code-security/concepts/code-scanning/ai-powered-security-detections) and [AUTOTITLE](/code-security/concepts/code-scanning/autofix-for-code-scanning).
+
+{% endif %}
+
 ## Using more than your planned licenses
 
 Your account may have a limit on the number of licenses you can use. For example, volume billing specifies a set number of licenses.
 
@@ -94,14 +94,20 @@ The metered usage chart and usage break down table both show your current choice
 > [!NOTE]
 > Enterprise owners and billing managers can filter AI usage data by user. Organization owners cannot view user-level data directly—to see per-user consumption, download a usage report instead. See [Downloading usage reports](#downloading-usage-reports).
 
-If you use {% data variables.product.prodname_copilot_short %}, an additional **AI usage** view is listed under **Usage**. You can use this view to dig deeper into how your enterprise is consuming {% data variables.product.prodname_ai_credits_short %} and where additional spend is occurring. For example:
+If your account uses {% data variables.product.prodname_ai_credits_short %}, an additional **AI usage** view is listed under **Usage**. You can use this view to understand included and metered usage across products, including {% data variables.product.prodname_copilot_short %} and {% data variables.product.prodname_AS %}.
+
+To review combined AI Scan and agentic autofix usage, open the **AI usage** view, under "Group by," select **Products**, then review **{% data variables.product.prodname_AS %}**. These features share the Code Security AI Credits SKU, so their usage is reported together within the product total, not as separate totals for each feature.
+
+You can use the view to answer questions such as:
 
 * What's our total {% data variables.product.prodname_ai_credits_short %} consumption across all users?
 * Which users are the heaviest consumers, and are they within their budget?
 * Which models are driving the most spend?
 * How widespread is adoption in the organizations where we rolled out {% data variables.product.prodname_copilot_short %}?
 
-To understand how {% data variables.product.prodname_ai_credits_short %} are pooled across your enterprise and what the usage data represents, see [AUTOTITLE](/copilot/concepts/billing-and-usage/organizations-and-enterprises/billing).
+For information about {% data variables.product.prodname_copilot_short %} allowances and how {% data variables.product.prodname_ai_credits_short %} are pooled across your enterprise, see [AUTOTITLE](/copilot/concepts/billing-and-usage/organizations-and-enterprises/billing).
+
+For information about {% data variables.product.prodname_AS %} AI-credit billing, see [AUTOTITLE](/billing/concepts/product-billing/github-advanced-security#how-ai-feature-usage-is-billed).
 
 {% endif %}