{
  "schemaVersion": 1,
  "name": "@tryvitris/website-harness",
  "version": "1.5.0",
  "title": "Daily package maintenance in existing site care",
  "notesScope": "package",
  "notes": [
    "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."
  ],
  "repository": "https://github.com/jackperrotta/vitris-harness",
  "readmePath": "README.md",
  "ref": "v1.5.0",
  "documentation": "# Vitrus Website Harness\r\n\r\nVitrus Website Harness gives a coding agent the context, design guidance, and checks to build distinctive websites. It includes a static site compiler, a template library, media tools, and an optional Cloudflare backend for leads, analytics, and owner administration. Each website lives in its own repository.\r\n\r\nThe package is [`@tryvitris/website-harness`](https://www.npmjs.com/package/@tryvitris/website-harness). Bring your own coding agent and Node.js 24 or newer. Generation normally ends with a verified local preview; Cloudflare launch is a separate, explicit step.\r\n\r\n## Create a website\r\n\r\nAn optional separate business admin is available through `vitris admin setup|status|verify`; new-site `--admin` prepares follow-up instructions. See the [admin integration guide](docs/ADMIN.md) for pinned packages, local plan/apply, backend grants and the separate customer-account Cloudflare rollout.\r\n\r\nThis checkout targets the published admin runtime and contracts at exact version **1.0.0**. Earlier website-harness releases may retain older pins until a reviewed upgrade. Admin 1.0 includes lead follow-up, interface/color improvements, account lifecycle and optional operational modules; installing it does not update a deployed website backend or activate live booking, email or payments.\r\n\r\n```bash\r\nnpx --package @tryvitris/website-harness@1.4.0 vitris site create \\\r\n  --dir acme --slug acme --name \"Acme Shop\" \\\r\n  --from https://old-site.example --template \"Still & Field\" \\\r\n  --content-file ./acme-notes.md\r\ncd acme\r\nnpm install\r\nnpx playwright install chromium\r\n```\r\n\r\nReplace the example values with your own. Use `--blank` instead of `--from` for a new site. `--template` accepts a catalog ID, name, or hosted preview URL; `--content` accepts supplied text directly. Both are optional. See the [CLI guide](docs/CLI.md) for input and media policies.\r\n\r\nOpen the **site directory** in your coding agent and ask it to build the site. It follows the site's `AGENTS.md` and the prepare → `agent/CURRENT.md` → work → complete loop until the local preview is ready. To start or resume manually, use `npm run go`; for a later change, use `npm run go -- --change \"Describe the change\"`.\r\n\r\nTo browse templates from a harness checkout, run `npm ci`, then `npm run templates:gallery` and open <http://127.0.0.1:4390/>. The gallery loads the hosted catalog. See the [template library guide](agent/refs/template-library.md) for creating and publishing templates.\r\n\r\n## Built-in skills\r\n\r\nAfter creation, new sites also include the discoverable `vitris-site-manager` skill and `SITE-MANAGER.md` operational handbook. `vitris manage prepare --site SITE` refreshes the site context and recurring review brief; production publication refreshes the handoff automatically. Reviews cover live health, analytics, harness updates, compatibility, anomalies and consistency with the accepted site design. Findings and fixes stay local for review; connect the owner's cadence and timezone through the agent's actual scheduler to activate recurring reviews. See the [site manager workflow](agent/refs/site-manager.md).\r\n\r\nThe harness loads stage-specific instructions from [`agent/refs/`](agent/refs/) automatically. These are not installed agent slash commands: describe the work to your agent, and the workflow selects the relevant guidance. The creative workflow also has the following named skills; their prerequisites are included when needed.\r\n\r\n| Skill | What it does |\r\n| --- | --- |\r\n| `business-positioning` | Ground the offer and distinguishing value in business evidence. |\r\n| `narrative` | Organize the visitor journey, questions, and supporting proof. |\r\n| `visual-research` | Adapt useful principles from visual references. |\r\n| `art-direction` | Turn the central idea into a coherent visual direction. |\r\n| `typography` | Establish readable, expressive type hierarchy. |\r\n| `composition` | Shape page layout, rhythm, and visual priority. |\r\n| `media-direction` | Select authentic imagery and identify media gaps. |\r\n| `copy-layout` | Develop page copy and layout together. |\r\n| `purposeful-interaction` | Choose interactions that help visitors act or decide. |\r\n| `responsive-design` | Preserve hierarchy and usable controls across screen sizes. |\r\n| `visual-critique` | Identify consequential visual weaknesses in rendered pages. |\r\n| `visitor-journey` | Test whether visitors can complete intended tasks. |\r\n| `motion-direction` | Plan useful movement and quiet intervals. |\r\n| `motion-page` | Compose motion across each page's journey. |\r\n| `motion-statistics` | Present supplied numbers accessibly, with motion where useful. |\r\n| `motion-phrases` | Pace text without hiding essential copy. |\r\n| `motion-choreography` | Coordinate imagery, captions, and process accents. |\r\n\r\nFor example, ask your agent to “improve the mobile layout,” “review the visitor journey,” or “adapt this template to the business.” The workflow includes additional guidance for template adaptation, copy, accessibility, SEO, browser checks, and launch. See the [workflow guide](agent/WORKFLOW.md) and [creative skill registry](src/agent/creative-skills.ts).\r\n\r\n## Develop the harness\r\n\r\nCustomer sites build and verify locally, then upload the exact finished bundle directly to Cloudflare Pages. Use `npm run deploy:preview` for a hosted preview and `npm run deploy` for explicitly requested production publication. GitHub stores source; hosted deployment automation is opt-in. See [Cloudflare setup](docs/CLOUDFLARE.md) for new sites and migration of existing sites.\r\n\r\n```bash\r\nnpm ci\r\nnpx playwright install chromium\r\nnpm run typecheck\r\nnpm test\r\nnpm run verify:package\r\n```\r\n\r\nFor a local checkout, run `npm run build:cli` and create a sibling site with `--harness file:../vitris-harness`. See [distribution](docs/DISTRIBUTION.md) for package and upgrade details, and [official testing](docs/OFFICIAL-TEST.md) for frozen baselines.\r\n\r\n## More information\r\n\r\n- [Active-agent quickstart](docs/QUICKSTART.md) and [workflow guide](agent/WORKFLOW.md)\r\n- [Cloudflare setup](docs/CLOUDFLARE.md), [contact forms](docs/CONTACT-FORMS.md), and [credential safety](docs/SECURITY.md)\r\n- [Stock and customer media](docs/STOCK-MEDIA.md) and [icon guide](agent/refs/icons.md)\r\n- [Evaluation protocol](agent/EVALUATION.md) and [CLI reference](docs/CLI.md)\r\n\r\nMIT licensed. Hosted demonstrations and third-party media have their own license records; see [NOTICE](NOTICE).\r\n\r\nOptional standard customer booking: see [scheduling](docs/SCHEDULING.md) for the source-only test booking component, compatible admin API, and paired local preview.\r\n\n\n## Daily package maintenance\n\nThe 1.5.0 candidate integrates `vitris manage updates` into the existing daily care run. It checks actual website and identity-bound separate-admin dependencies against complete stable public releases, then provides pinned preparation/testing plans. It reuses the current scheduler and care lease, preserves authored configuration and follows existing publication permissions. See [package maintenance](agent/refs/package-updates.md).\n",
  "documentationSha256": "d52a9e46fcd91ddaca9d3d8ca3f16aa588cd6d52c733d3c4d95a935251107226"
}