feat: positioning pass, editions comparison, demo paths + docs restructure

Marketing site:
- Standardize on diagram-led category ("network diagram & documentation software")
  and "teams that manage infrastructure" ICP across pages, Organization schema, llms.txt
- SEO/audit fixes: unresolved {{SERVICE_COUNT}} in home schema, services ItemList
  numberOfItems, annual-billed-monthly pricing schema, unified service-count label,
  REVIEW_YEAR constant, "scheduled not continuous" wording, docs-link trailing slashes
- Homepage FAQ + FAQPage schema; reorder tail sections (testimonials/FAQ before final CTA)
- Dual-motion CTAs: persistent Talk to Sales; restore Live Demo to navbar (full env)
- Editions comparison (Cloud/Commercial/Community/Enterprise), deployment/price/limits
  derived from billing-plans.json
- Commercial: Talk to Sales primary, Request a Quote secondary
- Analytics: standardize ctaClicked destinations, instrument ArticleCTA + contact opens
- Wire generated comparison/guide pages into llms.txt; footer Resources leads with Documentation
- Normalize CTA/nav labels to Title Case

Docs:
- Reorganize guides into integrations/networking/operations subfolders
- OpenAPI + reference/config updates

Author: mayanayza

docs/content/docs/guides/docker-proxy.mdx …tent/docs/guides/integrations/docker.mdxdocs/content/docs/guides/docker-proxy.mdx renamed to docs/content/docs/guides/integrations/docker.mdx docs/content/docs/guides/docker-proxy.mdx renamed to docs/content/docs/guides/integrations/docker.mdx

@@ -1,11 +1,11 @@
 ---
-title: Set up a Docker Proxy
-description: How to use a Docker socket proxy to discover containers securely, including remote Docker hosts.
+title: Set up Docker discovery
+description: How Scanopy discovers Docker containers — the default local socket, plus using a socket proxy for restricted access or remote hosts.
 ---
 
 Scanopy daemons can discover Docker containers by connecting to the Docker API. By default, daemons connect directly to the local Docker socket (`/var/run/docker.sock`). A Docker socket proxy provides an additional security layer by restricting which Docker API operations are allowed — and enables discovering containers on remote hosts.
 
-For background on how credentials work — types, scope models, resolution order, and auto-assignment — see [Credentials](/using-scanopy/credentials/). Running Podman instead? See [Set up Podman discovery](/guides/podman/), which follows the same pattern.
+For background on how credentials work — types, scope models, resolution order, and auto-assignment — see [Credentials](/using-scanopy/credentials/). Running Podman instead? See [Set up Podman discovery](/guides/integrations/podman/), which follows the same pattern.
 
 ## Docker Discovery Modes
 
@@ -132,7 +132,7 @@ Scanopy daemon uses the following Docker API endpoints:
 **Why exec?** Scanopy uses `exec` to probe HTTP endpoints from inside containers that don't expose ports to the host. Without exec access, containers are still discovered but service detection may be less accurate.
 
 <Callout type="warn">
-**Migrating from daemon config?** If you previously configured Docker proxy via `--docker-proxy`, `SCANOPY_DOCKER_PROXY`, or the config file, you need to recreate it as a Docker Proxy credential. The daemon config flags are deprecated in v0.15.0 and will be removed in v0.16.0. See the [migration guide](/guides/unified-discovery-migration/) for details.
+**Migrating from daemon config?** If you previously configured Docker proxy via `--docker-proxy`, `SCANOPY_DOCKER_PROXY`, or the config file, you need to recreate it as a Docker Proxy credential. The daemon config flags are deprecated in v0.15.0 and will be removed in v0.16.0. See the [migration guide](/guides/operations/unified-discovery-migration/) for details.
 </Callout>
 
 ## Troubleshooting

docs/content/docs/guides/integrations/meta.json

@@ -0,0 +1,5 @@
+{
+  "title": "Integrations",
+  "defaultOpen": true,
+  "pages": ["snmp", "docker", "podman"]
+}

docs/content/docs/guides/podman.mdx …tent/docs/guides/integrations/podman.mdxdocs/content/docs/guides/podman.mdx renamed to docs/content/docs/guides/integrations/podman.mdx docs/content/docs/guides/podman.mdx renamed to docs/content/docs/guides/integrations/podman.mdx

