Purpose

This example is a controlled shell scripting lab. It is safe for local execution and uses generated data only.

Documentation

• Deutsch
• English

Files

• bin/file_permissions_umask.sh
• tests/smoke.sh
• data/input.txt
• config/default.env
• scenario.json
• run.sh

Run

./run.sh

The script writes temporary evidence below work/. The directory is ignored by Git.

Review Questions

• 1. How does this example demonstrate chmod, umask, Eigentümermodell und sichere Defaults with safe Bash behavior?
• 2. How does this example demonstrate chmod, umask, Eigentümermodell und sichere Defaults with safe Bash behavior?
• 3. How does this example demonstrate chmod, umask, Eigentümermodell und sichere Defaults with safe Bash behavior?
• 4. How does this example demonstrate chmod, umask, Eigentümermodell und sichere Defaults with safe Bash behavior?
• 5. How does this example demonstrate chmod, umask, Eigentümermodell und sichere Defaults with safe Bash behavior?
• 6. How does this example demonstrate chmod, umask, Eigentümermodell und sichere Defaults with safe Bash behavior?
• 7. How does this example demonstrate chmod, umask, Eigentümermodell und sichere Defaults with safe Bash behavior?
• 8. How does this example demonstrate chmod, umask, Eigentümermodell und sichere Defaults with safe Bash behavior?
• 9. How does this example demonstrate chmod, umask, Eigentümermodell und sichere Defaults with safe Bash behavior?
• 10. How does this example demonstrate chmod, umask, Eigentümermodell und sichere Defaults with safe Bash behavior?
• 11. How does this example demonstrate chmod, umask, Eigentümermodell und sichere Defaults with safe Bash behavior?
• 12. How does this example demonstrate chmod, umask, Eigentümermodell und sichere Defaults with safe Bash behavior?
• 13. How does this example demonstrate chmod, umask, Eigentümermodell und sichere Defaults with safe Bash behavior?
• 14. How does this example demonstrate chmod, umask, Eigentümermodell und sichere Defaults with safe Bash behavior?
• 15. How does this example demonstrate chmod, umask, Eigentümermodell und sichere Defaults with safe Bash behavior?
• 16. How does this example demonstrate chmod, umask, Eigentümermodell und sichere Defaults with safe Bash behavior?
• 17. How does this example demonstrate chmod, umask, Eigentümermodell und sichere Defaults with safe Bash behavior?
• 18. How does this example demonstrate chmod, umask, Eigentümermodell und sichere Defaults with safe Bash behavior?
• 19. How does this example demonstrate chmod, umask, Eigentümermodell und sichere Defaults with safe Bash behavior?
• 20. How does this example demonstrate chmod, umask, Eigentümermodell und sichere Defaults with safe Bash behavior?
• 21. How does this example demonstrate chmod, umask, Eigentümermodell und sichere Defaults with safe Bash behavior?
• 22. How does this example demonstrate chmod, umask, Eigentümermodell und sichere Defaults with safe Bash behavior?
• 23. How does this example demonstrate chmod, umask, Eigentümermodell und sichere Defaults with safe Bash behavior?
• 24. How does this example demonstrate chmod, umask, Eigentümermodell und sichere Defaults with safe Bash behavior?
• 25. How does this example demonstrate chmod, umask, Eigentümermodell und sichere Defaults with safe Bash behavior?
• 26. How does this example demonstrate chmod, umask, Eigentümermodell und sichere Defaults with safe Bash behavior?
• 27. How does this example demonstrate chmod, umask, Eigentümermodell und sichere Defaults with safe Bash behavior?
• 28. How does this example demonstrate chmod, umask, Eigentümermodell und sichere Defaults with safe Bash behavior?
• 29. How does this example demonstrate chmod, umask, Eigentümermodell und sichere Defaults with safe Bash behavior?
• 30. How does this example demonstrate chmod, umask, Eigentümermodell und sichere Defaults with safe Bash behavior?
• 31. How does this example demonstrate chmod, umask, Eigentümermodell und sichere Defaults with safe Bash behavior?
• 32. How does this example demonstrate chmod, umask, Eigentümermodell und sichere Defaults with safe Bash behavior?
• 33. How does this example demonstrate chmod, umask, Eigentümermodell und sichere Defaults with safe Bash behavior?
• 34. How does this example demonstrate chmod, umask, Eigentümermodell und sichere Defaults with safe Bash behavior?
• 35. How does this example demonstrate chmod, umask, Eigentümermodell und sichere Defaults with safe Bash behavior?
• 36. How does this example demonstrate chmod, umask, Eigentümermodell und sichere Defaults with safe Bash behavior?
• 37. How does this example demonstrate chmod, umask, Eigentümermodell und sichere Defaults with safe Bash behavior?
• 38. How does this example demonstrate chmod, umask, Eigentümermodell und sichere Defaults with safe Bash behavior?
• 39. How does this example demonstrate chmod, umask, Eigentümermodell und sichere Defaults with safe Bash behavior?
• 40. How does this example demonstrate chmod, umask, Eigentümermodell und sichere Defaults with safe Bash behavior?
• 41. How does this example demonstrate chmod, umask, Eigentümermodell und sichere Defaults with safe Bash behavior?
• 42. How does this example demonstrate chmod, umask, Eigentümermodell und sichere Defaults with safe Bash behavior?
• 43. How does this example demonstrate chmod, umask, Eigentümermodell und sichere Defaults with safe Bash behavior?
• 44. How does this example demonstrate chmod, umask, Eigentümermodell und sichere Defaults with safe Bash behavior?

