fix: show actual token in Helm NOTES.txt when single static token configured

* fix: filter kubernetes-only edges in MCP handler; add claude setup hints to mcp url

- mcp_builder.go: skip server-type edges when resolving MCP targets —
  server-type edges have no Kubernetes API, only SSH; including them
  in the MCP provider would fail or return empty toolsets
- mcp.go: after printing the MCP URL, print ready-to-use 'claude mcp add'
  command and Claude Desktop JSON snippet (includes bearer token from
  the active kubeconfig context when available)

Co-authored-by: Mangirdas Judeikis <mangirdas@judeikis.lt>

* fix: rename MCP target parameter from 'edge' to 'cluster'

'edge' is kedge-internal terminology. Users think in terms of clusters.
Renaming the query parameter to 'cluster' makes the MCP target selection
more intuitive for the broader community.

Co-authored-by: Mangirdas Judeikis <mangirdas@judeikis.lt>

* docs: document MCP integration in README, CONTRIBUTING, and DEVELOPERS

- README: add MCP to Features list, Quickstart section with example output,
  CLI reference entries for kedge mcp url
- CONTRIBUTING: add mcp packages to key packages table
- DEVELOPERS: add full MCP Integration section covering KubernetesMCP CRD,
  URL structure, request flow diagram, toolsets, target parameter, and
  per-edge MCP URL; update table of contents
- docs/developers.md: add MCP section for GitHub Pages site

Co-authored-by: Mangirdas Judeikis <mangirdas@judeikis.lt>

* fix: update e2e tests to use 'cluster' parameter name for MCP tools/call

GetTargetParameterName() was renamed from 'edge' to 'cluster' but the
e2e test was still passing "edge": edgeName as the tools/call argument,
causing 'upstream unavailable' because the MCP server couldn't resolve
the target.

Co-authored-by: Mangirdas Judeikis <mangirdas@judeikis.lt>

* docs: update MCP docs to use Kubernetes kind instead of KubernetesMCP

Follows the rename in #138: KubernetesMCP → Kubernetes, kubernetesmcps → kubernetes.
Update all URL examples, CRD references, and descriptions across README,
CONTRIBUTING, DEVELOPERS, and docs/developers.

Co-authored-by: Mangirdas Judeikis <mangirdas@judeikis.lt>

* fix: show actual token in helm NOTES.txt when single static token configured

When exactly one static token is configured, the post-install message
now shows the real token value so the user can copy-paste the login
command directly.  With multiple tokens the placeholder remains.

Co-authored-by: Mangirdas Judeikis <mangirdas@judeikis.lt>

---------

Co-authored-by: mjudeikis-bot <ai@faros.sh>
Co-authored-by: Mangirdas Judeikis <mangirdas@judeikis.lt>

Author: 3 people

deploy/charts/kedge-hub/templates/NOTES.txt

@@ -19,7 +19,11 @@ To access the hub locally:
 {{- if .Values.hub.staticAuthTokens }}
 
 Login (static token):
+{{- if eq (len .Values.hub.staticAuthTokens) 1 }}
+  kedge login --hub-url {{ .Values.hub.hubExternalURL | default "https://<hub-external-url>" }} --token {{ .Values.hub.staticAuthTokens | first }} {{ if or .Values.hub.tls.selfSigned.enabled .Values.hub.devMode }}--insecure-skip-tls-verify{{ end }}
+{{- else }}
   kedge login --hub-url {{ .Values.hub.hubExternalURL | default "https://<hub-external-url>" }} --token <your-static-token> {{ if or .Values.hub.tls.selfSigned.enabled .Values.hub.devMode }}--insecure-skip-tls-verify{{ end }}
+{{- end }}
 
   {{ len .Values.hub.staticAuthTokens }} static token(s) configured.