Files
OmniRoute/@omniroute
Prudhvi Vuda 685e598d32 fix(providers): declare explicit OpenCode plugin feature-flag defaults (#8608)
The OpenCode plugin `features` block (opencode.json) marks every toggle
`.optional()` with no default, and the effective value is applied implicitly
at each read site via the scattered `features.X !== false` (default-ON) /
`features.X === true` (default-OFF) convention. An operator who omits the
`features` block therefore cannot tell whether combos / autoCombos /
enrichment are enabled — they read the `autoCombos=0` startup diagnostic
(a count that can be 0 for reasons unrelated to the flags, e.g. missing auth)
and conclude the features are disabled when they are actually on.

Declare the defaults explicitly in one place and surface the effective flags:

- `OMNIROUTE_FEATURE_DEFAULTS` — the declared default state for every boolean
  `features.*` toggle, mirroring the existing read-site conventions exactly
  (runtime routing behaviour unchanged).
- `resolveEffectiveFeatureFlags(features)` — derives the effective boolean
  state for any (possibly-undefined) features object.
- Startup diagnostics now emit a `features(effective): ...` line so an operator
  who omitted the block can see combos/autoCombos/enrichment are on.

Purely additive: no read site changes, so the existing
`features: {} → {}` schema pass-through contract is preserved.

Closes #7624
2026-07-27 19:07:40 -03:00
..
2026-06-13 17:27:40 -03:00