Software Updates

Keep the investor site out of search and unlink it

• Every response on investor.katura1999.com now sends X-Robots-Tag
• noindex, nofollow (the page already had a noindex meta tag; the header
• covers every path on the host). The Investors link is removed from the
• retail footer and from the mining site's header and footer, which
• pointed at investors.katura1999.com. The page itself still works for
• anyone given the link.

Sign B2B email, proposals and reports as Rosser McIntosh

• The From name, signatures, proposal and assessment PDFs, the unsubscribe
• page and the outreach writing prompts now use Rosser McIntosh (one
• constant, KATURA_CONTACT_NAME). The self-introduction detectors match the
• new name as well as the old one. The investor page and the K99 team bio
• are unchanged.

Use rosser@katura1999.com as the B2B contact; read both outreach inboxes

• One constant (src/lib/contact.ts) now holds the address used as the
• outreach sender and reply-to, in signatures, proposals, assessment PDFs,
• llms.txt, JSON-LD and lead notifications. Env overrides still win.
• The Gmail reply poller reads rosser@ and the legacy zack@ (the first 97
• emails went out from zack@, so their replies land there). A mailbox that
• fails is recorded in the heartbeat without stopping the other, and a
• message seen twice through an alias is processed once.

Remove dead appointment-reminders cron job

• src/lib/appointments/reminders.ts queried an "Appointment" table that does
• not exist and swallowed the error, so the job ran every 2 hours (and inside
• daily-all) and never sent anything. Consultation reminders already run from
• /api/cron/consultation-reminders.

serve k99.katura1999.com's own robots.txt, sitemap and llms.txt

• k99 joins the B2B host map (route prefix /platform), so its discovery files are rewritten to its own routes.
• platform/robots.ts becomes platform/robots.txt/route.ts with the same rules, plus their /es and /pt variants.
• New platform/llms.txt.
• /login and /signup are dropped from the platform sitemap.

add salesguide.katura1999.com, the client walkthrough

