[AUDIT] Organize burn logs - 39 scattered ad-hoc scripts in /root #7
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Self-Audit Gap: Burn Logs and Scripts Completely Disorganized
Source: Burn Mode Fleet Manual, Section 2.4 ("COMMIT") and 4.5 ("Slice Big Work")
Current State: FAILED - 39 ad-hoc burn_*.py scripts scattered in /root with no organization.
Evidence
Scripts include: burn_820_full.py, burn_820_phase4.py, burn_820_sitrep_post.py, burn_assessment.py, burn_check_subs.py, burn_comments.py, burn_debug_nexus.py, burn_debug_nexus2.py, burn_detail.py, burn_detail_181.py, burn_discover.py, burn_discover2.py, burn_execute.py, burn_fenrir_audit.py, burn_fetch.py, burn_fetch_issues.py, burn_fetch_issues2.py, burn_final_report.py, burn_full_assignee_audit.py, burn_full_assignee_audit2.py, burn_issues.py, burn_mode_detail.py, burn_mode_fetch.py, burn_mode_query.py, burn_mode_sitrep.py, burn_post_implementation.py, burn_post_sitrep.py, burn_queue_audit.py, burn_read_issues.py, burn_sitrep.py, burn_sitrep_181.py, burn_sitrep_comments.py, burn_sitrep_fetch.py, burn_sitrep_fetch2.py, burn_tier3_assign.py, burn_tier3_audit.py, burn_tier3_audit2.py, burn_unassigned_list.py, burn_verify_assignee.py
Problems
Acceptance Criteria
~/.hermes/tools/burn/or similar organized pathPriority: MEDIUM
Technical debt that makes everything else harder. Clean workspace = clear thinking.