Practice Appendix: Example File Permissions Umask

This appendix is a working backlog for longer trainings, reviews and repetitions. Each task can be checked locally with Bash, test data and a Git repository.

A001. chmod, umask, Eigentümermodell und sichere Defaults

• Task: validate input and connect the observation explicitly to chmod, umask, Eigentümermodell und sichere Defaults.
• Evidence: Record the checked command, expected output, actual output and exit code.
• Operations question: What happens with empty input, missing files, missing tools and repeated execution?
• Security question: Can input become an option, path, glob, subshell, eval expression or secret leak?
• Recovery: Describe revert, cleanup, restore, secret rotation or manual correction.

A002. Bash

• Task: explain exit code and connect the observation explicitly to Bash.
• Evidence: Record the checked command, expected output, actual output and exit code.
• Operations question: What happens with empty input, missing files, missing tools and repeated execution?
• Security question: Can input become an option, path, glob, subshell, eval expression or secret leak?
• Recovery: Describe revert, cleanup, restore, secret rotation or manual correction.

A003. Testing

• Task: check quoting and connect the observation explicitly to Testing.
• Evidence: Record the checked command, expected output, actual output and exit code.
• Operations question: What happens with empty input, missing files, missing tools and repeated execution?
• Security question: Can input become an option, path, glob, subshell, eval expression or secret leak?
• Recovery: Describe revert, cleanup, restore, secret rotation or manual correction.

A004. Security

• Task: test error path and connect the observation explicitly to Security.
• Evidence: Record the checked command, expected output, actual output and exit code.
• Operations question: What happens with empty input, missing files, missing tools and repeated execution?
• Security question: Can input become an option, path, glob, subshell, eval expression or secret leak?
• Recovery: Describe revert, cleanup, restore, secret rotation or manual correction.

A005. chmod, umask, Eigentümermodell und sichere Defaults

• Task: review log output and connect the observation explicitly to chmod, umask, Eigentümermodell und sichere Defaults.
• Evidence: Record the checked command, expected output, actual output and exit code.
• Operations question: What happens with empty input, missing files, missing tools and repeated execution?
• Security question: Can input become an option, path, glob, subshell, eval expression or secret leak?
• Recovery: Describe revert, cleanup, restore, secret rotation or manual correction.

A006. Bash

• Task: trace cleanup and connect the observation explicitly to Bash.
• Evidence: Record the checked command, expected output, actual output and exit code.
• Operations question: What happens with empty input, missing files, missing tools and repeated execution?
• Security question: Can input become an option, path, glob, subshell, eval expression or secret leak?
• Recovery: Describe revert, cleanup, restore, secret rotation or manual correction.

A007. Testing

• Task: scope portability and connect the observation explicitly to Testing.
• Evidence: Record the checked command, expected output, actual output and exit code.
• Operations question: What happens with empty input, missing files, missing tools and repeated execution?
• Security question: Can input become an option, path, glob, subshell, eval expression or secret leak?
• Recovery: Describe revert, cleanup, restore, secret rotation or manual correction.

A008. Security

