Checklist

• I have searched existing enhancements and this is not a duplicate.
• This request covers a single enhancement (open a separate issue for each one).
• I have filled out the template below.

Adaptive Cover Pro version

No response

Is your enhancement related to a problem?

Context

The configuration menu of an ACP entry is getting quite long (16 entries in the screenshot below).
While each section has its purpose, I noticed that "Forced override" and "Custom positions"
share most of their semantics: both impose a fixed position on the cover when a trigger
condition is met.

Observation

If I understand correctly:

• A Custom position = a trigger entity + a forced position + (optionally) a minimum-mode floor
• A Forced override = effectively the same thing, but with priority 100 (highest),
  and it supports multiple trigger entities combined with OR logic

So the only real functional difference is:

1. The priority level (forced = top priority)
2. Forced override accepts several triggers, custom positions accept only one each

This makes "Forced override" feel like a special-case custom position rather than a
distinct concept — which adds menu length and cognitive load for new users trying
to figure out which one to use.

Describe the solution you'd like

Option A — Full merge (cleaner long-term, but breaking)

Extend custom positions to support:

• Multiple trigger entities with configurable OR/AND logic
• An explicit priority slider (instead of having a separate "forced" section)

Then deprecate / remove the "Forced override" menu entry.

Option B — Soft merge (non-breaking)

• Keep the existing 4 custom position slots untouched (no migration risk)
• Add a 5th slot specifically designed as the "forced" one:
  • Multiple triggers with OR logic
  • Pinned at top priority by default (configurable)
• Move "Forced override" UI under "Custom positions" as this 5th slot
• Remove the standalone "Forced override" menu entry

Option B has the advantage of not touching any existing user configuration, while
still reducing the menu length and unifying the mental model.

Option C — Pure UI grouping (lightest)

Just visually group "Forced override" + "Custom positions" under a single menu entry
"Custom positions & overrides", with sub-tabs inside. No semantic change, just less
scrolling.

Alternatives you've considered

No response

Additional context

No response