Skip to content

Board: dedupe orchestrator tasks per-ref — coarse dedupe hides multi-ref work #1196

Closed

Description

@dezren39

Part of epic #1184 (PM stack coherence review, 2026-10-26).

Split from #1162's scope. The in-flight lane dedupe is deliberately coarse: one shared ref or a title match drops the whole orchestrator entry, including its other refs (live.ts inFlightBoardItems). Real multi-ref work can therefore vanish from the board when a Kaneo card shares one ref.

Acceptance:

  • Dedupe is per-ref instead of per-task.
  • A multi-ref task deduped on one ref still shows with its remaining refs.
  • Render tests cover the multi-ref dedupe case.

Acceptance criteria

  • Board dedupe of orchestrator tasks is per-ref instead of per-task.
  • A multi-ref task deduped on one ref still shows on the board with its remaining refs.
  • Render tests cover the multi-ref dedupe case.

Activity

  1. added
    kind/bugSomething isn't working (prefixed form of the classic bug label)
    priority/normalOrdinary priority (the default)
    on Oct 27, 2026
  2. developing-today commented on Oct 27, 2026

    @developing-today
    Contributor
  3. added
    source/humanFiled directly by a human
    effort/sSmall: expected under 2 hours of work
    meta/enrichedIntake review done: acceptance criteria, links, and normalized labels added
    on Oct 28, 2026
  4. dezren39 commented on Oct 28, 2026

    @dezren39
    MemberAuthor

    Intake review

    Related: Part of epic #1184; split from #1162. Sibling batch: #1198, #1197, #1195.

    Notes / risks: Per-ref dedupe changes what the board shows for every multi-ref orchestrator entry — render tests should include the single-ref case to prove no regression.

    Suggested approach: Work in live.ts inFlightBoardItems; keep the coarse title-match behaviour out — only ref-level dedupe.

    Live check: verified still open and unheld this run; a merged-PR search on this run (2026-10-28T10:35:00Z) returned no PR resolving this issue, so it remains live work. Acceptance criteria appended to the body (original text preserved verbatim above it) and labels normalized by the fleet monitor.

  5. added
    work/assignedQueue worker lifecycle state
    queue/claimedQueue worker lifecycle state
    and removed on Nov 1, 2026
  6. 1 remaining item

  7. dezren39 commented on Nov 1, 2026

    @dezren39
    MemberAuthor

    Triage verdict: confirmed, route to implementation

    At main f00dde6, inFlightBoardItems discards a whole task when any ref matches an existing card, hiding unmatched refs. The existing board-in-flight test asserts this coarse behavior. Filter matching refs instead, preserve genuinely ref-less tasks, remove title-only cross-card dedupe, and retain the remaining refs and their proper repository. Add regression tests including rendered links, fully matched single refs, ref-less tasks, distinct-ref title matches and section repeats. No relevant linked/open PR was found in issue-number, function-name, or per-ref searches.

  8. dezren39 commented on Nov 1, 2026

    @dezren39
    MemberAuthor

    Triage complete: confirmed on current main and queued implementation follow-up task 4901. Issue remains open for the fix.

  9. dezren39 commented on Nov 1, 2026

    @dezren39
    MemberAuthor

    Picked up queue task 4901 for the board per-ref dedupe fix. Fresh check: issue #1196 remains open; relevant open-PR searches found no competing fix.

  10. dezren39 commented on Nov 1, 2026

    @dezren39
    MemberAuthor

    Queue task 4901 is complete with PR #3934 open: #3934. The focused board-in-flight suite passes; broader unrelated baseline failures are recorded in the task result.

  11. added a commit that references this issue on Nov 2, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

app/pm-stackpm-stack (Pad/Grist) in developing-today/codeeffort/sSmall: expected under 2 hours of workkind/bugSomething isn't working (prefixed form of the classic bug label)meta/enrichedIntake review done: acceptance criteria, links, and normalized labels addedpriority/normalOrdinary priority (the default)source/humanFiled directly by a human

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions