Directory plugins load in filesystem order, and one plugin's hook error silently skips the rest #45367

Description

Two related problems in how directory plugins are loaded:

1. Glob.scan in packages/opencode/src/config/plugin.ts returns plugin/*.ts in filesystem order, so plugin/00_base.ts and plugin/10_override.ts can initialize in either order — and that order can differ between two machines with the same checkout. Anything order-dependent (one plugin registering a default another overrides) becomes a coin flip.

2. In packages/opencode/src/plugin/index.ts, trigger() runs each plugin's hook via Effect.promise, so the first hook that throws aborts the loop and every later plugin's hook for that trigger is skipped, silently. One broken plugin disables the others for accumulating hooks like chat.params / chat.headers.

Blocking hooks (tool.execute.before, permission.ask, command.execute.before) are a deliberate exception — a throw there is how a plugin denies the action, so those should keep propagating on first throw.

Steps to reproduce

1. Put two plugins in plugin/, both implementing chat.params
2. Make the first one throw
3. The second plugin's hook never runs, and nothing is logged

Expected

Deterministic (sorted) load order, and a throwing non-blocking hook logged and skipped without taking the other plugins down with it.

OpenCode version

1.18.23