docs: move f3s/k8s deployment details out to homelab skill

Remove all f3s/k3s/cluster-specific deployment content from README.md,
AGENTS.md, and ychat/DOCKER.md. The DB-backed build's deployment status,
live URL, image tag, PVC, Helm chart, and ArgoCD app details now live in
the private homelab skill's references/ychat.md sub-reference instead of
this public repo.

- README.md: drop the 'Deploying to the f3s k3s cluster' section and the
  'Deployed to f3s' table note; genericize the emptyDir log note.
- AGENTS.md: drop the explicit f3s skill name from the deployment section;
  keep only a generic out-of-scope pointer to the homelab skill.
- ychat/DOCKER.md: remove the 'still running live on the f3s k3s cluster'
  History mention, the 'Not yet deployed to f3s' block, and the entire
  'Deploying to the f3s k3s cluster' section.

1 files changed, 5 insertions, 8 deletions

diff --git a/AGENTS.md b/AGENTS.md
index 739d2a0..269e525 100644
--- a/AGENTS.md
+++ b/AGENTS.md
@@ -19,11 +19,8 @@ steps, follow [README.md](README.md) and the per-subproject `DOCKER.md` /
 
 ## Deployment (homelab-only, not in this repo)
 
-Deploying ychat to the f3s homelab k3s cluster (private registry push, Helm
-chart, ArgoCD Application, PVC for `/app/data`) is **homelab-specific and
-deliberately not documented in this public repo**.
-
-If you are running with the private `f3s` Amp skill available, its
-`references/ychat.md` reference has the full deployment runbook (image
-build/push, Helm chart path, ArgoCD app, storage/PVC notes). Load the `f3s`
-skill for those details. Without that skill, treat deployment as out of scope.
+Deploying ychat to a homelab cluster (private registry push, Helm chart,
+ArgoCD Application, PVC for `/app/data`) is **homelab-specific and out of
+scope for this public repo**. The full deployment runbook lives in the
+private homelab skill (its `references/ychat.md`). Load that skill for those
+details; without it, treat deployment as out of scope.