Make HAS_ALLOW_UNSAFE case insensitive (closes #35)

[chiliec]

What

Closes #35.

HAS_ALLOW_UNSAFE was only honored when set to the exact lowercase y, so common truthy spellings (Y, yes, YES) were silently ignored and the dynamic/unsafe check never ran. This matches the maintainer's +1 for case-insensitivity in the issue thread.

Fix

The guard now accepts y/Y and yes (any case) via glob patterns in [[ ]]:

if [[ "${HAS_ALLOW_UNSAFE}" == [Yy] || "${HAS_ALLOW_UNSAFE}" == [Yy][Ee][Ss] ]]; then

Glob patterns keep this bash 3.2-safe (macOS) — no ${var,,}. No breaking change: HAS_ALLOW_UNSAFE=N/empty/anything else still disables the unsafe path exactly as before.

Tests

Added a unit test asserting Y, yes, Yes, YES all enable the unsafe path (output no longer contains foobar not understood).

Validation

$ bats tests/unit/unit-tests.bats
ok 5 env var 'HAS_ALLOW_UNSAFE' is case insensitive
...
$ shellcheck has   # clean, exit 0

Verified genuine RED→GREEN: reverting only the source guard back to == "y" turns the new test red (foobar not understood reappears for Y/yes/…); restoring the fix makes it green.

Note: two tests (testing coreutils commands, status code in quiet mode still equal to number of failed commands) fail on a clean master checkout on my machine too — they are pre-existing and outside this diff (which touches only the HAS_ALLOW_UNSAFE guard + one new test).

Happy to adjust (e.g. narrow to just [Yy] if you'd rather not accept yes).

[kdabir]

Thanks for the contribution