Skip to content

[Tracker] BS open-issue triage — P0 sequencing, cross-cluster conflicts #645

@jakebromberg

Description

@jakebromberg

End-of-day triage of all open issues in this repo. Entry point for any contributor or agent picking up the work: where to start, what blocks what, which proposals overlap.

This tracker is intended to be edited in place, not appended to. When triage state changes, update the relevant section. Don't add a new "Updates YYYY-MM-DD" block.

Org-level entry point: WXYC/wiki#5 (cross-repo P0 sequencing + patterns).

P0 sequencing

Land before the LML metadata backfill epic (#631 family) ships in earnest. Rationale on each issue.

  1. Production flowsheet table is catastrophically bloated (1.4 GB heap, 24 live rows) #525 — flowsheet table 1.4 GB heap, 24 live rows, never autovacuumed. Silently degrades everything else. Code-side fix is operational (VACUUM FULL + per-table autovacuum settings ALTER TABLE) — no migration shipped, so this stays open until the operational pass runs.
  2. npm audit — 18 vulnerabilities (2 critical, 8 high) as of 2026-04-14 #75npm audit: 2 critical, 8 high vulns (per the 2026-04-14 comment; original title still says "moderate"). Title refresh requested in 2026-04-28 comment.
  3. Run LML entity-resolution pipeline to populate entity.identity in prod #572 — single-action unblocker (run LML entity-resolution pipeline in prod). Per the 2026-04-29 comment, superseded by Epic [Epic] E2 — Canonical identity record (library_identity) + LML write contract #663 (E2-BS) and slated to close as part of E2-BS step 1; treat as folded.
  4. Backfill library.artwork_url for Discogs-resolvable rows #637 — backfill library.artwork_url for Discogs-resolvable rows. Gates draft PR Denormalize library.artwork_url onto flowsheet on bin-pick #643 (held until library.artwork_url population is materially > 0.2%) and the bin-pick surface of Re-emit liveFs SSE event after metadata enrichment UPDATE lands #628.

After P0: the #631 family's remaining children — #640 (pilot — results recorded 2026-04-30 with provisional partition recommendation; both observability companions BS#669 and LML#229 have now merged, so the recommendation can be re-confirmed against actual cache_stats Sentry attributes if anyone wants to upgrade it from provisional) → #641 (rollout — native blockedBy now narrows to just #640 since #649 closed via PR #683) → #642 (close-out).

Open PRs held intentionally

Stale draft PRs

Scanner cluster (PRs #212, #213, #215, #217) was swept and closed 2026-05-09. Feature branches preserved on origin (feature/library-code-lookup-reviews, feature/scanner-gemini-integration, feature/scanner-batch-processing, feature/scanner-list-batch-jobs); reopen with fresh PRs if the scanner work resumes.

Severity

Cross-cluster conflicts (decide once before starting)

Artwork / metadata storage location

Decision (unchanged): defer #532 until #631's drain (#641) plateaus, then re-evaluate. Sequencing notes are on #637.

LML refactor cluster

Health-probe diagnosability

Per-show play_order semantics (resolved 2026-05-02)

Cross-repo dependencies (native + body prose)

BS issue Blocked by Status
#528 tubafrenzy#489, #490, #493, #495; docs#11 All open
#644 #628 Open (sibling fix)
#250, #251 #249 Open (graph projection chain)
#641 #640 (#649 closed via PR #683 2026-05-02; only the pilot remains)
#642 #641, #640 (#638, #639 closed; #649 closed)
#532 #641 Open (rollout plateau is the signal)
#637 #572 (soft) #572 superseded by #663
#655 tubafrenzy#496, docs#13, docs#16 All open
#665 library-metadata-lookup#226 #226 closed — BS-side #662 is unblocked

Native blockedBy relationships are visible in each issue's Relationships pill and queryable via GraphQL blockedBy.

Cross-repo runtime risks

Not strict blockers but cap realized hit rate / stability of the LML metadata backfill (recorded in #631 / #637 / #638 bodies):

Cluster map

Labels in use for cross-repo touch

lml (≈12), tubafrenzy (≈12), semantic-index (3), linkage, catalog-search-perf, mojibake, epic, Blocked!, flowsheet-metadata-backfill, cross-cache-identity, epic:e2-bs/epic:e2-lml/epic:e3-normalization/epic:e4-instrumentation. One-word repo-name labels (lml, tubafrenzy) are the convention.

How to find work

Metadata

Metadata

Assignees

No one assigned

    Labels

    choreMaintenance and housekeepingdocumentationImprovements or additions to documentation

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions