Ontempo · static evidence bundle
Map, QA and polish evidence
A public mirror of the local audit artifacts: the pixel-map QA run, the QA-harness report, the wave-31 engine-polish measurements and the map screenshots. Built so the evidence can be opened without the local stack.
This is not the application. It is a static evidence site. The tenant app needs its Postgres database and Next.js servers; the concrete options for a real public staging app are written up in docs/deploy/live-hosting.md in the repository.
1. Pixel map QA — PASS
Target: http://demo-kelowna-8rs0k.lvh.me:3012/listings?layout=map. The harness captured the real tile layer, decoded every tile with node:zlib, classified it (real / empty / blocked), panned the map and pixel-diffed the before/after frames.
- Map QA report (JSON — the harness writes JSON; the readable summary is this page)
- report.json · classifier self-test · negative-control case
- Screenshots: map before pan · map after pan · page 1440 · page after pan
- Raw tile captures:
assets/map/tiles/in this deployment (every fetched tile, 256 px; hundreds of files, linked individually would be noise)
2. QA harness report
The audit harness inventories every control on a page, runs axe, and flags dead controls and known defects. Numbers below are from the local run against the demo tenant; the JSON/HTML are the source of truth.
3. Wave-31 engine polish — before / after
The polish pass fixed shared-sheet and token-level issues across three live tenants. This bundle carries the measured JSON and the curated screenshots (crops of the fixed components plus full-page before/after at 1440 and 390).
- polish/README.md (the full write-up)
- Measurements: before · after · alignment before · alignment after · numerals before · numerals after · evidence
- Screenshots: stats/numerals after · before · home after · listings after · 86 curated crops/full pages live under
assets/polish/shots/
4. Interactive map evidence (wave 31 engine)
Screenshots from the engine probe: the map rendered full-page, zoomed in/out, and at 390 px. The probe script and evidence JSON are included for reproducibility.
- engine/evidence.json · probe.mjs (source)
- Screens: 1440 · 1440 full · 390 list · 390 map · zoomed in · zoomed out
5. Public staging host — pixel map QA (non-localhost)
The map harness was run against a public Cloudflare host serving the local renderer through a Worker + quick tunnel: ontempo-staging-bridge.website-010.workers.dev/listings?layout=map. The public host served the owner tenant's real page (/listings 200, "36 properties", 8 pins, same-origin /api/map/tiles/… JPEGs).
The public run proves tile authenticity through a real non-localhost host; the pan assertion fails on the bridge because the dev-server page loses its HMR WebSocket through the Worker (local run of the same harness PASSes pan — see §1). Full honesty in docs/deploy/live-hosting.md §4.
What this site proves — and what it does not
| Claim | Status |
|---|---|
| Real map tiles load and are detected as real (not grey/blocked) on the local app | Proven by the pixel harness (evidence above) |
| Panning the map changes the rendered map locally | Proven by post-pan pixel diff |
| The QA harness can inventory controls and run axe on a tenant page | Proven by the harness report above |
| Real tiles are served and classified as real on a public non-localhost host | Proven in §5 (12/12 real, 0 blocked, 8 pins) |
| Map interaction (pan) works through the temporary public bridge | No — pan check fails on the bridged dev page (HMR socket refused); see §5 |
| The public artifact site is the application | No — it is static files only; no tenant routing, no database, no server actions |
| A real public app deploy exists | No — needs managed Postgres + a Node host or OpenNext adapter; options and effort in docs/deploy/live-hosting.md §6 |