docs: migrate workflow to DooPlex-local execution

CLAUDE.md

@@ -3,7 +3,9 @@
 > Read automatically when Claude Code works in this repo. Stable orientation only — **current state
 > lives in `CONTEXT.md` and the tops of `hub/CHANGELOG.md` / `scripts/CHANGELOG.md` /
 > `website/CHANGELOG.md`**, never here. Cross-repo orientation (the felhom system, artifact
-> taxonomy, access): workspace-root `e:\git\CLAUDE.md`; this file is `felhom.eu`-specific.
+> taxonomy, access): workspace-root `/mnt/5_hdd/felhom.eu/git/CLAUDE.md`; this file is
+> `felhom.eu`-specific. A versioned copy of that workspace file lives at
+> `documentation/runbooks/workspace-CLAUDE.md`.
 
 ## Project overview
 
@@ -15,8 +17,9 @@ This repo contains:
   system**: `architecture/01..05-*.md`, `proxmox-platform.md`, `tests/phase*-findings.md`,
   runbooks, audits. Read these before designing.
 - **Skills** (`skills/`) — the versioned source of the Claude Code skills
-  (`felhom-build-deploy`, `felhom-ui-design`, `felhom-testing`); install/update with
-  `python scripts/install_skills.py` (junction into `~/.claude/skills/`).
+  (`felhom-build-deploy`, `felhom-ui-design`, `felhom-testing`, `felhom-app-catalog`);
+  install/update with `python3 scripts/install_skills.py` (symlink into `~/.claude/skills/` on
+  POSIX, junction on Windows — either way repo edits are live immediately).
 
 See `README.md` for full architecture/DNS/email/SEO docs. See `TASK.md` for the current task (if any).
 See `REUSE.md` before writing new code.
@@ -65,10 +68,11 @@ pushes; **you (Claude Code) implement**. A file being open in the editor is NOT
   SSH + the felhom-agent token). Mark a step HUMAN only when it genuinely needs physical presence, a
   real-world decision, or credentials CC truly lacks.
 - Validation of a push against a spec's criteria is project Claude's job, not yours, unless asked.
-- **Browser automation available** (`claude-in-chrome`): CC can drive `hub.felhom.eu`, the website,
-  or any `*.demo-felhom.eu` UI for live validation + screenshots. Caveat: tools attach only to a
-  session STARTED AFTER the bridge connected. Note: the hub UI is operator-password-gated — CC
-  cannot log in; verify UI changes via render tests instead.
+- **Browser automation is NOT available** in the DooPlex environment (`claude-in-chrome` was a
+  Windows-workstation capability). Validate at the endpoint level — invoke the exact endpoint the UI
+  invokes — and via render tests; say which method was used. The hub UI is operator-password-gated
+  anyway, so render tests were already the method for UI changes. Strict end-to-end UI coverage is a
+  manual click-through by the operator.
 
 > **In every repository where you make a change, update both files in that repo:**
 > - **`CHANGELOG.md`** — cumulative log, newest on top (here: per-area `hub/`, `scripts/`, `website/`).
@@ -93,14 +97,20 @@ pushes; **you (Claude Code) implement**. A file being open in the editor is NOT
 - **Config:** YAML via ConfigMap at `/etc/felhom-hub/hub.yaml`. Secrets via out-of-band
   `secretKeyRef` (never inline stringData — REUSE.md §3).
 
-## SSH access
+## Environment & access
 
-Use the Windows OpenSSH binary (Git Bash's ssh fails silently): `SSH=/c/Windows/System32/OpenSSH/ssh.exe`.
+Claude Code runs **on DooPlex (192.168.0.180, Debian 13, user `kisfenyo`)** — the k3s node itself.
+Repos in `/mnt/5_hdd/felhom.eu/git/`, build dirs in `/mnt/5_hdd/felhom.eu/build/`. `kubectl` and the
+image build/push are local commands; felhom-pve is one SSH hop.
 
-| Host | IP | User | Role |
-|------|----|------|------|
-| Build server (k3s node) | 192.168.0.180 | kisfenyo | Build + push images, `sudo kubectl` |
-| Demo Proxmox host | 192.168.0.162 | root@pam (SSH alias `felhom-pve`) | pveum/pct + live Proxmox validation |
+| Host | Access | Role |
+|------|--------|------|
+| **DooPlex (this host)** | local — `/mnt/5_hdd/felhom.eu/{git,build}/` | Build + push images, `sudo kubectl` |
+| Demo Proxmox host | `ssh felhom-pve` (root@192.168.0.162) | pveum/pct + live Proxmox validation |
+
+> **Legacy: Windows workstation.** Until 2026-07-19 CC ran on Windows 11 with repos in `E:\git\`,
+> and every remote command needed `SSH=/c/Windows/System32/OpenSSH/ssh.exe` (Git Bash's ssh fails
+> silently). Retained in case that environment is revived.
 
 ## Build & deploy — Hub (GitOps via ArgoCD)
 
@@ -118,14 +128,20 @@ truth is the **manifest**:
   happened — reconcile via the manifest, not the changelog.
 - Green gate before any hub commit: `go build ./... && go vet ./... && go test ./...` in `hub/`.
 
-Steps: commit+push code → `./build.sh <VER> --push` on 180 (`/mnt/5_hdd/felhom.eu/build/felhom-hub` — all felhom build dirs/repos moved off the SSD to `/mnt/5_hdd/felhom.eu/` on 2026-07-18) → bump
-`manifests/hub.yaml` tag + push → ArgoCD hard-refresh + sync (kubectl-patch method in the skill) →
-verify Synced/Healthy + rollout + image + startup log.
+> **Clean-tree gate before any build:** `git status --porcelain` must be empty and
+> `git rev-parse HEAD` must equal `git rev-parse origin/main` in the repo being built. An unpushed
+> change does not exist — never build a dirty or unpushed tree. The `git pull` in the build step
+> stays (it is a no-op when you work in this tree, and load-bearing if anything was pushed from
+> elsewhere).
+
+Steps: commit+push code → `cd /mnt/5_hdd/felhom.eu/build/felhom-hub && ./build.sh <VER> --push`
+(local) → bump `manifests/hub.yaml` tag + push → ArgoCD hard-refresh + sync (kubectl-patch method in
+the skill, now local `sudo kubectl`) → verify Synced/Healthy + rollout + image + startup log.
 
 ## Build & deploy — Website / Manifests
 
 - **Website** auto-deploys via git-sync; just push to `main` (live in 1–2 min). **Run
-  `python scripts/site_gates.py` after ANY website change**; new pages go into its `PAGES` list.
+  `python3 scripts/site_gates.py` after ANY website change**; new pages go into its `PAGES` list.
   Emergency edits: https://files.felhom.eu. All `website/` HTML is **UTF-8 with BOM** — preserve it.
 - **Manifests** are GitOps via the `felhom` app — commit to `main`, then deliberate sync.