Update content from depot/app

content/agents/overview.mdx

@@ -15,7 +15,7 @@ Current agent sandboxes support Claude Code, with more agents coming soon. By de
   <a
     href="/docs/agents/claude-code/quickstart"
     data-ph-capture-attribute-button-id="agents-docs-cta-to-quickstart"
-    className="text-radix-mauve12 font-semibold"
+    className="font-semibold text-radix-mauve12"
   >
     To dive into using remote agents on Depot, check out our Claude Code quickstart guide &rarr;
   </a>
@@ -107,7 +107,7 @@ depot claude --resume feature-auth "This looks good, but we need to add the conc
 Depot remote agent sandboxes are available on **all plans** and are billed at a usage rate of **$0.01/minute** with no included usage for remote agents.
 
 <DocsCTA>
-  <a href="/sign-up" data-ph-capture-attribute-button-id="agents-docs-cta" className="text-radix-grass12 font-semibold">
+  <a href="/sign-up" data-ph-capture-attribute-button-id="agents-docs-cta" className="font-semibold text-radix-grass12">
     Start your 7-day free trial to try remote agents on Depot &rarr;
   </a>
 </DocsCTA>

content/cache/integrations/sccache.mdx

@@ -90,15 +90,18 @@ DEPOT_TOKEN=your_token depot bake
 
 [Depot GitHub Actions runners](/docs/github-actions/overview) are pre-configured to use Depot Cache with sccache. Each runner launches with a `SCCACHE_WEBDAV_ENDPOINT` environment variable pre-configured with the connection details for Depot Cache.
 
-You don't need additional configuration. Run your sccache builds as normal:
+Tell Rust to compile via sccache, and run your sccache builds as normal:
 
 ```yaml
 jobs:
   build:
     runs-on: depot-ubuntu-24.04
     steps:
       - uses: actions/checkout@v4
-      - run: sccache --start-server && cargo build --release
+      - uses: mozilla-actions/sccache-action@v0.0.9
+      - run: cargo build --release
+        env:
+          RUSTC_WRAPPER: 'sccache'
 ```
 
 To disable automatic configuration, turn off **Allow Actions jobs to automatically connect to Depot Cache** in your organization settings page. You can then manually configure sccache as described in the Local workstation section.

content/cache/overview.mdx

@@ -27,6 +27,17 @@ Supported build tools can be configured to use Depot Cache, so that they store a
 
 This speeds up your builds and tests by orders of magnitude, especially for large codebases, as those builds and tests become incremental. Instead of always having to rebuild from scratch, only the parts of your codebase that have changed are rebuilt, and only affected tests are re-run.
 
+### Cache retention policy
+
+The default cache retention policy is to store the cache entries for 14 days with no limit on total cache size.
+
+Configure the cache retention policy on your organization's [settings page](/orgs/_/settings) to control time based retention and cache size limits.
+
+- Available values for time based retention: 7 days, 14 days (default), 30 days
+- Available values for size based retention: 25 GB, 50 GB, 100 GB, 150 GB, 250 GB, 500 GB, No limit (default)
+
+**Note:** Retention policy settings don't apply to Docker layer cache entries (shown as type `docker` in the [Cache Explorer](/orgs/_/cache)). To manage Docker cache retention, set cache policy per [project](/orgs/_/projects) in project Settings.
+
 ## Where can I use Depot Cache?
 
 Depot Cache is accessible anywhere you run your builds, in local development or from any CI/CD system. Additionally, all supported tools are pre-configured to use Depot Cache when using [Depot GitHub Actions Runners](/docs/github-actions/overview).
@@ -35,8 +46,4 @@ This means that build artifacts are shared between different members of your tea
 
 ## Pricing
 
-Depot Cache is available on all of our pricing plans. Each plan includes a block of cache storage. Each additional GB over the included amount is billed at **$0.20/GB/month**. See our [pricing page](/pricing) for more details.
-
-## Cache Retention
-
-Depot Cache retains build artifacts for a configurable amount of time. By default, artifacts are retained for 14 days. You can configure this retention period in the Depot Cache settings.
+Depot Cache is available on all of our pricing plans. Each plan includes a block of cache storage. Each additional GB over the included amount is billed at $0.20 per GB of usage. We calculate usage by taking a snapshot every hour and then averaging out those snapshots over the month. For more information about plans and included usage, see the [pricing page](/pricing).

content/cli/authentication.mdx

@@ -49,7 +49,7 @@ To add a trust relationship for GitHub Actions, you can go through the following
 5. Enter a GitHub User or Organization for the trust relationship
 6. Enter the name of the GitHub repository that will build images via Depot (Note: this is the repository name, not the full URL and it must match the repository name exactly)
 7. Click Add trust relationship
-8. Ensure your workflow has permission to use this OIDC trust relationship by setting the permission `id-token: write`.
+8. In your workflow file, add a `permissions` block to your job with `id-token: write` and `contents: read`.
 
 ### Adding a trust relationship for CircleCI
 

content/cli/reference.mdx

@@ -8,7 +8,7 @@ Below is a reference to the `depot` CLI, including all config, commands, flags,
 
 ## Specifying a Depot project
 
-Some commands need to know which [project](/docs/core-concepts#projects) to route the build to.
+Some commands need to know which [project](/docs/container-builds/overview#projects) to route the build to.
 
 For interactive terminals calling [`build`](#depot-build) or [`bake`](#depot-bake), if you don't specify a project, you will be prompted to choose a project when using an interactive prompt and given the option to save that project for future use in a `depot.json` file.