reanimator/bee
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases 1 Wiki Activity

app: ship a README.md in every support bundle and blackbox capture

Browse Source 
An agent handed a bundle path had no way to know its layout without
grepping through random logs first — confirmed by watching a separate
session read bee-nvidia.log before anything else on a real bundle. Embeds
a single README.md (bee-embed, internal/app/assets/) explaining what bee
is and giving direct answers to the questions someone analyzing a bundle
is most likely to ask (did the tests pass, what hardware is this, is a
service healthy, RAID/GPU/NVLink state, etc), written at the bundle root
by both BuildSupportBundle (support-bundle archive root, sibling of
manifest.txt) and blackboxWorker.syncCycle (removable-media boot-folder
root, which otherwise has no manifest.txt-equivalent pointing anywhere).

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
This commit is contained in:
Mikhail Chusavitin
2026-07-09 11:37:44 +03:00
co-authored by Claude Sonnet 5
parent cfaa15ec7c
commit 5aee146903
5 changed files with 226 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files
audit/internal/app/blackbox.go
+7
View File
@@ -433,6 +433,13 @@ func (w *blackboxWorker) syncCycle() error {
if err := syncDirectoryTree(w.runtime.exportDir, filepath.Join(root, "export")); err != nil {
return err
}
// Same doc pair the support bundle ships at its root — a blackbox
// capture on removable media has no manifest.txt/support-bundle
// equivalent to explain its layout, so without this an agent handed
// only the media would have nothing pointing it at README.md.
if err := writeBundleDocs(root); err != nil {
return err
}
if err := w.captureSnapshots(root); err != nil {
return err
}