reviewed_divergences:
- side: shuck-only
path_contains: "Bash-it__bash-it__"
reason: "C124 intentionally treats code after guarded exits as unreachable when one branch exits but the other branch still falls through to later statements. The remaining corpus cases are all that same fallthrough shape in helper scripts, package hooks, and project-closure code, and ShellCheck does not emit SC2365 for them, so these repo-family hits remain a stricter Shuck policy without hiding a distinct implementation bug."
- side: shuck-only
path_contains: "CISOfy__lynis__"
reason: "C124 intentionally treats code after guarded exits as unreachable when one branch exits but the other branch still falls through to later statements. The remaining corpus cases are all that same fallthrough shape in helper scripts, package hooks, and project-closure code, and ShellCheck does not emit SC2365 for them, so these repo-family hits remain a stricter Shuck policy without hiding a distinct implementation bug."
- side: shuck-only
path_contains: "HariSekhon__DevOps-Bash-tools__"
reason: "C124 intentionally treats code after guarded exits as unreachable when one branch exits but the other branch still falls through to later statements. The remaining corpus cases are all that same fallthrough shape in helper scripts, package hooks, and project-closure code, and ShellCheck does not emit SC2365 for them, so these repo-family hits remain a stricter Shuck policy without hiding a distinct implementation bug."
- side: shuck-only
path_contains: "SlackBuildsOrg__slackbuilds__"
reason: "C124 intentionally treats code after guarded exits as unreachable when one branch exits but the other branch still falls through to later statements. The remaining corpus cases are all that same fallthrough shape in helper scripts, package hooks, and project-closure code, and ShellCheck does not emit SC2365 for them, so these repo-family hits remain a stricter Shuck policy without hiding a distinct implementation bug."
- side: shuck-only
path_contains: "acmesh-official__acme.sh__"
reason: "C124 intentionally treats code after guarded exits as unreachable when one branch exits but the other branch still falls through to later statements. The remaining corpus cases are all that same fallthrough shape in helper scripts, package hooks, and project-closure code, and ShellCheck does not emit SC2365 for them, so these repo-family hits remain a stricter Shuck policy without hiding a distinct implementation bug."
- side: shuck-only
path_contains: "alexanderepstein__Bash-Snippets__"
reason: "C124 intentionally treats code after guarded exits as unreachable when one branch exits but the other branch still falls through to later statements. The remaining corpus cases are all that same fallthrough shape in helper scripts, package hooks, and project-closure code, and ShellCheck does not emit SC2365 for them, so these repo-family hits remain a stricter Shuck policy without hiding a distinct implementation bug."
- side: shuck-only
path_contains: "aristocratos__bashtop__"
reason: "C124 intentionally treats code after guarded exits as unreachable when one branch exits but the other branch still falls through to later statements. The remaining corpus cases are all that same fallthrough shape in helper scripts, package hooks, and project-closure code, and ShellCheck does not emit SC2365 for them, so these repo-family hits remain a stricter Shuck policy without hiding a distinct implementation bug."
- side: shuck-only
path_contains: "awslabs__git-secrets__"
reason: "C124 intentionally treats code after guarded exits as unreachable when one branch exits but the other branch still falls through to later statements. The remaining corpus cases are all that same fallthrough shape in helper scripts, package hooks, and project-closure code, and ShellCheck does not emit SC2365 for them, so these repo-family hits remain a stricter Shuck policy without hiding a distinct implementation bug."
- side: shuck-only
path_contains: "bats-core__bats-core__"
reason: "C124 intentionally treats code after guarded exits as unreachable when one branch exits but the other branch still falls through to later statements. The remaining corpus cases are all that same fallthrough shape in helper scripts, package hooks, and project-closure code, and ShellCheck does not emit SC2365 for them, so these repo-family hits remain a stricter Shuck policy without hiding a distinct implementation bug."
- side: shuck-only
path_contains: "bitnami__containers__"
reason: "C124 intentionally treats code after guarded exits as unreachable when one branch exits but the other branch still falls through to later statements. The remaining corpus cases are all that same fallthrough shape in helper scripts, package hooks, and project-closure code, and ShellCheck does not emit SC2365 for them, so these repo-family hits remain a stricter Shuck policy without hiding a distinct implementation bug."
- side: shuck-only
path_contains: "bittorf__kalua__"
reason: "C124 intentionally treats code after guarded exits as unreachable when one branch exits but the other branch still falls through to later statements. The remaining corpus cases are all that same fallthrough shape in helper scripts, package hooks, and project-closure code, and ShellCheck does not emit SC2365 for them, so these repo-family hits remain a stricter Shuck policy without hiding a distinct implementation bug."
- side: shuck-only
path_contains: "community-scripts__ProxmoxVE__"
reason: "C124 intentionally treats code after guarded exits as unreachable when one branch exits but the other branch still falls through to later statements. The remaining corpus cases are all that same fallthrough shape in helper scripts, package hooks, and project-closure code, and ShellCheck does not emit SC2365 for them, so these repo-family hits remain a stricter Shuck policy without hiding a distinct implementation bug."
- side: shuck-only
path_contains: "docker__docker-bench-security__"
reason: "C124 intentionally treats code after guarded exits as unreachable when one branch exits but the other branch still falls through to later statements. The remaining corpus cases are all that same fallthrough shape in helper scripts, package hooks, and project-closure code, and ShellCheck does not emit SC2365 for them, so these repo-family hits remain a stricter Shuck policy without hiding a distinct implementation bug."
- side: shuck-only
path_contains: "dylanaraps__pure-bash-bible__"
reason: "C124 intentionally treats code after guarded exits as unreachable when one branch exits but the other branch still falls through to later statements. The remaining corpus cases are all that same fallthrough shape in helper scripts, package hooks, and project-closure code, and ShellCheck does not emit SC2365 for them, so these repo-family hits remain a stricter Shuck policy without hiding a distinct implementation bug."
- side: shuck-only
path_contains: "gentoo__gentoo__"
reason: "C124 intentionally treats code after guarded exits as unreachable when one branch exits but the other branch still falls through to later statements. The remaining corpus cases are all that same fallthrough shape in helper scripts, package hooks, and project-closure code, and ShellCheck does not emit SC2365 for them, so these repo-family hits remain a stricter Shuck policy without hiding a distinct implementation bug."
- side: shuck-only
path_contains: "helmuthdu__aui__"
reason: "C124 intentionally treats code after guarded exits as unreachable when one branch exits but the other branch still falls through to later statements. The remaining corpus cases are all that same fallthrough shape in helper scripts, package hooks, and project-closure code, and ShellCheck does not emit SC2365 for them, so these repo-family hits remain a stricter Shuck policy without hiding a distinct implementation bug."
- side: shuck-only
path_contains: "juewuy__ShellCrash__"
reason: "C124 intentionally treats code after guarded exits as unreachable when one branch exits but the other branch still falls through to later statements. The remaining corpus cases are all that same fallthrough shape in helper scripts, package hooks, and project-closure code, and ShellCheck does not emit SC2365 for them, so these repo-family hits remain a stricter Shuck policy without hiding a distinct implementation bug."
- side: shuck-only
path_contains: "ko1nksm__shellspec__"
reason: "C124 intentionally treats code after guarded exits as unreachable when one branch exits but the other branch still falls through to later statements. The remaining corpus cases are all that same fallthrough shape in helper scripts, package hooks, and project-closure code, and ShellCheck does not emit SC2365 for them, so these repo-family hits remain a stricter Shuck policy without hiding a distinct implementation bug."
- side: shuck-only
path_contains: "leebaird__discover__"
reason: "C124 intentionally treats code after guarded exits as unreachable when one branch exits but the other branch still falls through to later statements. The remaining corpus cases are all that same fallthrough shape in helper scripts, package hooks, and project-closure code, and ShellCheck does not emit SC2365 for them, so these repo-family hits remain a stricter Shuck policy without hiding a distinct implementation bug."
- side: shuck-only
path_contains: "lmc999__RegionRestrictionCheck__"
reason: "C124 intentionally treats code after guarded exits as unreachable when one branch exits but the other branch still falls through to later statements. The remaining corpus cases are all that same fallthrough shape in helper scripts, package hooks, and project-closure code, and ShellCheck does not emit SC2365 for them, so these repo-family hits remain a stricter Shuck policy without hiding a distinct implementation bug."
- side: shuck-only
path_contains: "moovweb__gvm__"
reason: "C124 intentionally treats code after guarded exits as unreachable when one branch exits but the other branch still falls through to later statements. The remaining corpus cases are all that same fallthrough shape in helper scripts, package hooks, and project-closure code, and ShellCheck does not emit SC2365 for them, so these repo-family hits remain a stricter Shuck policy without hiding a distinct implementation bug."
- side: shuck-only
path_contains: "nvm-sh__nvm__"
reason: "C124 intentionally treats code after guarded exits as unreachable when one branch exits but the other branch still falls through to later statements. The remaining corpus cases are all that same fallthrough shape in helper scripts, package hooks, and project-closure code, and ShellCheck does not emit SC2365 for them, so these repo-family hits remain a stricter Shuck policy without hiding a distinct implementation bug."
- side: shuck-only
path_contains: "paulirish__dotfiles__"
reason: "C124 intentionally treats code after guarded exits as unreachable when one branch exits but the other branch still falls through to later statements. The remaining corpus cases are all that same fallthrough shape in helper scripts, package hooks, and project-closure code, and ShellCheck does not emit SC2365 for them, so these repo-family hits remain a stricter Shuck policy without hiding a distinct implementation bug."
- side: shuck-only
path_contains: "rvm__rvm__"
reason: "C124 intentionally treats code after guarded exits as unreachable when one branch exits but the other branch still falls through to later statements. The remaining corpus cases are all that same fallthrough shape in helper scripts, package hooks, and project-closure code, and ShellCheck does not emit SC2365 for them, so these repo-family hits remain a stricter Shuck policy without hiding a distinct implementation bug."
- side: shuck-only
path_contains: "super-linter__super-linter__"
reason: "C124 intentionally treats code after guarded exits as unreachable when one branch exits but the other branch still falls through to later statements. The remaining corpus cases are all that same fallthrough shape in helper scripts, package hooks, and project-closure code, and ShellCheck does not emit SC2365 for them, so these repo-family hits remain a stricter Shuck policy without hiding a distinct implementation bug."
- side: shuck-only
path_contains: "termux__termux-packages__"
reason: "C124 intentionally treats code after guarded exits as unreachable when one branch exits but the other branch still falls through to later statements. The remaining corpus cases are all that same fallthrough shape in helper scripts, package hooks, and project-closure code, and ShellCheck does not emit SC2365 for them, so these repo-family hits remain a stricter Shuck policy without hiding a distinct implementation bug."
- side: shuck-only
path_contains: "tteck__Proxmox__"
reason: "C124 intentionally treats code after guarded exits as unreachable when one branch exits but the other branch still falls through to later statements. The remaining corpus cases are all that same fallthrough shape in helper scripts, package hooks, and project-closure code, and ShellCheck does not emit SC2365 for them, so these repo-family hits remain a stricter Shuck policy without hiding a distinct implementation bug."
- side: shuck-only
path_contains: "xwmx__nb__"
reason: "C124 intentionally treats code after guarded exits as unreachable when one branch exits but the other branch still falls through to later statements. The remaining corpus cases are all that same fallthrough shape in helper scripts, package hooks, and project-closure code, and ShellCheck does not emit SC2365 for them, so these repo-family hits remain a stricter Shuck policy without hiding a distinct implementation bug."