Software Updates

waive the onboarding fee for inbound assessment leads

• the API writes an "entitlements" block onto the submission at capture time, with expiresAt explicitly null
• the internal notification carries a flagged callout so whoever quotes sees it before pricing anything
• /admin/assessments shows it on every row — every lead in that queue arrived through the form, which is exactly the stated condition
• the jeweler's confirmation email states it in writing, so they hold it independently of our records

Merge remote-tracking branch 'origin/main' into worktree-prospecting-upgrade

three-step monthly ladder, tiered project pricing, booth QR

• Pricing was uneven rather than wrong: the cheapest way in was $2,000/mo
• + $1,250 onboarding + ad spend, which is a ~$4,750 first month for a
• jeweler whose whole ad budget is often $1,000-2,000. And a plain
• solitaire and an articulated mechanism were both quoted "from $325".
• Monthly ladder, rendered from OFFERS via a new recurringTier field:
• K99 Visibility $1,500/mo local search, GBP, reviews, AI search
• K99 Growth $2,500/mo + one ad platform <- flagged as the start
• K99 Partner $4,500/mo + Google and Meta, CRO, credits
• $1,500 over $1,499: every other K99 price is round ($3,500, $1,250,
• $325), so a charm price would be the only one on the page reading as
• retail discounting, and it has to be said out loud at a booth all day.
• It also sits $250 above standalone Local SEO while containing it, which
• makes the upgrade argument itself.
• Project work now has real ladders instead of one "starting at":
• Websites $3,500 sprint / $8,000-15,000 rebuild
• CAD $200 simple / $325 standard / from $550 complex
• CAD Desk $1,250 for 5 ($250 ea) / $2,250 for 10 ($225 ea) — was
• $1,500 for 5, an 8% discount for committing to monthly volume
• Renders $125 image / $400 four-pack / $300 360 spin / $600 launch
• — priced publicly for the first time
• local-seo and paid-traffic drop off the public page (they are components
• of the programs now) but stay in OFFERS, so proposals can still quote
• either on its own. PROPOSAL_TIERS now presents the same ladder outbound,
• so a proposal and the website never quote different numbers.
• Booth QR (src/app/pitch/share-qr.tsx): fixed top-right button opens a
• sheet with the branded code for /go/services-pitch — the attributed
• smart link, which already resolves. Verified by decoding the rendered
• screenshot: reads back the correct URL down to 25% scale. Lazy — nothing
• is generated until first open. Falls back to an unbranded code if the
• logo asset fails, because a plain QR that scans beats a pretty one that
• never appears.
• Mobile: no horizontal overflow at 390px (measured); card padding cut from
• p-8 to p-6 so text isn't squeezed into a ~270px well; wholesale grid goes
• single-column; hero gets right padding so the headline clears the QR
• button.
• Also: the Modern Luxury / The Atlantan press logo is white-on-transparent
• artwork and was rendering invisibly on the light press strip. Inverted via
• CSS so the original asset stays untouched.

stop claiming the assessment is written by hand

