v2.0.0

Major release: unpinned mutating commands now deny instead of prompting — a strict secure-by-default tightening of the ambient-context threat model.

• Deny unpinned mutations; echo namespace in kube prompts by @karlkfi in #12

A mutating infrastructure command that pins no explicit target (kubectl delete pod x with no --context, terraform apply with no TF_WORKSPACE, aws s3 rm … with no --profile, …) now denies with a self-healing fix-it naming the flag to add, instead of asking. The ambient target is clobber-prone shared state a parallel session can repoint between writing and running the command, so it can't run until the target is explicit. The deny is machine-actionable — the agent re-runs pinned (which then defers) in one round trip rather than stalling a human. Kube deny/ask reasons now also echo the parsed namespace alongside the context. PROD_GUARD_OVERRIDE still downgrades any deny → ask.

Full Changelog: v1.1.0...v2.0.0