You cannot select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

Thomas Joise 0c3f6c2e3a fix(client-360): audit fixes for onboarding status line, tickets, dashboard ... Pre-ship audit swarm findings on the Client Detail redesign: - StatusLine's isPaymentStep now also matches the legacy advance_paid/ balance_paid keys (the generic fallback template's vocabulary on modules with no seeded per-module tail — WHATSAPP, ATM, AMC, ...), so ticking the payment step there opens the picker instead of silently stamping a date. - Every milestone-tick path (plain toggle, payment link, credentials, document link) now reloads the client-modules list so the module block header, summary table and status select never go stale after a tick. - A done payment/document milestone step now surfaces its link (linked document -> /documents/<id>; linked payment -> date/amount from the loaded ledger) instead of showing no evidence the link landed. - Tickets: guard TICKET_STATUS_LABEL lookups against non-status chip values (e.g. the synthetic "overdue" chip) that were throwing and blanking the whole console. - Dashboard: distinguish a failed "Onboarding stalled" fetch from a genuine empty result instead of reporting "Nothing stalled." on error. - Client 360 tickets tab: add the Type column, same rendering as the Tickets desk. - Drop the redundant read-only status badge next to the editable ClientModuleStatusSelect in the module block header. - Only mount NewTicketDialog while actually open, so it stops firing getModules/getTicketTypes on every Client 360 load. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>		1 day ago
..
hq	fix(scripts): audit + guard apply-onboarding-pipeline's setting writes	1 day ago
hq-web	fix(client-360): audit fixes for onboarding status line, tickets, dashboard	1 day ago