Centralize resolution status reconciliation with current beets associations #46

New issue

Closed

opened 2026-09-05 22:42:18 +00:00 by tophattedcat · 0 comments

tophattedcat commented

2026-09-05 22:42:18 +00:00

Owner

Problem

Reporting combines saved resolution_state with live beets associations, but only overrides the saved state when one or more associated items exist. If a previously matched beets item is deleted, list-tracks can display matched with an empty BEETS_ITEMS column.

Related state reconciliation is independently implemented in reporting, explicit-match displacement handling, and interactive matching. These implementations can drift as associations change outside normal sync.

Proposed change

Centralize how current associations, saved automatic outcomes, and permanent skips determine effective status. Keep reporting read-only and distinguish a saved decision from evidence of a current association.

Acceptance criteria

Removing a matched local item cannot leave it displayed as currently matched.
One association and multiple associations are represented consistently.
Saved ambiguity/unmatched outcomes and permanent skips retain their intended meaning.
Explicit reassignment, displaced tracks, and interactive matching use consistent rules.
Add regressions covering deletion and association changes between sync and reporting.

References: beetsplug/appleplaylists/__init__.py:330-337, __init__.py:422-443, __init__.py:479-498. Audit finding 5 (medium).

## Problem Reporting combines saved resolution_state with live beets associations, but only overrides the saved state when one or more associated items exist. If a previously matched beets item is deleted, list-tracks can display matched with an empty BEETS_ITEMS column. Related state reconciliation is independently implemented in reporting, explicit-match displacement handling, and interactive matching. These implementations can drift as associations change outside normal sync. ## Proposed change Centralize how current associations, saved automatic outcomes, and permanent skips determine effective status. Keep reporting read-only and distinguish a saved decision from evidence of a current association. ## Acceptance criteria - Removing a matched local item cannot leave it displayed as currently matched. - One association and multiple associations are represented consistently. - Saved ambiguity/unmatched outcomes and permanent skips retain their intended meaning. - Explicit reassignment, displaced tracks, and interactive matching use consistent rules. - Add regressions covering deletion and association changes between sync and reporting. References: `beetsplug/appleplaylists/__init__.py:330-337`, `__init__.py:422-443`, `__init__.py:479-498`. Audit finding 5 (medium).

tophattedcat referenced this issue from a commit

2026-09-06 11:16:26 +00:00

Fix sync and local workflows (#44 #45 #46 #47 #48 #49 #50)

tophattedcat referenced this issue from a pull request that will close it,

2026-09-06 11:16:27 +00:00

Fix sync reliability and local workflows for #44–#50 #51

tophattedcat closed this issue

2026-09-06 13:54:54 +00:00