docs
    site-kit: Changelog
    v8.13.4.md

    @sonordev/site-kit Changelog

    8.13.4

    • Preserve the measurement and privacy client boundary in packaged layouts for Next.js webpack builds. Page content keeps its server rendering, and the optional privacy notice remains lazy.
    • Share the client runtime checks used to stamp bundled chunks and reject client code in server entries.

    8.13.3

    • Prepare form verification during field interaction so Send can use the setup already in progress. Managed forms announce when a submission is pending.

    • Limit how long managed forms wait for verification. A stalled verification keeps the visitor’s answers and lets them try sending again.

    • Explain when a server-rendered form is getting ready. An early send expires after six seconds, and answers carry over when the form loads.

    • Add an opt-in deadline for form submissions. A request without a confirmed receipt keeps the visitor’s answers visible and asks them to check with the business before sending again.

    • Track a new campaign touch when its query changes on the same page under current advertising consent. Repeated touches don't add a page view.

    • Keep an eligible first-party advertising session across pages in the same tab with Sonor's built-in privacy choices. The visitor can choose again if Sonor can't verify the existing session.

    • Give an in-flight landing view up to 150 ms to finish alongside bounded form verification. Forms can continue if the landing view is still pending.

    8.13.2

    • Add an optional Company field to the booking widget. The widget trims the name and leaves it out of the request when the field is blank.
    • Show the confirmed hold status beside Change meeting format when that control is available. The status can wrap on narrow screens.
    • Show a readable message when booking types fail to load and let visitors try the lookup again.

    8.13.1

    • Tidy the analytics-traffic contract's documentation.
    • Use /blog in the publication path examples, and in the error for a publication route that isn't a local path.
    • Stop asking again for the site's measurement configuration after an answer that would come back the same. 8.13.0 asked again after 10 seconds, 30 seconds and a minute whatever had gone wrong, so a host the project doesn't list (a 400 or a 403) cost three extra requests on every page load. It now asks again only when there was no answer at all, or the answer was a timeout (408), a conflict it can't read (409), a request to slow down (429) or a server error (5xx). Any other refusal, and a configuration that doesn't fit this site, waits for a reconnect or a reload.

    8.13.0

    • Keep Sonor's privacy choices on screen while a refresh of the site's measurement configuration is failing, so a choice in progress isn't closed under the visitor. They're offered on a site that has an enabled configuration, and on a configured site that has none in hand while its visit measurement is running (see the next entry).
    • Let a visitor turn visit measurement off while the site's measurement configuration is stale or switched off. On a policy that asks only for advertising purposes, visit measurement keeps running in that state (see the entries on analytics waiting for a visitor's choice and on stale configurations). The full choices can't be saved then, because they belong to one configuration revision, so a refusal of visit measurement is the one choice the notice takes. The built-in choices stay on screen in that state, and so does a notice the site mounts itself. Its dialog lets the visitor turn visit measurement off and nothing else: advertising is disabled and the dialog says its settings are unavailable. Refusing stops analytics at once, with no reload, and the refusal holds across a reload, into the configuration that is saved afterwards under any revision, and if the site is unconfigured. A grant is never stored in that state. When a current configuration is back, Sonor records the refusal, with every advertising purpose denied, and the notice still asks about advertising. ConsentReadContext has a new optional refusalOnly field that says the site is in that state; a consent manager can ignore it.
    • Add SiteKitMeasurement, from the new @sonordev/site-kit/measurement entry: the Resonance runtime and Sonor's privacy choices as childless siblings, for a layout that isn't SiteKitLayout. SiteKitLayout now mounts the same components, so the runtime, the default consent owner and the notice behave the same in both. Mount it once, after the page, in the layout that publishes the credential.
    • Let a BookingWidget tell Sonor where a booking came from with a new source prop ('main-site' by default; also 'audit-page', 'portal', 'proposal' and 'email-cta'). The values are exported as BOOKING_SOURCES, with BookingSource and BookingAttribution types.
    • Add a defaultGuest prop to BookingWidget that prefills the guest's name, email and phone. It fills only empty fields, so what a guest has typed is never overwritten.
    • Tag widget bookings with the booking page's campaign: createBooking now sends the utm_* parameters and the gclid and fbclid click IDs it finds in the page URL. They're read only while the visitor allows analytics, and while it's off the booking's sourceUrl is cut to the origin and path so no query string travels either. Values you pass yourself win, and a Sonor API that doesn't store them yet ignores them. Managed forms and analytics now read the same parameters through one shared reader; a form's empty utm_* value is now sent as absent instead of as an empty string.
    • Lay out the booking calendar and time list by the widget's own width instead of the window's, so a widget in a narrow column stacks. The widget now fills its parent's width, and is 340px wide in a parent that sizes itself to its content (an inline-block, or a flex item with no width); give that parent a width to change it. Browsers without container queries keep the window-width rule.
    • Fix the booking docs: the import is @sonordev/site-kit/sync, and the sync page now lists autoSelectFirstDay, every styles key, source, defaultGuest and the campaign tags.
    • Let ManagedForm apply explicit updates to an open draft while keeping its current step and other answers. Native field options can be disabled for direct selection.
    • Add a ManagedForm option to skip automatic transport retries and expose the response status on HTTP submission errors.
    • Add Sonor's privacy choices to SiteKitLayout. On a site with an enabled measurement configuration and no consent manager of its own, the layout shows them by itself after the visitor's first interaction, in the site's measured colors and type, clear of the chat launcher. A site needs no consent code or CSS for it. Advertising waits for the visitor's choice on that site, and analytics do too when the site's measurement policy lists analytics_storage among its required purposes. Set the policy link, the button label or the prompt style with privacyChoices={{ privacyUrl, launcherLabel, promptMode }} (PrivacyChoicesConfig), and turn the notice off with privacyChoices={false}.
    • Keep analytics running through a stale measurement configuration. When Sonor answers that a site's configuration is stale (a measured page moved or went away), the page used to turn analytics off site-wide until the configuration was saved again. It now keeps asking every 30 seconds, leaves advertising and measurement proof off, and lets analytics follow the policy Sonor names: they record when the policy doesn't require them, unless the visitor refused, and wait when it does. An answer that doesn't say which still turns them off.
    • Ask for the site's measurement configuration again when the read of it fails. A page whose first read failed (the network, or a server error) stayed unconfigured, recording no analytics, until a reload or a reconnect. It now asks again after 10 seconds, 30 seconds and a minute.
    • Keep a visitor's refusal of visit measurement when the site's configuration or policy revision changes, and while the site has no configuration. It stands for the same project and site for as long as the preference lasts (up to 180 days), on a reload and on a page that is already open when the revision changes, and a runtime that stops keeps it too. A grant is never carried across a revision, and advertising is asked again as before: after a kept refusal the panel's accept button reads "Allow advertising" and allows advertising only.
    • Make Sonor's built-in notice reflect the site's policy. When the policy requires analytics, the notice asks as before and the visit-measurement box starts unchecked. When it asks only for advertising purposes, analytics already record, so the box starts checked and the notice says the site measures visits, that the visitor can turn that off, and that advertising waits for their choice. Rejecting, or saving with the box unchecked, still turns visit measurement off, and a visitor who refused earlier sees it unchecked. While the controls are unavailable the notice says nothing about what is measured or can be turned off, and once advertising is allowed it stops saying advertising waits.
    • Make analytics wait for a visitor's choice only when the site's measurement policy requires it. Sonor's privacy choices offer all four purposes, and they used to hold analytics back on any configured site where they were mounted, even when its policy asked only for advertising purposes, so such a site recorded no page views until a visitor opened the choices and allowed measurement. Now one rule decides: analytics wait for an explicit grant only when the policy lists analytics_storage among its required purposes, as before. On a site whose policy lists only advertising purposes they record as they did, advertising still waits for the visitor, and a visitor who declines visit measurement stops them. An explicit refusal always stops analytics. A site's own consent manager is unchanged: what it declares counts, and analytics don't run ahead of its answer.
    • Stop Sonor's privacy choices, including a ResonanceConsentPreferences the site mounts itself, from holding back analytics on a site with no measurement configuration. That site records analytics as it did before, and the layout's notice isn't shown or downloaded there.
    • Let a site's own mounted notice or consent manager take the place of the layout's default. A ResonanceConsentPreferences the site mounts itself takes over, and a choice the visitor already made carries over to it when it keeps the default maxAgeDays. A site with its own consent manager passes privacyChoices={false} as well as registering its adapter with registerResonanceConsentAdapter, so that consent manager is the only one asking. Once a consent manager's adapter has registered, the layout never offers its built-in choices again on that page: if the adapter unregisters, nothing that needs consent runs until it registers again.
    • Keep one Google click identifier when a link carries more than one kind: gclid, then gbraid, then wbraid. A link that repeats any of them still carries none.
    • Send the campaign source marker (sonor_source) with the page view only.
    • Stop a refused measurement request from pausing the site's other Sonor requests, so forms keep submitting. The new sonorFetch option forbiddenIsRefusal is for a route whose 403 refuses one request and leaves the credential good. A 401 still pauses.
    • Leave Sonor's privacy notice out of the analytics page-text scrape, so a page reads the same with or without it. A page's own dialog elements are read as before.

    8.12.0

    • Add opt-in footer privacy settings, a first-visit panel and inherited theme tokens to the existing consent component. Customize keeps the native dialog and returns focus to the initiating control. Existing callers retain the floating launcher and dialog presentation.

    8.11.0

    • Add opt-in first-party privacy preferences for sites without an existing consent manager. Visitors can choose measurement and advertising separately, reopen their choices, and withdraw. Preferences bind current native configuration and policy revisions and expire independently of native receipts.

    8.10.0

    • Add opt-in Google address suggestions for existing managed text fields. Manual entry stays available, and the same controlled input works in classic, spotlight and stage forms. Suggestions load after interaction, support keyboard and touch selection, and use Sonor's managed browser key.

    8.9.0

    • Keep the CTA bar's actions and page content server-rendered on dynamic routes with Next.js Cache Components. Pathname-dependent CTA behavior and the Resonance runtime wait inside their own Suspense boundaries.

    • Add @sonordev/site-kit/resonance, the measurement runtime that connects your site's consent manager to scoped consent receipts and approved advertising destinations. Register one adapter for the consent manager you already use; the runtime reads its current choices, never creates a banner, and keeps the visitor proof in memory only. SiteKitLayout mounts it as a childless sibling, so pages and managed forms render the same when measurement is unavailable. Google tags load only after the required advertising grants. Sites that don't configure it behave as before.

    • Gate analytics collection, identity initialization, Signal and retries by the visitor's current purpose permission. Explicit denial drops pending tracking work, and a later grant starts fresh without replaying what was denied. A site with no configured requirement keeps its first-party analytics behavior, recorded as an unknown policy rather than a consent grant. Forms and chat keep working without optional measurement.

    • Show an experiment variant as a measured exposure only when the server confirms the visitor's current assignment. Without that confirmation, or without consent, the control content shows. Accepted forms are still recorded as conversions by the server, never by the browser.

    • Add the Meta browser pixel loader, switched off in this release. 8.9.0 can't start it: this build implements no loader controls revision, so even a capability witness from Sonor's server can't enable it, and a later release turns it on. When it's on, it will load Meta's script only after the three advertising grants, on pages a person has approved, with a clean address, no fragment and a clean referrer, outside frames, previews and signed-in areas. It mints Meta's own first-party cookies and sends no browser events, passes no user data, reads nothing from the page and attaches no listeners. A site that already has a Meta pixel or a tag manager gets a status code instead of a second pixel. Withdrawing consent pauses the pixel and expires _fbp and _fbc. The same-page cookie observation now also requires the page to be approved. Read getResonanceMeasurementStatus() for the current blocker codes, and see the Resonance page for the Content Security Policy hosts a strict site will need.

    • Attach one optional Google click identifier to a new consented page-view occurrence. Only the current matching address is read, after advertising permission, including when analytics consent is denied. Ambiguous values are rejected, and nothing is kept in query history or browser storage.

    • Load less for the same behavior: consent state is read through smaller shared readers that keep permission checks synchronous across bundles, and campaign validation schemas stay out of the deferred Signal runtime.

    • The Resonance schemas and rules this release uses are the ones published in @sonordev/contracts 2.22.0.

    8.8.1

    • Add optional full-wordmark presentation to runtime OG cards. Branded cards keep one photograph while fitting the title, and existing cards retain their layout. Use resolved logo assets and intrinsic dimensions with the metadata-file factory.

    8.8.0

    • @sonordev/site-kit/portfolio/contract adds the verification, a proof-stage case study section for a build a Lighthouse run can't honestly score, such as an app behind a sign-in. It's a short list of checks, each saying what was checked, where, how, when, what came out and what it doesn't cover. New: portfolioVerification in PORTFOLIO_SECTION_TYPES (in the proof stage), verificationProblems, readVerificationChecks, verificationLink, isVacuousScope, isPlaceholderText, isRealDay, latestVerificationDay, PORTFOLIO_VERIFICATION_JSON_SCHEMA, the PortfolioVerificationData and VerificationCheck types and the limits VERIFICATION_MAX_CHECKS, VERIFICATION_FIELD_MAX_CHARS and VERIFICATION_EARLIEST_DAY. Nothing was removed or renamed. A Record<PortfolioSectionType, ...> of your own needs an entry for portfolioVerification before it type-checks.
    • A verification completes the proof stage on its own once it has a check a page can show: caseStudyStageStatus accepts it where it expected a Performance section (STAGE_CORE_ALTERNATES, stageCoreSections), and now reads each section's data to tell. A reported number's date has to be a real day; 2026-02-31 used to pass. The same code ships as @sonordev/contracts 2.16.0.
    • Analytics, the layout, SEO, chat and popups load about 4 KB less gzipped JavaScript than they did in 8.7.0. The message a framed page posts to tell its embedder it has painted lived in the case study rules, so every page carried all of them. It's now its own small module, and @sonordev/site-kit/portfolio/contract still exports it.

    8.7.0

    • Add opt-in managed landing-page reads and a bounded server-rendered layout through website/landing/server. Published reads are site scoped and uncached. Private previews use inert conversion controls and suppress reporting.
    • Share campaign normalization and the funnel cache tag with @sonordev/contracts. Existing authored landing-page imports remain available.
    • llms.txt describes each page with its best source: the page's public summary, then its curated meta description, the meta description the page serves, its schema description and, last, a cleaned copy of its scraped text. A summary that mentions a phone number or an email address loses just that part and is still used; it used to be thrown away whole, and the page fell back to its scrape. Notes are cut at a sentence or word boundary, and a lead-in such as "This page covers" is dropped.
    • A page whose title is its path is named from the path ("Accounting", not /features/accounting). A page that answered with an error, a noindex page and a utility page (cart, thank-you, login) are left out, and each path is listed once.
    • The page index lists the home page and the key pages first, then one group per section of the site, with the legal pages last. When maxPages is smaller than the site, every section stays represented, most valuable first, instead of the end of an alphabetical list being cut.
    • Sections now read About, Contact, Services, Site Pages, Portfolio, FAQ, with ## Optional last. The contact block prints an address on one line with hours, and is left out when it has nothing in it. Service links are absolute URLs. The line under the name is the first sentence of the description, not the text up to its first full stop.
    • getLocalData fills gaps field by field. An empty field from Sonor no longer deletes the business name, description, phone or address the site supplies, and the site's data is read whenever Sonor leaves services, FAQs, pages or those fields empty.
    • The analytics page-text scrape keeps elements apart and leaves out menus, form fields, buttons and dialogs, so stored page text no longer runs a heading into the paragraph after it.

    8.6.0

    • Managed file fields can accept private documents with drag and drop, upload status, removal and retry. Configure validation.private_attachments and validation.max_files to accept up to four PDF, JPEG, PNG or WebP files, each up to 10 MB. This requires Sonor's private attachment endpoints; documents never fall back to public media uploads.
    • Lazy date and file controls continue loading correctly when React Strict Mode cleans up and restarts their effects.

    8.5.2

    • Booking requests include the browser's existing visitor and analytics session IDs so Sonor can connect the recorded journey to the accepted booking's CRM contact. Slot-hold session ownership stays separate.
    • The shared booking API covers both the widget and custom booking screens, and leaves tracking IDs absent when analytics hasn't created them.

    8.5.1

    • Add AiDiscoveryLinks and SiteKitLayout.llmsDiscovery for static HTML links to public AI resources, preserving framework font and stylesheet preload headers across host adapters.
    • Keep HTTP discovery options compatible while recommending HTML for Next layouts. Layout links target only configured public resources; private preview headers and reporting protections remain separate.

    8.5.0

    • Legacy article entries include Press Kit 1.2's responsive supporting-photo adapter and strict topic-cluster reads from the same source.
    • Optimized article photos retain their canonical source identity, preventing duplicate insertion after image URLs change.

    8.4.0

    • Article MCP reads use canonical/category routing, full archive/body search, pagination and long-content continuation.
    • Managed forms expose accepted publication enrollment receipts and a retry that preserves entered values.
    • Legacy article entries bundle Press Kit 1.1 compatibility from the same source.
    • Private previews suppress analytics, Signal and public discovery; approved article CTAs use the existing consent-aware event transport.

    8.3.0

    • Extract publication components and article data helpers into @sonordev/press-kit 1.0.0, with existing article imports kept compatible through source shims built from the same implementation.
    • Add the framework-free /shared entry for site-scoped requests, URL shaping and safe JSON-LD.

    8.2.0

    • Article photo placement uses the same pure contract as Sonor's editor and preview: exact section anchors, missing prose diagnostics, duplicate detection, and independent website placement.
    • A saved heading ID keeps its image attached when that heading's wording changes; stale anchors are skipped rather than guessed.

    8.1.0

    • Supporting article photos. The default Article server component places approved photo snapshots after the introduction or the opening paragraph of an exact section heading. Figures include descriptions, optional credit captions, intrinsic dimensions, and lazy loading. Missing or ambiguous headings are skipped; existing inline images aren't duplicated. Older articles render unchanged.
    • Custom publications and feeds. insertArticlePhotos, articlePhotoCss, and ArticleEditorialPhoto are exported from the article entries. Custom renderers can apply the same placement contract to their HTML. RSS and Atom include the approved photos; the public get_article MCP tool exposes their descriptions and placements without private planning data.
    • Sonor owns the photo plan. The authenticated app and MCP save source selection, image briefs, focal points, and readiness. Sites consume only editorial_photos from the public article response. This release doesn't add public write tools.

    8.0.1

    • server-only is a dependency. The entries that run only on the server (@sonordev/site-kit/server, /seo/server, /forms/server and the others that import the server-only marker) didn't list it. A Next build never noticed, because Next supplies its own copy, but a Node script or a test that imported one of those entries from a pnpm install failed with ERR_MODULE_NOT_FOUND. site-kit now depends on server-only ^0.0.1, so the import resolves anywhere. Inside a build Next still uses its own copy, so nothing changes for a site. Outside Next, load a server entry under the react-server condition (node --conditions=react-server), the way a server component loads it; without that condition, server-only stops the import on purpose.
    • Moving a commerce site to 8? Use sonor-setup 7.3.1 or later. Its codemod writes the pnpm-workspace.yaml line it adds as valid YAML, and it adds @sonordev/commerce-kit only to a project whose code imports commerce, not to one that merely mentions it in a code sample or a redirect table. docs/MIGRATING-TO-8.md says so too.

    8.0.0

    Two things leave site-kit in this release. Commerce (products, services, events and checkout) and the new memberships module move into their own package, @sonordev/commerce-kit, which versions and releases on its own. And the entries for the modules Sonor retired, Engage and the Sanity CMS, are removed, as the 7.0, 7.1 and 7.2 notes said they'd be. A site that uses neither changes nothing: update site-kit and rebuild.

    The commerce move is about release independence and package surface, not bundle size. site-kit's root entry was already types-only and no core entry referenced commerce, so visitors to a site without commerce never downloaded any of it. What changes is that checkout, the busiest money path on a site, can ship a fix without a site-kit release, and site-kit's package is about 8% smaller to download and about 13% smaller on disk than 7.4.0.

    Breaking: commerce moved to commerce-kit

    @sonordev/site-kit/commerce and @sonordev/site-kit/commerce/server are removed, and the root entry no longer re-exports the commerce types. Nothing is left behind at the old paths, so an import you miss fails the build. The subpath stays the same, so it's a swap of the package name:

    WasNow
    @sonordev/site-kit/commerce@sonordev/commerce-kit/commerce
    @sonordev/site-kit/commerce/server@sonordev/commerce-kit/commerce/server
    Commerce types imported from the root, @sonordev/site-kit@sonordev/commerce-kit

    The root types were CommerceOffering, CommerceCategory, CommerceVariant, CommerceSchedule, OfferingType, Cart, CartItem, EventCheckoutProps and CheckoutLineItem. Install @sonordev/commerce-kit beside site-kit 8; it lists site-kit 8 or newer as a peer dependency.

    The codemod (sonor-setup 7.3.0 or later) does the swap. npx sonor-setup codemod --only site-kit-8 shows what it would change and writes nothing; add --write to apply it. It rewrites the imports, then adds @sonordev/commerce-kit to package.json and raises site-kit's range to ^8.0.0 when your code imports commerce, and it flags anything it can't rewrite safely, such as an offerings option with no reader. Then install and build. The full guide is docs/MIGRATING-TO-8.md.

    The new entries export what the old ones did, under the same names, and your styles still apply: the components keep their site-kit- class names, and brand tokens still come from site-kit's brand.css, which your site imports as before. A few things behave better, all listed in commerce-kit's changelog: the shopping events now reach Sonor, server helpers return whole offerings and cache them under a tag Sonor expires when you edit, and a product marked sold out keeps its page. In your server log, a failed fetch starts with [commerce-kit] instead of [site-kit/commerce].

    Memberships is new in this release and ships only in commerce-kit; it was never part of a site-kit release. See Memberships.

    Breaking: the retired Engage and CMS entries are removed

    Both modules were retired in Sonor, nothing renders from them any more, and their entries were kept through 7.x so old imports kept building. They're gone, with nothing to replace them:

    • @sonordev/site-kit/engage. Website chat is @sonordev/site-kit/chat and popups are @sonordev/site-kit/website/popups. npx sonor-setup codemod --write moves each name that has a home there and flags the rest (EngageWidget, which SiteKitLayout already mounts for you). The deprecated type names the root re-exported from it (EngageElement, WidgetConfig and the rest) are gone too: use SitePopup and SitePopupConfig.
    • @sonordev/site-kit/cms, /cms/server, /website/cms and /website/cms/server, with their optional peer dependencies @portabletext/react and @sanity/image-url, which you can uninstall. No project has CMS pages and Sonor no longer serves them. Site copy is managed copy: ManagedSlot, ManagedRichText, ManagedLink and ManagedList from @sonordev/site-kit/website/slots.
    • ManagedContent, getManagedContentData and getContentBlock from @sonordev/site-kit/seo, and their types. Content blocks are retired for the same reason; use ManagedRichText.

    The codemod flags an import of any of these with the fix, and npx sonor-setup manifest --json lists them under removed. Nothing else changes for a site that never imported them.

    MCP: offerings need a reader

    list_offerings, the opt-in agent tool for priced products, services and events, used to read commerce directly. It takes its reader as an option now, so site-kit doesn't depend on commerce-kit. The tool, its ranking and its rule that a private price is never shown stay in site-kit.

    // 7.x
    sonorMcpServer({ businessName: 'Example Studio', offerings: { path: '/shop' } })
    
    // 8.0
    import { getOfferingsResult } from '@sonordev/commerce-kit/commerce/server'
    
    sonorMcpServer({ businessName: 'Example Studio', offerings: { path: '/shop', read: getOfferingsResult } })

    getOfferingsResult reports a failed request as "the catalog is unavailable"; the plain getOfferings also works, but it reads an outage as an empty catalog. A site that doesn't pass offerings changes nothing, and list_services is unchanged (it reads core data). Without read, sonorMcpServer throws when the server is built, with a message that says what to pass. See MCP and agent tools.

    New: @sonordev/site-kit/runtime

    The browser transport and API-address reader that packages built on site-kit share: sonorFetch (the site credential, retries with a timeout, one token refresh, and a pause after an authentication failure) and getClientApiConfig, plus readAnalyticsIdentity for the visitor's analytics ids. commerce-kit is built on it, and it's public API under semver. A site doesn't need to import it, since forms, analytics and the other modules already go through it. See Building a kit.

    What isn't affected

    A site that doesn't import commerce, one of the removed entries, or pass offerings to sonorMcpServer changes nothing. The other deprecated paths from 7 still work, because sites still import them: ./middleware (with createMiddleware), ./sitemap, ./robots, ./redirects, ./og, ./llms, ./images, ./slots, ./landing and ./cta-bar, plus SiteKitLayout's engage prop and the options that are accepted and ignored. Earlier notes said they'd go in 8.0; they stay until sites have moved off them, and will go in a later major. npx sonor-setup codemod --write moves a site onto the new homes whenever you like.

    Also

    • SEO: pages get a self-referencing canonical by default (alternates.canonical './', resolved against metadataBase) when Sonor has none set. getManagedMetadata takes a new scope: 'layout' option, so a root or shared layout doesn't hand one path's managed canonical and hreflang to every route beneath it, and alternates now merge key by key (in getManagedMetadata and withManagedMetadata), so a page that sets only languages keeps its canonical. See Canonical URLs.
    • Server fetches let Next steer the render. serverApiFetch caught the errors Next throws on purpose (a page turning dynamic during the build, redirect(), notFound()) like failed requests: it retried them and then returned nothing, so such a page could be built with no data. It passes them on now. Kits that make their own server calls get the same check as isNextControlFlow from @sonordev/site-kit/server, which also exports SITE_CACHE_TAGS, the cache tags Sonor expires through Live updates. There's a new one, commerce, for products, events and membership plans.
    • Pages keep working when the browser blocks site storage. The visitor and session ids are set up while the page first renders, and a browser set to block site data threw an error right there, which could break the whole page. The ids now stay in memory for that page instead, and forms, popups and analytics carry on with them.
    • Browser modules read the Sonor API address and site credential from one place. During server rendering, booking, Signal and the form helpers now follow SONOR_API_URL like forms already did, so a staging site's server-rendered URLs point at staging. commerce-kit gets the same behavior through @sonordev/site-kit/runtime.
    • Autocomplete tokens for forms you draw yourself. autocompleteFor is now exported from @sonordev/site-kit/forms. A form built with useForm can set autoComplete={autocompleteFor(field)} on its own controls and get the same token a ManagedForm control gets (given-name, email, tel and so on, or none when a field has no confident match), so a custom form no longer needs a list of its own. The type of its argument is exported as AutocompleteField. See Autocomplete on your own controls.
    • The stage form layout meets WCAG AA contrast. Its step numbers and the labels of answered steps measured between 3.4:1 and 4:1 against white, under the 4.5:1 AA asks for small text; they sit at about 5:1 now, and are still quieter than an open step's label.

    7.4.0

    • Reviews can include a project-managed photo, caption, and alternative text. Text-only reviews remain visible while imagery is pending for Broadcast.
    • VisualReviewCard and VisualReviewGallery are available from the server-safe reputation entry point. TestimonialSection also displays attached review photos.
    • Token minting supports a cold Next.js Cache Components prerender, including the default 404 page. Each mint stays fresh across deploys and token expiry, without changing form initialization or putting a raw API key into successful token responses.

    7.3.0

    AI assistants can discover a site's existing MCP tools through more of the surfaces they read.

    • WebMCP registers promptly. Supported browsers discover tools when the component mounts; ordinary browsers make no discovery request. Optional defer remains available, and ordinary rerenders no longer replace registrations.
    • Experimental AI catalog. createMcpAiCatalogHandler and buildMcpAiCatalog advertise the existing server card from /.well-known/ai-catalog.json. Cards can serve the draft media type at /api/mcp/server-card; legacy card URLs retain JSON. Discovery responses support public caching, CORS and ETags without reading the request during static rendering.
    • Discovery in llms.txt. The shared mcp configuration accepts an optional catalog URL and position: 'after-intro'. Build-time files and route handlers use the same section, including when the handler serves an older static file. Existing site-authored MCP sections stay intact.
    • Companion CLI: sonor-setup 7.2.0 generates the catalog and canonical card routes while preserving custom-server implementations and compatibility aliases.

    7.2.0

    Forms, popups and booking now work the way AI agent browsers, autofill and screen readers expect, Sonor's schema can't put a template's placeholders on a live page, and the retired Engage module is gone from the kit. No site changes needed: update the package and rebuild.

    Engage is gone

    Engage was retired in Sonor; its chat lives in Messages and its popups in Website. The kit now matches.

    • Chat and popups load on their own. Website chat is @sonordev/site-kit/chat and popups are @sonordev/site-kit/website/popups. SiteKitLayout mounts SiteChat and SitePopups as separate deferred siblings, so a site with popups off never downloads the chat, and the other way round. The popups entry is 16% smaller.
    • Popups render from blocks only. A popup made in Engage Studio (one without blocks) isn't drawn: make it again in Website → Popups & Banners. DesignRenderer and its types are removed.
    • New: SiteChat in ./chat, the standalone chat mount (idle-deferred, gated like analytics), and the popup types under their own names in ./website/popups (SitePopup, SitePopupConfig, SitePopupTargeting, SitePopupTrigger, SitePopupType).
    • @sonordev/site-kit/engage still builds through 7.x. ChatWidget and the chat types re-export from it, the popup types keep their old names (EngageElement is SitePopup), and EngageWidget draws SiteChat and SitePopups. sonor-setup's codemod moves the imports. It's removed in 8.0.

    See Website chat and Popups and banners.

    Agent-ready forms

    • Autocomplete tokens. Name, email, phone, company, address and website fields carry the matching autocomplete token (given-name, email, tel, organization, postal-code, and so on), read from the field's CRM destination, then its type, slug or a short label. A field it can't match confidently gets none, since a wrong token is worse than no token.
    • Accessible wiring. Every control is tied to its label, help text and error (aria-describedby, aria-invalid, errors announced with role="alert"). Radio and checkbox groups are named by their question, rating stars say which one is chosen, and the required asterisk is hidden from assistive tech, since required already says it.
    • WebMCP. The interactive form declares itself as a tool (toolname, tooldescription, and toolparamdescription on fields with help text), so a browser that supports WebMCP can offer it to an agent. Forms never set toolautosubmit: an agent fills the form and the person still sends it. When an agent does send it, the browser gets the outcome back, and the submission is marked "Sent by an AI assistant" in Sonor.
    • Nothing typed is lost. The server-rendered form stays on the page until the interactive one has loaded. What was typed or autofilled carries across, focus stays in its field, and a Send pressed early is held and sent once the form is ready. The server form's Send button is disabled until it can catch a submit, and a visitor without JavaScript is told why the form won't send.
    • submit() returns the outcome. From useForm and the form render props: { status: 'sent' | 'invalid' | 'failed' | 'busy' | 'next_step', ... }. useForm also returns handleSubmit and toolAttributes for custom markup: <form {...toolAttributes} onSubmit={handleSubmit}>.
    • ServerForm's enhance prop is deprecated and ignored. Every server form upgrades to the interactive one.

    See Forms.

    Popups wait for forms, and every popup is a named dialog

    • A popup or toast that opens on its own (immediately, after a delay, on scroll or on exit intent) waits while the visitor is in the middle of a form: focus in a field, a filled-in field not yet sent, or a form that's sending. It opens a moment after they leave the form, or once it's sent. Banners still show at once.
    • A popup is a modal dialog named by its heading: it takes focus, keeps Tab inside, closes on Escape and returns focus where it was. A toast is a named non-modal dialog and a bar is a named region. Close buttons are named "Close".

    See Popups and banners.

    BookingWidget

    • Day buttons are named with the full date, year included ("Wednesday, October 7, 2026"), and time buttons with the time and date in the booking's time zone. The picked day and time are pressed (aria-pressed). Confirm is named with what it confirms ("Confirm 10:30 AM, Wednesday, October 7, 2026"). Every name starts with what its button shows, so voice control still works. What the widget sends is unchanged.

    See Sync.

    SEO and AI visibility

    • Template placeholders never reach the page. ManagedSchema, LLMSchema and generateAllArticleSchemas drop placeholder nodes from Sonor-supplied schema: a URL on a reserved example domain, a name like "Example" or "Your Business Name", a placeholder phone, a slot like [Resident Name] or {plan.name}, or an object that's only a note. Real siblings and parents stay, and an article whose stored schema is nothing but placeholders gets its generated schema instead. Your own additionalSchemas are never touched. The rule is @sonordev/contracts/schema-placeholders.
    • llms.txt summaries end at a word. A long page summary ends at a sentence or a whole word, never mid-word.

    See SEO and Articles.

    Also

    • Built and tested against Next.js 16.3.8, the September 30 security release. Update next on each site; the peer range is unchanged.
    • The 7.0 migration guide covers sonor-setup 7.1.2's proxy fix: on a src/app site the proxy belongs in src/.

    7.1.2

    Docs and comments only; no code changes.

    • The module READMEs, AGENTS.md, the 7.0 migration guide and the code comments use fictional businesses and example.com in their examples, and describe spam protection without the detail of how it decides.
    • Messages and comments say "Sonor" where they said "Portal", the product's old name. Identifiers are unchanged.
    • This changelog starts at 7.0. Earlier releases are listed in the repository's docs/CHANGELOG-BEFORE-7.md.

    7.1.1

    • BookingWidget now asks every guest for a phone number before confirming a meeting, and sends it with the booking for CRM and Google Contacts use.

    7.1.0

    Live updates (new)

    • @sonordev/site-kit/revalidate: the route Sonor calls when content changes, as a one-line file. Pages stay cached, and an edit in Sonor (managed copy, metadata, an article, a portfolio item) regenerates only the pages and cache tags it touched, within seconds:

      // app/api/seo-revalidate/route.ts
      export { POST } from '@sonordev/site-kit/revalidate'

      createRevalidateRoute({ publicationBasePath }) for a site with articles. It reads SONOR_API_KEY on every call, so there's no new secret. See Live updates.

    • Ping: { "ping": true } on its own regenerates nothing and answers { ok, ping, version }, so Sonor can confirm the route is installed before it promises an edit will go live in seconds. createSeoRevalidationHandler answers it too, so existing routes built on it need no change.

    • SEO fetches carry the seo cache tag and slot fetches take theirs from the shared list (SITE_CACHE_TAGS, @sonordev/contracts/site-cache), the names Sonor sends.

    • The Managed copy docs pointed at a separate slots route with its own secret, which Sonor never called. They point at the one route now.

    Edit on page (new)

    • Sonor's dashboard can open the live site with its managed copy outlined: click any of it to edit it, and see text, rich-text and link changes on the page before publishing. Nothing to install beyond 7.1: no login, no secret, no route. The overlay loads only when Sonor frames the page with ?sonor_edit; every other visitor gets an unchanged page and about 40 bytes of extra JavaScript. It finds copy by its visible text, so markup and CSS stay exactly as written, and it never writes anything itself.
    • DEFAULT_FRAME_ANCESTORS adds https://app.sonor.io, so the dashboard can frame the site. A site that sets its own frame-ancestors should use the default list.
    • <ManagedRichText>: paragraphs, bold, italic, links and lists, edited in Sonor and rendered as elements (never HTML). A string child is the fallback.
    • <ManagedLink>: a label and a destination editable together; renders a plain <a>, or pass a render function for your own button.
    • <ManagedList>: repeatable items (title, body, link, image) with your markup, e.g. a services grid or an FAQ.
    • getSlot(id, { type, fallbackValue }) resolves any of them without a component. A value is only used when its kind matches what the code renders, so changing a slot's kind in code falls back rather than breaking.
    • Slots contract v2: the signature covers the structured value. Sonor still serves text to older site-kit releases.
    • New docs page: Managed copy.
    • List items take photos: Sonor uploads them with the project's files and records their size, so a gallery is a <ManagedList> (see "Lists with photos" in the Managed copy docs).

    Deprecated (removed in 8.0)

    • ./cms, ./cms/server, ./website/cms, ./website/cms/server: the Sanity CMS is retired. No project had CMS pages and Sonor no longer serves them, so these render nothing. Use managed copy.
    • <ManagedContent> / getManagedContentData (./seo): content blocks are retired for the same reason. Use <ManagedRichText>.

    7.0.2

    • The docs ship in the package: every module README, the migration guide and this changelog, listed in a new docs.json. sonor.dev reads them straight from the published release, so the docs there always match latest.
    • README fixes: a broken link to the articles docs, "Portal" where it meant Sonor, and a reCAPTCHA variable site-kit no longer reads.

    7.0.1

    • reportToolCallsToSonor sends the x-sitekit-version header every other site-kit request carries, so Sonor records which site-kit a tool call came from (its kit_version was empty).

    7.0.0

    A major: one entry per Sonor module, a root that runs nothing, ESM only, Next 16 only, a 0.6 MB package, Cache Components support, and MCP tools every site can give agents. Most sites move in one command when next touched: npx sonor-setup codemod --write, then build. The full guide is docs/MIGRATING-TO-7.md. Copies of sites on 4.2, 5.8 and 6.5 were migrated that way and built.

    Agents: MCP tools for every site (new)

    • @sonordev/site-kit/mcp/sonor: the tools sites used to hand-roll, written once over the fetchers the site's own pages use. sonorMcpServer / sonorMcpTools: get_business_profile, list_services, search_faq, find_pages, list_articles, get_article, get_reviews, plus opt-in list_offerings, check_availability and get_inquiry_form + send_inquiry. send_inquiry goes through Sonor's agent-inquiry door: the person must have said yes, and the call carries the agent's badge and human_approved.
    • Who called. createMcpHandler takes onToolCall; reportToolCallsToSonor sends each call (tool, outcome, the agent's name, never the arguments) to Sonor after the response. The dashboard's AI Visibility tab and Echo show which agents used the site, and Echo offers the fix for a failing tool.
    • npx sonor-setup mcp writes the whole wiring: server file, endpoint with reporting, the server card at both well-known paths, and on Netlify the rate-limited relay plus MCP_TRANSPORT_SECRET.
    • A custom MCP server is left alone. A site that runs its own (a re-site-kit site, say) gets nothing automatic: sonor-setup mcp writes nothing there, and no llms.txt section is added. Every piece is opt-in for it (reporting, some built-in tools, the section). See src/mcp/README.md.
    • Discovery. llms.txt gains an "Agent access" section (added to the build-time file automatically for the built-in server only; mcp: false, createSitemap({ llmsAgentAccess }) or --no-agent-access turn it off), and createProxy({ llmsDiscovery: { mcpServerCard: true } }) links the card as rel="service-desc".

    Breaking

    • ESM only. "type": "module"; each export is { types, default }. Next and the kits are unaffected; Node 20.19+/22.12+ require() it, which covers a next.config.ts. engines.node is >=20.19.
    • Next 16 only (next peer ^16).
    • The root entry is types-only (plus SITE_KIT_VERSION). BookingWidget → ./sync, AffiliatesWidget/useAffiliates → the new ./affiliates, commerce → ./commerce, ManagedImage → ./website/images, signal → ./signal, reputation → ./reputation, redirects → ./seo/redirects, LandingPage → ./website/landing; formatBookingTime/formatBookingDate are formatTime/formatDate on ./sync. The codemod rewrites these.
    • The setup CLI is its own package, sonor-setup. npx sonor-setup works unchanged; a site whose scripts run it adds it as a dev dependency (the codemod does). The site-kit bin alias is gone. sonor-register-sitemap stays here.
    • No source maps in the package, and no .d.ts.maps.
    • Removed, no site used them: ./search, ./search/contract, ./redirects/not-found (with x-sk-path and SK_PATH_HEADER), ./setup, LocationPageContent/getLocationSection, identifyTopicClusters, formatContentSignals, the SiteKitConfig type, and the postinstall GEO bootstrap (site-kit runs nothing at install; use npx sonor-setup geo).
    • The register-sitemap bin's .env precedence is Next.js's: the real environment wins, then .env.production.local, .env.local, .env.production, .env. It used to let .env.local override a variable the host had set. dotenv is gone (Node's util.parseEnv).

    Smaller and lighter

    • The tarball is 0.60 MB (2.24 MB unpacked), from 4.03 MB (17 MB) in 6.x.
    • One markdown library, marked. The chat widget renders its lexer tokens as React elements (raw HTML shows as text; only http(s), mailto, tel and relative links keep an address). react-markdown and its 85 packages (~8 MB) are gone from every site's install.

    New

    • Cache Components. A site can turn on Next 16's cacheComponents: nothing in site-kit's render path reads the wall clock or Math.random any more (deadlines, TTLs and jitter use performance.now(); the forms' render stamp is set on mount). The integration harness builds the fixture both ways.
    • @sonordev/contracts, a new dependency-free package: the rules site-kit shares with the Sonor APIs and the dashboard (popup blocks, site hosts, seo_pages resolution, title quality, llms sanitizers, forms, fleet, slots, portfolio). site-kit's */contract entries are the same code.
    • sonor-setup codemod moves middleware.ts to proxy.ts (Next 16's rename) with createMiddleware → createProxy, deterministically and offline. It flags a file that sets runtime instead of moving it.

    Fixed

    • The seo/website homes one directory deeper than their source shipped declarations that pointed at themselves (e.g. seo/og/route exported nothing to TypeScript); ./website/slots dropped ./slots' default export; BookingWidget and TestimonialSection could land in a non-client entry and fail a server page's prerender. verify-dts and the build now check all three.

    Kept through 7.x

    • Every 6.6 path (./sitemap, ./og, ./llms, ./images, ./engage, ./middleware, …) still works as an alias of its new home, marked deprecated in the agent manifest; so do createMiddleware and SiteKitMiddlewareConfig. They go in 8.0.
    • SiteKitLayout's engage prop, alongside chat and popups.
    • Deprecated options sites still pass (contentSignals, nativeReturnTo, ManagedScripts) are no-ops until 8.0.