workspace-to-monitor-force-assignment with 'main' and 'secondary' patterns not working as expected

[Echarnus]

What's happening (Actual behavior)

My config specifies:

• Workspaces 6, 7, 8, 9 → go to 'secondary' monitors
• Workspace M → go to 'main' monitor

But what's actually happening:

• Workspaces 6-9 appear on my main monitor (Built-in Retina Display)
• Workspaces 10-11 appear on my secondary monitors (ASUS VG32VQ1B and VG248)
• This is the opposite of what I configured

What I'm expecting (Expected behavior)

• Workspaces 6-9 should appear on my secondary/external monitors
• Workspace M should appear on my main/built-in monitor
• Workspaces 10-11 shouldn't be assigned anywhere since I never configured them

The Config

[workspace-to-monitor-force-assignment]
6 = 'secondary'
7 = 'secondary'
8 = 'secondary'
9 = 'secondary'
M = 'main'

Environment

• AeroSpace version: 0.19.2-Beta (d246f25)
• macOS: Sonoma or later
• Multiple monitors: 3 total

Monitor setup (from aerospace list-monitors):

1. Built-in Retina Display
2. ASUS VG32VQ1B
3. VG248

Root Cause

The generic patterns 'main' and 'secondary' in workspace-to-monitor-force-assignment appear to be either:

1. Reversed - main/secondary logic is backwards
2. Not matching correctly - the pattern matching is broken
3. Inverted internally - AeroSpace's definition doesn't match expectations

Using specific monitor names as a workaround works, but breaks portability when switching between different sets of monitors.