CHW-2001 PolicyViolation

Default message: request blocked by configured policy; review the policy that matched in the policy audit log
HTTP status: 403 (client)
Reason: POLICY_BLOCK

Problem. A configured policy matched this request and blocked it. Cause. One or more of the active policies on the target repository evaluated to deny for this coordinate — commonly age-gate, origin, or signature requirements. Fix. The 403 body names the rule and the fact that fired, and when you hold exceptions:manage it also prints a runnable chainsaw exception create for the exact coordinate; run that to allow the package. Without that permission, the message names who to ask. Four other routes, in the order most people want them: wait out the window, if the rule is an age gate and the message gave you a clear date; ask an admin to switch that one rule to monitor, which keeps the finding and stops the refusal; chainsaw policy disable <policy-id>, using the id from the X-Chainsaw-Policy-Id response header; or, if you want your package manager pointed back at the upstream registry entirely, chainsaw uninstall-hook <manager> (add --all for every manager) — it restores your .npmrc / pip.conf / .cargo/config.toml from the backups it made and revokes the credential it minted. HTTP 403.