feat: ScanList entity + DM32 Scan.csv import/export

[pskillen]

Problem

DM32 CPS exports a separate Scan.csv (scan lists) with channel Scan List FK columns. The internal codeplug model has no ScanList entity today — zones serve as the scan unit on OpenGD77 only.

#67 (DM32 import/export) deliberately defers scan lists so the first DM32 slice can ship channels, zones, contacts, talk groups, and RX group lists.

Intended outcome

Add a vendor-neutral ScanList entity and wire it through import/export for DM32 (and future formats with separate scan-list files).

Internal model (proposed)

interface ScanList {
  id: string;
  name: string;
  memberChannelIds: string[];
  priorityChannel1Id: string | null;
  priorityChannel2Id: string | null;
  designedTxChannelId: string | null;  // resume channel on scan stop
  hangTimeMs: number | null;
  prioritySweepTimeMs: number | null;
  talkback: boolean;
  digitalScanMode: 'talkgroup' | 'time-slot' | 'carrier';
  analogScanMode: string;   // TBA
  scanTxMode: 'current-channel' | 'last-activated-channel' | 'designated-channel' | ;
  meta?: EntityMeta;
}

// Channel addition
scanListId: string | null;

DM32 wire

File	Role
Scan.csv	Scan list definitions (11 columns, 16-member cap)
Channels.csv Scan List column	FK to scan list name

Reference: dmr-programming dm32-codeplug-csv skill.

Deliverables

• Data model + schema migration + merge/import resolution (mirror Zone member pattern)
• ImportEntityKind: 'scanLists' + adapter parseScanLists?
• DM32 import/export for Scan.csv + channel Scan List column
• Tier-3 reference: docs/reference/dm32/scan-lists.md
• Round-trip: Scan.csv + channel Scan List column in dm32RoundTrip.system.test.ts
• CRUD UI for scan lists (optional follow-up if import/export lands first)

Dependencies

• Blocks full verbatim round-trip of DM32 Scan.csv on #67
• Related: #67

Out of scope

• OpenGD77 scan semantics (zone = scan on 1701)
• Scan list policy / layout automation in dmr-programming

[pskillen]

Complementary mechanism — not a duplicate (#164)

This ticket (#125) and #164 address different layers of scan support. They are not mutually exclusive — an operator may use both manual scan lists and zone-derived automation in the same codeplug.

#125 — manual ScanList entity (this ticket)

• First-class ScanList[] in the internal model + channel.scanListId FK.
• Faithful import/export round-trip of DM32 Scan.csv (and future formats).
• Operator CRUD for scan lists independent of zones — full wire fidelity (priority channels, hang time, digital scan mode, scanTxMode, …).
• Use when the CPS layout does not map cleanly to “one scan list per zone” or when the operator wants explicit control.

#164 — zone-derived scan automation

• Policy on zones, not a separate scan-list editor:
  • Per zone membership: includeInScanList (honoured on DM32/CHIRP; ignored on OpenGD77 where zone = scan).
  • Per zone: generateScanCarrier — export-time dummy carrier channel (e.g. 145.5 simplex) as first zone member + derived scan list named after the zone.
• Respects Channel.scanSkip; does not use OpenGD77 Zone Skip vendor field.
• Generated DM32 scan lists default scanTxMode = last activated channel.
• May ship export-only synthesis of Scan.csv before feat: ScanList entity + DM32 Scan.csv import/export #125’s persisted entity exists; integrates when feat: ScanList entity + DM32 Scan.csv import/export #125 lands.

Coexistence (TBD in implementation)

When both exist: manual ScanList from #125 vs zone-generated lists from #164 need documented merge/precedence rules (e.g. manual scanListId on a channel wins over zone derivation; warn on name collisions).

#164 explicitly out of scope for full manual scan-list CRUD — that stays here.