@@ -3,7 +3,7 @@ title: Set up Podman discovery
 description: How Scanopy discovers Podman containers and pods, via the local socket or a remote Podman API proxy.
 ---
 
-Scanopy daemons discover Podman containers and pods by connecting to the Podman API. Because Podman exposes a Docker-compatible API, discovery works the same way as [Docker](/guides/docker-proxy/): the daemon lists running containers, maps their networks and published ports, identifies containerized services, and creates container bridge subnets automatically.
+Scanopy daemons discover Podman containers and pods by connecting to the Podman API. Because Podman exposes a Docker-compatible API, discovery works the same way as [Docker](/guides/integrations/docker/): the daemon lists running containers, maps their networks and published ports, identifies containerized services, and creates container bridge subnets automatically.
 
 For background on how credentials work — types, scope models, resolution order, and auto-assignment — see [Credentials](/using-scanopy/credentials/).
 
@@ -85,7 +85,7 @@ Discovered Podman containers show up as first-class **Podman Container** service
 
 ## Required API Operations
 
-Scanopy uses the same API operations for Podman as it does for Docker — listing and inspecting containers, listing networks for subnet discovery, and `exec` to probe HTTP endpoints inside containers that don't publish ports to the host. When you put a proxy in front of the socket, allow these operations. See [Required Docker API Permissions](/guides/docker-proxy/#required-docker-api-permissions) for the endpoint-by-endpoint list — the Podman compatibility API mirrors it.
+Scanopy uses the same API operations for Podman as it does for Docker — listing and inspecting containers, listing networks for subnet discovery, and `exec` to probe HTTP endpoints inside containers that don't publish ports to the host. When you put a proxy in front of the socket, allow these operations. See [Required Docker API Permissions](/guides/integrations/docker/#required-docker-api-permissions) for the endpoint-by-endpoint list — the Podman compatibility API mirrors it.
 
 ## Troubleshooting
 
@@ -103,4 +103,4 @@ Scanopy uses the same API operations for Podman as it does for Docker — listin
 
 ### SSL certificate errors
 
-For HTTPS endpoints, see the [Docker Proxy SSL troubleshooting](/guides/docker-proxy/#ssl-certificate-errors) steps — certificate handling is identical.
+For HTTPS endpoints, see the [Docker Proxy SSL troubleshooting](/guides/integrations/docker/#ssl-certificate-errors) steps — certificate handling is identical.

…content/docs/guides/snmp-credentials.mdx …ontent/docs/guides/integrations/snmp.mdxdocs/content/docs/guides/snmp-credentials.mdx renamed to docs/content/docs/guides/integrations/snmp.mdx docs/content/docs/guides/snmp-credentials.mdx renamed to docs/content/docs/guides/integrations/snmp.mdx

@@ -1,6 +1,6 @@
 ---
-title: Set up SNMP credentials
-description: Configure SNMP community strings to enrich discovered hosts with device details, interfaces, and neighbor data.
+title: Set up SNMP discovery
+description: Configure SNMP credentials to enrich discovered hosts with device details, interfaces, and neighbor data.
 ---
 
 For background on how credentials work — types, scope models, resolution order, and auto-assignment — see [Credentials](/using-scanopy/credentials/).

docs/content/docs/guides/meta.json

@@ -1,5 +1,5 @@
 {
   "title": "Guides",
   "defaultOpen": true,
-  "pages": ["unified-discovery-migration", "snmp-credentials", "sharing-topology", "multiple-daemons", "scanning-remote-subnets", "scanning-vpn-networks", "docker-proxy", "podman", "macvlan-setup", "oidc", "prometheus-setup"]
+  "pages": ["integrations", "networking", "operations"]
 }

…cs/content/docs/guides/macvlan-setup.mdx …docs/guides/networking/macvlan-setup.mdxdocs/content/docs/guides/macvlan-setup.mdx renamed to docs/content/docs/guides/networking/macvlan-setup.mdx docs/content/docs/guides/macvlan-setup.mdx renamed to docs/content/docs/guides/networking/macvlan-setup.mdx

@@ -0,0 +1,5 @@
+{
+  "title": "Networking & Deployment",
+  "defaultOpen": true,
+  "pages": ["multiple-daemons", "scanning-remote-subnets", "scanning-vpn-networks", "macvlan-setup"]
+}