enhance(docker): explicit risk-class policy for optimal security

Remove implicit global action in favor of explicit per-class definitions:
- all 9 classes now clearly defined (safe→allow, unknown→deny, etc.)
- eliminates gotcha where safe commands would prompt with action:"prompt"
- fail-closed policy now explicit in config, not just implicit
- unattended mode (non_interactive:deny) is unambiguous and secure

Ordering by risk severity: allow → prompt → deny.

Co-Authored-By: Claude Haiku 4.5 <noreply@anthropic.com>

Author: jkyberneees

docker/config.restricted.json

@@ -1,15 +1,17 @@
 {
   "sandbox": false,
   "dangerous": {
-    "action": "prompt",
     "non_interactive": "deny",
     "classes": {
-      "destructive": "deny",
-      "system_write": "prompt",
+      "safe": "allow",
+      "local_write": "allow",
+      "install": "prompt",
       "network_egress": "prompt",
       "code_execution": "prompt",
-      "install": "prompt",
-      "local_write": "allow"
+      "system_write": "prompt",
+      "unknown": "deny",
+      "destructive": "deny",
+      "blocked": "deny"
     },
     "allowlist": [],
     "denylist": ["rm -rf /"]