/**
 * Settings-driven permission rules (Slice 3 / PERM track).
 *
 * The schema mirrors Claude Code's `settings.json` `permissions` block:
 *
 *   {
 *     "permissions": {
 *       "allow": ["Edit(src/**)", "Write(./output/**)"],
 *       "deny":  ["*(~/.ssh/**)", "Read(./.env)"],
 *       "ask":   []
 *     }
 *   }
 *
 * OwlCoda adds one sugar: `*(pattern)` matches any tool, equivalent to
 * writing every Tool-form individually. Bare strings (no `Tool(...)` wrapper)
 * are rejected at parse time to keep the grammar unambiguous.
 *
 * Loaded from three files in precedence order (rules MERGE; deny across any
 * layer always wins):
 *   1. `~/.owlcoda/settings.json`             — user-level
 *   2. `<cwd>/.owlcoda/settings.json`          — project shared
 *   3. `<cwd>/.owlcoda/settings.local.json`    — project local (gitignored)
 *
 * v1 enforcement scope (PERM track): path-shape rules compiled into baseline
 * provenance ledger evidence and consulted by the existing admission gate.
 * `Bash(...)` command-pattern rules are PARSED but NOT ENFORCED — they emit
 * a load-time warning so users who paste a CC `settings.json` over know
 * what's been ignored. See spec §17 for the full enforcement matrix.
 */
export {};
//# sourceMappingURL=permission-rule-types.js.map