• Task: mark security risk and connect the observation explicitly to Security.
• Evidence: Record the checked command, expected output, actual output and exit code.
• Operations question: What happens with empty input, missing files, missing tools and repeated execution?
• Security question: Can input become an option, path, glob, subshell, eval expression or secret leak?
• Recovery: Describe revert, cleanup, restore, secret rotation or manual correction.

A009. chmod, umask, Eigentümermodell und sichere Defaults

• Task: document recovery path and connect the observation explicitly to chmod, umask, Eigentümermodell und sichere Defaults.
• Evidence: Record the checked command, expected output, actual output and exit code.
• Operations question: What happens with empty input, missing files, missing tools and repeated execution?
• Security question: Can input become an option, path, glob, subshell, eval expression or secret leak?
• Recovery: Describe revert, cleanup, restore, secret rotation or manual correction.

A010. Bash

• Task: write review rule and connect the observation explicitly to Bash.
• Evidence: Record the checked command, expected output, actual output and exit code.
• Operations question: What happens with empty input, missing files, missing tools and repeated execution?
• Security question: Can input become an option, path, glob, subshell, eval expression or secret leak?
• Recovery: Describe revert, cleanup, restore, secret rotation or manual correction.

A011. Testing

• Task: validate input and connect the observation explicitly to Testing.
• Evidence: Record the checked command, expected output, actual output and exit code.
• Operations question: What happens with empty input, missing files, missing tools and repeated execution?
• Security question: Can input become an option, path, glob, subshell, eval expression or secret leak?
• Recovery: Describe revert, cleanup, restore, secret rotation or manual correction.

A012. Security

• Task: explain exit code and connect the observation explicitly to Security.
• Evidence: Record the checked command, expected output, actual output and exit code.
• Operations question: What happens with empty input, missing files, missing tools and repeated execution?
• Security question: Can input become an option, path, glob, subshell, eval expression or secret leak?
• Recovery: Describe revert, cleanup, restore, secret rotation or manual correction.

A013. chmod, umask, Eigentümermodell und sichere Defaults

• Task: check quoting and connect the observation explicitly to chmod, umask, Eigentümermodell und sichere Defaults.
• Evidence: Record the checked command, expected output, actual output and exit code.
• Operations question: What happens with empty input, missing files, missing tools and repeated execution?
• Security question: Can input become an option, path, glob, subshell, eval expression or secret leak?
• Recovery: Describe revert, cleanup, restore, secret rotation or manual correction.

A014. Bash

• Task: test error path and connect the observation explicitly to Bash.
• Evidence: Record the checked command, expected output, actual output and exit code.
• Operations question: What happens with empty input, missing files, missing tools and repeated execution?
• Security question: Can input become an option, path, glob, subshell, eval expression or secret leak?
• Recovery: Describe revert, cleanup, restore, secret rotation or manual correction.

A015. Testing

• Task: review log output and connect the observation explicitly to Testing.
• Evidence: Record the checked command, expected output, actual output and exit code.
• Operations question: What happens with empty input, missing files, missing tools and repeated execution?
• Security question: Can input become an option, path, glob, subshell, eval expression or secret leak?
• Recovery: Describe revert, cleanup, restore, secret rotation or manual correction.

A016. Security

• Task: trace cleanup and connect the observation explicitly to Security.
• Evidence: Record the checked command, expected output, actual output and exit code.
• Operations question: What happens with empty input, missing files, missing tools and repeated execution?
• Security question: Can input become an option, path, glob, subshell, eval expression or secret leak?
• Recovery: Describe revert, cleanup, restore, secret rotation or manual correction.

A017. chmod, umask, Eigentümermodell und sichere Defaults

• Task: scope portability and connect the observation explicitly to chmod, umask, Eigentümermodell und sichere Defaults.
• Evidence: Record the checked command, expected output, actual output and exit code.
• Operations question: What happens with empty input, missing files, missing tools and repeated execution?
• Security question: Can input become an option, path, glob, subshell, eval expression or secret leak?
• Recovery: Describe revert, cleanup, restore, secret rotation or manual correction.

A018. Bash

• Task: mark security risk and connect the observation explicitly to Bash.
• Evidence: Record the checked command, expected output, actual output and exit code.
• Operations question: What happens with empty input, missing files, missing tools and repeated execution?
• Security question: Can input become an option, path, glob, subshell, eval expression or secret leak?
• Recovery: Describe revert, cleanup, restore, secret rotation or manual correction.

