Stability Improvements, KPI/Filter/Search Fixes, and Column Reordering

[drkatz]

Summary

This PR consolidates a broad set of improvements focused on application stability under heavy update churn, dashboard/KPI correctness, filter/search behavior consistency, and issues table usability.

The scope includes backend watcher and polling pipeline hardening, UI diagnostics and stress tooling, KPI/filter logic fixes, search behavior fixes, and table column reordering support.

What Was Fixed

1. Fixed refresh pipeline contention by replacing debounce/isProcessing flow with a queue-based single-flight model in app/composables/useChangeDetection.ts.
2. Fixed high-churn freeze risk by adding poll backpressure scheduling in app/composables/usePollScheduler.ts and integrating it in app/pages/index.vue.
3. Fixed stale blocked indicators after blockers close by correcting blocked-state handling in app/composables/useIssues.ts and app/utils/issue-helpers.ts.
4. Fixed blocked/open/workflow mismatch in KPI stats and filtering logic in app/utils/issue-helpers.ts, app/components/dashboard/DashboardContent.vue, and app/pages/index.vue.
5. Fixed Open KPI filtering to exclude dependency-blocked issues when appropriate in app/utils/issue-helpers.ts.
6. Fixed blockedBy mapping from dependencies in server transformation logic in server/utils/bd-transformers.ts.
7. Fixed filter dropdown active-state rendering by switching to :model-value usage in filter dropdown components under app/components/issues/*FilterDropdown.vue.
8. Fixed active filter chips visibility during search in app/components/issues/IssueListPanel.vue.
9. Fixed search behavior so search respects active filters instead of bypassing them in app/utils/issue-helpers.ts.
10. Fixed left-panel KPI card ring clipping, truncation, and responsive sizing issues in app/components/dashboard/KpiCard.vue, app/components/dashboard/DashboardContent.vue, and app/pages/index.vue.
11. Fixed top-right header/window controls spacing/rendering behavior in app/components/layout/AppHeader.vue with related platform-side adjustments in src-tauri/src/lib.rs and src-tauri/tauri.conf.json.
12. Removed obsolete deleted-status handling across filtering and display paths in app/components/issues/*, app/composables/*, app/utils/issue-helpers.ts, and src-tauri/src/lib.rs.

What Was Added

1. Added watcher/poll diagnostics infrastructure via app/composables/usePipelineDiagnostics.ts.
2. Added diagnostics UI in app/components/layout/DebugPanel.vue.
3. Added churn stress test coverage in tests/composables/churn-stress.test.ts.
4. Added scheduler diagnostics and behavior tests in tests/composables/usePollScheduler.test.ts and tests/composables/usePipelineDiagnostics.test.ts.
5. Added queue/change-detection tests in tests/composables/useChangeDetection.test.ts.
6. Added churn stress runbook and helper script in docs/churn-stress-runbook.md and scripts/churn-stress.sh.
7. Added dashboard quick-list “Copy ID” action in app/components/dashboard/QuickList.vue.
8. Added column drag-and-drop reordering in app/components/issues/ColumnConfig.vue with persistence support in app/composables/useColumnConfig.ts.
9. Added “All” KPI interaction that applies all status filters in app/composables/useFilters.ts and app/pages/index.vue.

What Was Refined

1. Refined KPI defaults and ordering, including workflow-first behavior and “Total” rename to “All” in app/components/dashboard/DashboardContent.vue and app/pages/index.vue.
2. Refined blocked-by presentation by moving details into StatusBadge tooltip and removing redundant icon usage in issue table/details components.

Validation

1. pnpm test passes.
2. pnpm build passes.
3. Branch history preserves commit granularity while being rebased onto current upstream master to enable clean PR comparison.

[w3dev33]

Thanks for this substantial PR! Solid work overall — the pipeline architecture and KPI logic are well thought out. Here's what I found during review:

Bugs

1. issue-helpers.ts — stats.ready never computed. It's declared and initialized to 0 in computeStatsFromIssues but never populated. Either compute it or remove it from the interface.

2. issue-helpers.ts:79 — leftover tombstone check in isIssueWorkflow(). The tombstone status was removed everywhere else but this reference remains.

3. lib.rs:normalize_issue_status — tombstone silently becomes open. Old deleted issues could resurface as open with no indication. Consider filtering them out instead of mapping to open.

4. QuickList.vue — uses console.error instead of logFrontend. Project convention requires using the native logger (logFrontend('error', ...)) so errors end up in the log file.

5. AppHeader.vue — Linux/Windows padding fix was added then fully reverted. Commit 54f07db added platform-aware padding, but commit 084564e reverted it entirely. Net diff is zero — was this intentional?

Needs Manual Verification

• tauri.conf.json — titleBarStyle: "Overlay" was removed and "create": false was added. This changes macOS traffic light behavior. Please confirm the window controls still render correctly on macOS.

• ColumnConfig.vue — The SortableJS onEnd handler manually reverts DOM mutations using container.children[evt.oldIndex], which can be off-by-one when oldIndex > newIndex. Worth testing with rapid reordering.

Dead Code / Cleanup

• useColumnConfig.ts: reorderColumns() is exported but never called
• tailwind.css: 6 lines of tombstone CSS variables/gradients remain
• dashboard-stats.test.ts:91: still uses 'tombstone' as any
• useChangeDetection.ts + usePipelineDiagnostics.ts: use console.warn/console.debug instead of logFrontend() (project convention)

UX Questions

• clearFilters resets to Workflow view (not "show all") — is this the intended behavior?
• hasActiveFilters is true in the default Workflow state, so filter chips are always visible even on first launch.
• Column reordering is drag-only — no keyboard accessibility for users who can't use a mouse/trackpad.
• QuickList.vue — the clickable area for issue selection shrunk when the outer element changed from <button> to <div>.

What Looks Good

• Pipeline architecture (watcher → queue → backpressure → adaptive polling) is clean and well-scoped
• KPI blocked/open/workflow partitioning is correct and consistent between stats and filtering
• :model-value fix on filter dropdowns applied uniformly
• blockedBy mapping from dependencies handles both bd formats correctly
• Migration guards for persisted filters (tombstone removal) — good practice
• 256 tests passing, new churn stress tests added

Nice contribution — looking forward to a v2 with the fixes above!

[w3dev33]

A note on the broader context:

Thanks again for the effort here — it's clear you've put real thought into this. Many of the changes (KPI tiles, always-visible filter chips, blocked quick-list, etc.) reflect personal workflow preferences, and that's totally valid. Different users have different needs — for instance, I prefer only showing filter chips when they're actively filtering, while you prefer them always visible. Neither approach is wrong, it's a matter of taste.

That said, I'm not actively developing this project further (especially around the bd integration), so I don't think it makes sense to merge a PR of this scope into the main repo. It would set expectations of maintenance and direction that I can't commit to.

The best path forward is probably to keep your fork as your own adapted version. If others in the community are interested, the discussion is open — but for now I'll leave the main repo as-is.

Appreciate the contribution and the ideas!

[drkatz]

Thanks @w3dev33 for the review, good points and things to consider. I was working on these changes and pushed a few hours after the announcement for PaiR came out - Figured I'd PR just in case it was helpful. I will be continuing to maintain my fork as I encounter issues and find things to improve.

[w3dev33]

Thanks for the gracious response! Of course, feel free to keep evolving your fork of Beads however you see fit — it's great to see someone pushing it further.

If you're curious, you might also want to check out PaiR, the successor app. It already has quite a few improvements over this version. You're more than welcome to try it out and share any suggestions — present or future. Feedback is always appreciated!