Spaces: members must not receive a kubeconfig / see Kubernetes #150

Owner decision (2026-10-04): members should never receive a kubeconfig nor see Kubernetes concepts (namespaces, pods, PVCs). Today Spaces hands the member a kubeconfig and the cloud-ui / website (apps.md, examples.md) expose Kubernetes terms on purpose. Scope to define later: replace kubeconfig-based access with product-level operations, remove Kubernetes vocabulary from member-facing copy and API messages.

Related: hide-internals PRs (cloud-ui #139, cloud-api #302, website #149) deliberately left Spaces/Kubernetes copy untouched for this reason.

🤖 Generated with Claude Code