A019. Testing

• Task: document recovery path and connect the observation explicitly to Testing.
• Evidence: Record the checked command, expected output, actual output and exit code.
• Operations question: What happens with empty input, missing files, missing tools and repeated execution?
• Security question: Can input become an option, path, glob, subshell, eval expression or secret leak?
• Recovery: Describe revert, cleanup, restore, secret rotation or manual correction.

A020. Security

• Task: write review rule and connect the observation explicitly to Security.
• Evidence: Record the checked command, expected output, actual output and exit code.
• Operations question: What happens with empty input, missing files, missing tools and repeated execution?
• Security question: Can input become an option, path, glob, subshell, eval expression or secret leak?
• Recovery: Describe revert, cleanup, restore, secret rotation or manual correction.

A021. chmod, umask, Eigentümermodell und sichere Defaults

• Task: validate input and connect the observation explicitly to chmod, umask, Eigentümermodell und sichere Defaults.
• Evidence: Record the checked command, expected output, actual output and exit code.
• Operations question: What happens with empty input, missing files, missing tools and repeated execution?
• Security question: Can input become an option, path, glob, subshell, eval expression or secret leak?
• Recovery: Describe revert, cleanup, restore, secret rotation or manual correction.

A022. Bash

• Task: explain exit code and connect the observation explicitly to Bash.
• Evidence: Record the checked command, expected output, actual output and exit code.
• Operations question: What happens with empty input, missing files, missing tools and repeated execution?
• Security question: Can input become an option, path, glob, subshell, eval expression or secret leak?
• Recovery: Describe revert, cleanup, restore, secret rotation or manual correction.

A023. Testing

• Task: check quoting and connect the observation explicitly to Testing.
• Evidence: Record the checked command, expected output, actual output and exit code.
• Operations question: What happens with empty input, missing files, missing tools and repeated execution?
• Security question: Can input become an option, path, glob, subshell, eval expression or secret leak?
• Recovery: Describe revert, cleanup, restore, secret rotation or manual correction.

A024. Security

• Task: test error path and connect the observation explicitly to Security.
• Evidence: Record the checked command, expected output, actual output and exit code.
• Operations question: What happens with empty input, missing files, missing tools and repeated execution?
• Security question: Can input become an option, path, glob, subshell, eval expression or secret leak?
• Recovery: Describe revert, cleanup, restore, secret rotation or manual correction.

A025. chmod, umask, Eigentümermodell und sichere Defaults

• Task: review log output and connect the observation explicitly to chmod, umask, Eigentümermodell und sichere Defaults.
• Evidence: Record the checked command, expected output, actual output and exit code.
• Operations question: What happens with empty input, missing files, missing tools and repeated execution?
• Security question: Can input become an option, path, glob, subshell, eval expression or secret leak?
• Recovery: Describe revert, cleanup, restore, secret rotation or manual correction.

A026. Bash

• Task: trace cleanup and connect the observation explicitly to Bash.
• Evidence: Record the checked command, expected output, actual output and exit code.
• Operations question: What happens with empty input, missing files, missing tools and repeated execution?
• Security question: Can input become an option, path, glob, subshell, eval expression or secret leak?
• Recovery: Describe revert, cleanup, restore, secret rotation or manual correction.

A027. Testing

• Task: scope portability and connect the observation explicitly to Testing.
• Evidence: Record the checked command, expected output, actual output and exit code.
• Operations question: What happens with empty input, missing files, missing tools and repeated execution?
• Security question: Can input become an option, path, glob, subshell, eval expression or secret leak?
• Recovery: Describe revert, cleanup, restore, secret rotation or manual correction.

A028. Security

• Task: mark security risk and connect the observation explicitly to Security.
• Evidence: Record the checked command, expected output, actual output and exit code.
• Operations question: What happens with empty input, missing files, missing tools and repeated execution?
• Security question: Can input become an option, path, glob, subshell, eval expression or secret leak?
• Recovery: Describe revert, cleanup, restore, secret rotation or manual correction.

A029. chmod, umask, Eigentümermodell und sichere Defaults

