alexlazarian

Design: mise run dev:doctor rate-review

Goal

Add health-check coverage to domains/rate-review/setup-info.toml so that mise run dev:doctor rate-review surfaces the status of every rate-review service and infrastructure dependency -- matching the pattern already in place for the select domain.

Scope

alexlazarian

CLU-603: How We Addressed Ben's Review Feedback

PR #2583 · final commit 1d253619

---

Ben's feedback (verbatim summary)

1. Documents has a distinct processing/syncing case — rows are empty not because there are no documents, but because uploads haven't resolved yet. That's not "no documents yet," and collapsing it there was wrong.
2. The five loosely-related props (emptyHeading, emptySubtext, emptyAction, isFiltered, onClearSearch) push inference to call sites and let filter-empty silently fall through to true-empty copy or CTAs.

alexlazarian

CLU-530: Surface Medical Provider Source + Fix Provider Details Column

Date: 2026-05-17
Ticket: CLU-530
Scope: ui-2.0 frontend + api-hub backend

---

Summary

alexlazarian

CLU-354: Add Expense Quick Action — Transaction Link & Auto-Fill Enhancements

Date: 2026-05-18 Branch: alexlazarian/clu-354

---

Overview

Two enhancements to the "Add Expense" quick action form:

alexlazarian

PricingMatrix Component Extraction: A Diagram-Driven Walkthrough

---

Act 1 — The problem: everything tangled in one place

graph TD
    subgraph BID["select-bid — one monolithic matrix module"]
        MT["MatrixTable\nentry point"]

alexlazarian

CLU-470 hotfix-1 — Law Firm edit blocked when fee % sum != 100

QA report

the current hard validation requiring Fee % to sum to exactly 100% is blocking us from making any edits or adding new law firms. even with Law Firm Admin and Tekmir Admin permissions, the system triggers a "Failed to update law firm" error because the total doesn't hit 100% mid-edit.

Issue

alexlazarian

Diffly Reviewer Cockpit — Setup Guide

Diffly is a VS Code extension for reviewing git diffs. The Reviewer's Cockpit turns AI-generated review findings into a triageable workflow inside the panel: per-finding Agree / Disagree / Dismiss / Asked chips, an "Ask Author" list of absences (missing tests, missing rate limits, etc.), a suggested review order, and a one-click batched GitHub review post.

The cockpit is driven by a single file at the repo root: .diffly/findings.json. Diffly's file watcher picks up changes automatically — no reload needed.

This gist documents the JSON schema, the prompt for generating it with any coding agent, and a few examples.

---

alexlazarian

JUS-1204 — TinyMCE → Tiptap migration verification report

Captured: 2026-05-04 PR: #630 — Modernization of bid /setup/ pages PRE worktree: .worktrees/jus-1204-pre @ origin/main (15d626697d) POST branch: alexlazarian/JUS-1204-followup-select (HEAD)

---

TL;DR

alexlazarian

JUS-1204 Verification Checklist — Tiptap Migration

Date: 2026-05-01 Branch: alexlazarian/JUS-1204-followup-select Scope: Confirm the TinyMCE → Tiptap migration introduces no user-visible regressions across the Select domain (15 editor surfaces, the shared message-form gem, the bidder text-answer flow, three Rails apps, and three email templates).

The plan is split into two phases. Before merge is everything a person on a dev laptop with the local stack running can confirm (build, click-through, dev mail-catcher). After deploy is everything that needs the staging environment, real mail clients, real production-shape data, or a longer soak window.

Tick a checkbox only when you have personally observed the expected behaviour or output. If a check is non-applicable (e.g. you have no permissions on a particular surface), strike it through with a note rather than ticking it.

alexlazarian

JUS-1204 — Select editor migration: checkpoint 1

Date: 2026-05-01 Branch: alexlazarian/JUS-1204-followup-select (off main) Status: 5 of 15 surfaces migrated. Launchpad fully done at code level. Ready for browser verification.

What landed

Three commits on the branch: