Third customer testimonial card (Matias, Ozone Gliders LTD), quote
lightly edited for clarity from his emailed feedback with his OK.
Testimonial grid switched to auto-fit columns so three cards share
the row on desktop and stack on mobile as before.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01WznVjAfmyCi4LdNSVevMFb

…ial-i4ma4f

content: add Ozone Gliders testimonial to home page

…e attribution via project settings

…ial-i4ma4f

content: use Matias Nombarasco's full name; hide Claude commit attribution

The sitemap shipped to production lived at demo/public/sitemap.xml and
listed only 9 URLs. router/routes.ts had grown to 16 public routes, so
the 7 most recently added marketing guides — react-pivot-table-no-watermark,
vue-pivot-table-free, react-datagrid-csv-export, vue-datagrid-filter-sort-search,
react-datagrid-calculated-fields, vue-datagrid-column-resize and
nextjs-datagrid-pivot-table — were prerendered and live but never submitted
to search engines.

A second, more complete sitemap existed at demo/sitemap.xml, but Vite's
root is `demo` and publicDir therefore resolves to demo/public, so that
file was never copied into the build output. demo/robots.txt was a dead
duplicate of demo/public/robots.txt for the same reason.

Generate the sitemap in scripts/prerender.mjs from the same ROUTES list
that drives prerendering, so a newly added guide is always listed, and
delete the three stale/dead static files.

Verified: build:demo emits dist-demo/sitemap.xml with all 16 URLs.

Stamping every URL with the build date meant all 16 <lastmod> values
bumped on every deploy, including pages unchanged for months — the kind
of always-wrong freshness signal that teaches crawlers to distrust the
sitemap's dates entirely.

Date each route from the last commit touching its content files (Home.vue
for /, VsAgGrid.vue for the comparison page, MarketingGuide.vue +
router/routes.ts for guide pages), and omit the optional <lastmod> tag
when git can't answer (no repo, or a shallow CI clone whose truncated
history contains no commit for those files).

Verified: build:demo now emits per-route dates (e.g. /vs-ag-grid at its
June commit date) that hold stable across rebuilds.

…egy-tco8pw

fix(seo): generate sitemap.xml from routes at build time with git-derived lastmod

Both CI triggers pointed at a `main` branch that doesn't exist — the
repo's default branch is `master` — so the CI workflow has never run
once: every PR to date merged with zero checks.

Fixing the branch name alone would turn CI red immediately, because
`pnpm type-check` fails on a fresh checkout: workspace packages resolve
each other's types from built dist output (e.g. tinypivot-server imports
@smallwebco/tinypivot-core). Add a build step before type-check in the
lint job.

Verified locally in CI order: pnpm lint, pnpm build, pnpm type-check,
pnpm test:unit — all green (241/241 tests).

deploy.yml also watches `main` but is left untouched: it targets GitHub
Pages, which is not enabled for this repo (the site deploys via Vercel),
so pointing it at master would only add a failing workflow.

…egy-tco8pw

ci: run CI on master, and build packages before type-check

1. React: switching datasets with an invalid config reset the pivot axes
   but not fieldFilters, so exclusions from the previous dataset silently
   filtered the next one and were persisted under its storage key. Clear
   filters in that branch, mirroring Vue's clearConfig().

2. Filtering out every value rendered the generic "Your pivot table will
   appear here" placeholder, indistinguishable from an unconfigured
   pivot. Both skeletons now say the rows are hidden by axis filters when
   filters are active and the result is empty.

3. The axis filter panel mounted one checkbox per unique field value with
   no cap, freezing the tab on high-cardinality columns. Rendering is now
   capped at 200 values with a "N more — search to narrow the list" hint;
   the All/None quick actions still act on the full value set.

4. drillthrough.ts kept a private copy of the value-stringification
   contract that packages/core exports as stringifyPivotValue; the two
   could silently diverge and desync drill-through matching from pivot
   key building. Use the shared helper.

Verified: lint, build, type-check, and unit tests (241/241) all pass;
existing blank-handling drill-through tests cover the contract in (4).

…egy-tco8pw

fix(pivot): four axis-filter bugs found in review