This repository holds customer-run support tooling: scripts and small programs that operators use on Linux VMs to gather diagnostics or apply narrow, documented workarounds. Tools are meant to work on partially broken hosts, with minimal assumptions about network, GPU, containers, or privilege.
| Area | Purpose |
|---|---|
customers/ |
Packaged tools distributed with support (Go binaries, dashboards, assets). |
docs/ |
Planning notes and indexes; authoritative behavior is always the code plus per-project AGENTS.md. |
Root .sh scripts |
Focused one-off utilities (when present). |
-
customers/vm-troubleshooting/—gather-info: static Go binary that collects VM diagnostics into a single.tar.gzwith manifest, report stream, and summaries.- Quick map:
customers/vm-troubleshooting/CODEMAP.md - Extended reference:
customers/vm-troubleshooting/ARCHITECTURE.md
- Quick map:
-
customers/vm-troubleshooting-dashboard/— Local web app (Go API + SQLite + React) to ingest and browsegather-infoarchives.
- Repo-wide policy, monorepo discovery, and root-only verification (e.g. root shell scripts):
AGENTS.md - Per-project build/test commands and stack rules: that project's
AGENTS.md(collector) orAGENTS.md(dashboard).
Workstreams and follow-up hardening are described under docs/plans/. Those documents are specifications and history: always confirm behavior in the current tree and tests (for example docs/plans/post-audit-hardening.md outlines post-audit dashboard and collector hardening goals).
Use the AGENTS.md inside the project you are changing (collector or dashboard) for exact commands. The repo root AGENTS.md only lists checks for root-level assets (e.g. specific shell scripts).