Update docs for ToolHive v0.16.0 (#687)

* Update docs for ToolHive v0.16.0

- Add thv skill builds and thv skill builds remove guide content to
  skills-management.mdx with example output and CLI reference link
- Fix MCPOIDCConfig status column name READY → VALID in auth-k8s.mdx
  (breaking change in v0.16.0: condition type renamed for consistency)
- Document MCPServerEntry CRD in K8s intro with note that controller
  ships in a future release
- Clarify VirtualMCPServer Redis session storage enables cross-pod
  restore and survives pod restarts

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

* Address PR review feedback

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

* Fix Prettier formatting in intro.mdx

---------

Co-authored-by: Claude Sonnet 4.6 <noreply@anthropic.com>

Author: reyortiz3

docs/toolhive/guides-cli/skills-management.mdx

@@ -301,6 +301,50 @@ authenticated before pushing.
 
 :::
 
+## List and remove locally-built skill artifacts
+
+After building skills locally, you can view and manage the artifacts stored in
+your local OCI store.
+
+### List locally-built artifacts
+
+```bash
+thv skill builds
+```
+
+This lists all OCI skill artifacts built locally with `thv skill build`. The
+output shows the tag, digest, name, and version of each artifact:
+
+```text
+TAG                                       DIGEST              NAME        VERSION
+ghcr.io/my-org/skills/my-skill:v1.0.0     sha256:a1b2c3d4...  my-skill    1.0.0
+my-skill:latest                           sha256:e5f6a7b8...  my-skill
+```
+
+For JSON output:
+
+```bash
+thv skill builds --format json
+```
+
+### Remove a locally-built artifact
+
+To remove an artifact from the local OCI store:
+
+```bash
+thv skill builds remove <TAG>
+```
+
+For example:
+
+```bash
+thv skill builds remove my-skill:latest
+```
+
+This removes the artifact and cleans up its blobs from the local store. If
+multiple tags share the same digest, the blobs are retained until all tags
+pointing to that digest are removed.
+
 ## Next steps
 
 - [Configure your AI client](./client-configuration.mdx) to register clients

docs/toolhive/guides-k8s/auth-k8s.mdx

@@ -187,7 +187,7 @@ Check the MCPOIDCConfig status:
 kubectl get mcpoidc -n toolhive-system
 ```
 
-The `REFERENCES` column shows which workloads use this config. The `READY`
+The `REFERENCES` column shows which workloads use this config. The `VALID`
 column confirms validation passed.
 
 ### Benefits of MCPOIDCConfig

docs/toolhive/guides-k8s/intro.mdx

@@ -21,9 +21,9 @@ quickly using a local kind cluster. Try it out and
 The operator introduces new Custom Resource Definitions (CRDs) into your
 Kubernetes cluster. The primary CRDs for MCP server workloads are `MCPServer`,
 which represents a single MCP server running in Kubernetes, `MCPRemoteProxy`,
-which represents an MCP server running outside the cluster that is proxied by
-ToolHive, and `VirtualMCPServer`, which represents a virtual MCP server gateway
-that aggregates multiple backend MCP servers.
+which represents an MCP server hosted outside the cluster that ToolHive proxies,
+`VirtualMCPServer`, which aggregates multiple backend MCP servers behind a
+single endpoint.
 
 All ToolHive CRDs are registered under the `toolhive` category, so you can list
 every ToolHive resource in your cluster with a single command:
@@ -67,8 +67,8 @@ or Gateway. To learn how to expose your MCP servers and connect clients, see
 
 ## Which resource type should I use?
 
-The operator introduces three resource types for MCP workloads. Choose based on
-where your MCP server runs and how many servers you need to manage:
+The operator introduces resource types for MCP workloads. Choose based on where
+your MCP server runs and how many servers you need to manage:
 
 | Resource             | Use when                                                                                                          |
 | -------------------- | ----------------------------------------------------------------------------------------------------------------- |

docs/toolhive/guides-vmcp/scaling-and-performance.mdx

@@ -67,8 +67,9 @@ kubectl autoscale deployment vmcp-<VMCP_NAME> -n <NAMESPACE> \
 ### Session storage for multi-replica deployments
 
 When running multiple replicas, configure Redis session storage so that sessions
-are shared across pods. Without session storage, a request routed to a different
-replica than the one that established the session will fail.
+are shared across pods and survive pod restarts. Without session storage, a
+request routed to a different replica than the one that established the session
+will fail, and sessions are lost when pods restart.
 
 ```yaml title="VirtualMCPServer resource"
 spec: