CON-1518: Host docs IA mockup updates

docs.json

@@ -588,26 +588,67 @@
         "tab": "Host",
         "groups": [
           {
-            "group": "Concepts",
-            "icon": "lightbulb",
+            "group": "Before You Host",
+            "icon": "compass",
             "pages": [
               "host/hosting-overview",
-              "host/understanding-verification",
-              "host/earning"
+              "host/supported-hardware",
+              "host/persona-decision-guide",
+              "host/earning",
+              "host/guide-to-taxes"
+            ]
+          },
+          {
+            "group": "Set Up",
+            "icon": "wrench",
+            "pages": [
+              "host/quickstart",
+              "host/account-hosting-agreement",
+              "host/hardware-prep",
+              "host/storage-setup",
+              "host/network-ports",
+              "host/installing-host-software",
+              "host/headless-install",
+              "host/vms"
             ]
           },
           {
-            "group": "Guides",
-            "icon": "warehouse",
+            "group": "Verify & List",
+            "icon": "badge-check",
             "pages": [
               "host/optimization-guide",
               "host/verification-stages",
+              "host/understanding-verification",
               "host/how-to-self-test",
               "host/market-metrics",
+              "host/self-test-reference",
+              "host/pricing-your-listing",
+              "host/not-in-search"
+            ]
+          },
+          {
+            "group": "Operate",
+            "icon": "gauge",
+            "pages": [
+              "host/first-24-hours",
+              "host/reliability-uptime",
+              "host/maintenance-windows",
+              "host/removing-recreating-machines",
+              "host/fleet-operations",
+              "host/common-errors-diagnostics",
               "host/datacenter-status",
               "host/payment",
-              "host/guide-to-taxes",
-              "host/vms"
+              "host/workload-policy"
+            ]
+          },
+          {
+            "group": "Reference",
+            "icon": "book-open",
+            "pages": [
+              "host/common-host-questions",
+              "host/glossary",
+              "host/hosting-agreement",
+              "host/community"
             ]
           },
           {
@@ -808,7 +849,7 @@
     "links": [
       {
         "label": "FAQ",
-        "href": "/guides/reference/faq"
+        "href": "https://docs.vast.ai/guides/reference/faq"
       },
       {
         "label": "Discord",

host/account-hosting-agreement.mdx

@@ -0,0 +1,48 @@
+---
+title: "Account & Hosting Agreement"
+sidebarTitle: "Account & Agreement"
+description: "Host account conversion and agreement flow."
+"canonical": "/host/account-hosting-agreement"
+personas:
+  - pro-operator
+  - headless-operator
+  - business-owner
+  - hobbyist
+---
+
+<div className="persona-chips"><span className="persona-chip">All host personas</span></div>
+
+Use this page when a host account, hosting agreement, or Machines tab is not behaving as expected.
+
+<a id="separate-host-account" />
+## Do I need a separate host account?
+
+Yes. Use a dedicated account for hosting. Do not use the same account for both client rentals and host operations, because that setup is unsupported and can cause account and machine-management issues.
+
+## How to accept the hosting agreement
+
+Once your host account is created, open the [host setup guide](https://cloud.vast.ai/host/setup/). There is a link in the first paragraph to the hosting agreement. Read through the agreement. Once you accept, your account is converted to a hosting account, and a Machines link appears in the navigation. Your account can now list machines that are running the daemon software.
+
+<a id="host-features-tab" />
+## What must happen before I can see host features or the Machines tab?
+
+Your account must be enabled for hosting and the hosting agreement must be accepted. After the account is converted to a host account, the Machines navigation and other host features should become available.
+
+If the account still behaves like a client account, confirm that you are signed into the intended host account and that the agreement flow completed.
+
+<a id="agreement-stuck" />
+## What if I accepted the agreement but still see a client account?
+
+Confirm that you are signed into the correct dedicated host account, then refresh or sign out and back in. If the Machines tab is still missing, treat it as an account-state issue rather than a Linux install issue. Contact Vast support with the host account email and screenshots or error messages from the setup flow.
+
+## Stale or deprecated setup links
+
+Copy the install command only from the official setup page while signed into the host account. Commands from old notes, screenshots, third-party guides, or another account can contain expired or account-specific material. See [Installing Host Software](/host/installing-host-software#install-command).
+
+## Related pages
+
+| Topic | Read next |
+| --- | --- |
+| First-time setup path | [Hosting Quickstart](/host/quickstart) |
+| Installing the host software | [Installing Host Software](/host/installing-host-software) |
+| Agreement reference | [Hosting Agreement](/host/hosting-agreement) |

host/common-errors-diagnostics.mdx

@@ -0,0 +1,90 @@
+---
+title: "Common Errors & Diagnostics"
+sidebarTitle: "Errors & Diagnostics"
+description: "Common host errors and diagnostic collection paths."
+"canonical": "/host/common-errors-diagnostics"
+personas:
+  - pro-operator
+  - headless-operator
+---
+
+<div className="persona-chips"><span className="persona-chip">Pro Operator</span><span className="persona-chip">Headless / DC</span></div>
+
+Use this page for host errors that are not specific to install, networking, or self-test, and for collecting diagnostics before asking for help.
+
+<a id="logs" />
+## Where are installer, daemon, and self-test logs?
+
+For self-test failures, the CLI can create a diagnostic bundle. Default self-test bundles include:
+
+- `self-test-output.log`
+- `self-test-result.json`
+- `manifest.json`
+- `collection-errors.json`
+
+Runtime failures can also include:
+
+- `instance/show-instance.json`
+- `instance/container.log`
+- `instance/daemon.log`
+
+You can also create a manual diagnostic bundle with the Vast CLI. Use the current CLI reference for the exact command and run it from the host-enabled account that owns the machine.
+
+If you run diagnostics on the actual host, the bundle can include host-local artifacts such as kaalia logs, `dmesg`, `journalctl`, Docker daemon config, and mount information.
+
+<a id="red-error" />
+## What is this red error message on my machine?
+
+If the hosting software detects an error, that error message is listed on your machine in the machines page. Once the cause of the error has been resolved, most error messages are automatically cleared after 1-2 hours. The quickest way to learn more about resolving specific error messages is the hosting channels in [our Discord](https://discord.gg/hSuEbSQ4X8).
+
+<a id="docker-cache" />
+## My storage for clients is full of old stopped jobs — can I free up space?
+
+Try cleaning up the Docker build cache, as it sometimes frees up far more space than it claims. You can also clean up old unused images. For expired or deleted rental contracts that did not release their storage, run [vastai cleanup machine](/host/cli/cleanup-machine).
+
+<a id="nvidia-smi-fails" />
+## What should I do when nvidia-smi fails?
+
+Treat `nvidia-smi` failure as a host GPU or driver health problem. Check whether the NVIDIA driver is loaded, whether the GPU is visible on the PCIe bus, whether a reboot is needed after a driver or kernel update, whether there is an NVML driver/library mismatch, and whether system logs show NVRM, Xid, or PCIe errors. Do not keep a machine listed if it cannot reliably report GPU state.
+
+<a id="nvml-mismatch" />
+## What should I do for NVML driver/library mismatch?
+
+This usually means the NVIDIA userspace library and loaded kernel module are from different driver versions, often after an update. Plan downtime and reboot first. If the mismatch persists, clean up or reinstall the NVIDIA driver stack, then verify `nvidia-smi` before listing again.
+
+<a id="gpu-falls-off-bus" />
+## What should I do when a GPU falls off the PCIe bus?
+
+Treat this as a hardware, power, thermal, PCIe, or driver stability issue. Check logs for NVRM, Xid, and PCIe/AER errors. Power-cycle the machine, then inspect PSU capacity, power cables, risers, slots, PCIe lane settings, thermals, and any overclock or undervolt. Repeated bus drops should be fixed before the machine is listed again.
+
+<a id="bad-bandwidthtest2" />
+## What should I do for bad bandwidthtest2?
+
+`bad bandwidthtest2` is best treated as a machine health or verification error. It usually points at a GPU, PCIe, driver/runtime, or data-transfer problem. Check PCIe bandwidth and lane configuration, GPU seating, thermals, power, driver and NVML health, Xid errors, Docker GPU runtime behavior, and self-test diagnostic output. Rerun self-test after fixing the hardware or driver issue.
+
+<a id="failed-cdi" />
+## What should I do for failed to inject CDI devices?
+
+If logs or machine status mention failed CDI device injection, treat it as a container GPU device injection or runtime problem. Current self-test output may surface the same underlying issue as a startup or runtime failure instead of using the literal CDI text. Gather a diagnostic bundle, check Docker and NVIDIA container runtime/CDI configuration, confirm GPUs are visible on the host, inspect daemon and container logs, and check for related machine errors. If the configuration looks correct but containers still cannot receive GPU devices, escalate with logs and the machine details requested by support.
+
+<a id="collect-logs" />
+## What logs should I collect before asking for help?
+
+Include the account context, exact command, timestamps, screenshots or CLI output, tested external IP:port for network failures, and the self-test support bundle when available. If support asks for machine-specific details, share them in the support channel rather than a public community thread.
+
+Review bundles before sharing them.
+
+<a id="escalate-support" />
+## What should I escalate to Vast support?
+
+Escalate account conversion or hosting agreement issues, payment/tax/payout provider issues that the docs cannot resolve, backend machine records or ghost machines that normal UI/CLI actions cannot remove, API permission or account-visibility problems, suspected backend bugs, and cases where self-test or diagnostics show a platform state mismatch after following documented steps.
+
+Local Ubuntu, Docker, GPU driver, hardware, power, thermals, and consumer network setup are primarily host responsibilities. Bring logs and diagnostics when asking for help.
+
+## Related pages
+
+| Topic | Read next |
+| --- | --- |
+| Install-time failures | [Installing Host Software](/host/installing-host-software#install-failures) |
+| Self-test error strings | [Self-Test Reference](/host/self-test-reference) |
+| Connectivity problems | [Network & Ports](/host/network-ports) |