Unverified50% confidenceFactExact time
The script chooses exit code 2 rather than 1 as the failure code because, by shell convention, 2 is commonly used for "usage error or condition not met," making it easy to distinguish a script crash from an active ledger rejection.
1
Sources
50%
Confidence
Long-term
Relevance
10/11/2026
First Seen
Sources
Related Entities
Related Claims
UnverifiedThe script should serve as a gate rather than a grade, exiting with a non-zero status code so that failures surface in the terminal.69% similarUnverifiedFixed an issue where file permission rules containing uncompilable patterns (such as an unclosed [) caused all file editing operations to fail due to invalid regular expressions; such deny rules now fall back to guarding only the literal path64% similarUnverifiedWhen using basename in a batch processing loop, variables must be wrapped in double quotes if the path or filename contains spaces; otherwise, the shell will misinterpret spaces as argument separators, causing the script to fail.61% similarUnverifiedBash permission rules with the intermediate pattern :* were previously skipped in settings files; the new version makes them take effect from all sources and issues a warning about the matching method at startup.57% similarUnverifiedWhen the operating system denies access to the managed settings file, Claude Code now issues a warning and continues to start without that file's policies, rather than refusing to start outright; other read errors and unparseable files still abort the session.57% similar
Cite This Claim
Stable URI
https://kongchang.com/claim/999333API
curl https://kongchang.com/api/v1/knowledge/claims/999333MCP
get_claim(id=999333)