[0.9.1] Kubernetes discovery — manual release-validation hand tests

[tnaum-ms]

Summary

Several Kubernetes service discovery behaviors in #621 are timing-, platform-, or packaging-sensitive and were verified by unit tests but not confirmed by hand. This issue tracks the manual release-validation pass for the 0.9.1 patch. None of these are code changes — they are sign-off checks. If any fails, file a separate bug.

Source: PR #621 pre-merge review (docs/ai-and-plans/PRs/621-kubernetes-discovery/pre-merge-code-review.md, findings 2.6 and 2.9) plus the live-verification checklist in docs/ai-and-plans/PRs/621-kubernetes-discovery/bugbash-090-kubernetes-ux-review.md (§8.5).

Checklist

Packaging / native deps (review finding 2.6)

• Install the packaged VSIX on a clean machine (not the dev workspace) and open a ClusterIP port-forward tunnel end to end. bufferutil / utf-8-validate are externalized (not bundled); ws treats them as optional and should degrade gracefully, but a require() of a missing external would throw if ws ever hard-requires them. Confirm the tunnel works without those native modules present.

Open Interactive Shell on ClusterIP (review finding 2.9)

• Expand a ClusterIP target so the tunnel is up, then Open Interactive Shell against it and confirm it connects (or is gracefully guarded) rather than being handed an opaque 127.0.0.1 with no tunnel. The §9.4 change removed the menu exclusion and relies on expand-to-connect establishing the tunnel first; this path was never verified live.

Timing- / platform-sensitive behaviors (UX review §8.5)

• Reveal-on-add expands and selects the new source from a cold cache (#22).
• Drag-and-drop: valid kubeconfig, non-kubeconfig file, directory, duplicate, and a mixed batch (#26).
• Windows display of %USERPROFILE%\.kube\config renders correctly in the tree description, tooltip, and the file dialog (#23/#24).
• Reload window while a ClusterIP tunnel is active, then reconnect — confirm the tunnel re-establishes (the #30 defensive EADDRINUSE/cancellation hardening; no confirmed repro, so verify deliberately).
• Modal error fires once for a broken source (rename ~/.kube/config away): the notification is modal, "Remove this kubeconfig source" is absent from the in-tree recovery list (it lives in the context menu), the first recovery child reads "Click here to retry", and hitting Refresh repeatedly does not re-fire the modal (only expand / explicit retry does) (#2/#19/#25).

Acceptance criteria

• Every box above is exercised and ticked, or a follow-up bug is filed for any failure.
• Packaging (2.6) is validated specifically against a built VSIX on a clean environment, not F5/dev host.

References

• PR feat(kubernetes): add multi-source service discovery #621 — feat(kubernetes): add multi-source service discovery
• Pre-merge review: docs/ai-and-plans/PRs/621-kubernetes-discovery/pre-merge-code-review.md (2.6, 2.9)
• UX review: docs/ai-and-plans/PRs/621-kubernetes-discovery/bugbash-090-kubernetes-ux-review.md (§8.5)