@tryvitris/website-harness 0.1.0-beta.5 → 0.1.0-beta.6

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/README.md CHANGED
@@ -8,10 +8,12 @@ Sites own their visual components. The optional harness block library supplies s
8
8
 
9
9
  The default template gallery is `artifacts/templates/gallery.html`. Run `npm run templates:gallery` and open `http://127.0.0.1:4390/`. It displays the live Cloudflare library and automatically includes future publications. Publish complete new demonstrations with `npm run templates -- publish --bundle ABSOLUTE_TRANSIENT_DIRECTORY`; see `agent/refs/template-library.md`. Source fixtures contain original Vitris instructional material; external demonstrations remain hosted with their own provenance records.
10
10
 
11
- MIT licensed. The public npm package is `@tryvitris/website-harness`; prerelease `0.1.0-beta.5` uses the `beta` dist-tag. Bring your own coding agent. Optional hosting uses your own Cloudflare account; see [Cloudflare setup](docs/CLOUDFLARE.md) and [credential safety](docs/SECURITY.md).
11
+ MIT licensed. The public npm package is `@tryvitris/website-harness`; prerelease `0.1.0-beta.6` is available through the `beta` and `latest` dist-tags. Bring your own coding agent. Optional hosting uses your own Cloudflare account; see [Cloudflare setup](docs/CLOUDFLARE.md) and [credential safety](docs/SECURITY.md).
12
12
 
13
13
  Requires Node 24 or newer. Hosted demonstrations and third-party media have their own license records; see NOTICE.
14
14
 
15
+ The npm package contains the bundled JavaScript CLI and APIs, TypeScript declarations, starter templates, agent kit, and required runtime assets. The complete TypeScript development source and tests are in the [GitHub repository](https://github.com/jackperrotta/vitris-harness).
16
+
15
17
  ## Start a client website
16
18
 
17
19
  Each client gets an independent site directory and Git repository. **That client directory is where you open your coding agent and build the website.** This source repository maintains the reusable harness, compiler, knowledge, media catalog, and optional backend.
@@ -21,7 +23,7 @@ To use a local checkout, build and pack it, then generate a site:
21
23
  ```bash
22
24
  npm ci
23
25
  npm pack
24
- node bin/vitris.js site create --dir ../acme --slug acme --name "Acme Shop" --from https://old-site.example --harness ../vitris-harness/tryvitris-website-harness-0.1.0-beta.5.tgz
26
+ node bin/vitris.js site create --dir ../acme --slug acme --name "Acme Shop" --from https://old-site.example --harness ../vitris-harness/tryvitris-website-harness-0.1.0-beta.6.tgz
25
27
  cd ../acme
26
28
  npm install
27
29
  npx playwright install chromium
@@ -33,7 +35,7 @@ The tarball path is relative to the generated site directory. Adjust it for your
33
35
  The public beta starter command is:
34
36
 
35
37
  ```bash
36
- npx --package @tryvitris/website-harness@0.1.0-beta.5 vitris site create --dir acme --slug acme --from https://old-site.example
38
+ npx --package @tryvitris/website-harness@0.1.0-beta.6 vitris site create --dir acme --slug acme --from https://old-site.example
37
39
  ```
38
40
 
39
41
  Use `--blank` when there is no existing website. New sites pin the creating harness version. `--harness file:../vitris-harness` explicitly opts into local development; run `npm run build:cli` in that checkout first. Jev is optional and off by default. Backend and Cloudflare credentials are not required to author and preview a static site locally.
@@ -27,7 +27,7 @@ At the same configuration level, current names take precedence. CLI build overri
27
27
  Stop its workflow first. From the harness checkout, preview changes:
28
28
 
29
29
  ```bash
30
- node bin/vitris-migrate-site.js --site ../acme --harness ../vitris-harness/tryvitris-website-harness-0.1.0-beta.5.tgz
30
+ node bin/vitris-migrate-site.js --site ../acme --harness ../vitris-harness/tryvitris-website-harness-0.1.0-beta.6.tgz
31
31
  ```
32
32
 
33
33
  Add `--apply` to perform the displayed changes. The command backs up affected files under the client's `agent-backups/`, renames the package dependency and known script paths, and converts the backend origin key. Conflicting old/new origins fail before writes. Client pages, components, media, secrets, existing lockfile, and workflow state are preserved. Repeating it makes no further edits.
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@tryvitris/website-harness",
3
- "version": "0.1.0-beta.5",
3
+ "version": "0.1.0-beta.6",
4
4
  "description": "Vitris agent harness for building and verifying customer websites, with a static compiler, media tools, and optional Cloudflare backend.",
5
5
  "type": "module",
6
6
  "exports": {