• Task: document recovery path and connect the observation explicitly to chmod, umask, Eigentümermodell und sichere Defaults.
• Evidence: Record the checked command, expected output, actual output and exit code.
• Operations question: What happens with empty input, missing files, missing tools and repeated execution?
• Security question: Can input become an option, path, glob, subshell, eval expression or secret leak?
• Recovery: Describe revert, cleanup, restore, secret rotation or manual correction.

A030. Bash

• Task: write review rule and connect the observation explicitly to Bash.
• Evidence: Record the checked command, expected output, actual output and exit code.
• Operations question: What happens with empty input, missing files, missing tools and repeated execution?
• Security question: Can input become an option, path, glob, subshell, eval expression or secret leak?
• Recovery: Describe revert, cleanup, restore, secret rotation or manual correction.

A031. Testing

• Task: validate input and connect the observation explicitly to Testing.
• Evidence: Record the checked command, expected output, actual output and exit code.
• Operations question: What happens with empty input, missing files, missing tools and repeated execution?
• Security question: Can input become an option, path, glob, subshell, eval expression or secret leak?
• Recovery: Describe revert, cleanup, restore, secret rotation or manual correction.

A032. Security

• Task: explain exit code and connect the observation explicitly to Security.
• Evidence: Record the checked command, expected output, actual output and exit code.
• Operations question: What happens with empty input, missing files, missing tools and repeated execution?
• Security question: Can input become an option, path, glob, subshell, eval expression or secret leak?
• Recovery: Describe revert, cleanup, restore, secret rotation or manual correction.

A033. chmod, umask, Eigentümermodell und sichere Defaults

• Task: check quoting and connect the observation explicitly to chmod, umask, Eigentümermodell und sichere Defaults.
• Evidence: Record the checked command, expected output, actual output and exit code.
• Operations question: What happens with empty input, missing files, missing tools and repeated execution?
• Security question: Can input become an option, path, glob, subshell, eval expression or secret leak?
• Recovery: Describe revert, cleanup, restore, secret rotation or manual correction.

A034. Bash

• Task: test error path and connect the observation explicitly to Bash.
• Evidence: Record the checked command, expected output, actual output and exit code.
• Operations question: What happens with empty input, missing files, missing tools and repeated execution?
• Security question: Can input become an option, path, glob, subshell, eval expression or secret leak?
• Recovery: Describe revert, cleanup, restore, secret rotation or manual correction.

A035. Testing

• Task: review log output and connect the observation explicitly to Testing.
• Evidence: Record the checked command, expected output, actual output and exit code.
• Operations question: What happens with empty input, missing files, missing tools and repeated execution?
• Security question: Can input become an option, path, glob, subshell, eval expression or secret leak?
• Recovery: Describe revert, cleanup, restore, secret rotation or manual correction.

A036. Security

• Task: trace cleanup and connect the observation explicitly to Security.
• Evidence: Record the checked command, expected output, actual output and exit code.
• Operations question: What happens with empty input, missing files, missing tools and repeated execution?
• Security question: Can input become an option, path, glob, subshell, eval expression or secret leak?
• Recovery: Describe revert, cleanup, restore, secret rotation or manual correction.

A037. chmod, umask, Eigentümermodell und sichere Defaults

• Task: scope portability and connect the observation explicitly to chmod, umask, Eigentümermodell und sichere Defaults.
• Evidence: Record the checked command, expected output, actual output and exit code.
• Operations question: What happens with empty input, missing files, missing tools and repeated execution?
• Security question: Can input become an option, path, glob, subshell, eval expression or secret leak?
• Recovery: Describe revert, cleanup, restore, secret rotation or manual correction.

A038. Bash

• Task: mark security risk and connect the observation explicitly to Bash.
• Evidence: Record the checked command, expected output, actual output and exit code.
• Operations question: What happens with empty input, missing files, missing tools and repeated execution?
• Security question: Can input become an option, path, glob, subshell, eval expression or secret leak?
• Recovery: Describe revert, cleanup, restore, secret rotation or manual correction.

A039. Testing

• Task: document recovery path and connect the observation explicitly to Testing.
• Evidence: Record the checked command, expected output, actual output and exit code.
• Operations question: What happens with empty input, missing files, missing tools and repeated execution?
• Security question: Can input become an option, path, glob, subshell, eval expression or secret leak?
• Recovery: Describe revert, cleanup, restore, secret rotation or manual correction.

A040. Security

