feat(launch-readiness-batch): UAT drains, navigation refactor, launch infra, trackers
Bundles the rest of the in-flight work from this UAT round into one
checkpoint. Each sub-area is independent; see the headings below.
UAT polish (drained 11 findings from active-uat.md):
- Dialog primitive default bumped sm:max-w-xl/lg:max-w-3xl →
sm:max-w-2xl/lg:max-w-4xl so multi-field forms + PDF previews
aren't cramped at 1440-1920px.
- Notes tab badge aggregation: new countFor{Client,Yacht,Company}
Aggregated helpers in notes.service mirror the listFor*Aggregated
symmetric-reach joins. yacht-tabs + company-tabs render the
badge; client-tabs already had badge support.
- Supplemental-info form polish bundle: BrandedAuthShell gains a
`width: 'sm' | 'md'` prop (md uses min-h-dvh scroll instead of
fixed inset-0 pin so long forms scroll naturally). Form picks up
port branding (logoUrl + backgroundUrl + appName) via
loadByToken. Address fields completed (street + city + region +
postal + country). Port name eyebrow + success-state copy added.
- new-document-menu Upload-file landing toast: per-file completion
emits toast.success with action link to the destination entity
or folder.
- interest-tabs OverviewTab "from client" pill on Email + Phone
rows via new EditableRow `inheritedFrom` prop.
- create-document-wizard subject picker → segmented button strip
(5 types visible at once).
Launch infra:
- UTM column wiring (Init 1b step 4): migration
0089_website_submissions_utm.sql adds utm_source/medium/campaign/
term/content + composite index (port_id, utm_source, received_at)
for per-campaign rollups. website-inquiries intake accepts the
five fields. Residential intake intentionally untouched per audit
scope.
- Invoicing module gate (Init 1c spike): new
invoices-module.service + invoices layout guard + registry entry
invoices_module_enabled (default false). Audit conclusion in
launch-readiness.md: payments table is canonical money path;
/invoices flow is parallel infrastructure now hidden by default.
Smart-back navigation refactor:
- Replaced breadcrumb component with history-aware Back button.
New route-labels.ts + use-smart-back hook +
navigation-history-tracker so back falls through to the parent
route when there's no prior page in history.
- Sidebar / topbar / mobile-topbar adopt the new pattern; old
breadcrumb-store kept for back-compat consumers but the
breadcrumbs component is gone.
- 6 detail pages (admin/errors per-id + codes, invoices/
upload-receipts, reports kind, tenancies detail, analytics
metric, client detail) migrated.
Trackers + docs:
- docs/launch-readiness.md — master pre-launch tracker. Includes
the reports gap audit (cross-cutting filter set, Marketing +
Financial blockers, custom builder remaining entities, scheduled
CSV/XLSX, template scope picker).
- docs/superpowers/audits/active-uat.md — 15 findings flipped
OPEN → SHIPPED locally with fix-applied notes; 4 OPEN remaining
(each blocked on user input or cross-repo).
- CLAUDE.md — minor session notes carried forward.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
This commit is contained in:
22
src/lib/db/migrations/0089_website_submissions_utm.sql
Normal file
22
src/lib/db/migrations/0089_website_submissions_utm.sql
Normal file
@@ -0,0 +1,22 @@
|
||||
-- 0089_website_submissions_utm.sql
|
||||
--
|
||||
-- Capture UTM attribution columns on website_submissions so the
|
||||
-- Marketing report (and downstream attribution analysis) can group
|
||||
-- inquiries by campaign / source / medium without re-parsing the JSON
|
||||
-- payload on every read.
|
||||
--
|
||||
-- All five columns are nullable: UTM presence is opportunistic
|
||||
-- (driven by whatever the marketing site's tracker plumbed through),
|
||||
-- not a hard requirement on intake. Index over (port_id, utm_source,
|
||||
-- received_at) makes "campaign performance for the last 90 days" a
|
||||
-- single index scan.
|
||||
|
||||
ALTER TABLE website_submissions
|
||||
ADD COLUMN utm_source text,
|
||||
ADD COLUMN utm_medium text,
|
||||
ADD COLUMN utm_campaign text,
|
||||
ADD COLUMN utm_term text,
|
||||
ADD COLUMN utm_content text;
|
||||
|
||||
CREATE INDEX idx_ws_utm_source
|
||||
ON website_submissions (port_id, utm_source, received_at);
|
||||
@@ -54,6 +54,15 @@ export const websiteSubmissions = pgTable(
|
||||
/** Capture-time metadata for debugging. */
|
||||
sourceIp: text('source_ip'),
|
||||
userAgent: text('user_agent'),
|
||||
/** UTM attribution columns. Opportunistic — populated when the
|
||||
* marketing site's tracker pulled them out of the query string or
|
||||
* the referrer. Indexed jointly with port_id + received_at via
|
||||
* migration 0089 for fast per-campaign rollups. */
|
||||
utmSource: text('utm_source'),
|
||||
utmMedium: text('utm_medium'),
|
||||
utmCampaign: text('utm_campaign'),
|
||||
utmTerm: text('utm_term'),
|
||||
utmContent: text('utm_content'),
|
||||
receivedAt: timestamp('received_at', { withTimezone: true }).notNull().defaultNow(),
|
||||
/** Triage workflow state. Default 'open'; transitions to
|
||||
* 'converted' (operator created a client/interest from this row),
|
||||
@@ -70,6 +79,7 @@ export const websiteSubmissions = pgTable(
|
||||
index('idx_ws_port_received').on(table.portId, table.receivedAt),
|
||||
index('idx_ws_kind').on(table.kind),
|
||||
index('idx_ws_triage_state').on(table.portId, table.triageState, table.receivedAt),
|
||||
index('idx_ws_utm_source').on(table.portId, table.utmSource, table.receivedAt),
|
||||
],
|
||||
);
|
||||
|
||||
|
||||
Reference in New Issue
Block a user