Move Storage docs off the reserved runtime route

content/(dynamic)/meta.ts

@@ -4,5 +4,14 @@ export default defineMeta({
   title: "Dynamic",
   collapsed: false,
   order: 5,
-  pages: ["zero-runtime", "functions", "database", "environment-variables", "crons", "storage", "logs", "wordpress"],
+  pages: [
+    "zero-runtime",
+    "functions",
+    "database",
+    "environment-variables",
+    "crons",
+    "object-storage",
+    "logs",
+    "wordpress",
+  ],
 });

content/(dynamic)/wordpress.mdx

@@ -5,7 +5,7 @@ description: Every Space runs a WordPress behind its static files. Run WP-CLI ag
 
 After this page you can run any WP-CLI command against a Space, call the Abilities its runtime publishes with a token you mint from the API, and know where the database console lives.
 
-Every Space is backed by a WordPress install. Your published files serve in front of it, so a static Space never touches it and never pays for it. It is there because it is what makes a Space more than a bucket: [Zero](/zero-runtime) apps run on it, [Storage](/storage) is its media library, and [Database](/database) is its MySQL. This page covers the two ways to reach that WordPress directly.
+Every Space is backed by a WordPress install. Your published files serve in front of it, so a static Space never touches it and never pays for it. It is there because it is what makes a Space more than a bucket: [Zero](/zero-runtime) apps run on it, [Storage](/object-storage) is its media library, and [Database](/database) is its MySQL. This page covers the two ways to reach that WordPress directly.
 
 ## `sf wp`
 
@@ -84,7 +84,7 @@ The table prints `ABILITY | CATEGORY | MODE | REQUIRES`. The `REQUIRES` column i
 
 ### Storage Abilities
 
-Five Abilities in the `zero-storage` category are registered by the runtime, so every Space publishes them whether or not it has ever published an app. They are the media library, the same objects [Storage](/storage) manages.
+Five Abilities in the `zero-storage` category are registered by the runtime, so every Space publishes them whether or not it has ever published an app. They are the media library, the same objects [Storage](/object-storage) manages.
 
 | Ability | Mode | Does | Needs |
 | --- | --- | --- | --- |

content/(dynamic)/zero-runtime.mdx

@@ -51,7 +51,7 @@ sf publish
 | Queries, mutations, and actions | The read, transactional write, and outbound-work paths your client calls. Queries are live. | This page |
 | Environment variables | `ctx.env`, from `.env.server` or `sf env`. | [Environment variables](/environment-variables) |
 | Crons | Scheduled GETs against your own paths, declared in `sf.jsonc`. | [Crons](/crons) |
-| Storage | Runtime object storage for visitor uploads. | [Storage](/storage) |
+| Storage | Runtime object storage for visitor uploads. | [Storage](/object-storage) |
 | Logs | What your handlers wrote, plus every request the edge served. | [Logs](/logs) |
 
 ## The `@spacefast/zero` package

scripts/redirect-rules.mjs

@@ -18,6 +18,11 @@ const authoredRedirectRules = [
     status: 301,
     to: `${deploymentBase}/zero-runtime`,
   },
+  {
+    from: `${deploymentBase}/storage`,
+    status: 301,
+    to: `${deploymentBase}/object-storage`,
+  },
 ];
 
 const aliasFamilies = [