Path-write safety checks gain 'uncertain' and internal hard-deny outcomes

What

A safety check is a point where Claude Code stops before writing to a file path it considers risky. This release changes how that check reaches its verdict:

• settings and uncertain outcomes: one kind of safetyCheck reason now classifies the write as "settings", a second kind returns "uncertain", and a safetyCheck on a blockedPath is handled differently. Before, the result was only "settings" or "none".
• Denials kept: when the path check hits a deny, it no longer stops there and returns that deny's reason. It keeps the deny, combines it with the safety-check message, and adds an also list that can include internalHardDeny.
• No automatic approval: the classifier, the part of auto mode that approves actions without asking you, can no longer approve these cases.
• New internalHardDeny permission class: the table of permission reasons gains a servedUnplaceable field. It is true only on internalHardDeny and false on every other class. Where internalHardDeny is actually assigned as a reason was not found, and the code that reads it was not confirmed.

Why

This changes when a path-write safety check defers to you and when it defers to your settings. If you use auto mode, you may see different wording when a write is denied, and some of these denials can no longer be approved automatically.