Remove operate/ section; add aliases to all new-IA destinations

Delete the entire operate/ directory (162 non-draft pages, excluding
SLAM which was already migrated). Add 97 aliases across 67 destination
pages so every operate/ URL resolves to its new-IA equivalent.

Also fixes:
- 404.html card links (operate/install/setup → set-up-a-machine/overview)
- camera-model-next-steps.md include (operate/ camera links → new paths)
- 4 pre-existing stale UI labels (Component or service → Configuration
  block; Click Test → Expand TEST section)

446 body-text references to /operate/ remain across tutorials and other
pages. These redirect through aliases and are a follow-up cleanup task.

Full mapping documented in code-map/operate-removal-plan.md.
13 pages on the revisit list where the alias is accepted but unique
content needs a proper new-IA home.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

Author: shannonbradshaw

docs/build-apps/concepts/how-apps-connect.md

@@ -6,6 +6,8 @@ layout: "docs"
 type: "docs"
 description: "The transport paths the SDK uses, the session safety mechanism, and what the SDK reconnects automatically."
 date: "2026-04-10"
+aliases:
+  - /operate/reference/sessions/
 ---
 
 A Viam client application needs to reach a machine that may be on a different network, behind a NAT, or both. This page describes the transport paths the SDK uses, the session safety mechanism, and how the SDK reconnects when the network drops.

docs/build-apps/overview.md

@@ -7,6 +7,7 @@ type: "docs"
 description: "Build software that uses a Viam SDK to talk to your machines and the Viam cloud, from web dashboards to long-running backend services."
 date: "2026-04-10"
 aliases:
+  - /operate/control/
   - /operate/control/headless-app/
   - /product-overviews/sdk-as-client/
   - /program/sdk-as-client/

docs/build-modules/deploy-a-module.md

@@ -7,6 +7,8 @@ type: "docs"
 description: "Package, upload, and distribute a module through the Viam registry."
 date: "2025-01-30"
 aliases:
+  - /operate/modules/deploy-a-module/
+  - /operate/reference/advanced-modules/docker-modules/
   - /build/development/deploy-a-module/
   - /development/deploy-a-module/
   - /extend/modular-resources/upload/

docs/build-modules/manage-modules.md

@@ -8,6 +8,7 @@ icon: true
 tags: ["modular resources", "components", "services", "registry"]
 description: "Update or delete your existing modules, or change their privacy settings."
 aliases:
+  - /operate/modules/advanced/manage-modules/
   - /use-cases/deploy-code/
   - /use-cases/manage-modules/
   - /how-tos/manage-modules/

docs/build-modules/module-reference.md

@@ -7,6 +7,9 @@ type: "docs"
 description: "Reference for module developers: lifecycle, interfaces, meta.json schema, CLI commands, environment variables, and registry rules."
 date: "2025-03-05"
 aliases:
+  - /operate/modules/advanced/logging/
+  - /operate/modules/advanced/metajson/
+  - /operate/modules/advanced/module-configuration/
   - /development/module-reference/
   - /operate/modules/lifecycle-module/
   - /operate/modules/lifecycle-of-a-module/

docs/build-modules/overview.md

@@ -6,6 +6,10 @@ layout: "docs"
 type: "docs"
 description: "Understand the two kinds of modules and how to extend your machine with custom hardware drivers and application logic."
 aliases:
+  - /operate/modules/
+  - /operate/modules/advanced/
+  - /operate/reference/advanced-modules/
+  - /operate/reference/advanced-modules/create-subtype/
   - /build-modules/from-hardware-to-logic/
 ---
 

docs/build-modules/platform-apis.md

@@ -6,6 +6,7 @@ layout: "docs"
 type: "docs"
 description: "Write your validate and reconfigure functions to handle dependencies in your custom modular resource."
 aliases:
+  - /operate/modules/advanced/platform-apis/
 date: "2025-11-05"
 ---
 

docs/build-modules/use-registry-modules.md

@@ -6,6 +6,8 @@ layout: "docs"
 type: "docs"
 description: "Before writing a module, check whether one already exists. The registry has more than hardware drivers."
 date: "2026-04-17"
+aliases:
+  - /registry/
 ---
 
 Before you write a module, check whether one already exists. The Viam registry contains more than hardware drivers. Many software capabilities you might want to build are already published as modules you can configure and use directly.

docs/build-modules/write-a-driver-module.md

@@ -7,6 +7,7 @@ type: "docs"
 description: "Build a module that implements a resource API and runs as a separate process."
 date: "2025-01-30"
 aliases:
+  - /operate/modules/write-a-driver-module/
   - /build/development/write-a-module/
   - /development/write-a-module/
   - /development/write-a-driver-module/

docs/hardware/common-components/add-a-base.md

@@ -7,6 +7,8 @@ type: "docs"
 description: "Add and configure a base to drive a mobile robot with movement commands."
 date: "2025-03-07"
 aliases:
+  - /operate/reference/components/base/
+  - /operate/reference/components/base/boat/
   - /hardware-components/add-a-base/
 ---