Clean up Python log analysis documentation

infra-run/scripts/README.md

@@ -1,6 +1,6 @@
 # infra-run/scripts
 
-This directory groups executable tooling used across the `infra-run` project. It separates shell-first operational scripts from future Python-based utilities while keeping both under one automation entry point.
+This directory groups executable tooling used across the `infra-run` project. It separates shell-first operational scripts from Python-based analysis utilities while keeping both under one automation entry point.
 
 ## Diagram
 
@@ -9,16 +9,17 @@ flowchart TD
   A["scripts"] --> B["bash"]
   A --> C["python"]
   B --> D["Operational toolkits"]
-  C --> E["Future helper utilities"]
+  C --> E["Analysis helper utilities"]
 ```
 
 ## Scope
 
-- `bash` - current implementation area with operations toolkits.
-- `python` - reserved space for future supporting utilities.
+- [bash](./bash/) - operational toolkits for host health checks, disk-full triage, Veritas examples, and GPFS examples.
+- [python](./python/) - read-only tools for local log parsing, reporting, and structured operational analysis.
 
 ## Notes
 
-- The repository currently emphasizes Bash because it maps directly to day-to-day Linux operations.
-- The structure leaves room for higher-level helpers without mixing concerns.
+- Bash remains the right default for direct host checks and operational wrappers.
+- Python is used where parsing, report generation, comparison, or JSON output is clearer than shell.
 - Bash tooling should remain safe by default, readable, and validated with `../../scripts/check-bash.sh` from the repository root.
+- Python tooling should remain read-only by default, standard-library based, and validated with `../../scripts/check-python.sh` from the repository root.