• The confirmation email said "a real person goes through every submission by
• hand" and justified first-come-first-served with "because each one is done
• properly rather than generated." The report is generated and then reviewed
• and approved — so that was an overclaim, and it also implicitly denied that
• any AI is involved.
• Reworded to the part that is verifiable and still carries the weight: we look
• at the site, socials, search and AI visibility; every finding is tied to
• something we can point you at; the report is reviewed and approved before it
• goes out. First come first served is now stated as the policy it is —
• "requests are worked through in the order they arrive" — rather than
• justified by a mechanism that isn't true. Neither version says anything about
• how the report is produced, which is the right amount to say.
• The same claim was on the page ("go through your whole online presence by
• hand") and the in-browser success screen ("A real person here will go through
• your website…"), stated more strongly than the email. Fixing only the email
• would have left the page contradicting it, so all three now match.
• Both the API route and the form carry a COPY RULE in the header: claim
• neither extreme — not "written by hand", not "instant" — and promise the
• 48–72 hour window and the contents, not the process. Internal admin copy
• corrected the same way ("nothing goes out unapproved" rather than "a manual
• job"), since it was describing the pipeline wrongly too.
• Also removed the early-access checkbox from the form. It offered the project
• workspace, whose section came off the page earlier, so it was asking about
• "your system" with nothing on screen explaining what that meant.

Merge remote-tracking branch 'origin/main' into worktree-prospecting-upgrade

file every ad-hoc migration by domain and date-stamp them

• scripts/db-migrations/applied-sql/<domain>/ is the single home for hand-run SQL: 222 files across 32 domain folders, with a generated README index listing every file by date
• scripts/db-migrations/runners/ holds the 21 one-off Node/TS/shell runners (zero references anywhere, safe to relocate)
• supabase/storage-policies/ holds the 3 bucket-policy files that were loose at the supabase/ root
• every archived .sql now opens with its authoring date as a comment (-- 9 MAY 2026), taken from the filename timestamp where one exists, otherwise from the commit that introduced the file
• prisma/migrations/<ts>_<name>/migration.sql — Prisma checksums these in _prisma_migrations; editing one breaks migrate deploy on Vercel. Added a README there explaining that, and why loose .sql must not go back in.
• supabase/migrations/*.sql — the Supabase CLI owns that flat layout and every filename already carries its date.
• docs/**/*.sql — documentation artifacts, referenced by name from many docs.

web dev section, colour press, $100 CAD credit, admin queue

• New Websites & Web Development block, given its own full-width layout with the stack named (Next.js/React/TypeScript, Postgres/Prisma/Supabase, Stripe and Shopify/WooCommerce migrations, Vercel, Core Web Vitals, structured data, 24 locales). It's the one service where the buyer — or the buyer's nephew who "does computers" — wants the actual stack before they'll believe it. Added at page level rather than to SERVICES, which is organised around jewelry craft and also feeds the homepage and /services grids.
• Press strip moved above the services grid and rendered in full colour.
• Every service CTA ("Audit My AI Visibility", "Build My Brand", …) now links to #assessment instead of a service detail page. They were the only dead ends on the page — someone clicking those wants us to do it, not to read.
• $100 new-client credit toward a first CAD design, under the price grid.
• Removed the "Apply for a wholesale account" CTA and the whole "people who'd actually do the work" section.
• Renders gallery moved to sit directly above "What it costs" (still hidden while its folder holds no images).
• The assessment intro now makes the follow-on explicit: the report already says what to work on, so there's no discovery phase to pay for and we can start immediately.
• Explicit data promise under the form: never sold, rented, or shared, used only to prepare the assessment, deleted on request.

admin/collections: fix per-keystroke focus loss; make the page campaign-ready

• Real <form>: Enter submits, spinner while saving, no double-submit, disabled without a name
• Client slug generator now mirrors the server's ("Silver & Pearls" -> silver-pearls, not silver--pearls), with a live URL preview and blur-time normalization
• Featured is exclusive server-side: featuring one collection un-features the rest, so the /collections banner has one owner
• revalidatePath on every mutation route: admin edits and curation go live immediately instead of waiting out the 30-min ISR window
• Manage-products search matches metal/gemstone/collection name; 'Select all shown' bulk-select; 'N will move here / N will leave' summary before saving
• Delete uses a styled confirmation dialog with piece-count-aware copy instead of the native confirm()
• Featured badge overlays the card image; mosaic list gets a loading spinner; create dialog scrolls; deprecated onKeyPress replaced

narrow to services sellable today; add renders gallery + press

• Removed the whole "approve your piece on a video call" section and the project-workspace early access section. The in-meeting tooling and the client workspace are how we WORK with clients, not something on sale, so they belong on the page only once they are. demos.tsx is kept, unrendered, for when that changes; the accuracy contract at the top of pitch-client says why.
• Casting & Production dropped from the service grid, and Bridal Growth System from the price list. Both are filtered at the page level rather than deleted from SERVICES / OFFERS, because those catalogues also drive the homepage grid, /services, and the outbound proposal generator, where they still belong.
• "Katura Wholesale — 7.77 Collection" shows as plain "Wholesale" with the 7.77 Collection called out in the body copy. Display-only override, so proposals keep the formal name.
• Identity is now explicitly K99 Jeweler Services throughout — hero eyebrow, metadata, footer.

jeweler services page at pitch.katura1999.com

• Service cards render from SERVICES in lib/k99/capabilities, which declares itself the single source of truth and forbids present-tense promises for anything "rolling_out". The status chip renders next to every card, so the page cannot drift from it. K99 Business Platform correctly shows "Rolling out"; the six sellable services show "Available now".
• Prices render from OFFERS in lib/prospecting/config — the same productized catalogue already used in proposals sent to prospects, with real figures, scope and boundaries. Do not hand-write prices on the page; change them there and both stay in step.
• The assessment deliverables are derived from the actual generator: evidence categories and sources from JewelerEvidence, findings / quickWins / plan90Day / independentFactCheck from GeneratedProposalV2, and the copy-ready asset + implementation + verify-after steps from ComplimentaryAction, which is gated so no brief ships without at least one verified free action. If the generator changes, change that list.
• The four animated demos recreate software that ships today (live meeting translation, CAD shared in-call, in-call invoice + e-signature, and the project workspace using its real status values). Each is labelled an illustration rather than a live session.

throttle the translation tail — the other 5x of the DeepL burn

• af432921 stopped the minutes page re-billing whole transcripts. This is the
• live-meeting half of the same problem, plus the latency defects found while
• measuring it.
• DeepL hit 282,000 characters in one day, exhausting the quota and tripping
• the circuit breaker nine minutes into a call. Root cause was not the
• provider: the same speech was billed five to six times over, because the
• incremental translator retranslated the volatile tail on EVERY Deepgram
• interim (~3-6/sec). Measured on one 49-minute meeting: 828 chunk requests
• for 128 sentences, 21,556 chars of tail churn against 4,674 chars of actual
• speech. And that is one browser — each participant translates independently,
• so a two-person bilingual call runs two of these.
• Tail throttle (incremental-translate.ts): identical tails are deduped,
• one request in flight at a time, issues spaced by tailMinIntervalMs
• (700ms default), and only the newest pending tail is ever sent. Committed
• chunks are untouched, so captions still progress at full cadence — only the
• speculative last few words lag. Waives the cooldown right after a chunk
• commits, since commits are bounded by speech cadence, not interim cadence.
• Finals de-blocked (translate.ts): the MeetingTranslationCache INSERT was
• awaited before responding, holding every final caption behind a
• cross-region Postgres write (iad1 -> us-west-2). At matched character counts
• finals cost a flat +1,450ms over chunks — even 0-15 char finals ran 1384ms
• vs 2845ms. Now runs via after(). This matters more since af432921 raised the
• persist cap to 1000 chars: 8x more rows written, all of it blocking.
• Stale finals can no longer corrupt the live sentence
• (meeting-room-client.tsx): finals resolve at p50 2.9s / max 5.7s, by which
• time the speaker has moved on. The handler called incrementalRef.reset() and
• nulled translationSinkRef unconditionally, wiping the translator mid-way
• through the CURRENT sentence and spilling its output into the transient
• overlay. 16% of requests (153/956) landed out of order. Now guarded by a
• segment token; the transcript update still always runs, since it is
• addressed by line id and can only correct its own sentence.
• Pair mode removed (transcript-view.tsx): one layout now — original left,
• translation right. The old EN|PT column pinning needed a full transcript
• pass PER COLUMN to render text already on screen in its own language, and
• same-language lines were billed as auto-detect round-trips that returned
• the input. Net -213 lines.
• MeetingTranscript gains translatedText/translatedLanguage, written back
• (non-blocking) by the minutes route. Exports — PDF and email have no
• translation logic at all — can now render Original | Translation off the
• row. Migration is additive and idempotent; readers must check
• translatedLanguage before trusting the text.
• Subtitle overlay: pointer-events-auto on the scroller. The floating wrapper
• is pointer-events-none so clicks fall through to the video, but that also
• swallowed wheel events, so the existing sticky-bottom scroll-back could
• never fire and older lines were unreachable. Plus persisted height/width and
• +50% default font and overlay width, host and guest.

piece previews in admin + campaign-grade public collection pages

• every card now previews its actual pieces — first 8 live products as thumbnails (hover = name/price, click-through to the product) with an honest live count (the old count included drafts/archived)
• assignment sheet: each product row shows metal · gemstone and, when the piece lives in another collection, an amber 'in <Collection> — will move here' warning (collectionId is a single FK; moves were silent before)
• product search now matches metalType and gemstone ('pearl' finds pearls)
• create/edit form exposes what the API always accepted: Featured toggle (labeled as the campaign-target switch) + SEO title/description
• renders a real hero: collection name, curator's description, piece count, hero image with overlay when set (before: NO copy at all — an h1 over a bare grid, unfit for paid traffic)
• ItemList schema added alongside CollectionPage + Breadcrumb
• client grid h1 suppressed under the hero (single h1 per page)
• the admin Featured toggle now actually drives the featured banner (was hardcoded to 'bridal'/first)
• admin-curated featuredImages mosaic finally shown on tiles (was saved but never rendered)

Sterling Silver — the material collection, optimized to the max

• queried by Product.metalType (NOT a DB Collection row — collectionId is a single FK, so a Collection would pull the silver Chasing Ring / Starfish / Pearl pieces OUT of their home collections; a material query lets every sterling piece live in both places)
• localized metadata in all 24 locales (CATEGORY_SEO 'sterling-silver') + nav/footer/category copy in all 24 message files
• ItemList + BreadcrumbList (via CategoryPage) PLUS CollectionPage schema and the first visible FAQ + FAQPage schema on any shop page
• CategoryPage extended with a metalType filter mode (material categories span every jewelryType; take raised to 60 for them)
• header nav, footer shop column, legacy siteConfig nav all link it
• sitemap: /creations/sterling-silver at 0.8 weekly; STATIC_CONTENT_DATE bumped to 2026-08-20
• /collections index: Sterling Silver mosaic tile (live images + count) linking to the landing page, included in the ItemList schema
• llms.txt Shop section: Sterling Silver line, worded to disambiguate retail silver jewelry from the /precious-metals buying service
• llms-full.txt: new '## Collections' section (all DB collections + the material collection) so models can recommend browsable pages, not just individual pieces

one Country control — full Central + South America currency coverage

• Product/Collection JSON-LD priceCurrency is now truthfully USD — it was labeling the unconverted USD price with the locale's currency ($5,000 ring marked €5,000 for German visitors; Merchant Center mismatch)
• /SiteMap.aspx 500 fixed (relative NextResponse.redirect throws)

drop applied one-off product-image primary data fix

• fix_product_images_primary.sql was a one-time backfill, now verified applied
• in production (0 products with images but no primary). Recoverable from git
• history if the backfill is ever needed again.

additive state-wide discovery + physical mail as a first-class channel

• discovery response now returns before/after prospect totals — the console proves every run is purely additive (discovery has never deleted, but the operator couldn't see that)
• Entire-state mode: pick a state, the console sweeps its metros one search at a time (all 50 states + DC curated in metros.ts), each new prospect auto-assigned to the metro it was found under; per-metro progress log, partial-failure tolerant, board refreshes as results land
• JewelerMailPiece model + SQL migration (supabase/migrations/20260819)
• print edition PDF = the v2 proposal + a navy closing card page with the piece's unique QR ("We found something.")
• landing page /proposal/[token] — "Prepared exclusively for <business>", call CTA + digital proposal; QR scans, views, and CTA clicks all recorded as ProspectingEvents (offline mail becomes an attributable channel)
• lifecycle: DRAFT → submit (test_sk_ dry-runs free; live needs POSTGRID_LIVE_APPROVED="true", fails closed) → webhook tracks printing/ mailed/delivered; webhook treats payloads as hints and re-fetches every letter from the API before acting
• delivery writes the timed follow-up call onto the prospect's nextStep ("delivered 47 minutes ago" call), exactly once; manual mark-mailed/ mark-delivered escape hatches for hand-assembled PRESENTATION/EXECUTIVE kits
• same integrity gates as the stage-2 proposal email (v2 + fact-check + validity window); unlike email, physical may be a first touch by design

automated site-fetch evidence — kill the manual-capture bottleneck

• Extracts: title/meta/H1s, JSON-LD types (LocalBusiness/JewelryStore/ Product incl. @graph), canonical, robots noindex, viewport, image-alt coverage, indexable prices, cart/checkout signals, platform detection (Shopify/Woo/Wix/Squarespace/BigCommerce), named nav collections, sitemap.xml status.
• Feeds the previously-dead 14-signal seo-audit.ts: assessSeo() now runs on real fetched signals — the "free SEO audit" door-opener is finally backed by data, and its quick wins quote what was actually observed.
• V3 provenance columns go live: sourceExcerpt, sourceHttpStatus, sourceFetchedAt, sourceContentHash (sha256), canonicalUrl, sourceType=FIRST_PARTY_SITE, verificationMethod=FETCH_MATCH, verificationStatus=VERIFIED, claimScope, validUntil (+90d).
• Absences are dated + scoped ("We did not identify X in our fetch on <date>"), never absolute; commerce-reality evidence deliberately feeds the "lacks e-commerce is contradicted" Luxor rule.
• Refetch supersedes prior machine-captured rows (marked STALE, never deleted — historical proposals keep their sources); human-entered evidence untouched.
• Optional PageSpeed Insights (mobile score + LCP) when PAGESPEED_API_KEY / GOOGLE_PAGESPEED_API_KEY is set; fail-soft.
• 3 new tests (fixture HTML through stubbed fetch): rich-store persona, bare-brochure absence phrasing, unreachable-site fail-soft. Full prospecting suite: 78/78.

keep media staging folders (Katura/, izzy/) out of git history

• 89MB+ of brand photos, lookbook PDFs, and campaign images were sitting
• untracked in the repo root (56 files of IDE noise). They belong in the
• media library / Supabase storage — ignoring them instead of committing
• keeps clones and deploys lean.

Merge admin walkthrough: dashboard truth, activity, orders, auth, dialogs, analytics

• dashboard: fail-closed tenant scoping, coherent stat cards, store-local days
• activity: the server page that was committed empty in May now exists
• orders: honest stats, real search, atomic money math, working cache busts
• welcome splash removed (and its re-arm on every login)
• auth/profile: session-aware logins, self photo/password, es locale saves
• dialogs: 512px cap fixed for all 81 wide dialogs; QR tracking is a real page
• analytics: one hub, four grouped tabs, URL-carried timeframe, campaigns rollup

one hub, four questions, one timeframe

• /admin/analytics/conversions|traffic|orders rendered TWO stacked layouts: the (marketing) route group's layout was a near-verbatim copy of the outer one — its own context, its own module caches, its own KPI card grid, header, and timeframe picker, plus a second tab bar overlapping the outer eight. Every visit double-fetched the 21-query conversions endpoint and showed two "days" pickers that could disagree about the period on one screen. The inner layout is now a pass-through that re-exports useMarketingContext from the real provider; the three pages needed zero changes.
• The hub nav is now grouped: Overview · Acquisition (conversions, traffic, campaigns, hero, affiliates) · Sales (orders, products, customers, reviews) · Team (team, time-tracking), rendered as a primary row plus the active group's sub-views. Every existing URL is preserved; hero, affiliates and time-tracking — pages that existed but appeared in no navigation at all — finally have a home.
• The hub's period selector now lives in the URL (?days=) and every nav link carries it, so the window follows you across tabs, survives refresh, and is shareable. Previously each surface defaulted independently.
• /admin/analytics/campaigns: smart links and QR codes in one sortable table (7d / 30d / all-time), each row clicking through to its operational page; cross-links to email campaigns and media performance. Comparing campaign assets previously meant flipping between two separate trees.
• The Marketing sidebar entry "Conversions" was a duplicate pointer into the hub — removed; its keywords merged into the single Analytics entry.
• Two dead /admin/stella/* links fixed (analytics layout, CRM marketing stub), same rot family as the Under Development drift.
• Stella Marketing Hub dropped from Under Development: it is launched.

paper-archive: client matching, historical orders on the books, honest dates

• Client matching: each card is checked against User accounts, CRM contacts, and other already-linked cards (email near-certain, phone strong, name token overlap). The review panel shows "Linked to customer · N orders" or states plainly "as far as we know, this is not currently a Katura client" with one-tap Create client record (CRM contact, source=PAPER_ARCHIVE). Linked clients flow into invoice promotion (customerType USER/CRM_CONTACT instead of ANONYMOUS).
• Record as historical order: a CONFIRMED receipt becomes a real Order — the entity every revenue dashboard and the cap-table valuation compute from — dated to the CARD via customOrderDate, tagged source=PAPER_ARCHIVE (filterable like Shopify imports), created as DELIVERED history with no fulfillment/email side effects. Line items as written; deposit noted in internalNotes; synthetic archive+ email only when the card has none (and flagged).
• Honest dates: recordDatePrecision (exact/~month/~year/unknown) set in review; order promotion requires at least a year so revenue periods stay defensible.

fix the 512px cap on every "wide" dialog; QR tracking gets a real page

• The owner's report — QR tracking data "opens in a separate window that's too
• small" — turned out to be systemic, not a QR quirk.
• DialogContent bakes sm:max-w-lg into its base class, and tailwind-merge
• cannot reconcile width classes across responsive variants. So all 81 admin
• call sites that pass an unprefixed max-w-* (max-w-4xl analytics dialogs,
• email compose, calendar events, cap-table forms, audit detail…) kept BOTH
• classes — and at ≥640px the base sm:max-w-lg won. Every dialog written as
• wide has been rendering 512px on desktop. DialogContent now applies its
• default cap only when the caller doesn't set a max-width of their own; one
• fix, all 81 sites get their intended size.
• QR codes also get the organization Smart Links already had: a dedicated
• /admin/marketing/qr/[id] page (preview, inline rename/destination editing,
• archive/delete, scan analytics with 7/30/90d windows) instead of a dialog
• bolted onto the list. New GET endpoint returns a single code with scan
• counts; list rows and the create flow navigate to the page; the old
• QrDetailDialog is deleted.

auth/profile: session-aware logins, self-service profile, es locale saves

• Both /employee-login and /login showed the password form to people who were already signed in — while any direct /admin link sailed straight through — so signing in twice felt mandatory. Both pages now check the session server-side and redirect to the callbackUrl (or /admin, /account).
• Settings → Profile rendered a self photo-upload widget for every employee, but the API it posts to was MANAGER/OWNER-only: a control the UI hands you that always 403s. Self-upload is now allowed; managing OTHERS' photos still requires manager/owner.
• Even after an upload, the JWT pinned name/image from the moment of login ("reload to refresh session" does nothing for a JWT). The existing 5-minute role re-check now refreshes name/image too.
• Nobody could change their OWN password while signed in — the PUT handled password only in the manage-others branch, so managers could set employee passwords but self-service meant the public forgot-password email flow. Own-profile password change added (min 8 chars) plus a Change Password section in Settings → Profile (en/pt/es).
• Choosing Español saved the cookie but the server preference 400'd: every adminLocale allowlist said ['en','pt'] while the admin ships es. All three allowlists now accept es, so the language survives a new device.
• The provider declared `settings` TWICE (interface, en, and pt objects) — a small orphaned block shadowed the real one in the type, which is why every t.settings.* on the settings page has been a type error masked by ignoreBuildErrors. Duplicates removed (es had the same problem); ~10 pre-existing type errors gone.

drop last splash re-arm (reset-password page)

remove the welcome splash

• A 2.8-second full-screen overlay plus 600ms fade stood between sign-in and
• the dashboard — and the login form re-armed it on every login by clearing
• the once-per-session flag, so it fired far more often than once. Confirmed
• unwanted by the owner. Both the overlay and the re-arm are gone; the
• greeting line in the header remains.

pnpm 10 + node 22 in prisma-migrate workflow

• pnpm 9 treats any pnpm-workspace.yaml as a workspace declaration and
• hard-errors on ours, which holds only pnpm-10 settings (ignoredBuiltDependencies)
• and no packages field: 'ERROR packages field missing or empty'. Local dev and
• the lockfile are pnpm 10; only this workflow pinned 9. First surfaced on the
• paper-archive push because the workflow triggers only on prisma/** paths.
• Node 20 → 22: runners deprecate 20 and were forcing 24 anyway.

paper-archive: one-tap promotion of a confirmed card into a standard SalesInvoice

• "Create invoice" on any CONFIRMED receipt/cost-sheet/note builds the same
• SalesInvoice object /admin/invoices/new creates, then jumps straight to
• the invoice editor.
• Mapping reproduces EXACTLY what is written on the card — no derived math:
• line items as written; tax and shipping as their own written lines
• (taxRateBp stays 0); a deposit already received becomes a negative
• "Less: deposit received via Zelle/Venmo" line, so the invoice's amount
• due equals the card's amount due. Internal notes carry provenance (record
• id, card date, original image link).
• Guards: CONFIRMED records only (human-verified digits), never templates or
• payment proofs, promoted at most once (linkedInvoiceId, new column —
• migration applied to Supabase and recorded resolve-style).