Mike Swanson
0c000109dc
Compressed memory store 104 -> 71 files via four passes: - Syncro: 19 scattered feedback_syncro_* files merged into 3 rule files (api/billing/workflow) + an on-demand feedback_syncro_history.md for incident detail, quotes, and tech/product ID tables. - Four near-duplicate merges: Howard paste-safety, Pluto build server, Howard backend deferral, IX server access (ssh+tailscale). - Per-cluster rule/state/history split applied to GuruConnect (2->1), Dataforth (3->2), Cascades (7->3), GuruRMM (13->3). - New reference_resource_map.md: single auto-loaded cheatsheet for "do I have access to X and how do I connect from this machine?" - MEMORY.md rewritten to match the new layout. Health: broken backlinks 8->7, overlap clusters 12->5, orphans 17->0.
995 B
995 B
name, description, metadata
| name | description | metadata | ||
|---|---|---|---|---|
| feedback_autonomous_infra_setup | During build/CI/infra/dev-tooling setup, just install prerequisites and push through routine steps autonomously; don't pause to ask before each one |
|
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_gururmm (the #bot-alerts internal-vs-client rule lives there).