@ultimat3/policy 2.0.0 → 3.0.0

package/CLAUDE.md

@@ -45,6 +45,12 @@ two differ, and it is why a surface that decides on input alone needs no edit.
   say it in a type (a config-driven route table, a policy resolved by name). Never default
   to allow.
 - `can()` validates its permission at declaration time, not at request time.
+- **`definePermissions()` merges, and an EMPTY registry is permissive.** It only ever `add`s, so a
+  package that declares its own names at import time (`@ultimat3/admin`'s policy bridge) cannot
+  clobber an app's set. What it does change is the mode: `isKnownPermission` answers `true` to
+  everything while nothing is declared, so the first declaration anywhere in the process turns
+  strict checking on for everyone. A test that uses `can()` declares the set it uses and restores
+  the one it found — never leans on the empty registry.
 - **`not()` never inverts `X_UNAUTHENTICATED`.** A null actor is not a fact about this
   actor's grants; inverting it makes `not(can('order:internal'))` a public door into the
   internal one. Any denial carrying that code propagates unchanged.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@ultimat3/policy",
-  "version": "2.0.0",
+  "version": "3.0.0",
   "description": "The one authz rule, evaluated identically in every surface",
   "license": "MIT",
   "type": "module",
@@ -31,6 +31,6 @@
     "test": "bun test"
   },
   "dependencies": {
-    "@ultimat3/core": "2.0.0"
+    "@ultimat3/core": "3.0.0"
   }
 }