chore(swap): remove canary md-*.md files and docs/superpowers

- Remove 115 canary md-*.md files (incremental swap helpers no longer needed)
- Remove 8 files under docs/superpowers (project planning/design docs that
  shouldn't ship in the documentation tree)

🤖 Generated by [robots](https://vyos.io)

9 files changed, 0 insertions, 1286 deletions

diff --git a/docs/automation/md-cloud-init.md b/docs/automation/md-cloud-init.md
deleted file mode 100644
index 6c25287d..00000000
--- a/docs/automation/md-cloud-init.md
+++ /dev/null
@@ -1,375 +0,0 @@
----
-lastproofread: '2026-04-13'
----
-
-(cloud-init)=
-
-# VyOS cloud-init
-
-VyOS instances in cloud and virtualized environments are initialized using the
-industry-standard `cloud-init`. Through `cloud-init`, VyOS injects SSH
-keys, configures network settings, and applies custom configurations during the
-initial instance boot.
-
-## Configuration sources
-
-VyOS `cloud-init` obtains configuration data from the following sources:
-
-- `meta-data`: Instance-specific details provided by the cloud platform or
-  hypervisor. In some cloud environments, this data is available via an HTTP
-  endpoint at `http://169.254.169.254`.
-- `network configuration`: Network settings such as IP addresses, routes, and
-  DNS (only available on certain cloud and virtualization platforms).
-- `user-data`: User-supplied CLI configuration commands.
-
-## User-data
-
-Major cloud providers support injecting `user-data` as plain text or base64
-encoding text during initial instance boot. As `user-data` has a strict size
-limit of \~16384 bytes, long configuration command lists can be compressed using
-`gzip`.
-
-The recommended method for configuring VyOS instances via `user-data` is to
-use the `cloud-config` syntax described below.
-
-## Cloud-config modules
-
-By default, VyOS enables only two `cloud-config` modules:
-
-- `write_files`: Inserts user-provided files such as encryption keys,
-  certificates, or `config.boot` into the filesystem during the initial
-  instance boot. See [Cloud-init-write_files] for file syntax and file format
-  requirements.
-- `vyos_userdata`: Executes user-provided CLI configuration commands during
-  the initial instance boot.
-
-The files to insert and the CLI commands to execute must be provided in a
-`cloud-config` YAML file.
-
-## Cloud-config file format
-
-`cloud-config` files are written in YAML and must begin with the
-`#cloud-config` line. Only `vyos_config_commands` and `write_files` are
-supported as top-level keys. The use of these keys is described in the
-following two sections.
-
-## Vyos_config_commands key
-
-Use the `vyos_config_commands` key to define configuration commands for
-initializing your VyOS instance. Commands must follow the set-style syntax
-and can include both `set` and `delete` statements.
-
-Syntax requirements:
-
-- Place one command per line.
-- Enclose values in single quotes.
-- Avoid single quotes within commands or values.
-
-Applying commands from `cloud-config` overrides both settings configured via
-`meta-data` and default VyOS settings. After commands are applied,
-`cloud-init` automatically performs `commit` and `save`.
-
-The following is an example of a `cloud-config` file:
-
-```yaml
-#cloud-config
-vyos_config_commands:
-  - set system host-name 'vyos-prod-ashburn'
-  - set service ntp server 1.pool.ntp.org
-  - set service ntp server 2.pool.ntp.org
-  - delete interfaces ethernet eth1 address 'dhcp'
-  - set interfaces ethernet eth1 address '192.0.2.247/24'
-  - set protocols static route 198.51.100.0/24 next-hop '192.0.2.1'
-```
-
-### Instance defaults/fallbacks
-
-If no external configuration data is provided, VyOS applies the following
-defaults:
-
-- **SSH:** port 22.
-- **Credentials:** `vyos`/`vyos`.
-- **Networking:** DHCP is enabled on the first Ethernet interface.
-
-All defaults can be overridden via `user-data` configurations.
-
-## Write_files key
-
-VyOS allows you to run custom scripts during the initial instance boot to
-execute operational, configuration, and standard Linux commands.
-
-Use the `write_files` key to insert these scripts into the
-`/opt/vyatta/etc/config/scripts/` directory.
-
-Depending on when your commands need to run, use one of the following paths:
-
-- `/opt/vyatta/etc/config/scripts/vyos-preconfig-bootup.script`: Commands
-  defined here are executed before the system configuration is applied.
-- `/opt/vyatta/etc/config/scripts/vyos-postconfig-bootup.script`: Commands
-  defined here are executed after the system configuration is applied.
-
-In both cases, commands are executed with `root` privileges.
-
-:::{note}
-Use the `/opt/vyatta/etc/config/` path instead of `/config/scripts/` as
-referenced in the {ref}`command-scripting` section. The `/config/scripts/`
-directory is not mounted when the `write_files` module runs.
-:::
-
-The following example shows how to use `write_files` to execute an
-operational command **after** the initial configuration is complete:
-
-```yaml
-#cloud-config
-write_files:
-  - path: /opt/vyatta/etc/config/scripts/vyos-postconfig-bootup.script
-    owner: root:vyattacfg
-    permissions: '0775'
-    content: |
-      #!/bin/vbash
-      source /opt/vyatta/etc/functions/script-template
-      filename=/tmp/bgp_status_`date +"%Y_%m_%d_%I_%M_%p"`.log
-      run show ip bgp summary >> $filename
-```
-
-You can combine standard Linux commands to fetch data and VyOS configuration
-commands (like `set` and `commit`) in the same script.
-
-The following example sets the `hostname` based on the instance identifier
-obtained from the EC2 Instance Metadata Service (IMDS).
-
-```yaml
-#cloud-config
-write_files:
-  - path: /opt/vyatta/etc/config/scripts/vyos-postconfig-bootup.script
-    owner: root:vyattacfg
-    permissions: '0775'
-    content: |
-      #!/bin/vbash
-      source /opt/vyatta/etc/functions/script-template
-      hostname=`curl -s http://169.254.169.254/latest/meta-data/instance-id`
-      configure
-      set system host-name $hostname
-      commit
-      exit
-```
-
-## NoCloud
-
-Injecting configuration data is not limited to cloud platforms. The NoCloud
-data source allows you to inject `user-data` and `meta-data` on
-virtualization platforms such as VMware, Hyper-V, and KVM.
-
-The simplest way to use the NoCloud data source is to create a `seed.iso`
-file and attach it to the virtual machine as a CD drive. The volume must be
-formatted as a VFAT or ISO 9660 file system with the label `cidata` or
-`CIDATA`.
-
-Create text files named `user-data` and `meta-data`. On Linux-based
-systems, use the `mkisofs` utility to create the `seed.iso` file. The
-following syntax adds these files to the ISO 9660 file system:
-
-```none
-mkisofs -joliet -rock -volid "cidata" -output seed.iso meta-data user-data
-```
-
-Once generated, attach the `seed.iso` file to your virtual machine. The
-following example shows how to attach the file as a CD drive using KVM:
-
-```none
-$ virt-install -n vyos_r1 \
-   --ram 4096 \
-   --vcpus 2 \
-   --cdrom seed.iso \
-   --os-type linux \
-   --os-variant debian10 \
-   --network network=default \
-   --graphics vnc \
-   --hvm \
-   --virt-type kvm \
-   --disk path=/var/lib/libvirt/images/vyos_kvm.qcow2,bus=virtio \
-   --import \
-   --noautoconsole
-```
-
-For more information on the NoCloud data source, visit the [NoCloud] page in
-the `cloud-init` documentation.
-
-## Troubleshooting
-
-If your configuration does not apply as expected, follow these troubleshooting
-steps:
-
-1. **Validate your YAML**: Ensure your `cloud-config` file follows proper
-   YAML syntax. Online resources such as [YAML Lint](https://www.yamllint.com/)
-   provide simple validation tools.
-2. **Check the logs**: `cloud-init` writes logs to `/var/log/cloud-init.log`.
-   Filter for VyOS-specific entries using:
-
-```none
-sudo grep vyos /var/log/cloud-init.log
-```
-
-## Cloud-init on Proxmox
-
-Before you begin, review the `cloud-init` [network-config-docs] to
-understand how to import user and network configuration data.
-
-Key considerations:
-
-- Define VyOS configuration commands in the `user-data` file.
-- Avoid including network configuration data in the `user-data` file.
-- If no network configuration data is provided, the DHCP client is enabled on
-  the first interface. This happens at the OS level and is not reflected in the
-  VyOS CLI.
-
-The following example shows how to disable the DHCP client on `eth0` to
-address this behavior.
-
-In this example:
-
-- **Proxmox IP address**: `192.168.0.253/24`.
-- **Storage**: The `local` volume is mounted at `/var/lib/vz` and contains
-  all content types, including snippets.
-
-The goal is to remove the default DHCP client from the first interface and
-apply a custom configuration during the initial instance boot using
-`cloud-init`.
-
-### Generate .qcow2 image
-
-First, generate a VyOS `.qcow2` image with `cloud-init` support from the
-[vyos-vm-images] repository:
-
-1. Clone the `vyos-vm-images` repository and comment out the `download-iso`
-   role in `qemu.yml`.
-2. Download your preferred VyOS `.iso` file and save it as `/tmp/vyos.iso`.
-3. Generate the `.qcow2` image (using a 10G disk size for this example):
-
-```sh
-sudo ansible-playbook qemu.yml -e disk_size=10 \
- -e iso_local=/tmp/vyos.iso -e grub_console=serial -e vyos_version=1.5.0 \
- -e cloud_init=true -e cloud_init_ds=NoCloud
-```
-
-This generates your new image at `/tmp/vyos-1.5.0-cloud-init-10G-qemu.qcow2`.
-
-4. Copy the resulting image to the Proxmox server:
-
-```sh
-sudo scp /tmp/vyos-1.5.0-cloud-init-10G-qemu.qcow2 root@192.168.0.253:/tmp/
-```
-
-### Prepare cloud-init files
-
-Create the following files on your Proxmox server to proceed with this setup:
-
-- `user-data`: Contains VyOS configuration commands.
-- `network-config`: Disables the DHCP client on the first interface.
-- `meta-data`: An empty file (required by `cloud-init`).
-
-All files must be placed in the `/tmp/` directory.
-
-Follow these steps to create the required files:
-
-1. Navigate to the `/tmp/` directory:
-
-   ```sh
-   cd /tmp/
-   ```
-
-2. Create the `user-data` file. Begin the file with `#cloud-config` and
-   include VyOS configuration commands.
-
-   ```none
-   #cloud-config
-   vyos_config_commands:
-     - set system host-name 'vyos-BRAS'
-     - set service ntp server '1.pool.ntp.org'
-     - set service ntp server '2.pool.ntp.org'
-     - delete interfaces ethernet eth0 address 'dhcp'
-     - set interfaces ethernet eth0 address '198.51.100.2/30'
-     - set interfaces ethernet eth0 description 'WAN - ISP01'
-     - set interfaces ethernet eth1 address '192.168.25.1/24'
-     - set interfaces ethernet eth1 description 'Coming through VLAN 25'
-     - set interfaces ethernet eth2 address '192.168.26.1/24'
-     - set interfaces ethernet eth2 description 'Coming through VLAN 26'
-     - set protocols static route 0.0.0.0/0 next-hop '198.51.100.1'
-   ```
-
-3. Create the `network-config` file. Include the following:
-
-   ```none
-   version: 2
-   ethernets:
-     eth0:
-       dhcp4: false
-       dhcp6: false
-   ```
-
-4. Create the required empty `meta-data` file.
-
-### Create seed.iso
-
-Once you have created the necessary files, generate the `seed.iso` image and
-mount it as a CD drive to the new VM.
-
-```sh
-mkisofs -joliet -rock -volid "cidata" -output seed.iso meta-data \
-user-data network-config
-```
-
-:::{note}
-Be careful while copying and pasting the above commands. Double quotes may need
-to be corrected.
-:::
-
-### Create the VM
-
-Note that the following settings apply to this particular example and may
-require adjustment for other setups:
-
-- **VM ID**: `555`.
-- **VM and .iso file storage**: The local volume (`directory` type,
-  mounted at `/var/lib/vz`).
-- **VM resources**: Can be modified as needed.
-
-The `seed.iso` file was previously created in the `/tmp/` directory. Move
-it to `/var/lib/vz/template/iso`:
-
-```sh
-mv /tmp/seed.iso /var/lib/vz/template/iso/
-```
-
-On the Proxmox server:
-
-```none
-## Create VM, import disk and define boot order
-qm create 555 --name vyos-1.5.0-cloudinit --memory 1024 --net0 virtio,bridge=vmbr0
-qm importdisk 555 vyos-1.5.0-cloud-init-10G-qemu.qcow2 local
-qm set 555 --virtio0 local:555/vm-555-disk-0.raw
-qm set 555 --boot order=virtio0
-
-## Import seed.iso for cloud init
-qm set 555 --ide2 media=cdrom,file=local:iso/seed.iso
-
-## Since this server has 1 nic, lets add network intefaces (vlan 25 and 26)
-qm set 555 --net1 virtio,bridge=vmbr0,firewall=1,tag=25
-qm set 555 --net2 virtio,bridge=vmbr0,firewall=1,tag=26
-```
-
-### Power on and verify the VM
-
-Power on the VM using the CLI or GUI. After it boots, verify the configuration.
-
-### References
-
-- Cloud-init [network-config-docs].
-- Proxmox [Cloud-init-Support].
-
-[cloud-init-docs]: https://docs.vyos.io/en/equuleus/automation/cloud-init.html?highlight=cloud-init#vyos-cloud-init
-[cloud-init-support]: <https://pve.proxmox.com/pve-docs/pve-admin-guide.html#qm_cloud_init>
-[cloud-init-write_files]: https://cloudinit.readthedocs.io/en/latest/topics/examples.html#writing-out-arbitrary-files
-[network-config-docs]: https://cloudinit.readthedocs.io/en/latest/topics/network-config.html
-[nocloud]: https://cloudinit.readthedocs.io/en/latest/reference/datasources/nocloud.html
-[vyos-vm-images]: https://github.com/vyos/vyos-vm-images
diff --git a/docs/automation/md-command-scripting.md b/docs/automation/md-command-scripting.md
deleted file mode 100644
index c1e1c239..00000000
--- a/docs/automation/md-command-scripting.md
+++ /dev/null
@@ -1,216 +0,0 @@
----
-lastproofread: '2026-03-16'
----
-
-(command-scripting)=
-
-# Command scripting
-
-VyOS supports executing configuration and operational commands non-interactively
-from shell scripts.
-
-To include VyOS-specific functions and aliases, source the
-`/opt/vyatta/etc/functions/script-template` file at the beginning of your
-script.
-
-```none
-#!/bin/vbash
-source /opt/vyatta/etc/functions/script-template
-exit
-```
-
-## Script execute permissions
-
-Simply placing script files in `/config/scripts/` does not mean the system
-can execute them.
-
-To make your scripts executable, grant them **execute permissions**. Use the
-following command:
-
-```none
-chmod +x /config/scripts/script-name.sh
-```
-
-## Run configuration commands
-
-In scripts, present configuration commands as in a standard configuration
-session.
-
-For example, to disable a BGP peer during a VRRP transition to the backup
-state, use the following syntax:
-
-```none
-#!/bin/vbash
-source /opt/vyatta/etc/functions/script-template
-configure
-set protocols bgp system-as 65536
-set protocols bgp neighbor 192.168.2.1 shutdown
-commit
-exit
-```
-
-## Run operational commands
-
-In scripts, **always** prefix operational commands with `run`.
-
-```none
-#!/bin/vbash
-source /opt/vyatta/etc/functions/script-template
-run show interfaces
-exit
-```
-
-## Run commands remotely
-
-You can execute multiple **operational commands** on a remote VyOS system by
-passing a script block over SSH.
-
-```none
-ssh 192.0.2.1 'vbash -s' <<EOF
-source /opt/vyatta/etc/functions/script-template
-run show interfaces
-exit
-EOF
-```
-
-Example output:
-
-```none
-Welcome to VyOS
-Codes: S - State, L - Link, u - Up, D - Down, A - Admin Down
-Interface        IP Address                        S/L  Description
----------        ----------                        ---  -----------
-eth0             192.0.2.1/24                      u/u
-lo               127.0.0.1/8                       u/u
-                ::1/128
-```
-
-## Other script languages
-
-If you use a scripting language other than bash, configure your script to
-output the relevant commands, and then source that output into a bash script.
-
-The following example demonstrates this two-step process:
-
-```python
-#!/usr/bin/env python3
-print("delete firewall group address-group somehosts")
-print("set firewall group address-group somehosts address '192.0.2.3'")
-print("set firewall group address-group somehosts address '203.0.113.55'")
-```
-
-```none
-#!/bin/vbash
-source /opt/vyatta/etc/functions/script-template
-configure
-source <(/config/scripts/setfirewallgroup.py)
-commit
-```
-
-## Execute configuration scripts
-
-In Linux, it is common practice to prefix system commands with `sudo`.
-
-In VyOS, if you prefix a script that modifies the configuration with `sudo`
-(see the code snippet below), subsequent manual configuration changes fail with
-the `Set failed` error. Recovery requires a system reboot.
-
-```none
-sudo ./myscript.sh # Modifies config
-configure
-set ... # Any configuration parameter
-```
-
-To avoid this issue, run scripts under the `vyattacfg` group using the `sg`
-command:
-
-```none
-sg vyattacfg -c ./myscript.sh
-```
-
-To ensure the script is executed under the `vyattacfg` group, safeguard it as
-follows:
-
-```none
-if [ "$(id -g -n)" != 'vyattacfg' ] ; then
-    exec sg vyattacfg -c "/bin/vbash $(readlink -f $0) $@"
-fi
-```
-
-## Executing pre-hooks/post-hooks scripts
-
-VyOS allows you to run custom scripts **before** and **after** each commit.
-
-Place your custom scripts in the following default directories:
-
-```none
-/config/scripts/commit/pre-hooks.d   - Directory with scripts that run before
-                                       each commit.
-
-/config/scripts/commit/post-hooks.d  - Directory with scripts that run after
-                                       each commit.
-```
-
-Scripts run in alphabetical order. Filenames must consist only of ASCII letters
-(upper and lowercase), digits (0-9), underscores (\_), and hyphens (-). No other
-characters are allowed.
-
-:::{note}
-Custom scripts are executed **without** root privileges. Prefix
-specific commands with `sudo` in your script when required.
-:::
-
-The following example shows the output after executing a post-hook script
-that runs the `show interfaces` command:
-
-```none
-vyos@vyos# set interfaces ethernet eth1  address 192.0.2.3/24
-vyos@vyos# commit
-Codes: S - State, L - Link, u - Up, D - Down, A - Admin Down
-Interface        IP Address                        S/L  Description
----------        ----------                        ---  -----------
-eth0             198.51.100.10/24                  u/u
-eth1             192.0.2.3/24                      u/u
-eth2             -                                 u/u
-eth3             -                                 u/u
-lo               203.0.113.5/24                    u/u
-```
-
-## Preconfig script on boot
-
-VyOS runs `/config/scripts/vyos-preconfig-bootup.script` at boot, **before**
-the system configuration is applied.
-
-Use this script to apply **pre-configuration** workarounds for unresolved bugs
-or enhancements not yet available in VyOS.
-
-The default script contains the following:
-
-```none
-#!/bin/sh
-# This script is executed at boot time before VyOS configuration is applied.
-# Any modifications required to work around unfixed bugs or use
-# services not available through the VyOS CLI system can be placed here.
-```
-
-## Postconfig script on boot
-
-VyOS runs `/config/scripts/vyos-postconfig-bootup.script` at boot, **after**
-the system configuration is applied.
-
-Use this script to apply **post-configuration** workarounds for unresolved bugs
-or enhancements not yet available in VyOS.
-
-The default script contains the following:
-
-```none
-#!/bin/sh
-# This script is executed at boot time after VyOS configuration is fully
-# applied. Any modifications required to work around unfixed bugs or use
-# services not available through the VyOS CLI system can be placed here.
-```
-
-:::{warning}
-For configuration or upgrade management issues, modify this script
-only as a last resort. Always try CLI-based solutions first.
-:::
diff --git a/docs/automation/md-index.md b/docs/automation/md-index.md
deleted file mode 100644
index 62e60f84..00000000
--- a/docs/automation/md-index.md
+++ /dev/null
@@ -1,16 +0,0 @@
-# VyOS Automation
-
-```{toctree}
-:maxdepth: 2
-
-vyos-api
-vyos-ansible
-terraform/index
-vyos-napalm
-vyos-netmiko
-vyos-salt
-command-scripting
-cloud-init
-vyos-pyvyos
-vyos-govyos
-```
diff --git a/docs/automation/md-vyos-ansible.md b/docs/automation/md-vyos-ansible.md
deleted file mode 100644
index 1ced72be..00000000
--- a/docs/automation/md-vyos-ansible.md
+++ /dev/null
@@ -1,99 +0,0 @@
----
-lastproofread: '2026-04-13'
----
-
-(vyos-ansible)=
-
-# Ansible
-
-VyOS can be configured using Ansible. To use it, install the `ansible`
-package and the `python3-paramiko` module.
-
-## Directory structure
-
-Arrange your Ansible project directory as follows:
-
-```none
-.
-├── ansible.cfg
-├── files
-│   └── id_rsa_docker.pub
-├── hosts
-└── main.yml
-```
-
-## File contents
-
-- `ansible.cfg`
-
-```none
-[defaults]
-host_key_checking = no
-retry_files_enabled = False
-ANSIBLE_INVENTORY_UNPARSED_FAILED = true
-```
-
-- `id_rsa_docker.pub`
-
-Contains only the SSH public key.
-
-```none
-AAAAB3NzaC1yc2EAAAADAQABAAABAQCoDgfhQJuJRFWJijHn7ZinZ3NWp4hWVrt7HFcvn0kgtP/5PeCtMt
-```
-
-- `hosts`
-
-Defines the target VyOS devices and the connection parameters required to reach
-them.
-
-```none
-[vyos_hosts]
-r11 ansible_ssh_host=192.0.2.11
-
-[vyos_hosts:vars]
-ansible_python_interpreter=/usr/bin/python3
-ansible_user=vyos
-ansible_ssh_pass=vyos
-ansible_network_os=vyos
-ansible_connection=network_cli
-```
-
-- `main.yml`
-
-Defines the configuration tasks to be applied to the target VyOS devices.
-
-```none
----
-
-- hosts: r11
-
-  connection: network_cli
-  gather_facts: 'no'
-
-  tasks:
-    - name: Configure remote r11
-      vyos_config:
-        lines:
-          - set system host-name r11
-          - set system name-server 203.0.113.254
-          - set service ssh disable-host-validation
-          - set system login user vyos authentication public-keys docker@work type ssh-rsa
-          - set system login user vyos authentication public-keys docker@work key "{{ lookup('file', 'id_rsa_docker.pub') }}"
-          - set system time-zone America/Los_Angeles
-          - set interfaces ethernet eth0 description WAN
-```
-
-## Run Ansible
-
-To apply the configuration, use the following command:
-
-```none
-$ ansible-playbook -i hosts main.yml 
-
-PLAY [r11] **************************************************************************************************
-
-TASK [Configure remote r11] *********************************************************************************
-
-PLAY RECAP **************************************************************************************************
-r11                         : ok=1    changed=1    unreachable=0    failed=0    skipped=0    rescued=0    ignored=0
-```
diff --git a/docs/automation/md-vyos-govyos.md b/docs/automation/md-vyos-govyos.md
deleted file mode 100644
index f1ad3e91..00000000
--- a/docs/automation/md-vyos-govyos.md
+++ /dev/null
@@ -1,186 +0,0 @@
----
-lastproofread: '2026-04-14'
----
-
-(vyos-govyos)=
-
-# Go-VyOS
-
-Go-VyOS is a Go library for configuring and managing VyOS devices through
-their API.
-
-- [GitHub repository](https://github.com/ganawaj/go-vyos): Hosts the source
-  code.
-- [Documentation](https://pkg.go.dev/github.com/ganawaj/go-vyos@v0.1.0/vyos):
-  Provides the complete API reference, including available types, functions, and
-  methods.
-
-## Installation
-
-To install Go-VyOS, run:
-
-```bash
-go install "github.com/ganawaj/go-vyos/vyos"
-```
-
-## Getting started
-
-### Import and disable TLS verification
-
-```none
-import "github.com/ganawaj/go-vyos/vyos"
-client := vyos.NewClient(nil).WithToken("AUTH_KEY").WithURL("https://192.168.0.1").Insecure()
-```
-
-### Initialize a VyDevice object
-
-```none
-import (
-  "github.com/ganawaj/go-vyos/vyos"
-  "os"
-)
-
-hostname := os.Getenv("VYDEVICE_HOSTNAME")
-port := os.Getenv("VYDEVICE_PORT")
-url := fmt.Sprintf("https://%s:%s", hostname, port)
-
-apikey := os.Getenv("VYDEVICE_APIKEY")
-verify_ssl := os.Getenv("VYDEVICE_VERIFY_SSL")
-
-client := vyos.NewClient(nil).WithToken(apikey).WithURL(url)
-
-if verify_ssl == "false" {
-  client = client.Insecure()
-}
-```
-
-## Use Go-VyOS
-
-### Configure, then set
-
-```none
-out, resp, err := c.Conf.Set(ctx, "interfaces ethernet eth0 address 192.168.1.1/24")
-if err != nil {
-    panic(fmt.Sprintf("Error: %v", err))
-}
-
-fmt.Println(out.Success)
-```
-
-### Show a single object value
-
-```none
-out, resp, err := c.Show.Do(ctx, "interfaces dummy dum1 address")
-if err != nil {
-    panic("Error: %v", err)
-}
-
-fmt.Println(out.Success)
-fmt.Printf("Data: %v\n", out.Data)
-```
-
-### Configure, then show object
-
-```none
-out, resp, err := c.Conf.Get(ctx, "interfaces dummy dum1", nil)
-if err != nil {
-    panic("Error: %v", err)
-}
-
-fmt.Println(out.Success)
-fmt.Printf("Data: %v\n", out.Data)
-```
-
-### Configure, then show multivalue object
-
-```none
-options := RetrieveOptions{
-    Multivalue: true,
-}
-
-out, resp, err := c.Conf.Get(ctx, "interfaces dummy dum1", options)
-if err != nil {
-    panic("Error: %v", err)
-}
-
-fmt.Println(out.Success)
-```
-
-### Configure, then delete object
-
-```none
-out, resp, err := c.Conf.Delete(ctx, "interfaces dummy dum1")
-if err != nil {
-    panic("Error: %v", err)
-}
-
-fmt.Println(out.Success)
-```
-
-### Configure, then save
-
-```none
-out, resp, err := c.Conf.Save(ctx, "")
-
-if err != nil {
-    panic("Error: %v", err)
-}
-
-fmt.Println(out.Success)
-```
-
-### Configure, then save file
-
-```none
-out, resp, err := c.Conf.Save(ctx, "/config/test300.config")
-
-if err != nil {
-    panic("Error: %v", err)
-}
-
-fmt.Println(out.Success)
-```
-
-### Show object
-
-```none
-out, resp, err := c.Show.Do(ctx, "system image")
-if err != nil {
-    panic("Error: %v", err)
-}
-
-fmt.Println(out.Success)
-fmt.Printf("Data: %v\n", out.Data)
-```
-
-### Generate object
-
-```none
-out, resp, err := c.Generate.Do(ctx, "pki wireguard key-pair")
-if err != nil {
-    panic("Error: %v", err)
-}
-
-fmt.Println(out.Success)
-fmt.Printf("Data: %v\n", out.Data)
-```
-
-### Reset object
-
-```none
-out, resp, err := c.Reset.Do(ctx, "ip bgp 192.0.2.11")
-if err != nil {
-    panic("Error: %v", err)
-}
-
-fmt.Println(out.Success)
-fmt.Printf("Data: %v\n", out.Data)
-```
-
-### Configure, then load file
-
-```none
-out, resp, err := c.ConfigFile.Load(ctx, "/config/test300.config")
-```
-
-[go-vyos]: https://github.com/ganawaj/go-vyos
diff --git a/docs/automation/md-vyos-napalm.md b/docs/automation/md-vyos-napalm.md
deleted file mode 100644
index 87567593..00000000
--- a/docs/automation/md-vyos-napalm.md
+++ /dev/null
@@ -1,152 +0,0 @@
----
-lastproofread: '2026-04-13'
----
-
-(vyos-napalm)=
-
-# NAPALM VyOS driver
-
-VyOS can be configured using the [NAPALM VyOS driver], which enables you to
-retrieve device data and apply configurations via SSH.
-
-:::{note}
-The `napalm-vyos` module is currently in testing.
-:::
-
-To use the NAPALM VyOS driver, install the following packages:
-
-```none
-apt install python3-pip
-pip3 install napalm
-pip3 install napalm-vyos
-```
-
-## Retrieve device data
-
-The following script connects to a VyOS device, retrieves device facts and
-the ARP table, and prints the output in JSON format.
-
-```none
-#!/usr/bin/env python3
-
-import json
-from napalm import get_network_driver
-
-driver = get_network_driver('vyos')
-
-vyos_router = driver(
-    hostname="192.0.2.1",
-    username="vyos",
-    password="vyospass",
-    optional_args={"port": 22},
-)
-
-vyos_router.open()
-output = vyos_router.get_facts()
-print(json.dumps(output, indent=4))
-
-output = vyos_router.get_arp_table()
-print(json.dumps(output, indent=4))
-
-vyos_router.close()
-```
-
-Output:
-
-```none
-$ ./vyos-napalm.py
-{
-    "uptime": 7185,
-    "vendor": "VyOS",
-    "os_version": "1.3.0-rc5",
-    "serial_number": "",
-    "model": "Standard PC (Q35 + ICH9, 2009)",
-    "hostname": "r4-1.3",
-    "fqdn": "vyos.local",
-    "interface_list": [
-        "eth0",
-        "eth1",
-        "eth2",
-        "lo",
-        "vtun10"
-    ]
-}
-[
-    {
-        "interface": "eth1",
-        "mac": "52:54:00:b2:38:2c",
-        "ip": "192.0.2.2",
-        "age": 0.0
-    },
-    {
-        "interface": "eth0",
-        "mac": "52:54:00:a2:b9:5b",
-        "ip": "203.0.113.11",
-        "age": 0.0
-    }
-]
-```
-
-## Apply a configuration
-
-To apply a configuration using NAPALM VyOS driver, you will need a file with
-configuration commands (`commands.conf`) and a script that executes and
-commits them (`vyos-napalm.py`).
-
-- `commands.conf`
-
-```none
-set service ssh disable-host-validation
-set service ssh port '2222'
-set system name-server '192.0.2.8'
-set system name-server '203.0.113.8'
-set interfaces ethernet eth1 description 'FOO'
-```
-
-- `vyos-napalm.py`
-
-```none
-#!/usr/bin/env python3
-
-from napalm import get_network_driver
-
-driver = get_network_driver('vyos')
-
-vyos_router = driver(
-    hostname="192.0.2.1",
-    username="vyos",
-    password="vyospass",
-    optional_args={"port": 22},
-)
-
-vyos_router.open()
-vyos_router.load_merge_candidate(filename='commands.conf')
-diffs = vyos_router.compare_config()
-
-if bool(diffs) == True:
-    print(diffs)
-    vyos_router.commit_config()
-else:
-    print('No configuration changes to commit')
-    vyos_router.discard_config()
-
-vyos_router.close()
-```
-
-Output:
-
-```none
-$./vyos-napalm.py
-[edit interfaces ethernet eth1]
-+description FOO
-[edit service ssh]
-+disable-host-validation
-+port 2222
-[edit system]
-+name-server 192.0.2.8
-+name-server 203.0.113.8
-[edit]
-```
-
-[napalm]: https://napalm.readthedocs.io/en/latest/base.html
-[NAPALM VyOS driver]: https://github.com/napalm-automation-community/napalm-vyos
diff --git a/docs/automation/md-vyos-netmiko.md b/docs/automation/md-vyos-netmiko.md
deleted file mode 100644
index 2e947b6a..00000000
--- a/docs/automation/md-vyos-netmiko.md
+++ /dev/null
@@ -1,76 +0,0 @@
----
-lastproofread: '2026-04-13'
----
-
-(vyos-netmiko)=
-
-# Netmiko
-
-VyOS can be configured using [Netmiko]. To use Netmiko, install the
-`python3-netmiko` module.
-
-## Example
-
-The following script connects to a VyOS device, applies configuration changes,
-commits them, and runs an operational mode command to verify the updated
-configuration.
-
-```none
-#!/usr/bin/env python3
-
-from netmiko import ConnectHandler
-
-vyos_router = {
-  "device_type": "vyos",
-  "host": "192.0.2.1",
-  "username": "vyos",
-  "password": "vyospass",
-  "port": 22,
-  }
-
-net_connect = ConnectHandler(**vyos_router)
-
-config_commands = [
-                   'set interfaces ethernet eth0 description WAN',
-                   'set interfaces ethernet eth1 description LAN',
-                  ]
-
-# set configuration
-output = net_connect.send_config_set(config_commands, exit_config_mode=False)
-print(output)
-
-# commit configuration
-output = net_connect.commit()
-print(output)
-
-# operational mode commands
-output = net_connect.send_command("run show interfaces")
-print(output)
-```
-
-Output
-
-```none
-$ ./vyos-netmiko.py
-configure
-set interfaces ethernet eth0 description WAN
-[edit]
-vyos@r4-1.5# set interfaces ethernet eth1 description LAN
-[edit]
-vyos@r4-1.5#
-commit
-[edit]
-vyos@r4-1.5#
-Codes: S - State, L - Link, u - Up, D - Down, A - Admin Down
-Interface        IP Address                        S/L  Description
----------        ----------                        ---  -----------
-eth0             203.0.113.1/24                    u/u  WAN
-eth1             192.0.2.1/30                      u/u  LAN
-eth2             -                                 u/u
-lo               127.0.0.1/8                       u/u
-                 ::1/128
-vtun10           10.10.0.1/24                      u/u
-[edit]
-```
-
-[netmiko]: https://github.com/ktbyers/netmiko
diff --git a/docs/automation/md-vyos-pyvyos.md b/docs/automation/md-vyos-pyvyos.md
deleted file mode 100644
index 2a9599d7..00000000
--- a/docs/automation/md-vyos-pyvyos.md
+++ /dev/null
@@ -1,138 +0,0 @@
----
-lastproofread: '2026-04-14'
----
-
-(vyos-pyvyos)=
-
-# PyVyOS
-
-PyVyOS is a Python library for configuring and managing VyOS devices through
-their API.
-
-**Key resources:**
-
-- [Documentation](https://pyvyos.readthedocs.io/en/latest/): Provides
-  installation, configuration, and usage instructions.
-- [GitHub repository](https://github.com/robertoberto/pyvyos): Hosts the
-  source code.
-- [PyPI](https://pypi.org/project/pyvyos/): Hosts distribution packages for
-  installation via the Python package installer (`pip`).
-
-## Installation
-
-To install PyVyOS via `pip`, run:
-
-```bash
-pip install pyvyos
-```
-
-## Getting started
-
-### Import and disable warnings for verify=false
-
-```none
-import urllib3
-urllib3.disable_warnings()
-```
-
-### Use API response class
-
-```none
-@dataclass
-class ApiResponse:
-    status: int
-    request: dict
-    result: dict
-    error: str
-```
-
-### Initialize a VyDevice object
-
-```none
-from dotenv import load_dotenv
-load_dotenv()
-
-hostname = os.getenv('VYDEVICE_HOSTNAME')
-apikey = os.getenv('VYDEVICE_APIKEY')
-port = os.getenv('VYDEVICE_PORT')
-protocol = os.getenv('VYDEVICE_PROTOCOL')
-verify_ssl = os.getenv('VYDEVICE_VERIFY_SSL')
-
-verify = verify_ssl.lower() == "true" if verify_ssl else True 
-
-device = VyDevice(hostname=hostname, apikey=apikey, port=port, protocol=protocol, verify=verify)
-```
-
-## Use PyVyOS
-
-### Configure, then set
-
-```none
-response = device.configure_set(path=["interfaces", "ethernet", "eth0", "address", "192.168.1.1/24"])
-if not response.error:
-    print(response.result)
-```
-
-### Configure, then show a single object value
-
-```none
-response = device.retrieve_return_values(path=["interfaces", "dummy", "dum1", "address"])
-print(response.result)
-```
-
-### Configure, then show object
-
-```none
-response = device.retrieve_show_config(path=[])
-if not response.error:
-    print(response.result)
-```
-
-### Configure, then delete object
-
-```none
-response = device.configure_delete(path=["interfaces", "dummy", "dum1"])
-```
-
-### Configure, then save
-
-```none
-response = device.config_file_save()
-```
-
-### Configure, then save file
-
-```none
-response = device.config_file_save(file="/config/test300.config")
-```
-
-### Show object
-
-```none
-response = device.show(path=["system", "image"])
-print(response.result)
-```
-
-### Generate object
-
-```none
-randstring = ''.join(random.choice(string.ascii_letters + string.digits) for _ in range(20))
-keyrand =  f'/tmp/key_{randstring}'
-response = device.generate(path=["ssh", "client-key", keyrand])
-```
-
-### Reset object
-
-```none
-response = device.reset(path=["conntrack-sync", "internal-cache"])
-if not response.error:
-    print(response.result)
-```
-
-### Configure, then load file
-
-```none
-response = device.config_file_load(file="/config/test300.config")
-```
-
-[pyvyos]: https://github.com/robertoberto/pyvyos
diff --git a/docs/automation/terraform/md-index.md b/docs/automation/terraform/md-index.md
deleted file mode 100644
index 9f741c35..00000000
--- a/docs/automation/terraform/md-index.md
+++ /dev/null
@@ -1,28 +0,0 @@
----
-lastproofread: '2026-03-23'
----
-
-# VyOS Terraform
-
-VyOS supports development infrastructure via Terraform and provisioning
-via Ansible.
-Terraform allows you to automate the deployment of instances on a number of
-cloud and virtual platforms. This section shows how to deploy VyOS on
-multiple platforms: AWS, Microsoft Azure, Google Cloud Platform (GCP),
-and VMware vSphere.
-For more information, see the
-official documentation for [Terraform] and [Ansible].
-
-```{toctree}
-:caption: Guides
-:maxdepth: 1
-
-terraformAWS
-terraformAZ
-terraformGoogle
-terraformvSphere
-```
-
-[ansible]: https://docs.ansible.com
-[install]: https://developer.hashicorp.com/terraform/tutorials/aws-get-started/install-cli
-[terraform]: https://developer.hashicorp.com/terraform/intro