docs: record Claude-Builder=PLUTO mapping + infra working-feedback memories

- Pluto memory/wiki/machine notes: Unraid VM "Claude-Builder" == hostname PLUTO ==
  172.16.3.36 (same box); RMM-agent access path when SSH key unauthorized; now also
  builds the GuruConnect Windows agent + hosts a Gitea Actions runner.
- New feedback memories: post #bot-alerts only for client/ticket-affecting RMM commands;
  proceed autonomously through routine infra/build prerequisites.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

.claude/memory/feedback_autonomous_infra_setup.md

@@ -0,0 +1,17 @@
+---
+name: feedback_autonomous_infra_setup
+description: During build/CI/infra/dev-tooling setup, just install prerequisites and push through routine steps autonomously; don't pause to ask before each one
+metadata:
+  type: feedback
+---
+
+For infrastructure / build / CI / dev-tooling setup, Mike wants forward momentum. **Don't stop to
+ask before routine prerequisite steps** — e.g. installing Node.js on a build VM, adding tools to
+PATH, installing a toolchain, registering a runner. Just do them and report.
+
+**Reserve check-ins for genuine decisions:** architecture forks, destructive or
+outward-facing/irreversible actions, ambiguous requirements, or anything touching client/production
+state. Routine "X needs to be installed" is not a decision — install it.
+
+Stated 2026-05-29 during the PLUTO Gitea-Actions-runner setup (re: installing Node for host-mode JS
+actions). Related: [[reference_pluto_build_server]], [[feedback_no_botalerts_internal_rmm]].