• Sections: why a jeweler rather than an agency; the four money levers (be found, get contacted, say yes to more work, sell before you make); seven service cards (search & AI visibility, paid growth, websites, CAD, renders, design & bench support, wholesale) each with who it is for, what we do, how it makes money, and price; a break-even calculator (the visitor's own average sale and margin -> extra sales a month to cover each monthly program); how we start (free assessment -> walkthrough -> $500 Fix Sprint -> program).
• Prices come from OFFERS; Portuguese labels and prices are localized (US$ 2.500/mês, "A partir de ...") and a test fails if English is left in a Portuguese price. No result is promised; the only arithmetic is the visitor's.
• proxy: salesguide.* rewrites to /salesguide with the html lang pinned (/pt -> pt); /salesguide/* redirects to the clean URL. robots.txt, sitemap.xml (with hreflang) and llms.txt are served from its own routes, and it is indexable only on its own host.

make the B2B sites findable and measurable

• src/lib/seo/b2b-sites.ts maps B2B hosts to their route trees and builds their robots.txt (AI crawlers named explicitly) and sitemaps.
• The proxy matches only those three files explicitly; B2B hosts are rewritten to their own routes, every other host passes straight through to the retail files.
• services.: new robots.txt, sitemap.xml and an llms.txt built from OFFERS/SERVICES, plus JSON-LD (Organization, ProfessionalService and an OfferCatalog with structured prices).
• marketing.: new llms.txt; robots.txt now names AI crawlers. The dead robots/sitemap branch in the marketing proxy section is removed.
• NEXT_PUBLIC_GA_B2B_ID: a separate GA4 property for marketing., services. and salesguide., so B2B leads never mix into retail reports. The one existing GA loader serves whichever property the host reports to; ad pixels stay retail-only.
• The consent banner (same component, cookie and rules) now shows on B2B hosts, in Portuguese on /pt; GA stays inert until Measurement is allowed.
• generate_lead / form-start events from the marketing and services forms are forwarded to GA4.

drop the always-waived $1,250 onboarding fee

• config: ONBOARDING_FEE_* and the waiver texts are gone; SETUP_INCLUDED_BOUNDARY replaces the Growth/Partner boundary. FIX_SPRINT_NEXT_STEP_TEXT states the paid next step once.
• services page: the waiver box is removed.
• assessment request: no waiver entitlement on the record; the internal alert drops the waiver note; the confirmation email names the $500 Fix Sprint instead.
• assessment delivery email: names the Fix Sprint with its credit terms, plus the $100 CAD credit.
• assessment PDF: points to the Fix Sprint without a price (the free report never carries pricing) and says there is no onboarding fee.
• admin assessment queue: the waiver chip is removed.
• revenue model: onboarding revenue is 0 on every channel.

cap the Fix Sprint scope and stop the credit stacking

• Scope was open-ended ("the top fixes from your assessment", three website fixes); on a messy site that is 10-15 hours. It is now about five hours of fixed deliverables: up to 10 Google Business Profile corrections, store structured data for one location, a five-question AI-search check before and after, the single highest-priority website fix, a review-request message with link and QR, and a report with a next-step plan and a 30-minute walkthrough.
• The $500 credit applies only to a standard-price monthly program and never combines with founding-client pricing; otherwise a converting founding client would get the sprint for free.
• Google can keep some profile edits under review for up to 30 days, so the terms promise submission during the sprint, not approval.
• Google Business Profile terms: the client keeps ownership of the profile (a free Google service) and Katura is added as a manager.
• Terms render as a list on the card; EN/PT FAQs match the new scope.

add the $500 K99 Fix Sprint as the paid first step

• OFFERS["fix-sprint"] in src/lib/prospecting/config.ts is the single definition: scope (assessment fixes, Google Business Profile cleanup, structured data, AI-search fixes, up to three website fixes, review setup, before/after report) and terms (14 days from access; the full $500 credited to month one if a monthly program starts within 30 days; no ranking or revenue promises). Proposals can now quote it.
• services.katura1999.com renders it as a "Start here" card above the monthly programs.
• marketing.katura1999.com FAQ (EN and PT) offers it as the smaller way to start.
• The "$1,250 -> $0" anchor on the free assessment is removed: the assessment was never sold at $1,250 (stated price $125, none paid), which fails the reference-pricing rule the constant itself documents.
• assessment-request falls back to TENANT_ZERO_ID instead of the nonexistent "katura-tenant-zero", which would have failed the FK.

look keys up by prefix and enforce per-key rate limits

• validateApiKey loaded every active key on the platform and bcrypt-compared each one, so every API request cost O(keys) bcrypt rounds — a slow path and a cheap way to burn CPU with junk keys. It now rejects anything that isn't ktr_(live|test)_<48 hex> outright and only compares keys sharing the stored keyPrefix (every existing key already has one in this format), using async bcrypt.
• The v1 API (authenticateRequest) ignored SaasApiKey.rateLimit. It now enforces it per key per minute and returns the standard 429 envelope. Like the tenant API it fails open if Redis is unavailable.

stop calling dropped loyalty tables and the nonexistent Customer model

• /api/loyalty and /api/loyalty/history now return 501 LOYALTY_UNAVAILABLE for signed-in users. src/lib/loyalty queries "LoyaltyPoints"/"LoyaltyTier"/"LoyaltyTransaction", which full_schema_sync dropped, and nothing ever awarded points. The lib is marked unused and kept as the reference for a Prisma rebuild.
• /api/platform/customers/export called db.customer.findMany, but there is no Customer model, so the tenant admin's Export button always failed. It now exports users who ordered on the tenant's storefronts (counting only that tenant's orders) from fields that exist on User, and prefixes formula-looking cells to prevent CSV injection.

overdue tracking, receipts, itemized email + PDF, agreements, refunds, deposit→balance, customer linking, reminders, partial pay, presets, bulk/export

• Letter / A4 PDF of the invoice (lib/invoices/pdf.tsx, @react-pdf with the embedded Playfair/Geist faces): header, bill-to, items, tax breakdown, deposit credit, payments, notes, the accepted agreement, PAID stamp. "Print / PDF" on the admin page opens it; "PDF" on the client page too. /admin/invoices/[id]/print now redirects to it.
• Invoice email is itemized (lines, tax, credit, address) with the PDF attached; variants for updated / reminder / due-soon / due-today / overdue / final. Brevo failures now throw instead of being swallowed.
• Payment receipt to the client after every payment (paid-in-full one sent once, receiptSentAt) and a short staff notification; refunds too.
• Daily sweep (lib/invoices/cron.ts, run by /api/cron/invoice-reminders) flips past-due invoices to OVERDUE and runs the sequence due in 3 days → due today → 7 days overdue → 3 weeks overdue, per invoice (autoRemindersEnabled), one email a day at most, stale stages skipped. Editing an overdue invoice with a future due date reopens it.
• Deposit / repair / balance / stone invoices show their agreement on the pay page; the client types their name to accept, the acceptance is recorded (SalesInvoiceAgreement: terms snapshot, IP, UA) and linked to the payment; the pay route refuses until accepted. Terms version pinned at send time. Shown on the admin page and in the PDF.
• "Refund via Stripe" (owner/manager) on card payments, recorded as a negative ledger row; charge.refunded / charge.dispute.* webhooks update the invoice (DISPUTED while open, PAID when won, REFUNDED when lost). amountPaid / amountDue / refunded / status are re-derived from the ledger.
• "Create balance invoice" on a paid deposit pre-fills the client and lines and credits what was paid (after tax). parentInvoiceId links them.
• Customer lookup (website accounts + CRM) in the form, linking customerType/customerId and pre-filling the address; account pages and the customer timeline show linked invoices.
• Saved line items (star a line to save it; "Add saved item…" picker).
• "Allow partial payments" (+ minimum): the client types an amount on the pay page; the balance stays due.

Merge pull request #6 from ZRosserMcIntosh/claude/sharp-bell-t1kdgc

• Invoices: edit, Stripe-calculated SC sales tax, client address, guaranteed-payable send

edit, Stripe-calculated sales tax, client address, guaranteed-payable send

• /admin/invoices/[id]/edit + PATCH /api/admin/invoices/:id for any unpaid open invoice (draft, sent, viewed, overdue). Saving re-prices it, replaces line items in one transaction, expires the Stripe page the client may already hold at the old amount, re-checks the pay link, and can email the updated invoice. Locked once a payment is recorded.
• Tax modes: Stripe Tax (shop pickup = head office in Stripe Tax settings, or shipped = client address), manual rate, or none. Live Stripe preview in the form with the jurisdiction breakdown; readable errors when Stripe Tax is off / unregistered for the state. Paid invoices are filed as Stripe Tax transactions. Per-line "taxable" toggle (non-taxable lines use txcd_00000000).
• Street/city/state/ZIP/country on the form (billingAddress existed but was never collected); shown on the admin, print and client invoice pages.
• Send builds the exact Stripe Checkout page the client will get and expires it; if Stripe refuses, nothing is sent and the reason is shown. "Check pay link" does the same on demand. Email is awaited (it was fire-and-forget in a serverless function) and failures are reported.
• Client page: Pay only on payable statuses, clear draft/void messages, friendly errors instead of raw JSON, itemized Stripe checkout with a tax line, and the success page records the payment itself so a late or lost webhook can't leave a paid invoice showing unpaid.

stop answering the storefront's own /api fetches with an empty 204

• The Clarity hard-navigation branch turns a soft navigation into an excluded
• page into a full page load by answering it with a 204. It recognised a soft
• navigation by Sec-Fetch-Dest: empty, Sec-Fetch-Mode: cors, same-origin and a
• storefront Referer, which is exactly what a page's own fetch('/api/...') sends,
• and /api is not a storefront segment, so isClarityOffPath() was true for it.
• With NEXT_PUBLIC_CLARITY_PROJECT_ID set, every GET /api/* from a storefront
• page by a visitor who allowed Measurement got an empty 204: /api/cart read as an
• empty bag, checkout bounced back to the cart, the success page failed to load
• its order and never fired the purchase. Exclude /api from the branch.

remove broken ShipStation Integration Tests workflow

• The workflow never ran a test: GitHub fails it at setup because it pins
• actions/upload-artifact@v3, and past that it would fail on npm ci (the
• repo uses pnpm, there is no package-lock.json) and on shipstation-test.ts,
• which does not exist. The ShipStation test scripts stay for manual runs.

keep main's 20261001 EngagementLead migration

• The overwrite keeps run-integration's tree, but this migration is already
• applied in production. It is idempotent (ADD COLUMN IF NOT EXISTS), and the
• schema here already declares the columns. Keeping the folder keeps the
• migrations directory in step with _prisma_migrations.

Merge main into run-integration, keeping run-integration's tree

• Rosser and Scoz agreed (2026-10-12) that the conversion work replaces main's
• code from f96633ca onward. main's 59 commits stay in history; their changes
• are not carried into the tree.

Merge branch 'f48-review-fixes' into run-integration

Merge branch 'final-review-fixes' into run-integration

cover Clarity and Google Ads together on the consent banner

• Accept all with both tags; withdrawing only Advertising clears _gcl_* and keeps Clarity;
• withdrawing only Measurement leaves _gcl_* alone.

clarify the dashboard mask is a backstop