ci: configure and stabilize CI/CD pipeline

- fix runner configuration issues
- correct workflow labels and execution environment
- resolve dependency issues in pipeline (python deps)
- improve reliability of automation runs

enterprise-infra-simulator/docs/architecture.md

@@ -0,0 +1,30 @@
+# Enterprise Infrastructure Simulator Architecture
+
+## Components
+
+- Operator interface: `make` targets and direct Ansible commands.
+- Inventory: static host groups in `inventory/hosts.ini`.
+- Automation: lifecycle playbooks in `playbooks/`.
+- Simulation scripts: controlled failure and scaling events in `scripts/`.
+- Evidence: logs, reports, scenario notes, and examples.
+
+## Data Flow
+
+```
+Operator
+  -> Make target or shell script
+  -> Ansible inventory
+  -> lifecycle playbook
+  -> managed Linux node
+  -> log/report artifact
+```
+
+Failure drills follow a parallel flow:
+
+```
+Operator -> simulate_failure.sh -> target node/service -> health check -> patch/hardening playbook -> evidence
+```
+
+## Notes
+
+The project favors explicit playbooks over hidden orchestration so the operational intent is visible during review. In a production implementation, the same workflows would typically run from a CI runner or automation controller with credentials supplied by a secret manager.