• Task: write review rule and connect the observation explicitly to Security.
• Evidence: Record the checked command, expected output, actual output and exit code.
• Operations question: What happens with empty input, missing files, missing tools and repeated execution?
• Security question: Can input become an option, path, glob, subshell, eval expression or secret leak?
• Recovery: Describe revert, cleanup, restore, secret rotation or manual correction.

A041. chmod, umask, Eigentümermodell und sichere Defaults

• Task: validate input and connect the observation explicitly to chmod, umask, Eigentümermodell und sichere Defaults.
• Evidence: Record the checked command, expected output, actual output and exit code.
• Operations question: What happens with empty input, missing files, missing tools and repeated execution?
• Security question: Can input become an option, path, glob, subshell, eval expression or secret leak?
• Recovery: Describe revert, cleanup, restore, secret rotation or manual correction.

A042. Bash

• Task: explain exit code and connect the observation explicitly to Bash.
• Evidence: Record the checked command, expected output, actual output and exit code.
• Operations question: What happens with empty input, missing files, missing tools and repeated execution?
• Security question: Can input become an option, path, glob, subshell, eval expression or secret leak?
• Recovery: Describe revert, cleanup, restore, secret rotation or manual correction.

A043. Testing

• Task: check quoting and connect the observation explicitly to Testing.
• Evidence: Record the checked command, expected output, actual output and exit code.
• Operations question: What happens with empty input, missing files, missing tools and repeated execution?
• Security question: Can input become an option, path, glob, subshell, eval expression or secret leak?
• Recovery: Describe revert, cleanup, restore, secret rotation or manual correction.

A044. Security

• Task: test error path and connect the observation explicitly to Security.
• Evidence: Record the checked command, expected output, actual output and exit code.
• Operations question: What happens with empty input, missing files, missing tools and repeated execution?
• Security question: Can input become an option, path, glob, subshell, eval expression or secret leak?
• Recovery: Describe revert, cleanup, restore, secret rotation or manual correction.

A045. chmod, umask, Eigentümermodell und sichere Defaults

• Task: review log output and connect the observation explicitly to chmod, umask, Eigentümermodell und sichere Defaults.
• Evidence: Record the checked command, expected output, actual output and exit code.
• Operations question: What happens with empty input, missing files, missing tools and repeated execution?
• Security question: Can input become an option, path, glob, subshell, eval expression or secret leak?
• Recovery: Describe revert, cleanup, restore, secret rotation or manual correction.

A046. Bash

• Task: trace cleanup and connect the observation explicitly to Bash.
• Evidence: Record the checked command, expected output, actual output and exit code.
• Operations question: What happens with empty input, missing files, missing tools and repeated execution?
• Security question: Can input become an option, path, glob, subshell, eval expression or secret leak?
• Recovery: Describe revert, cleanup, restore, secret rotation or manual correction.

A047. Testing

• Task: scope portability and connect the observation explicitly to Testing.
• Evidence: Record the checked command, expected output, actual output and exit code.
• Operations question: What happens with empty input, missing files, missing tools and repeated execution?
• Security question: Can input become an option, path, glob, subshell, eval expression or secret leak?
• Recovery: Describe revert, cleanup, restore, secret rotation or manual correction.

A048. Security

• Task: mark security risk and connect the observation explicitly to Security.
• Evidence: Record the checked command, expected output, actual output and exit code.
• Operations question: What happens with empty input, missing files, missing tools and repeated execution?
• Security question: Can input become an option, path, glob, subshell, eval expression or secret leak?
• Recovery: Describe revert, cleanup, restore, secret rotation or manual correction.

A049. chmod, umask, Eigentümermodell und sichere Defaults

• Task: document recovery path and connect the observation explicitly to chmod, umask, Eigentümermodell und sichere Defaults.
• Evidence: Record the checked command, expected output, actual output and exit code.
• Operations question: What happens with empty input, missing files, missing tools and repeated execution?
• Security question: Can input become an option, path, glob, subshell, eval expression or secret leak?
• Recovery: Describe revert, cleanup, restore, secret rotation or manual correction.

A050. Bash

• Task: write review rule and connect the observation explicitly to Bash.
• Evidence: Record the checked command, expected output, actual output and exit code.
• Operations question: What happens with empty input, missing files, missing tools and repeated execution?
• Security question: Can input become an option, path, glob, subshell, eval expression or secret leak?
• Recovery: Describe revert, cleanup, restore, secret rotation or manual correction.