Vitris / Open source
Website harness release notes.
What changed in each website harness version.
Website harness
@tryvitris/website-harness
1.5.0
Daily package maintenance in existing site care
- Adds a shared-registry package inventory and pinned preparation plan using admin maintenance SDK 1.5.0. Separate admin source is explicitly bound and revalidated against the website connection.
- Refreshes the generated daily care brief to prepare and test compatible website/admin updates within the existing coordinator and publishing permissions; no extra schedule is activated.
1.4.0
Daily, weekly and monthly site care
- Added one daily site-care coordinator that includes weekly and monthly reviews when due.
- Added durable review history, overlap protection, missed-period catch-up and finding deduplication.
- Added cloud-first scheduler setup with an explicit local fallback, plus schedule verification and change/pause guidance. Installing the package alone does not activate a schedule.
- Extended maintenance guidance for live health, analytics, website/admin release compatibility and consistency with each site's accepted design.
1.3.0
Site management and stable admin integration
- Added the discoverable vitris-site-manager skill, SITE-MANAGER.md handbook, generated site context and recurring-review handoff.
- Pinned the separate admin installer and contracts integration to stable 1.0.0, with reviewed setup and upgrade instructions.
- Added backend lead follow-up support, requiring a separately reviewed backend upgrade and additive migration on existing installations.
- Improved guidance for photography, cropping, hierarchy, spacing, interior pages, and form/booking focus, validation, loading, success and conflict states.
- Improved booking typography and website theme handoff. Package publication does not deploy customer sites or activate live booking.
1.2.0
Quick publishing by default
- Made build-only quick publishing the standard publication path.
- Added --full-review and the generated deploy:full script for comprehensive publication checks.
- Retained compilation, asset validation, exact staged bundle upload and hosted smoke checks in the quick path.
- Recorded the actual verification policy on releases without marking skipped reviews passed.
1.1.0
Website booking and typography
- Added the opt-in booking flow: service, availability, customer details, review and confirmation or approval request, connected to the separate admin calendar in test mode.
- Added private customer cancellation/rescheduling interfaces and paired website/admin setup verification.
- Included shared typography roles, readable defaults, responsive heading treatments and rendered typography checks; existing designs require a reviewed migration.
- Pinned the compatibility-corrected admin 0.1.0-alpha.2 archive. Existing backends, email delivery and live bookings require separate installation work.
1.0.2
Shared typography standards
- Added site typography roles for sizes, weights, spacing and named variants, with 18px body, 16px controls and 14px supporting-text defaults.
- Added consistent responsive H3 treatments and browser checks for the 12px rendered text floor and cross-route role consistency.
- Updated authoring guidance, template publication validation and refinement checks. New sites enable the policy; existing sites keep their appearance until reviewed migration.
1.0.1
More accurate refinement verification
- Fixed placeholder detection so JavaScript source does not produce false unresolved-content failures.
- Settled lazy-loaded images before refinement browser checks to avoid false broken-image reports.
- Added regression coverage for document checks and image readiness.
1.0.0
First stable website harness
- Promoted the website harness to its first stable release on npm's latest tag.
- Included separate business-admin setup, status and verification, with exact admin package pins, local plan/apply and scoped backend grants.
- Included the compatible admin v1 backend API for connection identity, leads, analytics and optional lead-status writes.
- Standardized local website builds and direct Cloudflare upload while keeping production rollout explicit.
0.1.0-beta.8
Publishing and leaner delivery
- Added quick-publish support and improved authenticated deployment checks and cross-platform regressions.
- Reduced unnecessary runtime delivery on generated preference pages and reused already compiled pages during builds.
- Improved browser provisioning, gallery readiness diagnostics and live-preview connection management.
- Released completed thumbnail observers for gallery previews.
0.1.0-beta.7
Template-led authoring
- Removed the active block-library system and made site-owned components adapted from the selected template the default authoring model.
- Resolved direct template inputs against the hosted catalog, pinned revisions and font assets, and added an explicit offline fallback.
- Strengthened section/gap verification in Chromium and tied fidelity review to hashed reference and implementation captures.
- Added managed build archives, retaining the three newest unmodified archives alongside the current build while preserving older unmanaged or modified folders.
0.1.0-beta.6
Complete npm documentation
- Corrected npm README discovery/indexing and refreshed package documentation.
- Verified the complete published package contents, fresh installation, CLI and API entry points.
0.1.0-beta.5
First public website beta
- Published the reusable harness under @tryvitris/website-harness with bundled JavaScript CLI/API entry points, declarations, starter templates and agent guidance.
- Included the static compiler, template workflow, media tools, SVG icons, motion verification and optional Cloudflare leads/analytics backend.
- Hardened backend authentication and release credential/package checks.
- Kept customer repositories, local preview and explicit Cloudflare launch separate from the reusable package.
0.0.0-stage
Registry staging placeholder
- Reserved the npm package name during publication setup. This was a staging placeholder, not an installable harness feature release; use a documented beta or stable version.