Summary

Fixes #8832

Root-level permission config in opencode.json was being ignored. The same config worked when placed under agent.build.permission but not at the root.

Examples that didn't work

Setting permissions at the root level had no effect — bash commands would still be auto-allowed instead of prompting:

{
  "permission": {
    "*": "ask",
    "bash": {
      "*": "ask",
      "ls *": "allow"
    }
  }
}

Similarly, this config intended to require approval for all bash except ls, but all commands ran without asking:

{
  "permission": {
    "*": "allow",
    "bash": {
      "*": "ask",
      "git log *": "allow",
      "ls *": "allow"
    },
    "edit": "ask"
  }
}

Moving the exact same config under agent.build.permission worked fine.

Cause

When multiple config sources are merged via mergeDeep (e.g. global config + project config), JavaScript object key ordering is not guaranteed. The catch-all "*": "ask" key could end up after specific tool keys like "bash" in the merged object.

fromConfig iterates with Object.entries(), so the { permission: "*", pattern: "*", action: "ask" } rule would appear after { permission: "bash", pattern: "ls *", action: "allow" } in the ruleset. Since evaluate uses findLast, the wildcard * rule won over the specific bash rule.

Fix

In fromConfig, wildcard permission keys (like "*") are now always processed before specific tool keys. This ensures specific tool rules appear later in the ruleset and take precedence via findLast, regardless of the key ordering in the config object.