Skip to content

Per-section sync 5/5: per-section results UI (confidence badges, apply or skip each section) #26

Closed

Description

@cchacs

Effort: L

Part of #8. Depends on sub-issues 3 and 4.

Present per-section sync results without overwhelming the user (the UX question in #8).

Scope

  • Show a per-section confidence badge next to each section's result.
  • Let the user apply or skip each section individually, plus an "apply all high-confidence" shortcut; review-each remains available.
  • Make clear what will change before applying (per-section factor/offset or shift) and that the change is baked in once applied.
  • Follow the host's v3 chrome and shortcut conventions (register any keyboard shortcuts through window.registerShortcut, which is also the subject of the separate editor keybinds issue Hardcoded keybinds in onKeyDown bypass window.registerShortcut #10).

Acceptance criteria

  • A song where one section has low confidence can be synced with that section skipped, in a few clicks.
  • The default action never applies a low-confidence section.
  • Works for a single-section song (collapses to the existing uniform flow).

Out of scope

The alignment engine, the baking, and the data model.

Activity

  1. pullfrog commented on Oct 2, 2026

    @pullfrog
  2. pullfrog commented on Oct 12, 2026

    @pullfrog

    Implemented #26 (per-section sync review UI) and opened PR #71: #71

    Per-section confidence badges, apply/skip toggles, apply-all-high-confidence, and a pre-apply factor/shift preview, all committing through the same applyPerSectionSync path as #25. Low-confidence sections default to skip; failed sections aren't selectable; single-section songs collapse to uniform. A reviewfrog self-review caught a focus-trap leak after toggle re-renders, decision/acceptance confusion on conflict-demoted sections, and a summary that miscounted forced sections — all fixed with a new DOM-driven suite. npm test 414 pass, lint clean.

    Pullfrog  | View workflow run | via Pullfrog | Using big-pickle (free) | 𝕏

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions